From: westoztux <wes...@gm...> - 2014-04-07 01:32:02
|
Hello All I have a 5 servers backing up happily with backuppc which runs debian 6 the other servers that have been running correctly for months are a mix of centos6 and debian 6 all servers run ssh on the same non-standard port and i have public key authentication setup on all servers. i have tried to add another server which is a debian 7 box and I can not get this server to backup it fails when trying to connect with this error on the client sshd[8911]: Connection closed by xxx.xxx.xxx.xxx [preauth] . If I try to manually connect with ssh -l backuppc xxx.xxx.xxx.xxx whoami it logs in and returns the backuppc user which i can see in the auth.log on the client. As on all servers I use backuppc as the user and add them to sudoers to be able to run rsync . I have been able to fix setup issues on the previous boxes by searching mainly these mailing lists but over the last couple weeks I have been unable to find the information I need . Im not sure if I missing something simple or there is something else going on if others can give me some ideas of what I need to check next to try and correct this issue it would be much appreciated. Thanks Regards Darren |
From: Adam G. <mai...@we...> - 2014-04-07 01:43:01
|
On 07/04/14 11:31, westoztux wrote: > Hello All > I have a 5 servers backing up happily with backuppc which runs debian 6 > the other servers that have been running correctly for months are a mix > of centos6 and debian 6 all servers run ssh on the same non-standard > port and i have public key authentication setup on all servers. i have > tried to add another server which is a debian 7 box and I can not get > this server to backup it fails when trying to connect with this error on > the client sshd[8911]: Connection closed by xxx.xxx.xxx.xxx [preauth] . > If I try to manually connect with ssh -l backuppc xxx.xxx.xxx.xxx whoami > it logs in and returns the backuppc user which i can see in the auth.log > on the client. As on all servers I use backuppc as the user and add them > to sudoers to be able to run rsync . I have been able to fix setup > issues on the previous boxes by searching mainly these mailing lists but > over the last couple weeks I have been unable to find the information I > need . Im not sure if I missing something simple or there is something > else going on if others can give me some ideas of what I need to check > next to try and correct this issue it would be much appreciated. Thanks > Make sure you are running the command: ssh -l backuppc xxx.xxx.xxx.xxx whoami FROM the backuppc server AND AS the backuppc user, AND xxx.xxx.xxx.xxx is the exact same hostname that backuppc will use when attempting to run the backup. You should see the command line backuppc runs in the failed logs, you can get the hostname from there. You may simply need to add the host key for backuppc, which you will be able to do from the above. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au |
From: westoztux <wes...@gm...> - 2014-04-07 08:07:47
|
On 07/04/14 09:42, Adam Goryachev wrote: > On 07/04/14 11:31, westoztux wrote: >> Hello All >> I have a 5 servers backing up happily with backuppc which runs debian 6 >> the other servers that have been running correctly for months are a mix >> of centos6 and debian 6 all servers run ssh on the same non-standard >> port and i have public key authentication setup on all servers. i have >> tried to add another server which is a debian 7 box and I can not get >> this server to backup it fails when trying to connect with this error on >> the client sshd[8911]: Connection closed by xxx.xxx.xxx.xxx [preauth] . >> If I try to manually connect with ssh -l backuppc xxx.xxx.xxx.xxx whoami >> it logs in and returns the backuppc user which i can see in the auth.log >> on the client. As on all servers I use backuppc as the user and add them >> to sudoers to be able to run rsync . I have been able to fix setup >> issues on the previous boxes by searching mainly these mailing lists but >> over the last couple weeks I have been unable to find the information I >> need . Im not sure if I missing something simple or there is something >> else going on if others can give me some ideas of what I need to check >> next to try and correct this issue it would be much appreciated. Thanks >> > Make sure you are running the command: > > ssh -l backuppc xxx.xxx.xxx.xxx whoami > > FROM the backuppc server AND AS the backuppc user, AND xxx.xxx.xxx.xxx > is the exact same hostname that backuppc will use when attempting to run > the backup. You should see the command line backuppc runs in the failed > logs, you can get the hostname from there. > > You may simply need to add the host key for backuppc, which you will be > able to do from the above. > > Regards, > Adam > Thanks Adam I can confirm that I can connect from the backuppc server and as the backuppc user to the host using the ip address which is the same address as used in the command that backuppc uses . Regards Darren |
From: Les M. <les...@gm...> - 2014-04-07 12:48:14
|
On Mon, Apr 7, 2014 at 3:07 AM, westoztux <wes...@gm...> wrote: > > I can confirm that I can connect from the backuppc server and as the > backuppc user to the host using the ip address which is the same address > as used in the command that backuppc uses . Does the target host output anything (like a message of the day greeting) before running the command you sent? The rsync implementation in backuppc can't handle extraneous data, although stock rsync can ignore it. -- Les Mikesell les...@gm... |
From: westoztux <wes...@gm...> - 2014-04-07 13:50:49
|
On 07/04/14 20:48, Les Mikesell wrote: > On Mon, Apr 7, 2014 at 3:07 AM, westoztux <wes...@gm...> wrote: >> I can confirm that I can connect from the backuppc server and as the >> backuppc user to the host using the ip address which is the same address >> as used in the command that backuppc uses . > > Does the target host output anything (like a message of the day > greeting) before running the command you sent? The rsync > implementation in backuppc can't handle extraneous data, although > stock rsync can ignore it. > Thanks Les When i log in via ssh directly to the client machine i see no motd. Do i need to check this another way ? If i run the backup command that backuppc uses from the server I get a strange character appear on the ssh terminal of the backuppc server , on the client in auth.log i see the server connect successfully and then run the command sudo: backuppc : TTY=unknown ; PWD=/home/backuppc ; USER=root ; COMMAND=/usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive -vv --ignore-times . /home/ . I have checked my other servers that are working and they return this same character if i run the command manually. Thanks Regards Darren |
From: Les M. <les...@gm...> - 2014-04-07 14:39:19
|
On Mon, Apr 7, 2014 at 8:50 AM, westoztux <wes...@gm...> wrote: >> >> Does the target host output anything (like a message of the day >> greeting) before running the command you sent? The rsync >> implementation in backuppc can't handle extraneous data, although >> stock rsync can ignore it. >> > Thanks Les > When i log in via ssh directly to the client machine i see no motd. Do i > need to check this another way ? If i run the backup command that > backuppc uses from the server I get a strange character appear on the > ssh terminal of the backuppc server , on the client in auth.log i see > the server connect successfully and then run the command sudo: > backuppc : TTY=unknown ; PWD=/home/backuppc ; USER=root ; > COMMAND=/usr/bin/rsync --server --sender --numeric-ids --perms --owner > --group -D --links --hard-links --times --block-size=2048 --recursive > -vv --ignore-times . /home/ . I have checked my other servers that are > working and they return this same character if i run the command > manually. Thanks If you don't see any output, then it sounds more like a problem with sudo starting rsync. Can you tell from the logs if the execution is sucessful? -- Les Mikesell les...@gm... |
From: westoztux <wes...@gm...> - 2014-04-07 15:33:35
|
On 07/04/14 22:39, Les Mikesell wrote: > On Mon, Apr 7, 2014 at 8:50 AM, westoztux <wes...@gm...> wrote: >>> Does the target host output anything (like a message of the day >>> greeting) before running the command you sent? The rsync >>> implementation in backuppc can't handle extraneous data, although >>> stock rsync can ignore it. >>> >> Thanks Les >> When i log in via ssh directly to the client machine i see no motd. Do i >> need to check this another way ? If i run the backup command that >> backuppc uses from the server I get a strange character appear on the >> ssh terminal of the backuppc server , on the client in auth.log i see >> the server connect successfully and then run the command sudo: >> backuppc : TTY=unknown ; PWD=/home/backuppc ; USER=root ; >> COMMAND=/usr/bin/rsync --server --sender --numeric-ids --perms --owner >> --group -D --links --hard-links --times --block-size=2048 --recursive >> -vv --ignore-times . /home/ . I have checked my other servers that are >> working and they return this same character if i run the command >> manually. Thanks > If you don't see any output, then it sounds more like a problem with > sudo starting rsync. Can you tell from the logs if the execution is > sucessful? > I dont think the process gets that far , when I start the backup from the backuppc gui i dont see a successful login in the auth.log I only see this sshd[30557]: Connection closed by xxx.xxx.xxx.xxx [preauth] |
From: Adam G. <mai...@we...> - 2014-04-07 15:56:26
|
What does backuppc record in the logs? What happens if you login as the backuppc user, and run the exact same command as seen in the logs? There is some difference between what you are doing to test what backuppc does, or else you are accidentally covering up the difference. You will need to find the difference, and fix it. We can't do that without the complete information, only guess at what you might have done differently. PS, you can also try running the ssh command like this: ssh hostname id | od -xa This will help verify you are not getting any extra characters. In your case, that would be: ssh hostname sudo id | od -xa PS, my guess is it is either a problem with the keys, hostname, etc, or else a problem with sudo. Try to configure backuppc to backup /bin or something as the unprivileged user (without sudo). Once that works, then complicate things with sudo. Divide (the potential problems) and conquer (the now smaller problems). Regards, Adam On 08/04/14 01:33, westoztux wrote: > On 07/04/14 22:39, Les Mikesell wrote: >> On Mon, Apr 7, 2014 at 8:50 AM, westoztux <wes...@gm...> wrote: >>>> Does the target host output anything (like a message of the day >>>> greeting) before running the command you sent? The rsync >>>> implementation in backuppc can't handle extraneous data, although >>>> stock rsync can ignore it. >>>> >>> Thanks Les >>> When i log in via ssh directly to the client machine i see no motd. Do i >>> need to check this another way ? If i run the backup command that >>> backuppc uses from the server I get a strange character appear on the >>> ssh terminal of the backuppc server , on the client in auth.log i see >>> the server connect successfully and then run the command sudo: >>> backuppc : TTY=unknown ; PWD=/home/backuppc ; USER=root ; >>> COMMAND=/usr/bin/rsync --server --sender --numeric-ids --perms --owner >>> --group -D --links --hard-links --times --block-size=2048 --recursive >>> -vv --ignore-times . /home/ . I have checked my other servers that are >>> working and they return this same character if i run the command >>> manually. Thanks >> If you don't see any output, then it sounds more like a problem with >> sudo starting rsync. Can you tell from the logs if the execution is >> sucessful? >> > I dont think the process gets that far , when I start the backup from > the backuppc gui i dont see a successful login in the auth.log I only > see this sshd[30557]: Connection closed by xxx.xxx.xxx.xxx [preauth] > > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees_APR > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ -- Adam Goryachev Website Managers www.websitemanagers.com.au |
From: westoztux <wes...@gm...> - 2014-04-08 09:38:24
|
On 07/04/14 23:56, Adam Goryachev wrote: > What does backuppc record in the logs? > What happens if you login as the backuppc user, and run the exact same > command as seen in the logs? > > There is some difference between what you are doing to test what > backuppc does, or else you are accidentally covering up the difference. > You will need to find the difference, and fix it. We can't do that > without the complete information, only guess at what you might have done > differently. > > PS, you can also try running the ssh command like this: > ssh hostname id | od -xa > > This will help verify you are not getting any extra characters. In your > case, that would be: > ssh hostname sudo id | od -xa > > PS, my guess is it is either a problem with the keys, hostname, etc, or > else a problem with sudo. Try to configure backuppc to backup /bin or > something as the unprivileged user (without sudo). Once that works, then > complicate things with sudo. Divide (the potential problems) and conquer > (the now smaller problems). > > Regards, > Adam > > On 08/04/14 01:33, westoztux wrote: >> On 07/04/14 22:39, Les Mikesell wrote: >>> On Mon, Apr 7, 2014 at 8:50 AM, westoztux <wes...@gm...> wrote: >>>>> Does the target host output anything (like a message of the day >>>>> greeting) before running the command you sent? The rsync >>>>> implementation in backuppc can't handle extraneous data, although >>>>> stock rsync can ignore it. >>>>> >>>> Thanks Les >>>> When i log in via ssh directly to the client machine i see no motd. Do i >>>> need to check this another way ? If i run the backup command that >>>> backuppc uses from the server I get a strange character appear on the >>>> ssh terminal of the backuppc server , on the client in auth.log i see >>>> the server connect successfully and then run the command sudo: >>>> backuppc : TTY=unknown ; PWD=/home/backuppc ; USER=root ; >>>> COMMAND=/usr/bin/rsync --server --sender --numeric-ids --perms --owner >>>> --group -D --links --hard-links --times --block-size=2048 --recursive >>>> -vv --ignore-times . /home/ . I have checked my other servers that are >>>> working and they return this same character if i run the command >>>> manually. Thanks >>> If you don't see any output, then it sounds more like a problem with >>> sudo starting rsync. Can you tell from the logs if the execution is >>> sucessful? >>> >> I dont think the process gets that far , when I start the backup from >> the backuppc gui i dont see a successful login in the auth.log I only >> see this sshd[30557]: Connection closed by xxx.xxx.xxx.xxx [preauth] >> >> >> >> ------------------------------------------------------------------------------ >> Put Bad Developers to Shame >> Dominate Development with Jenkins Continuous Integration >> Continuously Automate Build, Test & Deployment >> Start a new project now. Try Jenkins in the cloud. >> http://p.sf.net/sfu/13600_Cloudbees_APR >> _______________________________________________ >> BackupPC-users mailing list >> Bac...@li... >> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >> Wiki: http://backuppc.wiki.sourceforge.net >> Project: http://backuppc.sourceforge.net/ > Thanks Les and Adam for your help i will continue to look myself to find out the difference between my other servers and this server and what is causing the problem. Regards Darren |
From: Les M. <les...@gm...> - 2014-04-07 16:23:50
|
On Mon, Apr 7, 2014 at 10:33 AM, westoztux <wes...@gm...> wrote: >> on the client in auth.log i see >>> the server connect successfully and then run the command sudo: >>> backuppc : TTY=unknown ; PWD=/home/backuppc ; USER=root ; >>> COMMAND=/usr/bin/rsync --server --sender --numeric-ids --perms --owner >>> --group -D --links --hard-links --times --block-size=2048 --recursive >>> -vv --ignore-times . /home/ . >> If you don't see any output, then it sounds more like a problem with >> sudo starting rsync. Can you tell from the logs if the execution is >> sucessful? > I dont think the process gets that far , when I start the backup from > the backuppc gui i dont see a successful login in the auth.log I only > see this sshd[30557]: Connection closed by xxx.xxx.xxx.xxx [preauth] Oh, I thought your log entry above was from the backuppc run. If it is different manually, then you must not be doing the same thing. -- Les Mikesell les...@gm... |
From: Darren L. <wes...@gm...> - 2014-04-08 06:10:58
|
On Monday, April 7, 2014, Adam Goryachev < mai...@we...> wrote: > On 07/04/14 11:31, westoztux wrote: > > Hello All > > I have a 5 servers backing up happily with backuppc which runs debian 6 > > the other servers that have been running correctly for months are a mix > > of centos6 and debian 6 all servers run ssh on the same non-standard > > port and i have public key authentication setup on all servers. i have > > tried to add another server which is a debian 7 box and I can not get > > this server to backup it fails when trying to connect with this error on > > the client sshd[8911]: Connection closed by xxx.xxx.xxx.xxx [preauth] . > > If I try to manually connect with ssh -l backuppc xxx.xxx.xxx.xxx whoami > > it logs in and returns the backuppc user which i can see in the auth.log > > on the client. As on all servers I use backuppc as the user and add them > > to sudoers to be able to run rsync . I have been able to fix setup > > issues on the previous boxes by searching mainly these mailing lists but > > over the last couple weeks I have been unable to find the information I > > need . Im not sure if I missing something simple or there is something > > else going on if others can give me some ideas of what I need to check > > next to try and correct this issue it would be much appreciated. Thanks > > > > Make sure you are running the command: > > ssh -l backuppc xxx.xxx.xxx.xxx whoami > > FROM the backuppc server AND AS the backuppc user, AND xxx.xxx.xxx.xxx > is the exact same hostname that backuppc will use when attempting to run > the backup. You should see the command line backuppc runs in the failed > logs, you can get the hostname from there. > > You may simply need to add the host key for backuppc, which you will be > able to do from the above. > > Regards, > Adam > > -- > Adam Goryachev Website Managers www.websitemanagers.com.au > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees_APR > _______________________________________________ > BackupPC-users mailing list > Bac...@li... <javascript:;> > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > |