Transport endpoint is not connected is an error message that comes up userspace filesystem framework (also known as FUSE). This is an error specific to the Linux operating system as FUSE is a part of the Linux kernel. libfuse is a userspace library, and fuse mount is a mount utility. Both are part of the kernel module ‘fuse. ko’. There can be many potential reasons for this error message, one of the most common reasons being the crashing of the file system. Another more common reason is a segmentation fault that causes programs to crash. In this article, we will explore some of the possible ways to avoid or resolve this error.
Contents
- 1 What is FUSE?
- 2 SShfs
- 3 Solutions to Transport endpoint is not connected FUSE
- 3.1 Reboot the system
- 3.2 Remounting the File System
- 4 Gluster Transport endpoint is not connected
- 5 Socket.error [errno 107] Transport endpoint is not connected
- 5.1 How to fix Socket.error
- 6 Transport endpoint is not connected colab
- 6.1 Restart the runtime option
- 6.2 Remount the drive
- 7 FAQs on Transport Endpoint is Not Connected
- 7.1 What is UNIX?
- 7.2 What do you mean by segmentation fault?
- 7.3 Is macOS based on UNIX?
- 8 Conclusion
- 9 Trending Now
What is FUSE?
FUSE is short for Filesystem in USErspace. It is a free and open-source software interface that allows the non-privileged user to create their virtual file system on top of the system’s file system. The Fuse interface was initially only available for the UNIX-based operating systems. But now, it can also be used in macOS or Windows. Using fuse, users can create the file system of their choice without any admin privileges and without altering the kernel of the operating system.
SShfs
SShfs stands for Secured Shell file system. It allows the user to access the file system remotely using an encrypted ssh connection. It will enable the users to retrieve data from the directories and files of the remote workstations or servers. But if there’s some error in the FUSE virtual file system of the remote server, then the person sitting at the receiver end can receive a transport endpoint that is not connected error message as the response. Sometimes it could also happen due to a bad sshfs configuration or improper requests etc.
If you’re facing this issue with your sshfs response, then first establish a secured sshfs connection with the remote server, then employ the solutions suggested below to get rid of the ‘Transport endpoint is not connected error message.
Solutions to Transport endpoint is not connected FUSE
The following are the solutions or tricks to work around the Transport endpoint is not connected. Some of these ways are pretty simple and handy, while others are rather complex.
Reboot the system
The simplest way to resolve the ‘Transport endpoint is not connected’ error on a local machine is to reboot your computer. Sometimes due to some arbitrary reasons, memory faults can occur, or an I/O error can be encountered during the loading of programs from storage to main memory, which can result in unexpected behavior, ultimately leading to ‘transport endpoint is not connected. Rebooting the system would empty the main working memory and then load the operating system as a whole again, which could resolve the issue without any hassle.
Remounting the File System
In Linux, the fusermount utility gives you the power to mount or unmount the FUSE file system. This way, you could resolve the ‘transport endpoint is not connected’ without even restarting your computer. All you have to do is unmount your virtual file system for a while and then mount it again. This could resolve the issue without having to restart the computer. Enter the commands shown in the image in the terminal emulator to unmount and mount the virtual fuse file system.
If, for whatever reason, this doesn’t work, try running the following command to unmount the file system.
Gluster oracle’s distributed file system could aggregate data from multiple servers in single accessible userspace. The gluster client software interacts with many servers at the same time to retrieve data from various servers. But sometimes, due to conflicting port usage or firewall issues, the error message ‘Transport endpoint is not connected’ can appear. It can be resolved using the following gluster client commands.
gluster volume heal brick01 enableThis command would start a self-healing daemon process that synced the file system.
Socket.error [errno 107] Transport endpoint is not connected
OSError: [Errno 107] socket error Transport endpoint not connected and [Error 106] Transport endpoint is already connected, are two error that occurs while using the Socket python library. Socket library is used to create networking sockets in the application, and it can create both TCP and UDP sockets. If while creating the Socket, if the port is already is in use or has been initiated by another process, then a socket can not be created, and the Transport endpoint is not connected occurs.
How to fix Socket.error
Try the following ways to resolve the Socket. Error while using the Socket library in python.
- Try using a different port number.
- Update your python version to atleast Python 3.5.
- Update the Socket library using pip install sockets.
- Reboot the system.
Transport endpoint is not connected colab
Google colab is an online product by the Google research team. It allows the users to run their python code in the browsers, while google provides the necessary resources from its servers. This is an excellent tool for data analytics and machine learning modeling. It gives a jupyter notebook-like interface for user interactions. Google servers at the back end of the colab use the FUSE virtual file system for each of its users, which sometimes leads to the Transport endpoint not connecting error messages as a response. Try the following things to avoid this issue on google colab.
Restart the runtime option
Go to Runtime on the menu bar and select the restart runtime from the drop-down menu. Alternatively, press the CTRL + M.
Remount the drive
Run the following command in the colab shell to unmount and then remount the drive, which would resolve the issue.
!fusermount -u drive
!google-drive-ocamlfuse drive
FAQs on Transport Endpoint is Not Connected
What is UNIX?
Unix has become a Family of operating systems developed initially in Bell Labs in 1969.
What do you mean by segmentation fault?
A segmentation fault is reported when software or program tries to access the restricted portion of the memory space.
Is macOS based on UNIX?
macOS is based on a BSD codebase, a discontinued version of UNIX research.
Conclusion
FUSE is a pretty helpful feature initially implemented for the UNIX-based Operating system. It is now widely used by several system administrators to allow their users to create their virtual file system on top of the system’s file system without interfering with the underlying kernel operations of the operating system. But sometimes, due to some arbitrary reasons, errors like ‘ Transport endpoint is not connected’ can show up. Here, we provided you with the two most straightforward ways to resolve the issue.
Trending Now
-
Resolve Error Code E4301 Using These 4 Exciting Methods
●October 20, 2022
-
15 Incredible Ways to Fix Paramount Plus Keeps Pausing Error
by Amal Santosh●October 20, 2022
-
5 Strategies to Fix Adobe Short Media Token Validation Error Invalid Signature
by Amal Santosh●October 11, 2022
-
Fix the Apple TV 4K Turns off by Itself with 7 Wonderful Ways
by Amal Santosh●October 11, 2022
I got this error when trying to run ps4drv on Gentoo. The entire trace is :
ds4drv
[info][controller 1] Created devices /dev/input/js2 (joystick) /dev/input/event10 (evdev)
[info][bluetooth] Scanning for devices
[info][bluetooth] Found device A4:15:66:6F:3B:A0
Traceback (most recent call last):
File "/usr/bin/ds4drv", line 9, in <module>
load_entry_point('ds4drv==0.3.0', 'console_scripts', 'ds4drv')()
File "/usr/lib64/python2.7/site-packages/ds4drv/__main__.py", line 325, in main
for device in backend.devices:
File "/usr/lib64/python2.7/site-packages/ds4drv/backends/bluetooth.py", line 117, in devices
device = self.find_device()
File "/usr/lib64/python2.7/site-packages/ds4drv/backends/bluetooth.py", line 106, in find_device
return BluetoothDS4Device.connect(bdaddr)
File "/usr/lib64/python2.7/site-packages/ds4drv/backends/bluetooth.py", line 34, in connect
return cls(addr, ctl_socket, int_socket)
File "/usr/lib64/python2.7/site-packages/ds4drv/backends/bluetooth.py", line 41, in __init__
super(BluetoothDS4Device, self).__init__(addr, "bluetooth")
File "/usr/lib64/python2.7/site-packages/ds4drv/device.py", line 70, in __init__
self.set_operational()
File "/usr/lib64/python2.7/site-packages/ds4drv/backends/bluetooth.py", line 66, in set_operational
self.set_led(255, 255, 255)
File "/usr/lib64/python2.7/site-packages/ds4drv/device.py", line 82, in set_led
self._control()
File "/usr/lib64/python2.7/site-packages/ds4drv/device.py", line 75, in _control
flash_led2=self._led_flash[1], **kwargs)
File "/usr/lib64/python2.7/site-packages/ds4drv/device.py", line 130, in control
self.write_report(report_id, pkt)
File "/usr/lib64/python2.7/site-packages/ds4drv/backends/bluetooth.py", line 63, in write_report
self.ctl_sock.sendall(hid + data)
File "/usr/lib64/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 107] Transport endpoint is not connected
bluez version is 4.101
11 Years Ago
I’m trying to understand socket programming in python by experimenting a little. I’m trying to create a server that you can connect to by telnet and that echoes what you type in the telnet prompt. I don’t want to start using threads just yet. This is my code.
import socket
host = "127.0.0.1"
port = 8080
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
sock.bind((host,port))
sock.listen(1)
remote, address = sock.accept()
print "Connection from", address
while True:
data = sock.recv(1024)
remote.send(data)The server starts without errors, but when I connect with the telnet client I get, on the client side:
> telnet 127.0.0.1 8080
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Connection closed by foreign host.and on the server side:
> python server_test.py
Connection from ('127.0.0.1', 35030)
Traceback (most recent call last):
File "server_test.py", line 16, in <module>
data = sock.recv(1024)
socket.error: [Errno 107] Transport endpoint is not connectedCan anyone tell me what this error comes from and how to solve it?
Recommended Answers
All 4 Replies
11 Years Ago
Hi,
Can you tell me please how did you fix the problem ?!
Thanks!
11 Years Ago
Sorry, I don’t quite remember and right now I don’t have time to revisit the problem (master thesis deadline on thursday 
) . What I do remember is that I solved it by following the advice in the link; Read the manual…
Reply to this topic
Be a part of the DaniWeb community
We’re a friendly, industry-focused community of developers, IT pros, digital marketers,
and technology enthusiasts meeting, networking, learning, and sharing knowledge.
-
#1
I got many of the following error messages on the weekend:
Code:
2020-12-19T23:08:31+01:00: starting new backup reader datastore 'pbs-backup': "/pbs-backup"
2020-12-19T23:08:31+01:00: protocol upgrade done
2020-12-19T23:08:31+01:00: GET /download
2020-12-19T23:08:31+01:00: download "/pbs-backup/vm/121/2020-11-11T06:17:33Z/index.json.blob"
2020-12-19T23:08:31+01:00: TASK ERROR: connection error: Transport endpoint is not connected (os error 107)Code:
2020-12-19T23:08:28+01:00: starting new backup reader datastore 'pbs-backup': "/pbs-backup"
2020-12-19T23:08:28+01:00: protocol upgrade done
2020-12-19T23:08:28+01:00: GET /download
2020-12-19T23:08:28+01:00: download "/pbs-backup/vm/106/2020-12-18T17:26:30Z/index.json.blob"
2020-12-19T23:08:28+01:00: GET /download
2020-12-19T23:08:28+01:00: download "/pbs-backup/vm/106/2020-12-18T17:26:30Z/qemu-server.conf.blob"
2020-12-19T23:08:28+01:00: GET /download
2020-12-19T23:08:28+01:00: download "/pbs-backup/vm/106/2020-12-18T17:26:30Z/drive-scsi0.img.fidx"
2020-12-19T23:08:29+01:00: register chunks in 'drive-scsi0.img.fidx' as downloadable.
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/67c0/67c0b22f8b83187c7a2b6ddfb9e5806f8d04f48afea09bcfc1f2c65f38fd955f"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/bbf7/bbf78b5308dbc2ecead77ee443bb2a2450a13860d052ad440a4d84a24667819d"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/86b9/86b97f537079beabdbf1c5e47d387ca46360dde9dbaf28ff23fa65bba6a063e9"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/5d59/5d59058782ed164478adc82580ff2b3f89f40f3d224283a7e3b3dcdc656bb4a9"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/5a18/5a18aa9fb3c459f69f603fbf803c8ac6e3187e30161c9c17d70abb9958d33e3d"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/308b/308b4f403d83e065c3763515293723f5061f5a15a16de2f42d0e12a06c89db3d"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/80b6/80b647d4fd3115e0cc17788a90d3a676376f9da22e8787ac06d6e4c553441877"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/cc5f/cc5f5de499a0142897a52a9c935c93c875ded01f436e577452df39453050ede5"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/16f6/16f602494ff0a626f685f63e072734490d090e76550a3f77c764214e3cc1c3d3"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/e960/e9605688e420104aa459458b32abfa7cd1c2c335b4ae56152cbc7ee2058fbca6"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/e917/e917b77f72dc304db0ce7d1702b85f7cd062dbe92863e73809d76f869b787563"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/d2bb/d2bb007147d93bab357be31093586082232335ff6bab3879559960f3f658346b"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/3fe6/3fe6a9edbbde5a9e80f452bdd378712a3a0414c067551c7ef2a539a29bb8d63d"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/dde5/dde5d8c60ee71f58adf71f2928c3790b6c8453b67f1588616a18c5abeba21a95"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/e2ad/e2ad277b9fa5f5acba95f5dc7e6aabd4b5ed4cbcc7e6274c4e22bd3082d86582"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/c5be/c5be9d2c077d3c39569f4bbe4860e780b3b1f5a567a7c69cd3e70517f4f458e1"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/5560/55604ed98832ed42c1912c4ca8caadca8b44c490bdc70ad3d15a97b479e65d09"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/0c67/0c67f00838d4a4524d82d37a0bfa2e50975efd7764af17b671df350990c98b56"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/ff3c/ff3cd823f7cfc8f68a6b699afebc2b17d38ab3fad35ca76ad9310f01b1635d4d"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/4cae/4cae2b2b26604337212f09d6e3c3a92ad61779e4514de62bea43e6ef1417685f"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/595f/595f19bfaafd411bf7dbd6f4f4a4e5d5e64f496fdeccea6d48a9182bfe21f425"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/0130/0130817acc522f0b42dd43f57cbff651141c63e6723ece4444b3111969a61e67"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/4972/49724ea1bd939d8a31de3ce077e7fc7fd255cb918caf1fc9d00a6dac100be99e"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/6806/6806cde50f88a6fe35d2407826c37eb1129fddfaf40b19eebb60560b4ed26c01"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/ce07/ce07309a27817cb1144711f67d8d3fa1548c18f4283d77c965b31b6cff204bd4"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/9efb/9efb6ebf7bdf1846d8a7492d35350c9339e3cdae8873e830708a33466918cdc3"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/f100/f10031a4c903eb23ff2f343bfc5f79be459c1871d760d402857a43667d211b18"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/e6e3/e6e35d86cb40b752743fc2e8c15b434f8b87920b64e8afd3c0c892676d8577e6"
2020-12-19T23:08:29+01:00: GET /chunk
2020-12-19T23:08:29+01:00: download chunk "/pbs-backup/.chunks/0fd9/0fd98b496f02c6ab9d8ac18352d81f13a30611aadaa602097bc147bbb99a18fc"
2020-12-19T23:08:29+01:00: GET /download
2020-12-19T23:08:29+01:00: download "/pbs-backup/vm/106/2020-12-18T17:26:30Z/client.log.blob"
2020-12-19T23:08:31+01:00: TASK ERROR: connection error: Transport endpoint is not connected (os error 107)What does that mean? During weekend we have not configured any backups to datastore pbs-backup. Only a sync job for to a local remote datastore (removable usb disk) which did successfully get executed.
Is it possible that these are backups that were pruned from pbs-backup datastore thus cannot be verified on the removable datastore?
Talking of prune, I checked and realized that the configured prunge and gc settings are gone, and I don’t know why.
Last edited: Dec 21, 2020
-
#2
sync basically pulls the metadata and chunks via the download API path, so likely those log entries were just the sync? that they end with the transport message can happen when the client closes the connection before the server expected too.
-
#3
Hm, well the client and the server is on the same machine, as I configured a remote -> localhost as workaround to be able to sync the datastore content to an offline medium. So am I supposed to just ignore those kind of messages, or can I do something to make them disapear?
-
#4
yes, you can ignore those messages if the client-side (sync/backup/restore) does not complain/show any errors.
-
#5
Just to clarify — you mean as the following message which appears just after the last error message indicates the the sync finished successfully, then I can ignore it, right?:
Code:
2020-12-19T22:15:02+01:00: Starting datastore sync job 'local:pbs-backup:sandisk:s-f0eb4571-25bf'
2020-12-19T22:15:02+01:00: task triggered by schedule 'sat 22:15'
2020-12-19T22:15:02+01:00: Sync datastore 'sandisk' from 'local/pbs-backup'
2020-12-19T22:15:10+01:00: re-sync snapshot "vm/100/2020-12-11T17:10:01Z"
2020-12-19T22:15:10+01:00: no data changes
2020-12-19T22:15:10+01:00: re-sync snapshot "vm/100/2020-12-11T17:10:01Z" done
2020-12-19T22:15:10+01:00: percentage done: 7.58%
2020-12-19T22:15:10+01:00: sync snapshot "vm/100/2020-12-14T08:10:01Z"
2020-12-19T22:15:10+01:00: sync archive qemu-server.conf.blob
2020-12-19T22:15:11+01:00: sync archive drive-scsi0.img.fidx
2020-12-19T22:15:27+01:00: downloaded 660037055 bytes (38.04 MiB/s)
2020-12-19T22:15:27+01:00: got backup log file "client.log.blob"
2020-12-19T22:15:27+01:00: sync snapshot "vm/100/2020-12-14T08:10:01Z" done
2020-12-19T22:15:27+01:00: percentage done: 7.73%
2020-12-19T22:15:28+01:00: sync snapshot "vm/100/2020-12-14T09:10:01Z"
2020-12-19T22:15:28+01:00: sync archive qemu-server.conf.blob
2020-12-19T22:15:28+01:00: sync archive drive-scsi0.img.fidx
2020-12-19T22:15:33+01:00: downloaded 83810981 bytes (21.65 MiB/s)
2020-12-19T22:15:33+01:00: got backup log file "client.log.blob"
...
...
...
2020-12-19T23:08:29+01:00: downloaded 11392695 bytes (16.32 MiB/s)
2020-12-19T23:08:31+01:00: got backup log file "client.log.blob"
2020-12-19T23:08:31+01:00: sync snapshot "vm/106/2020-12-18T17:26:30Z" done
2020-12-19T23:08:31+01:00: percentage done: 85.57%
2020-12-19T23:08:31+01:00: re-sync snapshot "vm/121/2020-11-11T06:17:33Z"
2020-12-19T23:08:31+01:00: re-sync snapshot "vm/121/2020-11-11T06:17:33Z" done
2020-12-19T23:08:31+01:00: percentage done: 85.71%
2020-12-19T23:08:31+01:00: sync job 'local:pbs-backup:sandisk:s-f0eb4571-25bf' end
2020-12-19T23:08:31+01:00: TASK OK
-
#6
yes. basically the client (=sync in this case) is done, closes the connection, and the server only sees «connection is closed» and logs the warning.
-
#7
understood. Thanks for clarifying
-
#8
Is it still relevant that error in PBS Tasks after «Sync Job» on the same machine can be ignored ?
Code:
TASK ERROR: connection error: Transport endpoint is not connected (os error 107)Problem
Application has multiple Compute Hosts getting blocked causing long delays in workload processing.
Symptom
Messages like the following error are seen in SIM logs of the host(s) getting blocked:
2018-06-04 07:38:16.100 EST5EDT ERROR [7827:47387109566816] sim.frontend.SsmHandler — Code[S40016]: SimSsmHandler.cpp:458 Domain <SOAM>: Failed to connect to session manager. Session manager URL <compute.domain.com:port>, communication error <#107: Transport endpoint is not connected>. Session manager process may not be started or not operating correctly. It is possible that the session manager servicing this application has exceeded its number of client and service connections and has rejected the connection from current SIM. Check the session manager log to confirm this issue.
Cause
This issue may occur in conditions with peak workload running on large clusters. If the backlog parameter on SSM’s listening port is very low, some newly started SIMs may fail to register with SSM within the SIM’s startupTimeout period, when the no. of incoming connections for SSM from Client API and SIMs is much higher than the somaxconn limit set on the SSM process.
Diagnosing The Problem
1. SSH to SSM host and run the following commands:
a. netstat -anp | grep <SSM PID>
b. Identify the port numbers SSM is listening on for Clients and SIM connections. For example, as shown in highlighted lines below:
$ sudo netstat -anp | grep 39494
tcp 0 0 0.0.0.0:32001 0.0.0.0:* LISTEN 39494/ssm
tcp 0 0 0.0.0.0:31000 0.0.0.0:* LISTEN 39494/ssm
tcp 0 0 172.30.xx.xx:48790 172.30.xx.xy:1902 ESTABLISHED 39494/ssm
tcp 0 0 172.30.xx.xx:43415 172.30.xx.xy:1902 ESTABLISHED 39494/ssm
$ ss -an | grep 32001
LISTEN 0 128 *:32001 *:*
ESTAB 0 0 172.30.xx.xx:32001 172.30.xx.yy:50284
$ ss -an | grep 31000
LISTEN 0 128 *:31000 *:*
2. Get the soamax connections backlog on the host:
a. sysctl net.core.somaxconn
3. Get limits of SSM PID:
cat /proc/<SSM PID>/limits
Resolving The Problem
The backlog parameter for SSM process is configurable up to a max value of 1000.
Change the configuration on the SSM host to increase the backlog for ports SSM is listening on:
i. sudo sysctl net.core.somaxconn=1024 (or any value higher than 1000)
ii. sudo sysctl -p (this commits the value without needing to restart network services on the host)
iii. Restart SSM
iv. To check if changes are reflected:
— get SSM PID and the ports it is listening on via netstat command
v. sudo ss -an | grep <SSM_listening_port>
For example:
netstat -anp | grep ssm
tcp 0 0 0.0.0.0:43051 0.0.0.0:* LISTEN 2622/ssm
ss -an | grep 43051
tcp LISTEN 0 1000 *:43051 *:*
Whereas, if the somaxconn limit on the host is configured to a value lower than 1000, then the ss command will show that value instead of the default «128».
Related Information
[{«Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Product»:{«code»:»SSZUMP»,»label»:»IBM Spectrum Symphony»},»Component»:»SOAM;SSM;SIM»,»Platform»:[{«code»:»PF016″,»label»:»Linux»}],»Version»:»7.2;7.2.1″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]
Product Synonym
Platform Symphony
Greetings,
I am having some issues with NFS clients on two separate physical servers. Often ‘dmesg -T’ shows the following output several times an hour:
dmesg:
xs_tcp_setup_socket: connect returned unhandled error -107
/var/log/messages:
kernel: xs_tcp_setup_socket: connect returned unhandled error -107
This is apparently causing applications to hang for a time. I am unable to find any information regarding this error specifically for RHEL7. The server is a NetApp appliance with dozens of other NFS shares. We’ve tried re-creating the shares, just in case… and also connecting to shares we know are working, with the same results.
Anyone else having this issue? We’re pinned to RHEL 7.3.
A further note: This is a production server; the dev and test servers running the same application, same OS aren’t having this issue.
Distributor ID: RedHatEnterpriseServer
Release: 7.3
Linux hostname 3.10.0-514.26.2.el7.x86_64 #1 SMP Fri Jun 30 05:26:04 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Issue7887
Created on 2010-02-08 23:46 by twistedphrame, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (3) | ||
|---|---|---|
| msg99074 — (view) | Author: Jordan Apgar (twistedphrame) | Date: 2010-02-08 23:46 |
I have a simple tcp server and client where the server sits and waits for a message and then processes it, my client sends its first message to the server. On the server I receive: socket.error: [Errno 107] Transport endpoint is not connected when calling msg = self.socket.recv(self.buffer) My client receives the error: socket.error: [Errno 104] Connection reset by peer when calling msg = self.socket.recv(self.buffer) I was working on the server and client over the weekend and sending and receiving worked fine, I wanted to debug a few things and I get this when I try to run it (no changes made from what I had on the weekend) |
||
| msg99094 — (view) | Author: Amaury Forgeot d’Arc (amaury.forgeotdarc) *  |
Date: 2010-02-09 08:11 |
The issue tracker is not to a place to find problems in your code (network programming is difficult, even with python). Please ask your questions on the comp.lang.python newsgroup, where many people will be ready to help you. |
||
| msg99116 — (view) | Author: Jordan Apgar (twistedphrame) | Date: 2010-02-09 14:08 |
Sorry I was under the impression this was an issue with the socket module |
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:57 | admin | set | github: 52135 |
| 2010-02-09 14:08:15 | twistedphrame | set | messages: + msg99116 |
| 2010-02-09 08:11:17 | amaury.forgeotdarc | set | status: open -> closed
nosy: resolution: not a bug |
| 2010-02-08 23:46:54 | twistedphrame | create |