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 - automatic reboot procedures

Syntax
       /etc/reboot [ -n ] [ -q ]

Description
       The  ULTRIX  system is booted by loading a kernel image, usually into memory at location zero and transferring to zero.	Because the system
       is not reenterable, the kernel image must be read in from disk each time the system is bootstrapped.

       When the reboot of a running system is desired, is normally used.  If there are no users, can be used.  The command causes the disks to	be
       synced,	and  then  a multiuser reboot is initiated.  The system is booted and an automatic disk check is performed.  If the procedure suc-
       ceeds, the system is then brought up for the users.

       The system will reboot itself after a power failure or after a crash, provided auto-restart is enabled on your system.  A consistency check
       of the file systems will be performed and, unless the check fails, the system will resume multiuser operations.

Options
       -n   Prevents the disks from being synced.

       -q   Reboots quickly and ungracefully, without shutting down running processes first.

Files
       System code

See Also
       crash(8v), fsck(8), halt(8), init(8), newfs(8), rc(8), shutdown(8)

																	 reboot(8)