It turns out that the monitoring daemon that was running the vxiod command was not root, and so did not have access to some of the devices that vxiod tries to check for. Because of this it comes back w/ an unexpected (to the monitoring program) error, and so incorrectly reports that the daemons were not running. The problem was to set the root execute sticky bit permission on the 'asroot' program that is supposed to call the vxiod program, it now has the proper permissions and gets the results it is looking for. Thanks much to Adam Kirby for helping me with this. -Damon > -----Original Message----- > From: Damon LaCaille > Sent: Wednesday, April 25, 2001 8:45 AM > To: 'sunmanagers@sunmanagers.org' > Subject: vxio process not running > > Hi, > We're running Volume Manager on multiple E250's. I also run Big Brother > to monitor Veritas. It is saying that vxio processes are not running on 3 > of the 5 boxes, but those 5 boxes are still up and running. I can't get a > vx_list or do a vx_group check on them w/out this process running > apparently. > Is it safe to restart this process? If so, how would I go about it? > Any ideas? Am I in a really bad situation? :) Thanks much > > Damon >Received on Wed Apr 25 15:23:02 2001
This archive was generated by hypermail 2.1.8 : Wed Mar 23 2016 - 16:24:53 EDT