I'm running into what appears to be the exact same problem as Samrat. See comments inline below...
>Samrat Mitra wrote on 25.04.2007 at 12:11:34 [[BackupPC-users] Fwd: error in >running backuppc]: >> dear sir >> as mention ssh is configured to do X port forwarding >> does i have to check /etc/ssh/sshd_config >> there is a entry for X11Forwarding in sshd_config it was previously marked >> yes >> i changed it to no > >1. sshd_config only determines what the server side will allow. If the > client doesn't request X11Forwarding, the server won't somehow force it > upon the client. >2. In your case, the only sshd_config of interest would reside on the host > you are trying to back up (192.168.7.254, just to be over-clear). >3. Before you now go changing /etc/ssh/ssh_config on the BackupPC server, > you'd want to do that in the user configuration file ~backuppc/.ssh/config, > but, >4. that's not your problem. I've set ForwardX11 no and ForwardX11Trusted no in ~backuppc/.ssh/config, though this is apparently unrelated to what's going on. >> >Contents of file /var/lib/backuppc/pc/192.168.7.254/XferLOG.bad, modified >> >2007-04-24 14:59:09 >> > >> >Running: /usr/bin/ssh -q -x -l root 192.168.7.254 /usr/bin/rsync > ^^ >That should turn off X11 forwarding (not globally, not as default for the >user, but rather on a per-connection basis). That's perfectly fine as it is. > >> >--server --sender --numeric-ids --perms --owner --group --devices >> >--links --times --block-size=2048 --recursive --ignore-times . / >> >Xfer PIDs are now 6573 >> >Got remote protocol 1651076184 >> >Fatal error (bad version): Xlib: connection to ":0.0" refused by server > >That means the message comes from the remote side. It appears the login >process (i.e. probably shell startup) is executing an X11 application with >$DISPLAY incorrectly set to :0.0 (it should be unset, and the startup >scripts shouldn't do it in the first place, really). > >So: >- what is root's login shell on 192.168.7.254 (probably a bash, but you > never know ...)? >- what's in the relevant startup files (~root/.bashrc, ~root/.profile, > /etc/bash.bashrc, /etc/profile if I'm not mistaken). In particular, did > you modify any of them? Double check what you changed and remove the > part that's causing the problem ;-). >- For completeness' sake: which version of what distribution is running > on the client host? I can't speak for Samrat, but in my case the distribution is Debian "Sarge", root's shell is bash, there appears to be nothing of interest on the client system in root's dotfiles or the system profiles (all are untouched from the distribution defaults, in fact). Root does not have a ~/.ssh/config, and nothing related to X is enabled in the system ssh config files. Running ldd on the only binary executed in root's dotfiles (/usr/bin/mesg) tells me it's not linked against X11 (unsurprisingly). Oh, and nothing I can find is setting $DISPLAY. I feel silly for failing to track this down, but I seem to be completely stumped. Does anybody else have thoughts on how to debug this? - Ben ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
