System locked during shutdown

[David Owens_1]

While doing a "shutdown -h 0" on a rp5405, the system locked while performing the following task during shutdown.

Stopping VERITAS Enterprise Administrator Service (vxsvc)

It has only happen once but I was wondering if anyone else has experienced this. There may even be a patch that I don't know about.


David Owens
Ingersoll-Rand Co.

[S.K. Chan]

Looking through the list of patches for VxVM in ITRC I could not find anything that relates to vxsvc symptom that you're seeing. I personally have not seen this before. You might want to spend some time going through the patches yourself. The closest are probably VxVM Command Cumulative, VxVM Cmd Exec Fix, VxVM Startup Error.

[Rick Schopp]

This just happened to me. I just made an install of 11.i on an old E class box. Everything looked good until I tried "shutdown -y 0" to bring it to single user mode. It hung on "stopping VERITAS Enterprise Admin Services (vxsvc)." It has done this twice now.

[Gene P. Cooke]

I also have upgraded a D380 to 11i and have had the system shutdown hang twice (weekly automated reboot through cron) at 'Stopping VERITAS Enterprise Administrator Service (vxsvc)'.
I certainly would appreciate any feedback from others who may have found the underlying cause.

[Keith German]

I see the same issue with the VERITAS Enterprise Administrator Service on an rp8400 running 11.11.

Stopping VERITAS Enterprise Administrator Service (vxsvc)
Output from "/sbin/rc1.d/K999isisd stop":
----------------------------
VEA Server is shutting down ...

Whenever I reboot this server, the shutdown of VEA takes forever(30-40 minutes)! I usually just kill -9 vxsvc and see no adverse affects. I would like to know why this happens though. Any info would be appreciated.

Keith

[Patrick Wallek]

I had this happen today on a freshly installed 11.11 machine. I finally just a CTRL-SHIFT-| (that is the pipe symbol) and that seemed to kill it.

[Bill Hassell]

I would highly recommend patches for the Veritas product. It obviously is not happy about something. Look at the start/stop script in /sbin/init.d and see what commands are being run for each section (start and stop) then look at the docs for these commands. Make sure that the location (order) where the Veritas product is corret for start and stop as the product may depend on other subsystems to function correctly.