subsystems are all inoperative


 
Thread Tools Search this Thread
Operating Systems AIX subsystems are all inoperative
# 1  
Old 06-12-2008
subsystems are all inoperative

Hi,

As part of our maintenance schedule, we reboot our systems every few months to test HACMP and etc... etc....
It looked like everything was normal but when we tried to bring up HACMP, we didn't see anything in the /etc/hacmp.out and we didn't see any processes associated with HACMP running.

So, I looked at "lssrc -a" to see if the subsystems associated with HACMP was running and this is part of what I saw:

atlmboxa/root :/>lssrc -a|more
Subsystem Group PID Status
qdaemon spooler inoperative
writesrv spooler inoperative
lpd spooler inoperative
clvmd inoperative
inetd tcpip inoperative
gated tcpip inoperative
named tcpip inoperative
.....
.......
...........

All of the subsystems show up as inoperative, starting them manually does not help, rebooting the system does not help.

Has anyone seen this behavior before? If so, what is causing it and how do we fix it.

Thanks in Advance.
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. AIX

xntpd process inoperative

Hi All, After restarting the xntpd process for some reasons when i checked the status its showing inoprative eventhough xntpd process is running when i ps on it. $ lssrc -s xntpd Subsystem Group PID Status xntpd tcpip ... (1 Reply)
Discussion started by: ram1729
1 Replies

2. UNIX for Dummies Questions & Answers

Processes, Services, Daemon's and Subsystems

I'm just wondering what the differences/relationships there are between processes, services, daemons and subsystems? I keep coming across these terms but I can't find clear definitions/explanations of these terms. :confused: (3 Replies)
Discussion started by: quickfirststep
3 Replies
Login or Register to Ask a Question
REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME
reboot - reboot the system immediately SYNOPSIS
reboot [-f] DESCRIPTION
Reboot can be used to reboot the system after installing a new kernel. It does not inform the users, but does log it's actions in /usr/adm/wtmp and /usr/adm/authlog. The system is then rebooted with the reboot(2) systemcall. If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call. If the wtmp file exists, reboot logs itself as if it were a shutdown. This is done to prevent last(1) from talking about system-crashes. Reboot is registered as is in the authlog file. Reboot can only be executed by the super-user. Any other caller will be refused, either by reboot(8) or by reboot(2). SEE ALSO
reboot(2), shutdown(8), halt(8), boot(8). BUGS
The error message's given by reboot are not always useful. There are several routines that can fail, but which are not fatal for the pro- gram. AUTHOR
Edvard Tuinder (v892231@si.hhs.NL) REBOOT(8)