Re: selfcheck request timed out WAS Re: Running amanda client only
Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? On Wed, 13 Sep 2006 [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Toomas Aas wrote: [EMAIL PROTECTED] wrote: The server is reporting that client down, so I checked and noticed that the FBSD port for the amanda-client did not install amindexd or amidxtaped, although it did install amandad. Are all 3 needed for a client? No, for client only amandad is needed. Then I cannot figure out why I'm getting selfcheck request timed out from that client. The path in inetd.conf is correct, as is the user (amanda) and /tmp/amanda is owned by amanda and has debug files there (just config info). .amandaclients has localhost.fqdn as well as hostname.fqdn. That client IS running alot of IP addresses on it, but I've done that before with no trouble. Here is amcheck -c output: su-2.05b$ amcheck -c weekly Amanda Backup Client Hosts Check ERROR: old.amanda.client: [host someIP.comcastbiz.net: hostname lookup failed] WARNING: new.amanda.client: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.153 seconds, 2 problems found I understand the first error from the old client...there is no forward DNS on that IP (BTW, is there a way around that? Just have it look at IP address?). I can't figure out the cause of the second one...I went through everything on the FAQ-O-Matic about it... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: selfcheck request timed out WAS Re: Running amanda client only
[EMAIL PROTECTED] wrote: Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Frank On Wed, 13 Sep 2006 [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Toomas Aas wrote: [EMAIL PROTECTED] wrote: The server is reporting that client down, so I checked and noticed that the FBSD port for the amanda-client did not install amindexd or amidxtaped, although it did install amandad. Are all 3 needed for a client? No, for client only amandad is needed. Then I cannot figure out why I'm getting selfcheck request timed out from that client. The path in inetd.conf is correct, as is the user (amanda) and /tmp/amanda is owned by amanda and has debug files there (just config info). .amandaclients has localhost.fqdn as well as hostname.fqdn. That client IS running alot of IP addresses on it, but I've done that before with no trouble. Here is amcheck -c output: su-2.05b$ amcheck -c weekly Amanda Backup Client Hosts Check ERROR: old.amanda.client: [host someIP.comcastbiz.net: hostname lookup failed] WARNING: new.amanda.client: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.153 seconds, 2 problems found I understand the first error from the old client...there is no forward DNS on that IP (BTW, is there a way around that? Just have it look at IP address?). I can't figure out the cause of the second one...I went through everything on the FAQ-O-Matic about it... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: selfcheck request timed out WAS Re: Running amanda client only
On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Thanks for your reply. I did run it from the command line and it eventually times out, although it does not exit immediately if I type something. debug files are created in /tmp/amanda, but not with any useful info...just how it was compiled. There is absolutely nothing in /var/log/messages about amanda(d). I thought ldconfig was run upon boot...in any case, if I'm missing some kind of lib, wouldn't amanda complain about it when trying to build it? Thanks again for any help... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: selfcheck request timed out WAS Re: Running amanda client only
[EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Thanks for your reply. I did run it from the command line and it eventually times out, although it does not exit immediately if I type something. 2.4.5 will exit if you hit enter, 2.5 doesn't. debug files are created in /tmp/amanda, but not with any useful info...just how it was compiled. There is absolutely nothing in /var/log/messages about amanda(d). Inetd doesn't normally log unless you start it with a debug option. In your case, since a debug file is created then inetd is working so you may not need to check further on that. Post the debug file on the client and maybe we can see at what stage of the connection it stops. Are you running a firewall on or between the client? I thought ldconfig was run upon boot...in any case, if I'm missing some kind of lib, wouldn't amanda complain about it when trying to build it? The ldconfig suggestion is only relevant if running amandad from the command line returns a missing library error, sorry I wasn't clear about that. And yes it would complain on build, I was thinking more of cases where amanda lives on a shared filesystem or are copied to multiple machines. Frank Thanks again for any help... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: selfcheck request timed out WAS Re: Running amanda client only
On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Thanks for your reply. I did run it from the command line and it eventually times out, although it does not exit immediately if I type something. 2.4.5 will exit if you hit enter, 2.5 doesn't. The client is 2.5.0p2, the server is 2.4.5. Could that be an issue? If so, which one do you recommend? debug files are created in /tmp/amanda, but not with any useful info...just how it was compiled. There is absolutely nothing in /var/log/messages about amanda(d). Inetd doesn't normally log unless you start it with a debug option. In your case, since a debug file is created then inetd is working so you may not need to check further on that. Post the debug file on the client and maybe we can see at what stage of the connection it stops. Are you running a firewall on or between the client? No firewall that I've configured...I did just hook up via comcast business though...nmap from the client back to the server looks ok...I can ssh back, as well. the debug files had what looked like nothing but a config.log, until I just looked now and noticed this huge (48MB) debug file with 670 thousand lines of this: amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Running amanda client only
Hi: I've been using amanda for years, but I just reconfigured and updated some servers using the latest everything and updated the disklists for the newer format (integer/spindle). From FreeBSD ports, I just installed amanda-2.4.5 on the amanda server and amanda-2.5.0p2 on the client (the ports defaulted to those). The server is reporting that client down, so I checked and noticed that the FBSD port for the amanda-client did not install amindexd or amidxtaped, although it did install amandad. Are all 3 needed for a client? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
