[Veritas-bu] NBU 6.0 - Device Daemon not starting
2006-05-23 16:18:36
Subject: |
[Veritas-bu] NBU 6.0 - Device Daemon not starting |
From: |
gregcoleman at usa.com (Greg Coleman) |
Date: |
Tue, 23 May 2006 16:18:36 -0400 |
Small 2 node config. 1 master, 1 meda.
Media has 1 L500 tape library w/ 1 DLT drive.
Solaris 9 112233-07 NBU 6.0 MP2
ltid fails to start on the media server though the library/drive are configured
and visible via tpconfig and sgscan.
The ltid log file displays the following cryptic message at the time of exit:
17:14:33.095 [28444] <16> emmlib_UpdateHostEx: (0) UpdateMachine failed,
emmError = 4000002, nbError = 0
17:14:33.095 [28444] <16> AddAndVerifyHost: Failed to update this host. EMM
error code = 4000002
17:14:33.117 [28444] <16> AddAndVerifyHost: (-) Translating
EMM_ERROR_ArgInvalid(4000002) to 191 in the Media context
17:14:33.120 [28444] <3> logstderrmsg: Failed to validate this host with the
EMM server
17:14:35.260 [28444] <4> TermLtid: chmod dev files
Using the wizard from the master (new install): Device Configuration.
It scans the media server, discovers the robot and drive, prompts if I want to
commit the changes, then reponds with "Restarting Device Daemon". After a
while, that same message gets prefaced with a yellow exclamation mark, but no
further explanation. The changes are never committed and you are back to the
beginning again.
The only evidence of failure is the snippet from the log file above. At least
of where I know to look in 6.0.
Any takers on this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060523/ee52f931/attachment.html
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Veritas-bu] NBU 6.0 - Device Daemon not starting,
Greg Coleman <=
|
|
|