Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
Hi, > I had no idea that this way of composing a new thread, by moving the cc: = > address > amanda-users@amanda.org to the to: address amanda-users@amanda.org would = > constitute=20 > "hijacking." It is mistaken wrong to suggest that this was in any way = > intentional. This is not bad "per se", I do that all the time because I cannot remember the exact syntax of the list name. But along with changing the To: and Cc: and putting in a new Subject: you should also make sure to clean-up the References: header that is used to link one reply to the originating message. Best regards, Olivier
Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
Jon LaBadie wrote: On Thu, Mar 30, 2006 at 01:01:29PM -0800, Kevin Till wrote: Lengyel, Florian wrote: An amanda client that used to work on a debian host, before an apt-get update and an apt-get upgrade, and an installation of opennms (which installed the silly daemon identd for postgres) now gives me timeouts when I try Hi, What version of Amanda are you using? ssh support was added to Amanda 2.5.0. ?ssh support? is it optional/default/??? What parts might use it? optional which is part of the implementation to use the Security API. Default is "auth bsd". amdump will use it. I wonder why Florian would be hitting it (i.e. even using any aspect of ssh) by simply upgrading an existing amanda installation? please see other posts on this thread. -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
On Thu, Mar 30, 2006 at 01:01:29PM -0800, Kevin Till wrote: > Lengyel, Florian wrote: > >An amanda client that used to work on a debian host, before > >an apt-get update and an apt-get upgrade, and an installation > >of opennms (which installed the silly daemon identd for postgres) > >now gives me timeouts when I try > > Hi, > > What version of Amanda are you using? ssh support was added to Amanda 2.5.0. > ?ssh support? is it optional/default/??? What parts might use it? I wonder why Florian would be hitting it (i.e. even using any aspect of ssh) by simply upgrading an existing amanda installation? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
I had no idea that this way of composing a new thread, by moving the cc: address amanda-users@amanda.org to the to: address amanda-users@amanda.org would constitute "hijacking." It is mistaken wrong to suggest that this was in any way intentional. Nevertheless, my apologies. -Original Message- From: [EMAIL PROTECTED] on behalf of Mike Delaney Sent: Thu 3/30/2006 3:53 PM To: amanda-users@amanda.org Subject: Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved! On Thu, Mar 30, 2006 at 03:34:02PM -0500, Lengyel, Florian wrote: > I have no idea what this means. I started a new thread in good faith. You did not start a new thread. You replied to an unrelated message and simply changed the Subject: header, thereby hijacking the thread. Starting a new thread involves composing a brand new message, not replying to an existing message. <>
Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
--On March 30, 2006 1:01:29 PM -0800 Kevin Till <[EMAIL PROTECTED]> wrote: the "Did not receive identification string from:::10.10.32.247" should not have anything to do with Amanda. Seems to me someone try to login as amanda to that machine. It doesn't. This actually happens when someone or something opens the SSH port and never does anything and closes it. Monitoring apps do this a lot looking for the SSH banner. 'amanda' in the SSH lines is your host's name. The START lines indicate xinetd is starting amandad, so you should look in /tmp/amanda/amandad*.debug and /tmp/amanda/amcheck*.debug. They're date+time stamped files. Couple things to check, is amandad started correctly on the client? 1) /etc/init.d/xinetd restart and see if there is any error on /var/log/messages. 2) any error in /tmp/amanda/amcheck*.debug? Thanks! --Kevin Till Zmanda amcheck -m Daily /var/log/secure gives me this: [EMAIL PROTECTED] log]# tail secure Mar 30 13:15:03 amanda sshd[19449]: Did not receive identification string from:::10.10.32.247 Mar 30 13:20:03 amanda sshd[19495]: Did not receive identification string from:::10.10.32.247 Mar 30 13:25:03 amanda sshd[19538]: Did not receive identification string from:::10.10.32.247 Mar 30 13:30:04 amanda sshd[19584]: Did not receive identification string from:::10.10.32.247 Mar 30 13:32:24 amanda xinetd[2244]: START: amanda pid=19702 from=10.10.32.250 Mar 30 13:32:24 amanda xinetd[2244]: START: amanda pid=19705 from=10.10.32.250 Mar 30 13:35:04 amanda sshd[20042]: Did not receive identification string from:::10.10.32.247 Mar 30 13:40:05 amanda sshd[20088]: Did not receive identification string from:::10.10.32.247 Mar 30 13:45:05 amanda sshd[20131]: Did not receive identification string from:::10.10.32.247 [EMAIL PROTECTED] log]# -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com -- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler
Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
Lengyel, Florian wrote: An amanda client that used to work on a debian host, before an apt-get update and an apt-get upgrade, and an installation of opennms (which installed the silly daemon identd for postgres) now gives me timeouts when I try Hi, What version of Amanda are you using? ssh support was added to Amanda 2.5.0. the "Did not receive identification string from:::10.10.32.247" should not have anything to do with Amanda. Seems to me someone try to login as amanda to that machine. Couple things to check, is amandad started correctly on the client? 1) /etc/init.d/xinetd restart and see if there is any error on /var/log/messages. 2) any error in /tmp/amanda/amcheck*.debug? Thanks! --Kevin Till Zmanda amcheck -m Daily /var/log/secure gives me this: [EMAIL PROTECTED] log]# tail secure Mar 30 13:15:03 amanda sshd[19449]: Did not receive identification string from:::10.10.32.247 Mar 30 13:20:03 amanda sshd[19495]: Did not receive identification string from:::10.10.32.247 Mar 30 13:25:03 amanda sshd[19538]: Did not receive identification string from:::10.10.32.247 Mar 30 13:30:04 amanda sshd[19584]: Did not receive identification string from:::10.10.32.247 Mar 30 13:32:24 amanda xinetd[2244]: START: amanda pid=19702 from=10.10.32.250 Mar 30 13:32:24 amanda xinetd[2244]: START: amanda pid=19705 from=10.10.32.250 Mar 30 13:35:04 amanda sshd[20042]: Did not receive identification string from:::10.10.32.247 Mar 30 13:40:05 amanda sshd[20088]: Did not receive identification string from:::10.10.32.247 Mar 30 13:45:05 amanda sshd[20131]: Did not receive identification string from:::10.10.32.247 [EMAIL PROTECTED] log]# -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
On Thu, Mar 30, 2006 at 03:34:02PM -0500, Lengyel, Florian wrote: > I have no idea what this means. I started a new thread in good faith. You did not start a new thread. You replied to an unrelated message and simply changed the Subject: header, thereby hijacking the thread. Starting a new thread involves composing a brand new message, not replying to an existing message.
RE: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
Title: RE: Attempt to contact amanda gives sshd error -- dont know why sshd is involved! I have no idea what this means. I started a new thread in good faith. -Original Message- From: [EMAIL PROTECTED] on behalf of Stefan G. Weichinger Sent: Thu 3/30/2006 2:12 PM To: amanda-users@amanda.org Subject: Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved! Lengyel, Florian schrieb: > An amanda client that used ... Please don't hijack threads ... Thank you, Stefan.
Re: Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
Lengyel, Florian schrieb: > An amanda client that used ... Please don't hijack threads ... Thank you, Stefan.
Attempt to contact amanda gives sshd error -- dont know why sshd is involved!
Title: Attempt to contact amanda gives sshd error -- dont know why sshd is involved! An amanda client that used to work on a debian host, before an apt-get update and an apt-get upgrade, and an installation of opennms (which installed the silly daemon identd for postgres) now gives me timeouts when I try amcheck -m Daily /var/log/secure gives me this: [EMAIL PROTECTED] log]# tail secure Mar 30 13:15:03 amanda sshd[19449]: Did not receive identification string from:::10.10.32.247 Mar 30 13:20:03 amanda sshd[19495]: Did not receive identification string from:::10.10.32.247 Mar 30 13:25:03 amanda sshd[19538]: Did not receive identification string from:::10.10.32.247 Mar 30 13:30:04 amanda sshd[19584]: Did not receive identification string from:::10.10.32.247 Mar 30 13:32:24 amanda xinetd[2244]: START: amanda pid=19702 from=10.10.32.250 Mar 30 13:32:24 amanda xinetd[2244]: START: amanda pid=19705 from=10.10.32.250 Mar 30 13:35:04 amanda sshd[20042]: Did not receive identification string from:::10.10.32.247 Mar 30 13:40:05 amanda sshd[20088]: Did not receive identification string from:::10.10.32.247 Mar 30 13:45:05 amanda sshd[20131]: Did not receive identification string from:::10.10.32.247 [EMAIL PROTECTED] log]#
