Re: amanda client inetd problem
On 2006-08-11 14:41, Jeff Portwine wrote: I'm trying to configure a couple of new amanda clients, and when the amanda server was unable to get a response from them I looked in the system logs on one of the clients and I saw: Aug 11 08:32:27 client inetd[435]: /usr/local/libexec/amandad (pid 2479): exit status 127 Aug 11 08:32:27 client inetd[435]: /usr/local/libexec/amandad (pid 2480): exit status 127 Aug 11 08:32:27 client inetd[435]: amanda/udp server failing (looping or being flooded), service terminated for 10 min The first two lines are actually repeated a whole bunch of times before the final message... Any idea what could be causing this? My inetd entry looks like: amanda dgram udp wait backup /usr/local/libexec/amandad amandad Or was it nowait, and you changed it to wait (or fixed the username backup), but forgot to sig-HUP the inetd process after you fixed it? What happens when you execute the command /usr/local/libexec/amandad as user backup manually? It should timeout after 30 seconds; or if you type something on the keyboard, it will abort immediatly. More tips to check: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_failed -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: amanda client inetd problem
amanda dgram udp wait backup /usr/local/libexec/amandad amandad Or was it nowait, and you changed it to wait (or fixed the username backup), but forgot to sig-HUP the inetd process after you fixed it? No, I added the inetd entry as listed above and then actually rebooted the machine to make sure inetd restarted properly. What happens when you execute the command /usr/local/libexec/amandad as user backup manually? $ /usr/local/libexec/amandad /usr/local/libexec/amandad: error in loading shared libraries: libamclient-2.5.0p2.so: cannot open shared object file: No such file or directory However, that library does exist... $ ls -l /usr/local/lib/libam* -rwxr-xr-x1 root root 361796 Aug 11 08:07 /usr/local/lib/libamanda-2.5.0p2.so -rw-r--r--1 root root 1270664 Aug 11 08:07 /usr/local/lib/libamanda.a -rwxr-xr-x1 root root 875 Aug 11 08:07 /usr/local/lib/libamanda.la lrwxrwxrwx1 root root 20 Aug 11 08:07 /usr/local/lib/libamanda.so - libamanda-2.5.0p2.so -rwxr-xr-x1 root root99610 Aug 11 08:07 /usr/local/lib/libamclient-2.5.0p2.so -rw-r--r--1 root root 239810 Aug 11 08:07 /usr/local/lib/libamclient.a -rwxr-xr-x1 root root 889 Aug 11 08:07 /usr/local/lib/libamclient.la lrwxrwxrwx1 root root 22 Aug 11 08:07 /usr/local/lib/libamclient.so - libamclient-2.5.0p2.so so I'm not sure what the problem is. http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_failed I've been going through this list .. but so far not found exactly what the problem is :\ Thanks, Jeff
Re: amanda client inetd problem
On Fri, Aug 11, 2006 at 09:36:21AM -0400, Jeff Portwine enlightened us: amanda dgram udp wait backup /usr/local/libexec/amandad amandad Or was it nowait, and you changed it to wait (or fixed the username backup), but forgot to sig-HUP the inetd process after you fixed it? No, I added the inetd entry as listed above and then actually rebooted the machine to make sure inetd restarted properly. What happens when you execute the command /usr/local/libexec/amandad as user backup manually? $ /usr/local/libexec/amandad /usr/local/libexec/amandad: error in loading shared libraries: libamclient-2.5.0p2.so: cannot open shared object file: No such file or directory However, that library does exist... $ ls -l /usr/local/lib/libam* -rwxr-xr-x1 root root 361796 Aug 11 08:07 /usr/local/lib/libamanda-2.5.0p2.so -rw-r--r--1 root root 1270664 Aug 11 08:07 /usr/local/lib/libamanda.a -rwxr-xr-x1 root root 875 Aug 11 08:07 /usr/local/lib/libamanda.la lrwxrwxrwx1 root root 20 Aug 11 08:07 /usr/local/lib/libamanda.so - libamanda-2.5.0p2.so -rwxr-xr-x1 root root99610 Aug 11 08:07 /usr/local/lib/libamclient-2.5.0p2.so -rw-r--r--1 root root 239810 Aug 11 08:07 /usr/local/lib/libamclient.a -rwxr-xr-x1 root root 889 Aug 11 08:07 /usr/local/lib/libamclient.la lrwxrwxrwx1 root root 22 Aug 11 08:07 /usr/local/lib/libamclient.so - libamclient-2.5.0p2.so so I'm not sure what the problem is. Is /usr/local/lib in your ld.so.conf and did you run ldconfig after installing amanda? Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: amanda client inetd problem
That was my first thought too, but /usr/local/lib is already in /etc/ld.so.conf Have you the directory /usr/local/lib listed on /etc/ld.so.conf? This file is a kind of path for finding libraries. You probably don't have it. After adding it you have to run ldconfig to update the cache used to find libraries. -Jeff
Re: amanda client inetd problem
Jeff Portwine wrote: What happens when you execute the command /usr/local/libexec/amandad as user backup manually? $ /usr/local/libexec/amandad /usr/local/libexec/amandad: error in loading shared libraries: libamclient-2.5.0p2.so: cannot open shared object file: No such file or directory However, that library does exist... The library may exist but the system could not find it. Have you the directory /usr/local/lib listed on /etc/ld.so.conf? This file is a kind of path for finding libraries. You probably don't have it. After adding it you have to run ldconfig to update the cache used to find libraries. If amandad doesn't work when called by hand it won't work when called by inetd... ;-) Bye!
Re: amanda client inetd problem
On Fri, Aug 11, 2006 at 09:36:21AM -0400, Jeff Portwine wrote: amanda dgram udp wait backup /usr/local/libexec/amandad amandad Or was it nowait, and you changed it to wait (or fixed the username backup), but forgot to sig-HUP the inetd process after you fixed it? No, I added the inetd entry as listed above and then actually rebooted the machine to make sure inetd restarted properly. What happens when you execute the command /usr/local/libexec/amandad as user backup manually? $ /usr/local/libexec/amandad /usr/local/libexec/amandad: error in loading shared libraries: libamclient-2.5.0p2.so: cannot open shared object file: No such file or directory However, that library does exist... $ ls -l /usr/local/lib/libam* -rwxr-xr-x1 root root 361796 Aug 11 08:07 From a few things I'm guessing that both client and server are running on linux systems. Out of curiosity, which distros still use inetd rather than xinetd? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amanda client inetd problem - solved
I guess the problem was simply that it couldn't find the libraries in /usr/local/lib afterall, though I don't really know why. I tried making a symbolic link in /usr/lib to all the libam libraries in /usr/local/lib and it fixed the problem I was having.Maybe just running ldconfig would have fixed it afterall... but I didn't add /usr/local/lib to the ld.so.conf file myself, it was already there so it shouldn't have needed an ldconfig, but I guess you can't assume anything. At any rate , that particular problem seems to be solved.. thanks for the input. -Jeff
Re: amanda client inetd problem
On Fri, 11 Aug 2006, rom wrote:
Jeff Portwine wrote:
What happens when you execute the command /usr/local/libexec/amandad
as user backup manually?
$ /usr/local/libexec/amandad
/usr/local/libexec/amandad: error in loading shared libraries:
libamclient-2.5.0p2.so: cannot open shared object file: No such file or
directory
However, that library does exist...
And is it readable by the backup user?
The library may exist but the system could not find it.
Have you the directory /usr/local/lib listed on /etc/ld.so.conf? This file is
a kind of path for finding libraries. You probably don't have it.
After adding it you have to run ldconfig to update the cache used to find
libraries.
If amandad doesn't work when called by hand it won't work when called by
inetd... ;-)
What does `ldd /usr/local/libexec/amandad' say?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
Re: amanda client inetd problem
On Friday 11 August 2006 09:53, Jeff Portwine wrote: That was my first thought too, but /usr/local/lib is already in /etc/ld.so.conf Did you run, by hand, and as root, the ldconfig command to update those links? I have to do this when I install a new snapshot of amanda. Always. Have you the directory /usr/local/lib listed on /etc/ld.so.conf? This file is a kind of path for finding libraries. You probably don't have it. After adding it you have to run ldconfig to update the cache used to find libraries. -Jeff -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: amanda client inetd problem - solved
On Friday 11 August 2006 10:22, Jeff Portwine wrote: I guess the problem was simply that it couldn't find the libraries in /usr/local/lib afterall, though I don't really know why. I tried making a symbolic link in /usr/lib to all the libam libraries in /usr/local/lib and it fixed the problem I was having.Maybe just running ldconfig would have fixed it afterall... but I didn't add /usr/local/lib to the ld.so.conf file myself, it was already there so it shouldn't have needed an ldconfig, but I guess you can't assume anything. But, here anyway, anytime any of these libraries is updated or installed, ldconfig must be run, by root, in order for those libraries to become properly softlinked to their more generalized names. In the linux method of finding a file it needs, if you strace a process, you'll see how it searches for the resources a process needs, often by making 4 or 5 guesses, which if they fail, it will then consult the list, a cache file IIRC, and find the location by scanning this cache file, and the next open attempt is then successfull. But if that cache file isn't kept current, even that lookup with fail as the linkage it contains is stale. I believe that was the failure you were seeing. When usng a package manager such as rpm, the 'post-install' script will often do this for you, but from tarball installs where the 'make install', which would be the logical place to perform this after all the copying has been done, usually doesn't do a fresh run of ldconfig. Maybe we should file a bug against the amanda Makefile? Possibly, but now that I know it needs to do done, its almost a habit to do so, and a relatively minor nit to pick. :) At any rate , that particular problem seems to be solved.. thanks for the input. -Jeff -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: amanda client inetd problem
Jon LaBadie wrote: From a few things I'm guessing that both client and server are running on linux systems. Out of curiosity, which distros still use inetd rather than xinetd? Debian still uses inetd by default, although xinetd and several other variants are available as optional packages. Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda client inetd problem
On Friday 11 August 2006 10:21, Jon LaBadie wrote: On Fri, Aug 11, 2006 at 09:36:21AM -0400, Jeff Portwine wrote: amanda dgram udp wait backup /usr/local/libexec/amandad amandad Or was it nowait, and you changed it to wait (or fixed the username backup), but forgot to sig-HUP the inetd process after you fixed it? No, I added the inetd entry as listed above and then actually rebooted the machine to make sure inetd restarted properly. What happens when you execute the command /usr/local/libexec/amandad as user backup manually? $ /usr/local/libexec/amandad /usr/local/libexec/amandad: error in loading shared libraries: libamclient-2.5.0p2.so: cannot open shared object file: No such file or directory However, that library does exist... $ ls -l /usr/local/lib/libam* -rwxr-xr-x1 root root 361796 Aug 11 08:07 From a few things I'm guessing that both client and server are running on linux systems. Out of curiosity, which distros still use inetd rather than xinetd? The debian camp and its offspring ubuntu, hasn't made the switch yet that I'm aware of. I just installed kubuntu-6.06 on my milling machines box so I could stay reasonably well synched with the emc2 cvs, and was amazed that the default install was still using inetd, or at least the whole /etc/xinetd.d thing seemed to be missing. I installed it, but the basic install contains only: [EMAIL PROTECTED]:~$ ls /etc/xinetd.d chargen daytime echo time So its not as if the system would die if I did an rm -fR /etc/xinetd.d. The added advantages of xinetd over inetd would seeem to make it imperitive to switch, but then we all know the debian camp moves at glacial speed for the core stuff. Maybe thats an unfair remark Jon, I just did a cat of /etc/inetd.conf and found it only contains: #off# netbios-ssn stream tcp nowait root/usr/sbin/tcpd /usr/sbin/smbd so what the heck *are* they doing to control daemon launching? Me wanders off, scratching head in wonderment. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: amanda client inetd problem
Gene Heskett wrote: The debian camp and its offspring ubuntu, hasn't made the switch yet that I'm aware of. I just installed kubuntu-6.06 on my milling machines box so I could stay reasonably well synched with the emc2 cvs, and was amazed that the default install was still using inetd, or at least the whole /etc/xinetd.d thing seemed to be missing. I installed it, but the basic install contains only: [EMAIL PROTECTED]:~$ ls /etc/xinetd.d chargen daytime echo time So its not as if the system would die if I did an rm -fR /etc/xinetd.d. The added advantages of xinetd over inetd would seeem to make it imperitive to switch, but then we all know the debian camp moves at glacial speed for the core stuff. Maybe thats an unfair remark Jon, I just did a cat of /etc/inetd.conf and found it only contains: #off# netbios-ssn stream tcp nowait root/usr/sbin/tcpd /usr/sbin/smbd so what the heck *are* they doing to control daemon launching? Me wanders off, scratching head in wonderment. They add init scripts and run them as daemons, naturally. There is considerable delay in starting a program of any size, so leaving it running gives better response time. Back in the old days, there were memory constraints so many services were only started when needed via inetd, trading off response time for memory space. Any service called with any frequency should be run as a daemon. Amanda is one of those one-offs in that it usually only gets invoked once a day. Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
