Socket read error 107

socket.error: [Errno 107] Transport endpoint is not connected (Gentoo) #22

I got this error when trying to run ps4drv on Gentoo. The entire trace is :

bluez version is 4.101

The text was updated successfully, but these errors were encountered:

Does this happen everytime you try to connect the controller or only sometimes?

It happens everytime. If you need any other information tell me.

What kernel version, Python version and bluetooth dongle are you using?

The usb dongle is plugged on usb3 socket.
I have another dongle, will test with it.

Edit : It work fine with the other dongle :

Is there a need for bluetooth 4.0, because it work under windows with both dongles.

Exactly the same error here. Some news?

Is there a need for bluetooth 4.0, because it work under windows with both dongles.

Well, what seems to be happening is that the connection to the device is instantly dropped. I have no idea why though, it could be due to incomplete or bad driver for your dongle in bluez.

You could try pairing it in bluez first (requires bluez 5.14) and then run ds4drv in hidraw mode ( ds4drv —hidraw ).

Exactly the same error here. Some news?

What bluetooth dongle, bluez version and kernel do you use?

$ uname -a
Linux laptop 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ python —version
Python 2.7.5+
$ lsusb
Bus 001 Device 020: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Since you use bluez 5.14, does pairing it normally work?

$ bluetoothctl
[bluetooth]# version
Version 5.14

And now for pairing normally how should i do?
[bluetooth]# pair + MAC?

edit: I get this : Device not available

And now for pairing normally how should i do?

[bluetooth]# scan on No default controller available

No default controller available

[bluetooth]# show No default controller available

How can i set a default controller?

[bluetooth]# show No default controller available

Ah, my bad, seems like I gave you wrong command, this is the correct command to show your controllers: [bluetooth]# list
Then do [bluetooth]# select to set the default controller.

[bluetooth]# list [bluetooth]# select 60:6c:66:5b:f9:c2 Controller 60:6c:66:5b:f9:c2 not available

List shows me nothing, and even with the MAC of my bluetooth dongle it doesn’t set the default controller. I don’t understand..

edit : I tried with 2 bluetooth dongles, 1 on USB, and 1 of my laptop

That’s odd, what is the output of hciconfig ?

$ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 00:15:83:0C:BF:EB ACL MTU: 339:8 SCO MTU: 128:2 UP RUNNING PSCAN RX bytes:555 acl:0 sco:0 events:32 errors:0 TX bytes:385 acl:0 sco:0 commands:26 errors:0

and with my other dongle :

hci0: Type: BR/EDR Bus: USB BD Address: 60:6C:66:5B:F9:C2 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:589 acl:0 sco:0 events:34 errors:0 TX bytes:898 acl:0 sco:0 commands:33 errors:0

Got no clue what could be wrong, I guess you could try a different bluetooth tool like gnome-bluetooth to do the pairing.

When i started ./configure for bluez 5.14, i get this error :
checking systemd system unit dir. configure: error: systemd system unit directory is required
So i had to launch ./configure —disable-systemd but the dbus daemon which is started automatically by systemd, is used to read settings and for PIN pairing. Do you think it could be my problem?

Yes, if bluetoothd is not running it’s probably not possible to pair. Perhaps you should check if there is a package available for your distro instead of building manually to make sure things are correctly setup on your system. If not, check if there is a init script in /etc/init.d/ to start the daemon.

I just experienced the «Transport endpoint is not connected» error.
I have 2 dongles. The first one works fine and it’s a bluetooth 4.0 usb dongle.
The second one gives me the transport error and it’s a bluetooth 2.0 usb dongle.

The fact is that standard pairing is also problematic because it asks for a PIN, which does not happen to be necessary with the other device.

I managed to pair it using bluetoothctl after enabling the agent:

And then «ds4drv —hidraw» worked fine.

• Without the «agent on» command, pair fails with «Failed to pair: org.bluez.Error.AuthenticationRejected» with the bluetooth 2 dongle.
• The agent/pin steps are not necessary with the bluetooth 4 dongle.

I tried pairing my DS4 with bluez-simple-agent hci0 MAC , but i get this error :
Creating device failed: org.bluez.Error.ConnectionAttemptFailed: Page Timeout .

I was using bluez 5.14, I don’t know about bluez 4

I’ve pushed f3db91b which will make sure we don’t crash when this happens, and will attempt to retry the connection. I don’t think that will help much though, since it seems like our way of connecting directly to the DS4 without pairing only works on some dongles.

