Roundcube Community Forum
Release Support => Pending Issues => Topic started by: Jools on February 10, 2015, 10:40:19 AM
-
Hi All,
I have a server running 0.95 on Centos 7 with PHP version php-5.4.16-23.el7_0.3.x86_64 and apache 2.4.6-19.
The script completes with the following:
Running update script at target...
WARNING: Your configuration needs to be migrated!
We changed the configuration files structure and your two config files main.inc.php and db.inc.php have to be merged into one single file.
Do you want me to fix your local configuration? (y/N)
y
. backing up the current config file(s)...
. writing /var/www/roundcube/config/config.inc.php...
Done.
Your configuration files are now up-to-date!
WARNING: Mimetype to file extension mapping doesn't work properly!
Please check the 'mime_types' config option and run this script again.
Executing database schema update.
Updating database schema (2013042700)... [OK]
Updating database schema (2013052500)... [OK]
Updating database schema (2013061000)... [OK]
This instance of Roundcube is up-to-date.
Have fun!
All done.
I downloaded the mime.types file from a forum post about the same problem, saved it to /etc/httpd and put an entry in main.inc.php pointing to it but it still fails with the same error.
The main effect though, is that when logging into Roundcube, it drags for about a minute before timing out and the message panel on the right is blank. The only thing that does respond at this point is the about button which shows v. 1.0.0.
Restarting httpd on 0.95 takes about 2 seconds, 1.0.0 about 30.
If anyone can point me in the right direction I'd be grateful.
Cheers,
JPB
I've disabled all plugins before upgrading
-
Most likely Roundcube can't access the mime.types in the /etc dir. Try running Roundcube without pointing to a mime.types file, its possible that your cli is using an environment without it while the Apache version already has it. If you run into problem with attachments then you still have a mime types problem.
-
Hi,
Tried without the mime entry in the conf file and it still gave the same error. In the end, I set up an Ubuntu server, copied the working install from our mail server over to it (v0.9.5) and ran the upgrade process, end result is shown below.
According to the script output, the upgrade worked and no log entries are generated in the error log but the problem is exactly the same, i.e. white area where the messages should be, site times out and refuses to load. Only difference is that apache restarts in 5 seconds even though roundcube doesn't work.
Cheers ,
Julian
sent 1,009,218 bytes received 4,352 bytes 2,027,140.00 bytes/sec
total size is 994,601 speedup is 0.98
sending incremental file list
index.php
sent 13,000 bytes received 35 bytes 26,070.00 bytes/sec
total size is 12,910 speedup is 0.99
sending incremental file list
.htaccess
sent 1,663 bytes received 35 bytes 3,396.00 bytes/sec
total size is 1,573 speedup is 0.93
sending incremental file list
defaults.inc.php
sent 44,614 bytes received 35 bytes 89,298.00 bytes/sec
total size is 44,513 speedup is 1.00
sending incremental file list
CHANGELOG
sent 109,977 bytes received 35 bytes 220,024.00 bytes/sec
total size is 109,867 speedup is 1.00
sending incremental file list
README.md
sent 3,847 bytes received 35 bytes 7,764.00 bytes/sec
total size is 3,757 speedup is 0.97
sending incremental file list
UPGRADING
sent 2,922 bytes received 35 bytes 5,914.00 bytes/sec
total size is 2,832 speedup is 0.96
sending incremental file list
LICENSE
sent 35,239 bytes received 35 bytes 70,548.00 bytes/sec
total size is 35,147 speedup is 1.00
done.
Running update script at target...
WARNING: Your configuration needs to be migrated!
We changed the configuration files structure and your two config files main.inc.php and db.inc.php have to be merged into one single file.
Do you want me to fix your local configuration? (y/N)
y
. backing up the current config file(s)...
. writing /var/www/html/roundcube/config/config.inc.php...
Done.
Your configuration files are now up-to-date!
Executing database schema update.
Updating database schema (2013042700)... [OK]
Updating database schema (2013052500)... [OK]
Updating database schema (2013061000)... [OK]
This instance of Roundcube is up-to-date.
Have fun!
All done.
-
Hi,
Your last post does not make sense you say:
white area where the messages should be
but then
site times out and refuses to load
if they site doesnt load then how can you login and open a message to see a white area there?
I see you coppied some files when you were creating your Ubuntu copy but only files from the RC root and the default config. All the other files and your config file?
When you did the update from 0.9.5 to 1.1.0 did you actually copy all the new files into their right places? See here https://github.com/roundcube/roundcubemail/blob/master/UPGRADING#L31 and esp check about the vendor folder mentioned here https://github.com/roundcube/roundcubemail/blob/master/UPGRADING#L43.
-
Apologies, getting frazzled.
The login page appears. You put in your username and password. Hit enter. If you're lucky, two minutes later you'll be logged in. If not, it times out and you have to try logging in again. Also, used update script not manual install.
Once you log in, this is the view:
-
I realised I was talking about 1.1 but actually you are moving to 1.0.0. I'd suggest 1.0.5 at least rather than 1.0.0. Some of what I said about the vendor folder and stuff is for 1.1 only. so you can ignore that.
I realise now you mean you have run the installto.sh script and that is what the output is from. I didnt see that before.
I think perhaps you should try enabling the installer and running that, i think its the first step that does some checks that make sure everything is setup right. It might give some more clues about what is wrong.
-
Hiya,
No worries. I tried a manual update but that did the same. Ill roll it back to 0.95 and will have a go with 1.05. May even have a shot with the latest one and will get back with results.
Cheers,
Jools
-
OK, result is that I tried 1.1.0 and with all the plugins disabled on the 0.9.5 install, it seems to be working. Now I need to put them back and see which one's breaking it.