Re: SSHD errors: will not forward X11 connections
On Tue, 2006-06-27 at 09:32 +0200, [EMAIL PROTECTED] wrote: El día Monday, June 26, 2006 a las 09:47:45PM -0500, Andrew escribió: ... 30098: mprotect(0x28271000,786432,(0x5)PROT_READ|PROT_EXEC) = 0 (0x0) 30098: mmap(0x0,808,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,-1,0x0) = 674590720 (0x28357000) 30098: munmap(0x28357000,0x328) = 0 (0x0) 30098: sigprocmask(0x1,0x2808d820,0xbfbfeaf0)= 0 (0x0) 30098: sigprocmask(0x3,0x2808d830,0x0) = 0 (0x0) 30098: readlink(/etc/malloc.conf,0xbfbfdc60,63) ERR#2 'No such file or directory' 30098: issetugid() = 0 (0x0) 30098: mmap(0x0,4096,(0x3)PROT_READ|PROT_WRITE,(0x1002)MAP_ANON|MAP_PRIVATE,-1,0x0) = 674590720 (0x28357000) 30098: break(0x8075000) = 0 (0x0) 30098: break(0x8076000) = 0 (0x0) 30098: geteuid() = 0 (0x0) the truss output looks somewhat not complete; there is nothing to be seen about entering a user shell... matthias Yes, I see that. But it is complete; I passed the '-o' flag to truss to write _all_ output to a file. Just to be sure, I ran it again, and diff'ed the output files; they are the same. To be clear, I do get a shell prompt when I login via SSH. I'm thinking that trying to this out is going to turn into a large waste of time... -Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD errors: will not forward X11 connections
On Tue, Jun 27, 2006, Andrew wrote: ... Yes, I see that. But it is complete; I passed the '-o' flag to truss to write _all_ output to a file. Just to be sure, I ran it again, and diff'ed the output files; they are the same. To be clear, I do get a shell prompt when I login via SSH. I'm thinking that trying to this out is going to turn into a large waste of time... I haven't been following this thread, but from the Subject I would guess that there's may be problems with the client machine's ssh_config file, the target machines sshd_config file, or the command being executed. To enable X11 forwarding on the client side on recent versions of openssh, either the ``ssh -Y'' command or the ssh_config options ``ForwardX11'' and ``ForwardX11Trusted'' must be set to ``yes''. On the server side, the sshd_config file must have ``X11Forwarding'' set to ``yes'' to allow any client X11 forwarding. On older versions of openssh, the ``-X'' option was sufficient, but now ``-Y'' is necessary (although ``-X'' might work if ``X11Forwarding'' is ``yes'' in the ssh_config file). Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 The Constitution is a written instrument. As such, its meaning does not alter. That which it meant when it was adopted, it means now. -- SOUTH CAROLINA v. US, 199 U.S. 437, 448 (1905) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD errors: will not forward X11 connections
El día Tuesday, June 27, 2006 a las 04:05:52PM -0500, Andrew escribió: Yes, I see that. But it is complete; I passed the '-o' flag to truss to write _all_ output to a file. Just to be sure, I ran it again, and diff'ed the output files; they are the same. To be clear, I do get a shell prompt when I login via SSH. Try it with strace, does this produce more? matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclcpica.org/ http://guru.UnixLand.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD errors: will not forward X11 connections
On Mon, 2006-06-26 at 07:44 +0200, [EMAIL PROTECTED] wrote:
El día Sunday, June 25, 2006 a las 10:05:03PM -0500, Andrew escribió:
Hello,
I have a FreeBSD 6.1 machine at home that I use for remote backups, and
sort of an application server for my home network. I occasionally run
program with the X display forwarded to my laptop. Simple setup, has
always worked great, etc, etc.
Just last week, I went to login and run a program and I received the
following error (in /var/log/messages):
sshd[25306]: error: Failed to allocate internet-domain X11 display
socket.
Now, not to (intentionally) irritate anyone, but I haven't made any
changes in regards to the setup on either end of the connection that I'm
aware of. The only change at all that I've recently made, is that I
switch shells on the remote box (to zsh). I tried changing back to bash,
(my original setup), and the problem persists.
The permissions for sshd are:
-r-xr-xr-x 1 root wheel 168488 May 6 22:58 /usr/sbin/sshd
which looks correct to me. I really haven't a clue where to begin with
this one, besides a backup and re-install, which is an option, but is
also a rather large pain.
Suggestions?
Truss o strace down the SSH daemon to see what the underlying problem
for error: Failed to allocate... really is.
matthias
Hello,
I've restarted SSHD with LogLevel DEBUG, which did not produce any new
information; just gives the same error message (in /var/log/messages) as
before. I'm not sure how interested you are in this particular problem,
but I've attached the output from truss. The complete session that I
recorded using truss is as follows:
1. start truss on SSH server truss -f -p $PID - sshd-log.txt
2. login via SSH ssh -X $hostname
3. attempt to start an X application rhythmbox
4. logout
If you need any more info, or have other suggestions, please let me
know.
Thanks for your help!
-Andrew
3: (null)() = 1 (0x1)
3: accept(0x4,{ AF_INET 192.168.0.6:51251 },0xbfbfdda8) = 5 (0x5)
3: fcntl(5,F_GETFL,0x0) = 6 (0x6)
3: gettimeofday({1151375994 309421},0x0) = 0 (0x0)
3: getpid() = 3 (0x7530)
3: socket(0x1,0x2,0x0) = 6 (0x6)
3: fcntl(6,F_SETFD,0x1) = 0 (0x0)
3: connect(0x6,{ AF_UNIX /var/run/logpriv },106) = 0 (0x0)
3: sendto(0x6,0xbfbfcc60,0,0x0,NULL,0x0) = 65 (0x41)
3: close(6) = 0 (0x0)
3: fcntl(5,F_SETFL,0x2) = 0 (0x0)
3: pipe()= 6 (0x6)
3: socketpair(0x1,0x1,0x0,0xbfbfddb0)= 0 (0x0)
3: fork()= 30098 (0x7592)
30098: close(6) = 0 (0x0)
30098: close(3) = 0 (0x0)
30098: close(4) = 0 (0x0)
30098: close(-1) ERR#9 'Bad file descriptor'
30098: close(8) = 0 (0x0)
30098: getpid() = 30098 (0x7592)
30098: __sysctl(0xbfbfdd00,0x4,0x0,0x0,0x807c800,0x11) = 0 (0x0)
30098: __sysctl(0xbfbfdc28,0x2,0xbfbfdc30,0xbfbfdc24,0x28328509,0xf) = 0 (0x0)
30098: __sysctl(0xbfbfdc30,0x2,0xbfbfdcf8,0xbfbfdcfc,0x0,0x0) = 0 (0x0)
30098: setsid() = 30098 (0x7592)
30098: gettimeofday({1151375994 356856},0x0) = 0 (0x0)
30098: getpid() = 30098 (0x7592)
30098: socket(0x1,0x2,0x0) = 3 (0x3)
30098: fcntl(3,F_SETFD,0x1) = 0 (0x0)
30098: connect(0x3,{ AF_UNIX /var/run/logpriv },106) = 0 (0x0)
30098: sendto(0x3,0xbfbfcc80,0,0x0,NULL,0x0) = 87 (0x57)
30098: close(3) = 0 (0x0)
30098: dup2(0x5,0x0) = 0 (0x0)
30098: dup2(0x0,0x1) = 1 (0x1)
30098: dup2(0x7,0x4) = 4 (0x4)
30098: dup2(0x9,0x5) = 5 (0x5)
30098: close(9) = 0 (0x0)
30098: close(7) = 0 (0x0)
30098: execve(/usr/sbin/sshd,missing argument,missing argument)
30098: mmap(0x0,3608,(0x3)PROT_READ|PROT_WRITE,(0x1000)MAP_ANON,-1,0x0) =
671686656 (0x28092000)
30098: munmap(0x28092000,0xe18) = 0 (0x0)
30098: __sysctl(0xbfbfeaa8,0x2,0x2808e998,0xbfbfeaa4,0x0,0x0) = 0 (0x0)
30098:
mmap(0x0,32768,(0x3)PROT_READ|PROT_WRITE,(0x1002)MAP_ANON|MAP_PRIVATE,-1,0x0) =
671686656 (0x28092000)
30098: issetugid() = 0 (0x0)
30098: open(/etc/libmap.conf,0x0,0666) ERR#2 'No such file or
directory'
30098: open(/var/run/ld-elf.so.hints,0x0,00) = 3 (0x3)
30098: read(0x3,0xbfbfea70,0x80) = 128 (0x80)
30098: lseek(3,0x80,SEEK_SET)
SSHD errors: will not forward X11 connections
Hello, I have a FreeBSD 6.1 machine at home that I use for remote backups, and sort of an application server for my home network. I occasionally run program with the X display forwarded to my laptop. Simple setup, has always worked great, etc, etc. Just last week, I went to login and run a program and I received the following error (in /var/log/messages): sshd[25306]: error: Failed to allocate internet-domain X11 display socket. Now, not to (intentionally) irritate anyone, but I haven't made any changes in regards to the setup on either end of the connection that I'm aware of. The only change at all that I've recently made, is that I switch shells on the remote box (to zsh). I tried changing back to bash, (my original setup), and the problem persists. The permissions for sshd are: -r-xr-xr-x 1 root wheel 168488 May 6 22:58 /usr/sbin/sshd which looks correct to me. I really haven't a clue where to begin with this one, besides a backup and re-install, which is an option, but is also a rather large pain. Suggestions? -Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SSHD errors: will not forward X11 connections
El día Sunday, June 25, 2006 a las 10:05:03PM -0500, Andrew escribió: Hello, I have a FreeBSD 6.1 machine at home that I use for remote backups, and sort of an application server for my home network. I occasionally run program with the X display forwarded to my laptop. Simple setup, has always worked great, etc, etc. Just last week, I went to login and run a program and I received the following error (in /var/log/messages): sshd[25306]: error: Failed to allocate internet-domain X11 display socket. Now, not to (intentionally) irritate anyone, but I haven't made any changes in regards to the setup on either end of the connection that I'm aware of. The only change at all that I've recently made, is that I switch shells on the remote box (to zsh). I tried changing back to bash, (my original setup), and the problem persists. The permissions for sshd are: -r-xr-xr-x 1 root wheel 168488 May 6 22:58 /usr/sbin/sshd which looks correct to me. I really haven't a clue where to begin with this one, besides a backup and re-install, which is an option, but is also a rather large pain. Suggestions? Truss o strace down the SSH daemon to see what the underlying problem for error: Failed to allocate... really is. matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclcpica.org/ http://guru.UnixLand.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