For the record, the bluetooth dongle I’m using is built into my motherboard (Asus P8Z68-V) and is v2.1. It seems like 2.0 dongles have issues, but might work if paired in bluez 5.14 as @mtorromeo describes.

It’s now working. Thanks, i don’t know why i can’t do the pairing/connection with bluetoothctl, but with this last commit i don’t have the socket.error anymore!

edit: after starting ds4drv a second time, i get the socket.error again . T_T

I’ve got this error a few times now as well. I’m on Ubuntu 13.10 x64 with bluez 4 and using a broadcom BCM2046B1 2.0 dongle. I’m running the driver in raw bluetooth mode and everything works fine. While I haven’t figured out a way to reliably reproduce it I did find a way to get past the error by running blueman (bluetooth-manager) and deleting the wireless controller from the devices list. After that I can connect as usual. My laptop also has built-in bluetooth and a couple times I’ve seen the controller show up in the device list for the internal bluetooth as well. Again deleting it from the list of devices and trying to reconnect always results in success.

Again deleting it from the list of devices and trying to reconnect always results in success.

Sounds like bluetoothd might be interfering somehow, try killing it and see if it helps.

Источник

How Socket Error Codes Depend on Runtime and Operating System

Rider consists of several processes that send messages to each other via sockets. To ensure the reliability of the whole application, it’s important to properly handle all the socket errors. In our codebase, we had the following code which was adopted from Mono Debugger Libs and helps us communicate with debugger processes:

In the case of a failed connection because of a “ConnectionRefused” error, we are retrying the connection attempt. It works fine with .NET Framework and Mono. However, once we migrated to .NET Core, this method no longer correctly detects the “connection refused” situation on Linux and macOS. If we open the SocketException documentation, we will learn that this class has three different properties with error codes:

• SocketError SocketErrorCode : Gets the error code that is associated with this exception.
• int ErrorCode : Gets the error code that is associated with this exception.
• int NativeErrorCode : Gets the Win32 error code associated with this exception.

What’s the difference between these properties? Should we expect different values on different runtimes or different operating systems? Which one should we use in production? Why do we have problems with ShouldRetryConnection on .NET Core? Let’s figure it all out!

Digging into the problem

If we run it on Windows, we will get the same value on .NET Framework, Mono, and .NET Core:

10061 corresponds to the code of the connection refused socket error code in Windows (also known as WSAECONNREFUSED ). Now let’s run the same program on Linux:

As you can see, Mono returns Windows-compatible error codes. The situation with .NET Core is different: it returns a Windows-compatible value for SocketErrorCode (10061) and a Linux-like value for ErrorCode and NativeErrorCode (111). Finally, let’s check macOS:

Here, Mono is completely Windows-compatible again, but .NET Core returns 61 for ErrorCode and NativeErrorCode . In the IBM Knowledge Center, we can find a few more values for the connection refused error code from the Unix world (also known as ECONNREFUSED ):

• AIX: 79
• HP-UX: 239
• Solaris: 146

For a better understanding of what’s going on, let’s check out the source code of all the properties.

SocketErrorCode

These values correspond to the Windows Sockets Error Codes.

NativeErrorCode

In .NET Core, the native code is calculated in the constructor (see SocketException.cs#L20):

The Windows implementation of GetNativeErrorForSocketError is trivial (see SocketException.Windows.cs):

The Unix implementation is more complicated (see SocketException.Unix.cs):

TryGetNativeErrorForSocketError should convert SocketError to the native Unix error code. Unfortunately, there exists no unequivocal mapping between Windows and Unix error codes. As such, the .NET team decided to create a Dictionary that maps error codes in the best possible way (see SocketErrorPal.Unix.cs):

Once we have an instance of Interop.Error , we call interopErr.Info().RawErrno . The implementation of RawErrno can be found in Interop.Errors.cs:

Here we are jumping to the native function SystemNative_ConvertErrorPalToPlatform that maps Error to the native integer code that is defined in errno.h. You can get all the values using the errno util. Here is a typical output on Linux:

Note that errno may be not available by default in your Linux distro. For example, on Debian, you should call sudo apt-get install moreutils to get this utility. Here is a typical output on macOS:

Hooray! We’ve finished our fascinating journey into the internals of socket error codes. Now you know where .NET is getting the native error code for each SocketException from!

ErrorCode

Writing cross-platform socket error handling

There was a lot of work involved in tracking down the error code to check against, but in the end, our code is much more readable now. Adding to that, this method is now also completely cross-platform, and works correctly on any runtime.

Overview of the native error codes

We executed this program on Windows, Linux, and macOS. Here are the aggregated results:

Источник

ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below) #24879

