Web interface crashes
Added by Rob Stites over 10 years ago
When I run commands like 'Run JPEG Maker' or 'Run DogPicker' from the web interface, the system appears to crash. A page comes up saying "The Connection was Reset" and the following line comes up in /etc/http/error_log comes up:
[Fri Feb 28 09:14:58 2014] [notice] child pid 4585 exit signal Segmentation fault (11)
I can run these commands just fine by generating the command line statement with "Just Show Command" and executing it on the command line. I suspect the fix is very simple. Thanks.
Rob Stites
Replies (3)
RE: Web interface crashes - Added by Amber Herold over 10 years ago
Hi Rob,
Here are a few things to look at:
1. Make sure user permissions are correct, especially anything related to the web server apache user: http://emg.nysbc.org/projects/appion/wiki/File_Server_Setup_Considerations_Shared
2. Check the troubleshooting page and make sure there is not a firewall issue and you don't need to update ssh2: http://emg.nysbc.org/projects/appion/wiki/Potential_Problems
3. Configure your php.ini file to show warning messages (remove & ~E_WARNING) to see if that provides any clues: http://emg.nysbc.org/projects/appion/wiki/Configure_phpini
Let me know how it goes.
Amber
RE: Web interface crashes - Added by Rob Stites over 10 years ago
Resolution!
My permissions were set correctly. The problem is that Appion will not take my user password because it has characters in it that Appion will not accept. Can we expand the type of characters the password can accept?
Rob
RE: Web interface crashes - Added by Amber Herold over 10 years ago
That is curious. When you try to run a command directly from the webpage, it logs into the processing server using the username and password that are entered at the top right corner of the processing page. This username and password is not filtered by Appion at all. If you have enabled the Login feature of Appion (meaning each user must login to the Appion GUI in a login screen) then this password is indeed filtered and it is a bit strict on which characters are allowed. It is a bit confusing that there are 2 different login locations with different uses and requirements.
Perhaps the job submission was failing because the username and password used to log into the processing host were incorrect? In that case, I would expect the processing host to return an error that is then displayed to the user in the Appion GUI. We have had times when that message was not being displayed here because certain settings on the host caused the error message to not be returned.
It is nice to have the same login credentials for both the Appion login and the processing host login, which is not possible if the processing host login contains characters not allowed in Appion. I believe the characters were not allowed to avoid SQL injections during a time when the passwords were not yet encrypted in the database. I can revisit that feature and see if we can loosen things up now. In the meantime, the workaround is to have a different password for the Appion login, but continue to enter the correct processing host credentials in the processing pages.