Tutorial Starbound Server Management Console Release

Interesting, there are a few possibilities for that:

Legit:
If people log in from the same subnet, they will show up as the same IP. For example, 3 people all playing from the same house using the same router will all get IP x.x.x.x, no way to tell them apart. The same thing happens if someone opens multiple clients from the same machine.

Bug:
People are getting added, but not removed properly. If refreshing fixes it, then its probably this. Next time this happens, can you please confirm that the players in question are no longer on the server?

 

Hmmm it doesn't seem like they are not being removed properly as when I refresh I still have the same amount of players but they still have duplicate IPs. For example 9 people currently have the same IP then 5 other people have my IP even though they aren't in the same house, it's definitely some sort of weird bug... Possibly it may just not updating properly or something? :/

 

Download
https://googledrive.com/host/0B5a6CpXW311jQUdKU0VyV04waHc

v0.44
1230AM EST 12/30/2013

• Global announce when players join and leave
  • Disable it by editing the ISSMConsole.properties file and setting "ANNOUNCE_PLAYERS_JOINING_LEAVING=false"
• More bug fixes
  • Long packets are now properly encoded, this fixes MOTD length bug
  • Player file properly created again

 

Godly! However Icer, can you please tell us the errors you're restarting on. I don't want it to conflict what I have or don't have. I have yet to see it actually auto restart on it's own yet, without my .bat interference.

Edit: Can you make it so we can change the console name on the chat?

 

Hmmm I still don't get join/leaving messages or the MOTD show up in game... is there something i'm missing? >_<

 

Icer, new problems cropped up from 0.42 to 0.44 upgrade. It's picking up false positive errors, not sure which one because I am flooded with them. Also my clients are being reaped consistently, about like 6-7 of them at a time every minute or so. Similar thing that happens with starlight before.

 

Strange, i'm not getting that...

OS?

 

These are the current strings I am detecting as FATAL and rebooting the server on. Note: This only causes the reboot if you have the option set to TRUE in the .properties file.

"Error: TcpServer will close",
"Error: UniverseServer exception caught",
"DBExeption : Error",
"Error: Access violation detected at"

 

The latter 3 can be induced by mods easily, which are exactly why I'm getting false positives. I'll stick to my own error detection for now, but I still don't know why multiple clients were being reaped at a certain interval though. I don't get any other log other than people getting reaped over and over in one go under Windows Server 2008 R2

 

@Icer
http://community.playstarbound.com/...too-many-open-files.54833/page-2#post-1617768

also check this out, unknown if you use it but been using this patchover to fix the socket issue as well

 

I'm under Windows Server 2008, so I gotta pass on that~

 

The multiple world issue isn't fixed either.

 

yeah, i've seen the multi world issue... ughhh... seems people need to write their own server exe's just to fix all the server bugs... using a custom exe now...

 

Download
https://googledrive.com/host/0B5a6CpXW311jRjdfWDZDOWw0M0U

v0.45
7PM EST 12/30/2013

• Commands
  • Admins
    • Commands no longer require Admin Password!
    • Messages are displayed regarding the success of the command
    • "Command not found" no longer sent to client when valid command is used
  • All players
    • /players
      • Prints out a list of currently connected users
    • /version
      • Prints out the version of the server
• Server status JSON
  • Servers can now be queried for their status with an HTTP call
    • http://{server.IP}:21025/status
    • No further port forwarding required
    • Still beta, different browsers may have different results
  • JSON includes
    • Player Count
    • List of players
    • Console version
    • Server IP
    • Server version
    • Server Status
    • Server Name
      • Set in ISSMConsole.properties file; SERVER_NAME={name of server}
      • Only currently used in status JSON
    • Server Message
      • Set in ISSMConsole.properties file; SERVER_MESSAGE={server message}
      • Only currently used in status JSON

 

Great work! =)

I'm still not able to get MOTD.
/players says no such commands.
/version says no such commands.

 

I see these every now and then in 0.43 to 0.45 not 0.42, but it's not exactly at the time when it's disconnecting people:

Warn: I/O error in to 127.0.0.1:52834 NetSocket write loop or device closed: NetworkException: tcp send error to 127.0.0.1:52834 0 : (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

)
006FED05 (E:/Steamworks/Starbound/git/starbound/source/core/StarIODevice.hpp:9)
0043C2C3 (E:/Steamworks/Starbound/git/starbound/source/game/StarNetSocket.cpp:289)
0043D2D0 (E:/Steamworks/Starbound/git/starbound/source/game/StarNetSocket.cpp:235)
008646DC (E:/Steamworks/Starbound/git/starbound/source/core/StarThread_windows.cpp:74)
7665336A
779A9F72
779A9F45

When the server is disconnecting people, the log is only showing something like these, it can be singularly or en massed:

Info: Client 'Kuf'Ell' 7> (127.0.0.1:52834) disconnected
Info: Reaping client 'Kuf'Ell' 7> (127.0.0.1:52834) connection
Info: closing 127.0.0.1:52861 (1392)
Info: Client 'Azie' <61> (127.0.0.1:52861) disconnected
Info: Reaping client 'Azie' <61> (127.0.0.1:52861) connection
Warn: Perf: UniverseServer::run.innerloop millis: 177
Info: Client 'NathanH1717' <1> (127.0.0.1:52843) disconnected
Info: closing 127.0.0.1:52843 (636)
Info: closing 127.0.0.1:52843 (636)
Info: Reaping client 'NathanH1717' <1> (127.0.0.1:52843) connection

 

well, 0.43 is when I started packet injection. I can't reproduce your problem on my server though

When people DC, is there a chat message being sent to them? System restarting / player joining?

 

That doesn't make any sense. You allowed the auto-config to set your server port to 21024, right? If so, then all comms are going through ISSMConsole and messages should be getting published. I'll look into it further tomorrow.

Its possible there is something I'm missing in the packet inspection.

Can you also confirm that it says v0.45 on the web console?

 

Connection with server is no longer valid - or something of the sort it seems what they're saying. Even though I am connecting to the server with my client one country apart, it never seem to have disconnected me. Only everyone else.

/players and /version works on my end. I think /player should be a valid command too.

Edit: It also seems to leave some ghost connections as well. Some players report seeing their doubles.

Edit2: I actually forgot to report this too. I don't think the status page :21025/status was working either. Unless I had to use port 20124 which I forgot to check lol.

 

I have added a few more protections to my code to ensure that I don't inadvertently influence any connections between client and server. I loaded 8 clients on my local box and connected to my server. After about 10 minutes, one of the clients randomly disconnected. I will try to do some more testing, unfortunately as we all know, the Starbound Server code still has some work ahead of it, so I can't rule out the possible of an unstable server regardless of what my code does.

---------------

Status just isn't really ready yet. The problem is that when Starbound clients connect, they don't send any data; but when a browser connects, it sends the GET.

So I can try to read some the connection, which works great for browsers, but times out clients. I went with the second method which relays on the downstream service telling me that there is data to be read. As you have noticed, this is not always guaranteed. I'm going to try and find a more satisfactory method tomorrow.