Server Error 500

[szecca1]

@Tom-Elliott @Wayne-Workman How would I make sure of that? I figured it must be Apache but I am not sure how to check if it is running or where the error logs are?

[Wayne Workman]

@szecca1 What OS are you running FOG on?

[szecca1]

@Wayne-Workman Fedora Server

[Tom Elliott]

Error logs are at /var/log/httpd/error_log

[szecca1]

@Tom-Elliott

This is what i get when I type that in. Is there somewhere else I need to type this, this server is not a GUI so I cant just go into the OS.

[Tom Elliott]

@szecca1 you missed the d in httpd

[Tom Elliott]

@Tom-Elliott add to that and you have to read the file the command becomes tail -100 /var/log/httpd/error_log

[szecca1]

@Tom-Elliott

Theres more if you’d like

[Tom Elliott]

@szecca1 are you sure you have updated? What’s the revision on the cloud showing?

[szecca1]

@Tom-Elliott I apologize I was out yesterday sick. I just updated again today and still getting the same error. When I run the svn up command it is revision 4193 but thats all I see.

[Tom Elliott]

@szecca1 where are you running the svn up command

[szecca1]

@Tom-Elliott From putty remoted on to the FOG server

[Tom Elliott]

By where, I mean:

/root/trunk

/root/trunk/bin

etc…

[szecca1]

@Tom-Elliott cd /home/fog/svn/trunk/
basically copying what you told me in a message to run I believe

[Wayne Workman]

@szecca1 can you try to run the fog installer like this? ./installfog.sh -y

The “y” argument will automate it, and use your previous settings from the last install.

[szecca1]

@Wayne-Workman This is how I run the updates every time as per my conversation with Tom a few weeks ago:
cd /home/fog/svn/trunk
svn up
cd bin
./installfog.sh -y

[szecca1]

@szecca1 Randomly, everything just came back. Not sure why this occurred but everything seems to be fine now. Not sure if you guys changed something or what i randomly hit refresh and now the page works fine. Ugh thanks

[Wayne Workman]

@szecca1 Glad it’s fixed.

I’m going to go out on a limb and say that reinstalling FOG fixed it.

[Tom Elliott]

I’m thinking it was cache related as a refresh got it fixed.