Re: amandad error
Hi Paul Paul Bijnens wrote: Op ma 17-03-2003, om 22:57 schreef bao: xinetd[...]: execv( ../usr/libexec/amandad ) failed : Permission denied (errno = 13) Are the directory usr and libexec also accessible as amanda? Can you try: su amanda -c /usr/libexec/amandad I had already done a make install, but when I issued the command you suggested, this is what I see: ../amandad: line 1: cd:/../amanda-2.4.4/client-src: No such file or directory gcc: amandad.o: No such file or directory gcc: ./.libs/libamclient.so: No such file or directory gcc: ./common-src/.libs/libamanda.so: No such fiile or directory Why does it look at the source directory?? Hmmm This command should just sit there for about 30 seconds and then exit (if you type something it exists immediately). It also creates a file: /tmp/amanda/amandad.*DateTimeStamp*.debug with the error message (timeout or error receiving message).
RE: amandad error
Same Amanda id on both machines? Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bao Sent: Monday, March 17, 2003 4:29 PM To: amanda Subject: amandad error Hi list, I tested with Amanda-2.4.4 on a test machine and it is ok. But when I moved to the production machine, i get some errors. Backup server RH 8.0 kernel 2.4.18-19.8.0 Everything was set according to the test machine. When I run amcheck Weekyly, I get a selfcheck request timed out. Host down? syslog spills these: xinetd[...]: execv( ../usr/libexec/amandad ) failed : Permission denied (errno = 13) I have compared the config and file permissions on both machines, they're the same. Has anyone had this problem before??? Thanks,
Re: amandad error
Yes, this may be a big clue. Let me try shutting the other one off first. :) Thomas Hu wrote: Same Amanda id on both machines? Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bao Sent: Monday, March 17, 2003 4:29 PM To: amanda Subject: amandad error Hi list, I tested with Amanda-2.4.4 on a test machine and it is ok. But when I moved to the production machine, i get some errors. Backup server RH 8.0 kernel 2.4.18-19.8.0 Everything was set according to the test machine. When I run amcheck Weekyly, I get a selfcheck request timed out. Host down? syslog spills these: xinetd[...]: execv( ../usr/libexec/amandad ) failed : Permission denied (errno = 13) I have compared the config and file permissions on both machines, they're the same. Has anyone had this problem before??? Thanks,
Re: amandad error
Yes, same id. I thought that there might have been a collision, because syslog on the production machine says something like Deactivating service amanda due to excessive incoming connections. Restarting in 30 seconds. But after I had turned off amanda on the test machine, the error still occurs. Thomas Hu wrote: Same Amanda id on both machines? Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bao Sent: Monday, March 17, 2003 4:29 PM To: amanda Subject: amandad error Hi list, I tested with Amanda-2.4.4 on a test machine and it is ok. But when I moved to the production machine, i get some errors. Backup server RH 8.0 kernel 2.4.18-19.8.0 Everything was set according to the test machine. When I run amcheck Weekyly, I get a selfcheck request timed out. Host down? syslog spills these: xinetd[...]: execv( ../usr/libexec/amandad ) failed : Permission denied (errno = 13) I have compared the config and file permissions on both machines, they're the same. Has anyone had this problem before??? Thanks,
Re: amandad error
Op ma 17-03-2003, om 22:57 schreef bao: xinetd[...]: execv( ../usr/libexec/amandad ) failed : Permission denied (errno = 13) Are the directory usr and libexec also accessible as amanda? Can you try: su amanda -c /usr/libexec/amandad This command should just sit there for about 30 seconds and then exit (if you type something it exists immediately). It also creates a file: /tmp/amanda/amandad.*DateTimeStamp*.debug with the error message (timeout or error receiving message).
