topic Re: System Management Homepage Timeout in Server Management - Systems Insight Manager

System Management Homepage Timeout

John Valantine — Wed, 27 Jun 2007 09:57:34 GMT

Just upgraded to PSP 7.8, now all of a sudden my system management homepage is giving me timeout errors. I have seen other threads indicating a change to SNMP settings might be required (though everything was working before the upgrade to 7.8...). What I was hoping for is some instructions on how to add the public community. I am on RHEL 4. I assume I have to edit snmpd.conf, right? I really have no SNMP experience, and as I said, the systems management homepage just worked until now...

Thanks in advance

John Valantine

Re: System Management Homepage Timeout

Neysters, Lutz — Thu, 28 Jun 2007 03:49:40 GMT

First thing you should do is have a look at the log. Choose "logs" on the System Management Homepage (SMH) and click on "System Management Homepage Log". Scroll down until you see the latest entries. One of the entries should look like this:
"
ERROR LOG (severity=2) Thu Jun 21 16:29:52 2007
UI Timeout -- Nav Load Time: 916s [breakdown: dataprotection(Protect Your Data): 0s || hmanics(HP NIC Agent): 8s || hmaserv(HP Server Agent): 8s || vcagent(HP Version Control Agent): 900s || webagent(HP Foundation Agent): 0s || elm(backwards compatibility): 0s]
"

I my case the version control agent is always the culprit, if there's a timeout, sometimes because of the VCRM server being too slow, sometimes because the network connection is overloaded.
In Windows you could try and stop the service "HP version control agent" to verify. In Linux I don't know ...

Re: System Management Homepage Timeout

John Valantine — Thu, 28 Jun 2007 08:52:46 GMT

Thanks,

I just logged in, and here is what is in my log...

INFORMATION LOG (severity=0) Thu Jun 28 06:50:48 2007
User:root from XXX.XX.X.XXX was authenticated and authorized with 'Administrator' rights

Nothing about any times....

I also have to log in between each screen. Basically every link I click will give me the timeout message, then require me to log in again, then give me the timeout message again, then take me to the page...

Re: System Management Homepage Timeout

Neysters, Lutz — Fri, 29 Jun 2007 03:57:53 GMT

What was your PSP Version before upgrading?
What about settings/security on the SMH: What kind of trust mode? If it is "Trust by certificate", is your CMSs (Central Management Server) certficate in the Trusted Certficate List?

Can you open the SMH "locally" on the managed server without logging on again and again?
Do you have the same snmp read- and write-community on the CMS and the managed server?
all about snmp setting look here:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1001139

Did you try to stop the version control agenet / service temporarily.

Re: System Management Homepage Timeout

John Valantine — Fri, 29 Jun 2007 08:54:02 GMT

I was on 7.7 before. I will check the trust mode, I am not sure. I did not change anything, but perhaps the upgrade did. I did a bit more fussing with the snmpd.conf file, and if I make a few changes I can eliminate the timeouts and the SNMP settings on the SMH start appearing. Unfortunately, when I do that, all the screens contain no data, and my system identifier moves from unknown to 'NULL'.

I did try disabling vca, (I had seen that from a forum search so I tried that before I posted, I should have mentioned that). Thanks for the help, I'll keep working, but I am pretty close to out of ideas...

Re: System Management Homepage Timeout

Jesse Zellmer — Tue, 03 Jul 2007 15:53:37 GMT

This can sometimes happen because the VCA on a server loses connection to the VCRM (Version Control Repository Manager). I seen a thread where updating the VCRM to the latest version resolved this issue.

Re: System Management Homepage Timeout

CCyre — Tue, 18 Dec 2007 21:38:48 GMT

In my case, windows, I just had to retype in the VCA config where it asks what the name of the repository is and the id and pw to access it. Even though I had already done it before when I first added the server.