On 5/6/07, Andy Rabagliati <[EMAIL PROTECTED]> wrote: > On Sat, 05 May 2007, Benjamin Staffin wrote: > > I'm running into what appears to be the exact same problem as Samrat. > > See comments inline below... > > > > >> >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 . / > > > > 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? > > Nothing in that ssh line above *needs* X. > > If you ssh by hand from the backuppc server to the client, and say > 'echo $DISPLAY' what do you get ?
Oh you're going to love this. I thought I had already done exactly that and had simply forgotten to mention it in my original message, but I just went and verified. It turns out that my backuppc user didn't have the target client machine's ssh key fingerprint in its known_hosts file, because in my testing I had been sshing to it using a different name. I still don't understand why anything decided that $DISPLAY should be :0.0 (it doesn't get set when I ssh by hand, btw), but my guess is that ssh was trying to use ssh-askpass to pop up a "Trust this key fingerprint?" dialog. To prevent this, I seem to recall that openssh has a BatchMode flag that can be set (-o BatchMode yes) to prevent it from ever asking questions, and failing with an error message if requires manual input. (If only I had remembered to add the key fingerprint to known_hosts this never would have come up, of course) - 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/
