Hi guys, Wouldn't be out of the box, updating from 3.0.4.x to 3.0.5.x, using the ispconfig_update.sh command ? I mean, will any PHP versions or MySQL be changed, so that existing sites won't work afterwards ? Like PHP going from 5.3 to 5.6 fx. Thanks,
Thanks for your feedback. So if PHP or MySQL needs to be updated, then it's only 'the hard way' ? What about downtime? If I update ISPConfig to newest version, then Apache needs to be restarted, right ? That should normally only take seconds. Does the server needs to be rebooted after ISPConfig update ?
You simply install the updates of the linux distrbution. So thats quite easy. On Debain and ubuntu, you run: apt-get update && apt-get upgrade and on Centos you run yum update But you should run these commands anyway at least once a week to keep your system safe. The downtime is just a few seconds. no
After a successfull update, I do still have the "jobqueue" stuck bug. The server has not been rebooted after this update; maybe it would fix it ? I don't wan't to reboot it now, due to downtime in work hours.
See here for instructions to debug a stuck jobqueue (last chapter): http://www.howtoforge.com/forums/showthread.php?t=58408 A reboot is not required after ispconfig updates.
.. but why ? Afaik, the stuck bug was fixed in one of the newest releases. Before I got a green light for updating this server, I used the '/usr/local/ispconfig/server/server.sh' command each time. Now, I still have to use it, after the update. That doesn't make sense to me.
That depends on how you installed php. If you use the system php like I do, I just run apt-get upgrade on debian and I'am always up to date. If you use additional php versions, then you have to compile a updated version and e.g. switch to the new one by using symlinks.
