Login or Register to Ask a Question and Join Our Community


AIX

subsystems are all inoperative

Login to Discuss or Reply to this Discussion in Our Community

 
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

LEARN ABOUT HPUX

reboot

reboot(2)							System Calls Manual							 reboot(2)

NAME

       reboot - boot the system

SYNOPSIS

DESCRIPTION

       causes the system to reboot.  howto is a mask of reboot options (see specified as follows:

	      A file system sync is performed (unless
				  is set) and the processor is rebooted from the default device and file.

	      The processor is simply halted.
				  A sync of the file system is performed unless the flag is set.  should be used with caution.

	      On systems with cellular architecture, all cells in the partition are
				  rebooted  in order to reconfigure the stable complex configuration data.  On systems with non-cellular architec-
				  ture, the default is A sync of the file system is performed unless the flag is set.

	      Shut down the system firmware to a "ready to reconfigure" state and do not
				  reboot.  This option can be used only in combination with

	      A sync of the file system is not performed.

       Unless the flag has been specified, reboot(2) unmounts all mounted file systems and marks them clean so that it will not  be  necessary	to
       run fsck(1M) on these file systems when the system reboots.

       Only users with appropriate privileges can reboot a machine.

RETURN VALUE

       If successful, this call never returns.	Otherwise, a -1 is returned and is set to indicate the error.

ERRORS

       fails if this condition is encountered:

	      [EPERM]		  The effective user ID of the caller is not a user with appropriate privileges.

DEPENDENCIES

       The default file and device for is on the current root device.

AUTHOR

       was developed by HP and the University of California, Berkeley.

SEE ALSO

       reboot(1M), privileges(5).

																	 reboot(2)