Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Web interface inaccessible after upgrade + different pS versions in shell and web

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Web interface inaccessible after upgrade + different pS versions in shell and web


Chronological Thread 
  • From: Andrew Lake <>
  • To: Alex Moura <>
  • Cc:
  • Subject: Re: [perfsonar-user] Web interface inaccessible after upgrade + different pS versions in shell and web
  • Date: Tue, 7 Oct 2014 15:41:30 -0400

Hi Alex,

For the host with the web page that won't load, can you send me /var/log/perfsonar/web_admin/web_admin.log? Looking at the Apache logs it looks like the cgi script is hanging. web_admin.log will hopefully give a better idea of what it is doing while it hangs. Also, does the host have limited external network connectivity? My guess is that is contributing (since it checks with a remote lookup service to see if your host is registered) but want to understand better since we thought we protected things like this from happening in such cases.

For the host with the incorrect version in the login message, what happens when you run "/etc/init.d/generate_motd start" and then re-login?

Thanks,
Andy


On Oct 7, 2014, at 2:36 PM, Alex Moura <> wrote:


On 07/10/2014, at 13:45, Andrew Lake <> wrote:

Hi Alex,

On Oct 7, 2014, at 12:30 PM, Alex Moura <> wrote:

Hello, 

After upgrading a pS box from 3.3.2 to pS 3.4, its web interface stopped working:
------------------------------------------------------------------------------

Gateway Time-out
The gateway did not receive a timely response from the upstream server or application.

Can you SSH into the host?  The gateway timeout could be a number of things. That's what happens when apache doesn't respond. Maybe try restarting apache (/sbin/service/httpd restart) or rebooting the host. 

I did restart the http service and also rebooted the host, but the result is the same. 
Maybe there is another process, - i.e.: cassandra - which the web interface depends on?
Now I noticed there are lots of error messages in the http log like this:

/var/log/httpd/error_log:[Tue Oct 07 15:26:34 2014] [error] cassandra_db [DEBUG] Flush called



The shell is likely the more inaccurate of the two. I believe motd (the file that provides the login message) is regenerated after reboot. Did you reboot this host after upgrade?

Yes, I did.

The filtered log without the "cassandra_db Flush called” errors is available at: https://dl.dropboxusercontent.com/u/970090/error_log.txt


Thanks,
Alex
--------
WARNING: At least one of the links in the message below goes to an IP address (e.g. 10.1.1.1), which could be malicious. To learn how to protect yourself, please go here: https://commons.lbl.gov/x/_591B
--------




Archive powered by MHonArc 2.6.16.

Top of Page