On 23/03/11 16:03, Marcel de Rooy wrote:
Hi all,
I recently ran into apache timeout problems when running updatedatabase over the web installer on a larger number of records between 3.0 and 3.2.
Restoring a backup and temporarily increasing Timeout in apache config file resolved the situation. Not ideal..
But someone not paying full attention could even think that install was succesful, while the install process was killed halfway..
Are there already any ideas on preventing this kind of situations?
I've got into the habit of running updatedatabase at the commandline to avoid the timeout (and not knowing what the status is). We should probably at least warn the unwary in the docs, I think going from 3.0 to 3.2 there are a couple of lengthy steps. Cheers Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 845 557 5634 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com