500 Error during installation of 1.8.0.1

Gregl

I am trying to install v1.8.0.1. However it crashes with a 500 Server Internal error and I have been unable to determine the cause, after many hours of debugging. The server is running PHP 5.3.28I have determine that the following code snipped from class.dynamic_forms.php is part of the problem: static function getSelections() { $selections = array(); foreach (DynamicList:() as $list) { $selections = array($list->getPluralName(), SelectionField, $list->get('id')); } return $selections; }The DynamicList:() returns an object of class QuerySet, but this does not have the methods getPluralName(), get(), or the propery id. Also SelectionField is the name of a class, is that valid syntax?Is anyone else having problems. I really like osTicket and would like to use it but I may have choose something else if I can't get it installed.

ntozier

Whats the PHP error that you are receiving?What web server are you running?

Gregl

I don't get a PHP error, it kills the whole thing with at 500 Server error. I spent a couple of days trying to work out what the problem is and it was dying in the code I snipped, but when I commented that out it just died somewhere else and I didn't time to keep looking. However I have serious concerns about the quality of the code for the reasons I outlined above, this code just doesn't make sense unless there is something I don't know. I dumped the object that was returned from the call and 1) it is an object not an array so the foreach will iterate over the properties, and 2) there are no methods getPluralName() and get() anyway. What about passing a class name as a parameter? Can you do that? Maybe that's what is killing the PHP interpreter.

Gregl

The server is apache (LAMP).

ntozier

500 is an internal server error. Which is a generic http error indicating that something is wrong with the server. Ie. something went wrong server side. When this sort of thing happens, it causes an event to be logged. If as you say thats the code that that triggered it then you should see a error in your PHP error log. This logs location can vary based on your flavor of linux, you should check your php.ini and see where yours located and get the actual error. Or you could turn on error reporting in osTicket by editing \main.inc.php find these lines on or about line 49-50: ini_set('display_errors', 0);

ini_set('display_startup_errors', 0);

change them to:

ini_set('display_errors', 1);

ini_set('display_startup_errors', 1);And the error should be displayed in the browser window. I'll ask the devs to take a look at your thread here on the forums.

jared@osticket.com

Hey, I'm not going to defend or explain the above-cited code, but I think there are some new array iteration interfaces in PHP that @[deleted] might not be aware of.When Apache/PHP dies with 500, it should log some information to the php error log (sometimes in /var/log/httpd/error_log). Have you found any possible details in the error log file?

Gregl

There is no point setting the PHP error options, it never gets to the point of outputting anything.I have seen errors like this before in earlier PHP versions where the actual PHP interpreter dies so you don't get a php error (I think an unclosed class definition in an early version caused a similar problem). The Apache error log reports 500 Server Error "Premature end of script headers" because PHP died before it produced any output. If I put an echo "hello world"; in before the foreach() in the snippet above there is no 500 error, just "hello world" is output and nothing else. Apache is now happy because headers have been sent, but this does not change the fact that PHP died after the echo.With regards to jared's comment about php iteration interfaces you are correct, I just dumped the object and its methods, I didn't look at the definition. I'm going to hold off until I can upgrade our server to PHP 5.4 and see if that helps. I guess there must be something strange in our server setup because it seems no-one else is having this problem, although everything else on our server is fine.

Gregl

Just a short update - I upgraded the server to PHP 5.4 and it fixed the problem.

doubleuy

I'm trying to install version 1.8.1 with php 5.4, and hit the same error, when I click the continue button.Help needed... Any ideas anyone?

ntozier

@doubleuy please post your own thread with your information. Gregl's fix was upgrading his server to PHP 5.4 so obv you do not have the exact same problem.