Invalid language specification
-
I recently upgraded to Fog Trunk and now when I try to access the GUI page, I get an invalid language specification. I’m not sure what or how to fix this. Any ideas?
Thanks,
Jimmy
-
Please help us with some more information. Which OS are you running FOG on? Which version did you upgrade from (I guess 1.2.0 but please let us know)? What is the exact error message you see? Do you see anything related in your apache error log (http://www.codeasite.com/index.php/linux-a-apache/94-how-do-i-find-apache-http-server-log-files) when trying to access the web interface?
-
Upgraded from version 1.2.0. OS is CentOS 6.5. When I try to access server.com/fog/management/ it redirects to “Invalid language specification.” That’s all that comes up and nothing I do can I get around.
Restarted apache, and mysql didn’t help either.There is nothing out of the ordinary in the the apache logs.
10.1.1.180 - - [15/Nov/2015:08:37:35 -0800] “GET /fog/management/index.php HTTP/1.1” 200 30 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36”
10.1.1.180 - - [15/Nov/2015:08:37:40 -0800] “GET /fog/management/index.php HTTP/1.1” 200 30 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36”
10.1.1.180 - - [15/Nov/2015:08:41:02 -0800] “GET /fog/management/index.php HTTP/1.1” 200 30 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36” -
Actually we would like to see you generate that error message again, then view the apache error log in /var/log/httpd/error_log. The last few lines should indicate the current error. The access_log should only show use details when things go right.
-
I am aware that the death of the script will occur if the language specification is not correct, but I’m also unable to replicate the problem as you’re describing it. Are you, by chance, using a custom language specification for your environment which was not pre-coded within FOG?
-
Well, I went back to 1.2.0 with a backup of the older database. This works just fine, but the moment I upgrade to Trunk I get Invalid language specification the page. It could be something in the DB that is causing this. Anyway, I’ll stick to 1.2.0 for now.
-
@jimmmmmmah We need people like you who try out the most current version of FOG and report bugs. Otherwise we wouldn’t be able to find and fix all the issues. Please give it another go and hopefully we can figure things out together. See my first answer on where to find the apache error log file.
