>amcheck-server: could not get changer info: could not read result from
>"/usr/local/libexec/stc-changer"
Hmmmm. This says Amanda fork'd and ran /usr/local/libexec/stc-changer
but when it did a read to gather the result string (or an error message)
all it got was EOF.
When you ran stc-changer by hand, did you run this exact path to it?
In other words, did you run (as the Amanda user):
/usr/local/libexec/stc-changer -info
Maybe Amanda thinks it's installed here but it's really someplace else
(although that should have generated an error message)?
The implication is that stc-changer is either not running at all or it
is running but terminating immediately without a peep for some reason.
As you can tell from my first question :-), I'm not familiar with this
program (is there a URL?). Does it write log information anyplace?
If none of this helps, the next bigger hammer I'd pull out is to shift
stc-changer aside (mv stc-changer stc-changer-real) and put a script in
its place. First I'd have it do something simple just to make sure
things worked:
#!/bin/sh
echo "<none> just a bad response"
exit 0
Then I'd have it run stc-changer-real under truss and log all the system
call activity to a file, then grope through there.
One wild guess is that Amanda has cleared the environment of something
stc-changer needs. Like $TAPE? Or $CHANGER? Or $LD_LIBRARY_PATH?
What happens if you clear the environment and run your "by hand" test
(again, as the Amanda user):
env - HOME="$HOME" PATH="$PATH" /usr/local/libexec/stc-changer -info
>Chris
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
