- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Failed to allocate internet-domain X11 display soc...
Operating System - HP-UX
1752591
Members
2853
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2010 05:13 AM
04-27-2010 05:13 AM
Failed to allocate internet-domain X11 display socket.
Hi all! We recently upgraded some of our 11.11 and 11.23 servers' SSH to 5.30.007. For one of them, when we try to connect via "Reflections," we get prompted for a password and then nothing happens. The error in the syslog is:
Apr 27 09:07:01 testbox sshd[1951]: error: Failed to allocate internet-domain X11 display socket
Google mentions a bug in Solaris, but nothing for HP. It seems to be working okay on our other HP servers, and oddly enough if I ssh from another server I get right in. Thanks!!!
Apr 27 09:07:01 testbox sshd[1951]: error: Failed to allocate internet-domain X11 display socket
Google mentions a bug in Solaris, but nothing for HP. It seems to be working okay on our other HP servers, and oddly enough if I ssh from another server I get right in. Thanks!!!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2010 05:34 AM
04-27-2010 05:34 AM
Re: Failed to allocate internet-domain X11 display socket.
"Reflections"? You mean "Reflection X", a Windows application that allows you to use X11 applications remotely, right?
When using SSH with X11 forwarding (like Reflection X would probably do), sshd attempts to allocate a TCP port in the 6010+ range. The first SSH user that requests SSH forwarding gets port TCP/6010 (DISPLAY=localhost:10.0), if that port is occupied, TCP/6011 is used instead, etc.
Apparently something prevents sshd from allocating such a port in your case. Are the ports 6010... occupied by something else?
(If you have lsof installed, run "lsof -i tcp:6010" to see if port 6010 is in use. If you don't have it, use "netstat -af inet" and look for port numbers 6010 and above in the "Local Address" column.
If you make a command-line SSH connection from another server (without using the -X option that requests X11 forwarding), the extra TCP port is not required and the connection will succeed.
MK
When using SSH with X11 forwarding (like Reflection X would probably do), sshd attempts to allocate a TCP port in the 6010+ range. The first SSH user that requests SSH forwarding gets port TCP/6010 (DISPLAY=localhost:10.0), if that port is occupied, TCP/6011 is used instead, etc.
Apparently something prevents sshd from allocating such a port in your case. Are the ports 6010... occupied by something else?
(If you have lsof installed, run "lsof -i tcp:6010" to see if port 6010 is in use. If you don't have it, use "netstat -af inet" and look for port numbers 6010 and above in the "Local Address" column.
If you make a command-line SSH connection from another server (without using the -X option that requests X11 forwarding), the extra TCP port is not required and the connection will succeed.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP