question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed writing to socket

See original GitHub issue

Hey guys, getting enigma up and running using a docker-compose and I’ve gotten the server deployed but I’m having some issues.

Once Engima is up and running I try to telnet to the BBS and it connects, shows the “Connected to enigma” screen for about a half second then immediately disonnects

Checking the logs I see these following errors

{"name":"ENiGMA½ BBS","hostname":"885874a73efe","pid":18,"nodeId":1,"sessionId":"l9UVvMJyXkr","level":50,"err":{"message":"Object does not exist: No menu entry for \"telnetConnected\"","name":"EnigError","stack":"EnigError: Object does not exist: No menu entry for \"telnetConnected\"\n at Object.DoesNotExist (/enigma-bbs/core/enig_error.js:31:52)\n at locateMenuConfig (/enigma-bbs/core/menu_util.js:32:40)\n at nextTask (/enigma-bbs/node_modules/async/dist/async.js:4576:27)\n at Object.waterfall (/enigma-bbs/node_modules/async/dist/async.js:4587:9)\n at Object.awaitable [as waterfall] (/enigma-bbs/node_modules/async/dist/async.js:208:32)\n at getMenuConfig (/enigma-bbs/core/menu_util.js:24:11)\n at getMenuConfiguration (/enigma-bbs/core/menu_util.js:60:17)\n at nextTask (/enigma-bbs/node_modules/async/dist/async.js:4576:27)\n at Object.waterfall (/enigma-bbs/node_modules/async/dist/async.js:4587:9)\n at Object.awaitable [as waterfall] (/enigma-bbs/node_modules/async/dist/async.js:208:32)","code":-33002},"msg":"Object does not exist: No menu entry for \"telnetConnected\"","time":"2021-05-18T00:57:41.448Z","v":0} {"name":"ENiGMA½ BBS","hostname":"885874a73efe","pid":18,"level":40,"error":"write after end","msg":"Failed writing to socket","time":"2021-05-18T00:57:41.449Z","v":0} {"name":"ENiGMA½ BBS","hostname":"885874a73efe","pid":18,"level":40,"error":"Cannot call write after a stream was destroyed","msg":"Failed writing to socket","time":"2021-05-18T00:57:41.450Z","v":0} {"name":"ENiGMA½ BBS","hostname":"885874a73efe","pid":18,"level":40,"error":"Cannot call write after a stream was destroyed","msg":"Failed writing to socket","time":"2021-05-18T00:57:41.450Z","v":0} {"name":"ENiGMA½ BBS","hostname":"885874a73efe","pid":18,"level":40,"modInfo":{"name":"Telnet","desc":"Telnet Server v2","author":"NuSkooler","isSecure":false,"packageName":"codes.l33t.enigma.telnet.server.v2"},"error":"write after end","msg":"Client socket error","time":"2021-05-18T00:57:41.450Z","v":0}

I created a pastebin for my docker compose here: https://pastebin.com/Xp8iW90F

Note that PUID 113 is a system user that owns the enigma-bbs folder

not sure how to approach this, any help is appreciated thanks!

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
matthew-parlettecommented, Nov 28, 2021

I just got around this today, if you are using the docker container and the instructions to mount the various directories, then you most likely have an empty art directory in your container.

To fix this, I copied all of the art files (keeping the directory structure for the themes) from the repo into my art directory that is mounted in the docker container as /enigma-bbs/art.

There are some ways to fix the docker container to work around this, so I’ll try to get something in place and add a PR, but this workaround did the trick for me.

Let me know if you need any more details!

0reactions
NuSkoolercommented, Apr 8, 2022

I’ll try start looking at this soon, but definitely welcome help!

@jamespdaily did you try the updates?

Read more comments on GitHub >

github_iconTop Results From Across the Web

ERROR writing to socket · Issue #30 - GitHub
I've try to make the binary examples work on OS X Maverick (10.9.1) and linux, neither worked. I always get errors like: new...
Read more >
Socket TCP connection write failure - java - Stack Overflow
In windows/linux a successful send completion indicates the buffer is copied to the kernel mode socket buffer.
Read more >
ndmpcopy fails by error "Write to socket failed"
Issue. NetBackup NDMP backup fails by error " Write to socket failed ". " Interrupted system call " and " ...
Read more >
A socket write error occurs during application deployment with ...
As code is deployed to a server, the server can create a socket write error to WPSDB for an XA transaction. The log...
Read more >
STATUS CODE 24: Socket write failed - Veritas
Problem. A write operation to a TCP socket failed on a Windows client. · Error Message. Client bpbkar logs: · Cause. There are...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found