Server errno 32 ? ?

[RandomEvent]

Ok, I keep getting a error no 32 on my server hosted by the smelter.
Very nice, but what is it.
Is there a list of error numbers somewhere?

Logs on console show this.

17.09 01:42:04 [Multicraft] Server stopped
17.09 01:42:02 [Multicraft] Error writing to server: [Errno 32] Broken pipe
17.09 01:42:02 [Multicraft] Error writing to server: [Errno 32] Broken pipe
17.09 01:42:02 [Multicraft] Stopping server!
17.09 01:42:02 [Multicraft] Server shut down
17.09 01:42:01 [Server] INFO [SERVER] SERVER SHUTDOWN. ServerState saved!
17.09 01:42:01 [Server] INFO [SHUTDOWN] database closed successfully
17.09 01:42:01 [Multicraft] Skipped 148 lines due to rate limit (50/s)
17.09 01:42:00 [Server] INFO [SERVER] SERVER SECTOR WRITING STARTED #1800 active: true at (567, -4, -48) (ents: 0)
17.09 01:42:00 [Server] INFO [SERVER] SERVER SECTOR WRITING STARTED #2074 active: true at (565, -3, -48) (ents:

 

[0ldSkull]

"Broken pipe" is the description for that error. Basically it means that the socket being written to is no longer connected. My assumption from what you've posted is that this doesn't reflect a problem since it occurs after the server was shut down. (The timestamps in your post are in descending order.)

Those particular errors also appear to be from Multicraft, not the Starmade logs.

 

[RandomEvent]

Ah ok, thanks for the guidence. You are correect about the posted data, it is a copy paste direct from the multicraft console view.

This happens on a fairly regular basis so I will have a careful look to the actual log files next time and add them here.

I set a regular "/shutdown" command in the multicraft interface to happen every 3 hours.
Sometimes it reboots the game server, sometimes it just hangs (but not completely so does not trigger the server reboot on failure provided by theSmelter host).

 

[RandomEvent]

Hello again,

Well the server seems to have shut down again for no reason I can see.
This time I have attached logs of the last state and a copy from the multicraft consule.

Am using the standard "/shutdown 300" issued from the multicraft Command and Scheduled Tasks provision.
I have programmed this task to be run every 3 hours to reboot the server.
If someone could look and tell me why sometimes my server reboots ok and some not, I would be very grateful.
Is the issue perhaps nothing to do with starmade and instead my host and thier multicraft interface?
Or, is this an issue/bug with the server empty of people? It seems whenever I am connected and ingame the server reboots normally.

Also added the current state of the server as shown in theSmelter multicraft interface.

 

[Valck]

Hello again,

Well the server seems to have shut down again for no reason I can see.

[2015-09-21 13:41:40] [SERVER-LOCAL-ADMIN] END; ERROR: command not regognize (use /chat to broadcast)
[2015-09-21 13:42:00] [SERVER] SCHEDULED SHUTDOWN NOW EXECUTING. EXITING SERVER!

looks like a manual shutdown, or at least some (mis-)typed a command at the local console

EDIT: Actually, I'd guess this part

[Server] INFO [SERVER-LOCAL-ADMIN] END; ERROR: command not regognize (use /chat to broadcast)

indicates something related to the way external (custom? Multicraft?) scripts interact with the SM server process; there might be something wonky there.


Also, as

"Broken pipe" is the description for that error. Basically it means that the socket being written to is no longer connected. My assumption from what you've posted is that this doesn't reflect a problem since it occurs after the server was shut down. (The timestamps in your post are in descending order.)

Those particular errors also appear to be from Multicraft, not the Starmade logs.

this is not an error with StarMade, and maybe you should look for support on the Multicraft forums if such at thing exists.

 

[RandomEvent]

Thanks Valck

I probably cannot do much about this but I will raise a ticket with my host to see what they recommend.
The END command issued (as you said) by either the host or Multicraft is not under my control.
Might take awhile but I will update this thread as I find out more (if I find more).