Jump to content
Froxlor Forum
  • 0

Froxlor Update to 0.10.21 fails (Browser hanging for >10 Minutes, then error)

Go to solution Solved by d00p,


Hello there!

We are using Froxlor since a couple of years and never had an issue updating.
At the moment >700 domains are in our main system.
Now we tried to finally update our installation from to 0.10.21 using the usual .tgz-method, but unfortunately failed.
Login is displayed (after exchanging files and reloading) -> Login gets accepted -> Update confirmation notice is displayed -> Confirmation clicked -> Browser hangs (for >10 minutes)

Result: "Internal Server Error" and error.log just displays: "End of script output before headers: admin_updates.php"
I even had to increase "FcgidIOTimeout" to not having it timeout (I made several attempts, backing up files and db beforehand).

Any hint will be greatly appreciated. Many thanks in advance!


Link to post
Share on other sites

7 answers to this question

Recommended Posts

  • 0
  • Solution

The corresponding setting would be "Settings -> Cronjob settings -> Allow automatic database updates". 

I would frist stop the cron-daemon (so I'm control of the execution), adjust the settings and then run the cron manually using

php /var/www/froxlor/scripts/froxlor_master_cronjob.php --force --debug

I strongly recommend a prior backup :) If this does not work as expected, let me know, we'll figure something out to update your froxlor

Link to post
Share on other sites
  • 0

You can check how far the update went through (SELECT value FROM panel_settings WHERE varname = 'db_version')

I'm pretty sure it's right before an update where something is done with the domains-table or related to it...700 domains is a lot :)

Link to post
Share on other sites
  • 0

Ah yes, just how i thought. This was right before the adding of the new domain_ace field which then goes through all domains converting idna domains to their ace representation.

As you have a lot of domains this can of course take some time. I'd say in cases like this - CLI updater would be the better choice...Although the cronjob CAN (if allowed) include and handle these updates, i don't really recommend that - especially not on a live system.


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...