2021.06.02 12:53:41.924881 [ 50 ] <> ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below):

Poco::Net::SocketImpl::error(int, std::__1::basic_string const&) @ 0x11d0c84e in /usr/bin/clickhouse

Poco::Net::SocketImpl::peerAddress() @ 0x11d0eac6 in /usr/bin/clickhouse

DB::ReadBufferFromPocoSocket::ReadBufferFromPocoSocket(Poco::Net::Socket&, unsigned long) @ 0xe8de1ad in /usr/bin/clickhouse

DB::TCPHandler::runImpl() @ 0xf64c6be in /usr/bin/clickhouse

DB::TCPHandler::run() @ 0xf65f879 in /usr/bin/clickhouse

Poco::Net::TCPServerConnection::start() @ 0x11d138af in /usr/bin/clickhouse

Poco::Net::TCPServerDispatcher::run() @ 0x11d152c1 in /usr/bin/clickhouse

Poco::PooledThread::run() @ 0x11e4b9e9 in /usr/bin/clickhouse

Poco::ThreadImpl::runnableEntry(void*) @ 0x11e4784a in /usr/bin/clickhouse

start_thread @ 0x9609 in /usr/lib/x86_64-linux-gnu/libpthread-2.31.so

clone @ 0x122293 in /usr/lib/x86_64-linux-gnu/libc-2.31.so
(version 21.3.12.2 (official build))
2021.06.02 12:53:42.805405 [ 51 ] <> ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below):

Poco::Net::SocketImpl::error(int, std::__1::basic_string const&) @ 0x11d0c84e in /usr/bin/clickhouse

Poco::Net::SocketImpl::peerAddress() @ 0x11d0eac6 in /usr/bin/clickhouse

DB::HTTPServerRequest::HTTPServerRequest(DB::Context const&, DB::HTTPServerResponse&, Poco::Net::HTTPServerSession&) @ 0xf669c64 in /usr/bin/clickhouse

DB::HTTPServerConnection::run() @ 0xf668ad4 in /usr/bin/clickhouse

Poco::Net::TCPServerConnection::start() @ 0x11d138af in /usr/bin/clickhouse

Poco::Net::TCPServerDispatcher::run() @ 0x11d152c1 in /usr/bin/clickhouse

Poco::PooledThread::run() @ 0x11e4b9e9 in /usr/bin/clickhouse

Poco::ThreadImpl::runnableEntry(void*) @ 0x11e4784a in /usr/bin/clickhouse

start_thread @ 0x9609 in /usr/lib/x86_64-linux-gnu/libpthread-2.31.so

clone @ 0x122293 in /usr/lib/x86_64-linux-gnu/libc-2.31.so
(version 21.3.12.2 (official build))

The text was updated successfully, but these errors were encountered:

Источник

Socket Error Перечисление

Определение

Некоторые сведения относятся к предварительной версии продукта, в которую до выпуска могут быть внесены существенные изменения. Майкрософт не предоставляет никаких гарантий, явных или подразумеваемых, относительно приведенных здесь сведений.

Определяет коды ошибок для класса Socket.

Предпринята попытка получить доступ к объекту Socket способом, запрещенным его правами доступа.

Обычно разрешается использовать только адрес.

AddressFamilyNotSupported 10047

Указанное семейство адресов не поддерживается. Эта ошибка возвращается, если указано семейство IPv6-адресов, а стек протокола IPv6 не установлен на локальном компьютере. Эта ошибка возвращается, если указано семейство IPv4-адресов, а стек протокола IPv4 не установлен на локальном компьютере.

Выбранный IP-адрес является недопустимым в этом контексте.

На незаблокированном сокете Socket уже выполняется операция.

Подключение разорвано платформой .NET или поставщиком основного сокета.

Удаленный узел активно отказывает в подключении.

Подключение сброшено удаленным компьютером.

DestinationAddressRequired 10039

В операции на сокете Socket пропущен обязательный адрес.

Выполняется правильная последовательность отключения.

Поставщиком основного сокета обнаружен недопустимый указатель адреса.

Ошибка при выполнении операции, вызванная отключением удаленного узла.

Такой узел не существует. Данное имя не является ни официальным именем узла, ни псевдонимом.

Отсутствует сетевой маршрут к указанному узлу.

Выполняется блокирующая операция.

Вызов к заблокированному сокету Socketбыл отменен.

Предоставлен недопустимый аргумент для члена объекта Socket.

