-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP32 BLE/WiFi throws an error [E][WiFiClient.cpp:395] write(): fail on fd 54, errno: 11, "No more processes" - still not resolved #6129
Comments
I also got this error but in my case, it's a Wi-Fi AP as webserver by using WiFiManager. After started webserver, ESP writing response to client. This error showing up then crash. This only happended with latest release(2.0.2). Downgrade to 2.0.1, It works fine. |
I have exactly the same issue with my code. I use MQTT, BLE, and WiFi together on an ESP32. It runs for a while, and then resets at a quasi-random time. @MomePP: I didn't get your comment, I believe the WiFiClient is in the board definitions file, and no version 2.0.2 there. Or am I missing something? |
I didn't use the WiFiManager. h #include <WiFi.h> I use only these files in my code |
I have these: #include <WiFi.h> Different MQTT library, by the way. |
Sorry for the confusion. What I mean is version of ESP32 Arduino Core that i used and In my case i used |
Thanks, I changed to 2.0.1 now, let's see what happens. It usually takes less than 24 hours before it throws the error. |
Oops, it did it again. Changing the Arduino Core made no difference. What I notice is that some processes seem to struggle:
|
Hi, changed some library files and their versions. Still the issue available. Anybody identified any possible solutions? I reinstalled the Arduino ide, tried different versions of library files. No use... It is still makes me mad. |
Not a permanent solution but some how I am able to handle it. I am repeatedly sending data from esp to server, So this problem made some gap in the communication. As the error printed - [E][WiFiClient.cpp:395] write(): fail on fd 54, errno: 11, "No more processes" , I am able to point out the error code in the wificlient.cpp file. Upon printing the log, I made the ESP to restart. So ESP will get in to the active loop within few seconds rather than printing the error log in console for more than 10 seconds. But looking for a permanent solution. |
any solution for this. ? |
Hello all contributors, can you please retest this on v2.0.3-rc1? |
I'm closing the issue as expired due to no answer. If needed, please reopen it. Thanks for understanding. |
I do have a similar issue with chunked data (nothing related with BLE which i dont know what it is mentioned in this issue)
Seems like after the trailing sequence some data is still present in the buffer
Is it a server-side issue? |
Hey @VojtechBartoska, I am using 2.0.3 (stable) and experiencing the same issue. |
I'm reopening the issue and we will take a look on it. |
The issue is still existing and I am restarting the esp to overcome this quickly. Looking for a permanent solution. Using able scan, collection the Bluetooth tag id and their rssi value, publishing it using mqtt. |
Guys, please test PR #8541 and let me know if it works for you. I just hope it doesn't create a new issue :D |
Hello @PilnyTomas |
@PilnyTomas Works like a charm. Thanks for the effort! |
I think i found a workraround until all packages are updated with [email protected] in platformio.ini |
Same issue, also wifi drops out and fails to reconnect, and debugging of course also stopped logging sigh. |
will be fully addressed again in #8699 |
I get the same issuem I'm using WebSockets @ 2.4.1 and WiFi @ 2.0.0 I'm pretty sure that |
Hi, Is this issue is fully addressed? and in which version? I am still getting the same error in e[email protected] - Working with platformio. Also tried this with the following but no luck, |
version 2.0.14 of Arduino core |
I also have the same problem. |
hi guys. any update on this issue? I am having the same trouble here, |
This also happened to me. I noticed that also sometimes when I attempt to create a new task, the task creation fails. With error "not enough memory". I tried to reduce the size of the stacks of the tasks that I'm creating and it resolved both problems. New tasks are now always get created and this message do not appear anymore. You should of course not reduce the stack size too much so you'll not get stack overflow. Which is another annoying problem. |
How to completely solve this problem at the bottom level, apart from sending a small amount of data? |
I think this issue is caused when most of the memory is allocated and the system can't create new objects in order to perform its functions. Try to reduce your memory consumption. Like I did with reducing the size of tasks stack depth. You can check your task stack high watermark using uxTaskGetStackHighWaterMark() and see if you can reduce the stack depth of your tasks. |
Board
ESP32 devkit v4
Device Description
I am using ESP32 devkit v4
Hardware Configuration
no GPIO connections, ESP32 scans the BLE tags and sends their id and rssi values over mqtt
Version
latest master
IDE Name
Platform IO also uses arduino IDE 1.8.57.0
Operating System
Windows10
Flash frequency
80MHz
PSRAM enabled
no
Upload speed
115200
Description
ESP32 scans the available BLE tags and publishing the collected information over mqtt (Raspberry Pi 4 B is the broker). It was working fine in the last month.
now it started to print error in the console something like [E][WiFiClient.cpp:395] write(): fail on fd 54, errno: 11, "No more processes" and after some time it restarts. BLE scan runs in a freeRTOS task. MQTT publishing is in loop().
it works fine for around 5min(time interval is random) then fails and reboot as the log mentioned.
[E][WiFiClient.cpp:395] write(): fail on fd 54, errno: 11, "No more processes"
[E][WiFiClient.cpp:395] write(): fail on fd 54, errno: 113, "Software caused connection abort"
Sketch
will provide if requested.
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: