- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Insight Management agent do not start
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
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
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
тАО11-12-2007 02:54 AM
тАО11-12-2007 02:54 AM
during upgrade from Agent 3.5 to 3.7 (or 3.6 too) on several ES47, I have trouble on 2 of them.
hpsmhd doesn't seem to start, as I am running :
setld -l cpqim370 (same as /sbin/init.d/hpsmhd start)
The process is stuck on :
hpsmd: Could not determine the server's fully qualified domain name, using XX.XX.XX.XX for ServerName
Connected to 127.0.0.1:2301
and is waiting indefinetly...
Strange behaviour, because on other identical computer (hardware and OS) the upgrade went well.
Any suggestion will be greatly appreciated...
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2007 02:59 AM
тАО11-12-2007 02:59 AM
Re: Insight Management agent do not start
Check your /etc/hosts file, you should have one entry with the hostname + domain for your host, for example:
192.168.0.1 thihost.domain.com thishost
Also check if the hostname command returns the hostname + domain (fully qualified domain name).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2007 03:31 AM
тАО11-12-2007 03:31 AM
Re: Insight Management agent do not start
I have to precise that my computers don't have FQDN, they do not use DNS name. So, in /etc/hosts, I only have :
xx.xx.xx.01 hostH
xx.xx.xx.02 hostS
xx.xx.xx.03 hostG
and all /etc/hosts files are identical.
What is strange, is that installation fails on 2 of 3 computers, the 3rd one (hostH) has the same OS installation (disk clone). I also have the warning on it (hpsmd: Could not determine the server's fully qualified domain name, using XX.XX.XX.XX for ServerName
) but the installation continues to the end.
hostH and hostS are strictly identical (ES47) with 2 network cards on 2 separated networks (1 main, the other ties both computers directly), hostG is a dual ES47 (2 drawers) with 2 network interfaces in an agregate on main network.
Yes, I thinks that the pb is around the fact that hpsmhd launch itself on a bad NIC...
How to check that ? where is the file specifying which interface to use ? (if it is the good diagnostic...)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2007 12:03 AM
тАО11-16-2007 12:03 AM
Re: Insight Management agent do not start
192.168.0.1 thishost.local thishost
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2007 12:13 AM
тАО11-16-2007 12:13 AM
Re: Insight Management agent do not start
name.
>>> hostH and hostS are strictly identical >>> (ES47) with 2 network cards on 2
>>> separated networks (1 main, the other >>> ties both computers directly)
but this does not reflect in the hostfile you supply!
>>> xx.xx.xx.01 hostH
>>> xx.xx.xx.02 hostS
>>> xx.xx.xx.03 hostG
I would expect something like :
xx.xx.xx.01 hostH-nic1-net1
xx.xx.yy.01 hostH-nic2-net2
xx.xx.xx.02 hostS-nic1-net1
xx.xx.yy.02 hostS-nic2-net2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2007 12:21 AM
тАО11-16-2007 12:21 AM
Re: Insight Management agent do not start
Those netwwork I'm interrested in, is the "1st" one, because it is there that I have my Insight Manager Server (another computer under Windows 2003 srv) which is supposed to collect events...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2007 12:35 AM
тАО11-16-2007 12:35 AM
Re: Insight Management agent do not start
something like netdev_0 to ee0 for the main link and netdev_1 to ee1 for the crosslink.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2007 02:26 AM
тАО11-16-2007 02:26 AM
Re: Insight Management agent do not start
I'm not sure about this solution, because on the computer without trouble (hostH), I've :
> rcmgr mget | grep -i netdev
...
NETDEV_5=
NETDEV_4=
NETDEV_3=
NETDEV_2=
NETDEV_0="bcm0"
NETDEV_1="bcm4"
as on hostS.
and on the hostG (with nic combined by lag), this variables or not defined :
> rcmgr mget | grep -i netdev
...
NETDEV_5=
NETDEV_4=
NETDEV_3=
NETDEV_2=
-nil-
It will be the end of day work, here, but if you've got another good ideas, please suggest :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-19-2007 09:36 PM
тАО11-19-2007 09:36 PM
Re: Insight Management agent do not start
It has "fall" on start on the second host without the lag on the 2 nic...
but on this hostG, no way...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-22-2007 09:34 PM
тАО11-22-2007 09:34 PM
SolutionI do have configured netrain in wich NETDEV_0 is associated to nr0 :
NR_DEVICES="1"
export NR_DEVICES
NRDEV_0="nr0"
export NRDEV_0
NRCONFIG_0="ee0,ee1"
export NRCONFIG_0
NUM_NETCONFIG="1"
export NUM_NETCONFIG
NETDEV_0="nr0"
export NETDEV_0
IFCONFIG_0="10.1.3.26 netmask 255.255.0.0"
export IFCONFIG_0
For use with lag I would expect similar entries in this file.
as in http://unix.derkeiler.com/Mailing-Lists/Tru64-UNIX-Managers/2004-01/0147.html
i see conformed that one interface is configured through rc.config and the lag is formed by adding interfaces through /etc/inet.local