Dolibarr script install fails with 500 Internal Server Error
Dolibarr script install fails with 500 Internal Server Error
Submitted by support0 on Sun, 09/04/2011 - 09:34
Dolibarr wizard failed : HTTP/1.1 500 Internal Server Error
Status:
Closed (fixed)
Comments
Submitted by andreychek on Sun, 09/04/2011 - 09:37Comment #1
Howdy -- if you log in the Apache error logs for this Virtual Server (located in $HOME/logs/error_log), what error shows up in there at the time you received the "500 Internal Server Error"?
Submitted by support0 on Sun, 09/04/2011 - 09:59Comment #4
Maybe this is an issue with error reporting setting in php.ini - I tried using the script installer for vtigercrm and the install went a bit further... on the gui setup I got the error shown in the uploaded screenshot
Submitted by support0 on Mon, 09/05/2011 - 08:30Comment #7
Tried the manual install, and the failure was the same 500 error at the same point of installation steps. And you're right, the vtigercrm issue is unrelated. Please disregard my comment on that one, which you rightfully have already ;-)
Submitted by JamieCameron on Tue, 09/06/2011 - 00:56Comment #10
Sure, email me your login details at jcameron@virtualmin.com and I will take a look. I will need root SSH access, and the name of the domain you are trying to install into.
Submitted by JamieCameron on Tue, 09/06/2011 - 15:20Comment #13
Ok, I found the problem .. the dolibarr install process was really slow talking to your mysql database, causing it to run longer than the default 60 second timeout for PHP scripts. I increased this to 600 seconds, and the install completed OK. I did this at Server Configuration -> Website Options.
The next release of Virtualmin will fix this properly by turning off PHP timeouts during the script install process ..
Comments
Submitted by andreychek on Sun, 09/04/2011 - 09:37 Comment #1
Howdy -- if you log in the Apache error logs for this Virtual Server (located in $HOME/logs/error_log), what error shows up in there at the time you received the "500 Internal Server Error"?
Submitted by support0 on Sun, 09/04/2011 - 09:51 Comment #2
Looks like this is a problem for the dolibarr version 3.0 core?
[Sun Sep 04 09:48:40 2011] [warn] [client 192.168.1.2] mod_fcgid: stderr: PHP Notice: Undefined index: HTTP_ACCEPT_LANGUAGE in /home/iculist/public_html/dolibarr/core/class/translate.class.php on line 80 [Sun Sep 04 09:48:40 2011] [warn] [client 192.168.1.2] mod_fcgid: stderr: PHP Notice: Undefined index: HTTP_ACCEPT_LANGUAGE in /home/iculist/public_html/dolibarr/core/class/translate.class.php on line 80 [Sun Sep 04 09:48:40 2011] [warn] [client 192.168.1.2] mod_fcgid: stderr: PHP Notice: Undefined index: db_port in /home/iculist/public_html/dolibarr/install/etape1.php on line 550 [Sun Sep 04 09:49:41 2011] [warn] [client 192.168.1.2] mod_fcgid: read data timeout in 61 seconds [Sun Sep 04 09:49:41 2011] [error] [client 192.168.1.2] Premature end of script headers: etape2.php
Submitted by support0 on Sun, 09/04/2011 - 09:55 Comment #3
Thiinking it might be an issue with version 3.0, I tried the 2.9 script installer but got similar errors
[Sun Sep 04 09:52:39 2011] [warn] [client 192.168.1.2] mod_fcgid: stderr: PHP Notice: Undefined index: HTTP_ACCEPT_LANGUAGE in /home/iculist/public_html/dolibarr/core/class/translate.class.php on line 79 [Sun Sep 04 09:52:39 2011] [warn] [client 192.168.1.2] mod_fcgid: stderr: PHP Notice: Undefined index: HTTP_ACCEPT_LANGUAGE in /home/iculist/public_html/dolibarr/core/class/translate.class.php on line 79 [Sun Sep 04 09:52:39 2011] [warn] [client 192.168.1.2] mod_fcgid: stderr: PHP Notice: Undefined index: db_port in /home/iculist/public_html/dolibarr/install/etape1.php on line 541 [Sun Sep 04 09:53:40 2011] [warn] [client 192.168.1.2] mod_fcgid: read data timeout in 61 seconds [Sun Sep 04 09:53:40 2011] [error] [client 192.168.1.2] Premature end of script headers: etape2.php
Submitted by support0 on Sun, 09/04/2011 - 09:59 Comment #4
Maybe this is an issue with error reporting setting in php.ini - I tried using the script installer for vtigercrm and the install went a bit further... on the gui setup I got the error shown in the uploaded screenshot
Submitted by support0 on Sun, 09/04/2011 - 10:08 Comment #5
...
Submitted by JamieCameron on Sun, 09/04/2011 - 21:05 Comment #6
I don't think those vtigercrm issues are related..
If you try a manual install of dolibarr into the same domain (after deleting the existing failed install), does it work OK?
Submitted by support0 on Mon, 09/05/2011 - 08:30 Comment #7
Tried the manual install, and the failure was the same 500 error at the same point of installation steps. And you're right, the vtigercrm issue is unrelated. Please disregard my comment on that one, which you rightfully have already ;-)
Submitted by JamieCameron on Mon, 09/05/2011 - 12:08 Comment #8
If this happens even for a manual install, you might have to contact Dolibarr developers, as it seems like a bug in their install process..
When the manual install fails, due you also see the following line in the error log :
[Sun Sep 04 09:49:41 2011] [error] [client 192.168.1.2] Premature end of script headers: etape2.php
Submitted by support0 on Mon, 09/05/2011 - 19:28 Comment #9
Yes i get the same error on etape2.php
BUT
I took the same scripts, downloaded to my Mac, ran the install and NO Problems at all....
So, I am not going to take this to dolibarr developers.
Please help, can you look at my virtualmin? If so, I can make a private post with Username and Password to https://iculist.com:10000/
I have an upset client.
Submitted by JamieCameron on Tue, 09/06/2011 - 00:56 Comment #10
Sure, email me your login details at jcameron@virtualmin.com and I will take a look. I will need root SSH access, and the name of the domain you are trying to install into.
Submitted by support0 on Tue, 09/06/2011 - 10:31 Comment #11
Email sent, thx ;-)
Submitted by JamieCameron on Tue, 09/06/2011 - 15:08 Comment #12
Ok, trying it now ..
Submitted by JamieCameron on Tue, 09/06/2011 - 15:20 Comment #13
Ok, I found the problem .. the dolibarr install process was really slow talking to your mysql database, causing it to run longer than the default 60 second timeout for PHP scripts. I increased this to 600 seconds, and the install completed OK. I did this at Server Configuration -> Website Options.
The next release of Virtualmin will fix this properly by turning off PHP timeouts during the script install process ..
Submitted by support0 on Tue, 09/06/2011 - 16:04 Comment #14
You're awesome.
Submitted by Issues on Tue, 09/20/2011 - 18:23 Comment #15
Automatically closed -- issue fixed for 2 weeks with no activity.