Hi,
I have recently upgraded a large-ish (1gb) vb database from 2.2.6 -> 3.0.0 and have a problem. It's happened twice since the upgrade, the first time we had to reboot the server as load average was up to about 30.
The only resolution to this problem I have found is to restore the vbulletin-settings.xml using the packaged tools.php. This of course is not an acceptable solution as we lose all our customised settings and have to go through re-adding them.
This is the error displayed when anything is accessed (index.php, admin cp etc):
Warning: Invalid argument supplied for foreach() in /home/ffwa/public_html/forums/includes/sessions.php on line 266
Unable to add cookies, header already sent.
File: /home/ffwa/public_html/forums/includes/sessions.php
Line: 266
I have two queries:
i) What is causing this and how can we prevent if from happening?
ii) Is there a back-up facility in the admin cp to download our customised xml files (specifically vbulletin-settings.xml) so we can restore back to our settings should the problem persist.
Thanks
I have recently upgraded a large-ish (1gb) vb database from 2.2.6 -> 3.0.0 and have a problem. It's happened twice since the upgrade, the first time we had to reboot the server as load average was up to about 30.
The only resolution to this problem I have found is to restore the vbulletin-settings.xml using the packaged tools.php. This of course is not an acceptable solution as we lose all our customised settings and have to go through re-adding them.
This is the error displayed when anything is accessed (index.php, admin cp etc):
Warning: Invalid argument supplied for foreach() in /home/ffwa/public_html/forums/includes/sessions.php on line 266
Unable to add cookies, header already sent.
File: /home/ffwa/public_html/forums/includes/sessions.php
Line: 266
I have two queries:
i) What is causing this and how can we prevent if from happening?
ii) Is there a back-up facility in the admin cp to download our customised xml files (specifically vbulletin-settings.xml) so we can restore back to our settings should the problem persist.
Thanks
Comment