client
inetd[435]: /usr/local/libexec/amandad (pid 2480): exit status 127Aug 11
08:32:27client 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
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
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
Hi from Austria!
I was wondering, if it might be possible to reduce the open ports
induced by amanda to the local IP address (interface lo, 127.0.0.1) in
inetd.conf since I thought using amanda client and server on the same
machine. External nmap port scans of this server should not find any
it!!!
Donald L. (Don) Ritchey
Information Technology
Exelon Corporation
-Original Message-
From: Vlad Popa [mailto:[EMAIL PROTECTED]
Sent: Monday, April 25, 2005 12:42 PM
To: amanda-users@amanda.org
Subject: Is it possible to configure amanda and inetd just for
localhost?
Hi from Austria!
I
only client - the less ports open to the network,
the better.
One obvious way to achieve this is to use your favourite firewall
package. It may be also possible to achieve this with the means of inetd
(amanda services are started from there), but I'm not sure of that.
Surely inetd documentation
On Mon, Apr 25, 2005 at 01:04:06PM -0500, [EMAIL PROTECTED] wrote:
Vlad:
Please review the Amanda archives for discussions of the pitfalls of
using localhost as part of your backup configuration. This is a
subject that has been beaten into submission quite thoroughly.
The short answer
Hi from Austria too!
[EMAIL PROTECTED] wrote:
...
Don't do it!!!
...
Subject: Is it possible to configure amanda and inetd just for
localhost?
Is it a linux box ? Define some iptable rules or similar to
block access from other IP addresses.
Bye, Peter
WOTLmade
Hi there!
I'm new to amanda and have just been trying to install it from source,
unfortunately I don't know what entries need to go into /etc/inetd.conf
on either the server or client machines.
Could somebody let me know what I need to put there on the client and on
the server (which will also
I'm new to amanda and have just been trying to install it from source,
unfortunately I don't know what entries need to go into /etc/inetd.conf
on either the server or client machines.
Have you read docs/INSTALL and http://www.backupcentral.com/amanda.html?
In brief, you need amanda/amandad on
That's an excellent suggestion... read the docs!
Don't I feel like a bean!
Thanx =)
"John R. Jackson" wrote:
I'm new to amanda and have just been trying to install it from source,
unfortunately I don't know what entries need to go into /etc/inetd.conf
on either the server or client
22 matches
Mail list logo
