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:27client inetd[435]:
/usr/local/libexec/amandad (pid 2479): exit status 127Aug 11 08:32:27
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
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
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
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
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
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
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
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
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
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
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.
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
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
14 matches
Mail list logo
