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 - Restarts the machine SYNOPSIS
/usr/sbin/reboot [-dlnq] DESCRIPTION
When the system is running and multiple users are logged in, use the shutdown -r command to perform a reboot operation. If no users are logged in, use the reboot command. The reboot command normally stops all running processes, syncs the disks, logs the reboot, and writes a shutdown entry in the login accounting file, /var/adm/wtmp. The reboot command uses the sync call to synchronize the disks, and to perform other shutdown activities such as resynchronizing the hard- ware time-of-day clock. After these activities, the system reboots. By default, the system starts and the file systems are automatically checked. If the start-up activities are successful, the system comes up in the default run-level. You must have root privileges to use this command. Using the -n flag can result in file system damage. FLAGS
Generates a crash dump of the system before halting it. Can be used with any of the other flags. Does not log the reboot using syslog Does not sync the disks or log the reboot using syslog Performs a quick reboot without first shutting down running processes; does not log the reboot using syslog EXAMPLES
To enable the default reboot action, enter: reboot This command causes the system to stop all running processes, sync the disks, log the shutdown, and perform other routine shutdown and reboot activities. To shut down the system without logging the reboot, enter: reboot -l This command shuts down the system and performs all shutdown and reboot activities, except logging the shutdown. To reboot the system abruptly, enter: reboot -q This command reboots the system abruptly without shutting down running processes. FILES
Specifies the command path Specifies the login accounting file Specifies the path of the syslog daemon RELATED INFORMATION
Commands: fsck(8), halt(8), init(8), savecore(8) shutdown(8), syslogd(8) Functions: reboot(2), sync(2), syslog(3) delim off reboot(8)