transport endpoint is already connected что делать
Transport Endpoint is Already Connected #3
Comments
BnMcG commented May 29, 2019
The text was updated successfully, but these errors were encountered:
codypet commented Jul 18, 2019
I too am getting this error now after months of working fine. Any ideas?
Wed Jul 17 2019 23:03:39 GMT-0400 (Eastern Daylight Time)
Failed to update RoboVac status: [Errno 106] Transport endpoint is already connected
Connection lost. Reconnecting…
BnMcG commented Jul 18, 2019
Have you tried restarting Home Assistant and the Robovac? I think that’s how I «fixed» this when it happened to me, I’ll take a look at making the code a bit more robust.
codypet commented Jul 18, 2019
Yea I restarted it because in the past, that’s historically fixed the problem. Then I assumed maybe the Robovac wasn’t connecting to the server, but that’s not the problem either. I don’t have any other errors so this one is a head scratcher for me.
BnMcG commented Jul 18, 2019
What version of Home Assistant are you using?
codypet commented Jul 18, 2019
0.95.4 right now, and it’s been working fine for the last few weeks. I’m wondering if it’s related to something Eufy did. I didn’t go to 0.96.0 yet.
BnMcG commented Jul 18, 2019 •
I’ve been looking at that bug today and I can confirm that HA 0.95.4 works fine for me locally using the Robovac component, so it shouldn’t be any changes Eufy have made unless your Robovac has received an update mine hasn’t for some reason.
Just to clarify, have you restarted both Home Assistant and the Robovac?
codypet commented Jul 18, 2019
Yes, I have but will try it again when I get home from work in case it was something going on with my machine last night.
BnMcG commented Jul 18, 2019
How are you running Home Assistant, by the way? As far as I know this error should be transient and not persist across reboots, as I think it’s to do with a socket already being in use.
codypet commented Jul 18, 2019 •
Hassbian on a Raspberry Pi3 running Python 3.7.3.
codypet commented Jul 19, 2019 •
I went back and verified that my Eufy was connected to the right wifi router, and not the repeater, at the correct IP address, restarted it, and rebooted the whole pi. Still the same issue. Its bizarre because this hasn’t been a problem since you refreshed the layout about a month ago until now.
More Errors: (Hadn’t seen this 2 bytes one before)
Thu Jul 18 2019 22:49:04 GMT-0400 (Eastern Daylight Time) Failed to update RoboVac status: unpack requires a buffer of 2 bytes Thu Jul 18 2019 22:51:51 GMT-0400 (Eastern Daylight Time) Failed to update RoboVac status: [Errno 106] Transport endpoint is already connected
BnMcG commented Jul 19, 2019
OK, I’ve taken a closer look at the error and it’s a problem in the underlying Python library that communicates with the Robovac, not a problem with Home Assistant or the custom component.
The code is written such that it tries to send the instruction to the Robovac, and if that fails for whatever reason, there’s a catch-all where it will then try to connect to the Robovac and then send the instruction again. I think what’s happening is that sending the packet is failing for other reasons, the catch-all is triggered, it tries to reconnect, and then that fails because the connection already exists.
I’ll see if I can narrow down which exceptions are thrown in order to better handle errors.
BnMcG commented Jul 19, 2019
Can you try upgrading the custom component for me, restarting Home Assistant and seeing how you get on? I don’t think there’s a reliable way to reproduce this so it might just be a case of waiting and seeing if the transport error comes back.
codypet commented Jul 20, 2019
Alright. Now we have some errors. I don’t know what a file descriptor or a pipe is though.
Fri Jul 19 2019 23:07:33 GMT-0400 (Eastern Daylight Time) Failed to update RoboVac status: unpack requires a buffer of 2 bytes Fri Jul 19 2019 23:07:54 GMT-0400 (Eastern Daylight Time) [Errno 32] Broken pipe Traceback (most recent call last): File «/srv/homeassistant/lib/python3.7/site-packages/robovac/robovac.py», line 324, in _send_packet self.s.send(encrypted_packet_data) BrokenPipeError: [Errno 32] Broken pipe Fri Jul 19 2019 23:10:00 GMT-0400 (Eastern Daylight Time) [Errno 9] Bad file descriptor Traceback (most recent call last): File «/srv/homeassistant/lib/python3.7/site-packages/robovac/robovac.py», line 324, in _send_packet self.s.send(encrypted_packet_data) OSError: [Errno 9] Bad file descriptor Fri Jul 19 2019 23:10:00 GMT-0400 (Eastern Daylight Time) Failed to update RoboVac status: [Errno 9] Bad file descriptor
BnMcG commented Jul 20, 2019
codypet commented Jul 21, 2019
Ok restarting HA today and I lost the Eufy altogether and I think I know what part of the problem is. When I log into my wifi router there’s no Eufy. Not in the IP I have reserved for it, not anywhere. Eufy in the app still says its connected to my wifi router, and still works in the app. I don’t know why its not showing up in the router settings. I suspect with that missing, the HA configuration doesn’t see it either and therefore that’s why its not working in HA. I just. don’t know why the router says the Eufy isn’t there.
JXGA commented Jul 21, 2019
Might just be the router interface, have you tried pinging the Vac from the command line?
If it’s still showing connected on the app it must be there somewhere..
codypet commented Jul 21, 2019
So when I ping, something is reporting back right away so. I don’t know what’s going on.
codypet commented Jul 26, 2019
So Eufy started showing back up in my router again at the proper IP address, matching the login information and it still doesn’t show up and it still gives me the same errors. How is everyone faring with 0.96?
JXGA commented Jul 26, 2019
There is an update coming to the underlying module that serves this custom_component, hopefully won’t be long until it’s released.
It will still give an occasional error in the logs, but seems to work okay.
Transport endpoint is not connected after session started #334
Comments
pbmzero commented Jan 28, 2014
I have 20 different workstations and at any given moment one or two of them have a problem where I connect, authenticate, succeeds, begins renders about 3 or 4 blocks of the remote screen then frezees for 60 seconds, disconnects. The freeze always happens at the same spot. The problem usually goes away if i retry a couple times but sometimes it never fixes it. When it starts happening, it seems to happen in all browsers i attempt (Chrome, Firefox IE11) so it’s probably more about the communication. If i restart the webscokets proxy there is a good chance it might fix it but there are times when it does not. The VNC server is up, i can connect directly to it through the IP address directly while this is ongoing. This has been going on for several months. It looks like it disconnects right after sending the keyboard layout profile (if i look at the communication with wireshark)
Chrome:Version 31.0.1650.63 m (Win 7, 32)
NoVnC: 5.3.4? (Ubuntu 10.04 LTS 32)
TightVncServer: tightvnc-2.6.4-setup-32bit (Win 7, 32) with mirror driver installed
Output from the ws server:
1: 64.40.246.182: Plain non-SSL (ws://) WebSocket connection
1: 64.40.246.182: Version hybi-13, base64: ‘False’
1: 64.40.246.182: Path: ‘/websockify’
1: connecting to: 10.160.0.61:5900
1: handler exception: [Errno 107] Transport endpoint is not connected
Output from the chrome debug console:
New state ‘Authentication’, was ‘Security’. Msg: Authenticating using scheme: 2 util.js:110
New state ‘SecurityResult’, was ‘Authentication’. util.js:110
New state ‘ClientInitialisation’, was ‘SecurityResult’. Msg: Authentication OK util.js:110
New state ‘ServerInitialisation’, was ‘ClientInitialisation’. Msg: Authentication OK util.js:110
Screen: 1920×1080, bpp: 32, depth: 24, big_endian: 0, true_color: 1, red_max: 255, green_max: 255, blue_max: 255, red_shift: 16, green_shift: 8, blue_shift: 0 util.js:109
Setting viewport to full display region util.js:108
New state ‘normal’, was ‘ServerInitialisation’. Msg: Connected (unencrypted) to: util.js:110
Ignoring empty message util.js:108
First FBU latency: 172 util.js:109
The text was updated successfully, but these errors were encountered:
Transport endpoint is not connected
I currently have my mount points setup like this, I’m not sure what other details I should add here so let me know if I missed anything..
7 Answers 7
I have exactly the same problem. I haven’t found a solution anywhere, but I have been able to fix it without rebooting by simply unmounting and remounting the mountpoint.
For your system the commands would be:
fusermount: entry for /data not found in /etc/mtab
I get this error from the sshfs command from Fedora 17 linux to debian linux on the Mindstorms EV3 brick over the LAN and through a wireless connection.
This is remedied with the following command and trying again:
These additional sshfs options prevent the above error from concurring:
In order to use allow_other above, you need to uncomment the last line in /etc/fuse.conf :
There is a segmentation fault problem which was introduced in 0.1.39. You may check my repository that fixed this one meanwhile: https://github.com/vdudouyt/mhddfs-nosegfault
Now this answer is for those lost souls that got here with this problem because they force-unmounted the drive but their hard drive is NTFS Formatted. Assuming you have ntfs-3g installed (sudo apt-get install ntfs-3g).
Where hdd is the hard drive in question and the «/mnt/mount_point» directory exists.
Leaving my answer here in case this fix can aid anyone!
Transport endpoint is not connected
My code is this but not working
unable to read from socket [107]: Transport endpoint is not connected PHP Stack trace: Buffer =
Last Error = 107Transport endpoint is not connected
3 Answers 3
You have to accept a connection first! Inside your while() loop, do another while() like this:
It should work, as you intend.
OK, so the client socket is not connected.
As I wrote in a comment to previous answer, you can find fine example of solving this problem on PHP.net Examples Page. In the main article you’ll find a good example, how to make a listener without error, you’re refering to, for one client and in javier’s notice below, how to have the same for multi-client purpose.
Not the answer you’re looking for? Browse other questions tagged php sockets websocket or ask your own question.
Related
Hot Network Questions
Subscribe to RSS
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.11.25.40831
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
«transport endpoint is not connected» error after a write to a mounted volume crashes docker container. Docker Destop 2.2.0.0 #5584
Comments
plaht commented Jan 24, 2020
Expected behavior
I am able to mount a scala sbt docker image based on ubuntu to a volume and the sbt is able to create directories inside the mounted volume.
Actual behavior
I get an error that I am unable to create directory
Could not create directory /root/src/target/streams/compile/$global/$global/discoveredMainClasses
When rerunning a container, I am unable to perform basic bash operations such as «ls»
ls: cannot open directory ‘.’: Transport endpoint is not connected
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered:
plaht commented Jan 24, 2020
I’ve reverted back to Docker Desktop 2.1.0.5 with no issue.
ulrich commented Jan 27, 2020 •
@plaht Really sorry for the bug, we tried to reproduce the trouble but without success. Can you give an another way to reproduce the issue via a docker public image?
Thank you again for your feedback,
plaht commented Jan 27, 2020
I will try to reproduce with a public docker image on 2.2.0.0 and revert back.
ulrich commented Jan 27, 2020 •
I will try to reproduce with a public docker image on 2.2.0.0 and revert back.
Waiting your feedback!
Thank you,
ulrich commented Jan 29, 2020
@plaht don’t hesitate to come back toward us.
Thank you.
iwilliamson commented Feb 2, 2020 •
I’m having a very similar issue using 2.2.0.0.
In my case, I have a tree of source code mounted on /src. During the compile, the volume is dropped and I can only get the «Transport endpoint is not connected» message. The only way to fix it seems to be restarting docker desktop. The log contains the following errors: