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
SHUTDOWN(8)						    BSD System Manager's Manual 					       SHUTDOWN(8)

NAME
shutdown -- close down the system at a given time SYNOPSIS
shutdown [-Ddfhknprvxz] [-b bootstr] time [message ... | -] DESCRIPTION
shutdown provides an automated shutdown procedure for super-users to nicely notify users when the system is shutting down, saving them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties. Available friendlinesses: -b bootstr The given bootstr is passed to reboot(8) for the benefit of those systems that can pass boot arguments to the firmware. Currently, this only affects sun3 and sparc machines. -d shutdown will pass the -d flag to reboot(8) or halt(8) to request a kernel core dump. If neither the -h or -r flags are specified, then -d also implies -r. -f shutdown arranges, in the manner of fastboot(8), for the file systems not to be checked on reboot. -h The system is halted at the specified time, using halt(8). -k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all but super-user). -n Prevent the normal sync(2) before stopping. -p The system is powered down at the specified time, using poweroff(8). If the powerdown fails, or the system does not support soft- ware powerdown, the system will simply halt instead. -r The system is rebooted at the specified time, using reboot(8). -v To enable verbose messages on the console, pass -v to reboot(8) or halt(8). -x To enable debugging messages on the console, pass -x to reboot(8) or halt(8). -z To silence some shutdown messages on the console, pass -z to reboot(8) or halt(8). -D Prevents shutdown from detaching from the tty with fork(2)/ exit(3). time Time is the time at which shutdown will bring the system down and may be the word now or a future time in one of two formats: +number, or [[[[[cc]yy]mm]dd]hh]mm, where the century, year, month, day, and hour may be defaulted to the current system values. The first form brings the system down number minutes from the current time; the second brings the system down at the absolute time specified. If the century is not specified, it defaults to 1900 for years between 69 and 99, or 2000 for years between 0 and 68. A leading zero in the ``yy'' value is not optional. message ... Any other arguments comprise the warning message that is broadcast to users currently logged into the system. - If - is supplied as the only argument after the time, the warning message is read from the standard input. BEHAVIOR
At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on the terminals of all users logged in. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are dis- abled by creating /etc/nologin and copying the warning message there. If this file exists when a user attempts to log in, login(1) prints its contents and exits. The file is removed just before shutdown exits. At shutdown time, a message is written in the system log containing the time of shutdown, who initiated the shutdown, and the reason. Next a message is printed announcing the start of the system shutdown hooks. Then the shutdown hooks in /etc/rc.shutdown are run, and a message is printed indicating that they have completed. After a short delay, shutdown runs halt(8) or reboot(8), or sends a terminate signal to init(8) to bring the system down to single-user mode, depending on the choice of options. The time of the shutdown and the warning message are placed in /etc/nologin and should be used to tell the users why the system is going down, when it will be back up, and to share any other pertinent information. FILES
/etc/nologin tells login(1) not to let anyone log in /fastboot tells rc(8) not to run fsck(8) when rebooting /etc/rc.shutdown System shutdown commands SEE ALSO
login(1), wall(1), fastboot(8), halt(8), init(8), poweroff(8), reboot(8), rescue(8) BACKWARD COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility. HISTORY
The shutdown command appeared in 4.0BSD. BSD
October 4, 2011 BSD