Operating System - HP-UX
1835259 Members
2297 Online
110078 Solutions
New Discussion

Re: help with service gaurd and running package - URGENT

 
lawrenzo_1
Super Advisor

help with service gaurd and running package - URGENT

Hello,

Please help - we have had a system crash and the services running will not start in the alternative node.

When I run
#cmrunpkg
cmrunpkg : Node mbnahp67 is currently unable to run package art.
Check the syslog on node mbnahp67 and pkg log files for more detailed information.

can you tell me where the log files are or what I am doing wrong.
hello
4 REPLIES 4
Steven E. Protter
Exalted Contributor

Re: help with service gaurd and running package - URGENT

There are some logs in /etc/cmcluster

The syslog is /var/adm/syslog/syslog.log

There are errors releated to the package not starting and perhaps the crash in that file.

diagnostic:

tail -f /var/adm/syslog/syslog.log

start the cluster, then the package in another session.

You may see error messages that you need to either post here or act on.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Nguyen Anh Tien
Honored Contributor

Re: help with service gaurd and running package - URGENT

Hi lawrenzo.
You say so general so it is hard to determine your problem.
Pls post these log:
1, /var/adm/syslog/syslog.log
2, /etc/cmcluster/package_name/package_name.log

base on these info I will tell you the reason.
tienna
HP is simple
Hoang Chi Cong_1
Honored Contributor

Re: help with service gaurd and running package - URGENT

Hi

You need to check the package configuration (NODE_NAME set to mbnahp67 and the other one)
Then try:
#cmmodpkg -e -n mbnahp67

Regard,
Hoang Chi Cong
Looking for a special chance.......
lawrenzo_1
Super Advisor

Re: help with service gaurd and running package - URGENT

Thanks for all your help:

syslog was not too helpful as only denoted cannot start package.

node logs were not being written to - the issue seemed to be with the hung server, once the server had been rebooted and we ran

cmrunpkg -e -n -v

started fine.

Thanks again
hello