- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: systems management homepage on dl380 g7 is bla...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2013 10:01 AM
08-29-2013 10:01 AM
I'm trying to bring up the SMH on a DL380 G7. Going to the ip address:2301 gives standard info about re-directing to https:/...:2381. I do that and confirm the security exception. The browser url displays:
https://192.168.0.13:2381/cpqlogin.htm?RedirectUrl=/&RedirectQueryString=
but the window is blank. Any suggestions on what to check?
Thanks!
Solved! Go to Solution.
- Tags:
- SMH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2013 09:09 PM
08-29-2013 09:09 PM
Re: systems management homepage on dl380 g7 is blank
Hi,
What to check:
Check with different browser.
Clear cookies and browser history.
See if SNMP or WBEM is enbaled on the server.
Have you installed PSP onto this server?
Try to update to newer version of SMH.
Thank You!
I am a HP employee.
I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2013 03:44 AM
08-30-2013 03:44 AM
SolutionGood suggestions:
I have a group of BL460c & DL380s behind a firewall. All the systems are running RHEL 6.4. The only browser I have available is firefox 17.0.8 with java 6.0.51 plugin. The snmpd service is running. Cleared cookies, etc. Still the same. I have run service pack for proliant many times on this server. hp-asrd, hp-health, hp-snmp-agents, hpsmhd, and hpvca are all started. Currently running 7.1.2.3 of hpsmhd.
Ah.. figured it out. I looked at the web page source and saw several messages about insufficient permission. I then looked at the /opt/hp/hpsmh directory. There were several files in there, including smhpd.conf that were owned by root. I did a:
cd /opt/hp chown -R hpsmh:hpsmh hpsmh restart hpsmhd
and then reloaded the web page. Now I can see the login screen. :)
Thanks for the suggestions. It led me down the correct path. :)
- Tags:
- Permission
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2015 10:04 AM
02-16-2015 10:04 AM
Re: systems management homepage on dl380 g7 is blank
I've had this same issue as well and thought i would share my solution since this is one of the limited amount of results found.
I did a directory structure comparison between a healthy server and my problem server with the blank page issue. I found that somehow the file /opt/hp/conf/smhCertDate.txt had 640 permissions on my problem server. This was the only difference.
Once I fixed the permissions to match my healthy server (chmod 644), the issue was resolved. Login page came back without issues. This may be a less intrustive/risky way to solve the issue than a blanket chown -R