Приложение инициировало перекрывающуюся операцию, которая не может быть закончена немедленно.

Объект Socket уже подключен.

У датаграммы слишком большая длина.

Приложение пытается задать значение KeepAlive для подключения, которое уже отключено.

Не существует маршрута к удаленному узлу.

Отсутствует свободное буферное пространство для операции объекта Socket.

Требуемое имя или IP-адрес не найдены на сервере имен.

Неустранимая ошибка, или не удается найти запрошенную базу данных.

Приложение пытается отправить или получить данные, а объект Socket не подключен.

Основной поставщик сокета не инициализирован.

Предпринята попытка выполнить операцию объекта Socket не на сокете.

Перекрывающаяся операция была прервана из-за закрытия объекта Socket.

Семейство адресов не поддерживается семейством протоколов.

Слишком много процессов используется основным поставщиком сокета.

ProtocolFamilyNotSupported 10046

Семейство протоколов не реализовано или не настроено.

Протокол не реализован или не настроен.

Для объекта Socket был использован неизвестный, недопустимый или неподдерживаемый параметр или уровень.

Неверный тип протокола для данного объекта Socket.

Запрос на отправку или получение данных отклонен, так как объект Socket уже закрыт.

Произошла неопознанная ошибка объекта Socket.

Указанный тип сокета не поддерживается в данном семействе адресов.

Операция Socket выполнена успешно.

Подсистема сети недоступна.

Истекло время ожидания попытки подключения, или произошел сбой при отклике подключенного узла.

Слишком много открытых сокетов в основном поставщике сокета.

Не удалось разрешить имя узла. Повторите попытку позже.

Указанный класс не найден.

Версия основного поставщика сокета выходит за пределы допустимого диапазона.

Операция на незаблокированном сокете не может быть закончена немедленно.

Комментарии

Большинство из этих ошибок возвращается базовым поставщиком сокета.

Источник

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

1

07.06.2020, 05:02. Показов 7512. Ответов 0

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63

<?php
function SocketServer($limit = 0) {
    $starttime = time();
    $data = '';
    echo 'SERVER START' . PHP_EOL;
 
    echo 'Socket create...' . PHP_EOL;
    $socket = socket_create(AF_INET, SOCK_STREAM, SOL_TCP);
 
    if (false === $socket) {
        die('Error: ' . socket_strerror(socket_last_error()) . PHP_EOL);
    }
 
    echo 'Socket bind...' . PHP_EOL;
    $bind = socket_bind($socket, 'animalsearch.space', 8080); // привязываем к ip и порту
    if (false === $bind) {
        die('Error: ' . socket_strerror(socket_last_error()) . PHP_EOL);
    }
 
    echo 'Set options...' . PHP_EOL;
    // разрешаем использовать один порт для нескольких соединений
    $option = socket_set_option($socket, SOL_SOCKET, SO_REUSEADDR, 1);
    if (false === $option) {
        die('Error: ' . socket_strerror(socket_last_error()) . PHP_EOL);
    }
 
    echo 'Listening socket...' . PHP_EOL;
    $listen = socket_listen($socket); // слушаем сокет
    if (false === $listen) {
        die('Error: ' . socket_strerror(socket_last_error()) . PHP_EOL);
    }
 
    while (true) { // бесконечный цикл ожидания подключений
        echo 'Waiting for connections...' . PHP_EOL;
        $connect = socket_accept($socket); // зависаем, пока не получим ответа
        if ($connect !== false) {
            echo 'Client connected...' . PHP_EOL;
            echo 'Send message to client...' . PHP_EOL;
            
                if (false === ($recievedmessage = socket_read($socket, 1000, PHP_NORMAL_READ))) {
                echo "Не удалось выполнить socket_read(): причина: " . socket_strerror(socket_last_error($socket)) . "n";}
            
        } else {
            echo 'Error: ' . socket_strerror(socket_last_error()) . PHP_EOL;
            usleep(1000);
        }
 
        // останавливаем сервер после $limit секунд
        if ($limit && (time() - $starttime > $limit)) {
            echo 'Closing connection...' . PHP_EOL;
            socket_close($socket);
            echo 'SERVER STOP' . PHP_EOL;
            return;
        }
    }
}
 
error_reporting(E_ALL); // выводим все ошибки и предупреждения
set_time_limit(0);      // бесконечное время работы скрипта
ob_implicit_flush();    // включаем вывод без буферизации
 
// Запускаем сервер в работу, завершение работы через 60 секунд
SocketServer(60);

__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь

0