Hello,
I recently upgraded our only Solaris 8 box from Solaris 8 Maintenance
Update 2 to MU4. In addition, I hardened some of the security on the box,
among other things enabling BSM auditing. Now, amandad will not run from
inetd, although I can launch it from the command line without a problem.
The upgrade docs for Solaris warn of possible problems with applications
linked to libraries that have changed but I've rebooted, as well as
recompiled amanda and the problem persists.
In my logs, I see:
May 28 16:00:00 newt inetd[105]: [ID 858011 daemon.warning]
/usr/local/libexec/amandad: Hangup
May 28 16:00:02 newt last message repeated 38 times
May 28 16:00:02 newt inetd[105]: [ID 667328 daemon.error] amanda/udp
server failing (looping), service terminated
This occurs each time inetd attempts to launch amandad.
As soon as I disable kernel auditing and reboot, amandad launches fine
from inetd. I don't feel like downgrading this box to Solaris 8MU2 since
the upgrade took four hours (!!!!) just to see if it works with that
version and with auditing.
So is this an amandad problem or a Solaris problem or both? If anyone is
a Sun contract customer, the error messages and behaviour that is logged
is very similar to bug # 4335695, although that deals with the attempted
execution of non-existent applications by inetd.
Now I guess I have to decide which is more important - auditing a system
while its getting cracked or hosed or being able to restore a system after
its cracked or hosed. I guess I'll opt for the backup but I'm curious why
the two don't play nice with each other.
Kevin
--
Kevin M. Myer
Systems Administrator
Lancaster-Lebanon Intermediate Unit 13
(717)-560-6140
