[Bug][Linux][Dedicated server] Java Exceptions when using nohup + Workaround

[Seoson]

Hello there,

aas the title idciates I've got a problem running StarMade on a dedicated server. While the server itself works more or less good, it is filling up my hardrive with exception messages.

According to "WarSong" (or something similar; I'm very bad at remebering names) that was caused by using the wrong Java VM. I've changed my VM from OpenJDK to Oracles Java to resolve the issue, however nothing changed.

Exception:


java.io.IOException: Bad file descriptor
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:272)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:273)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:154)
at java.io.BufferedReader.readLine(BufferedReader.java:317)
at java.io.BufferedReader.readLine(BufferedReader.java:382)
at org.schema.schine.network.server.ServerController$SystemInListener.run(SourceFile:97)
at java.lang.Thread.run(Thread.java:744)


(There are two more at the very top of the logs, however they should matter since It's only complaining that the settings.cfg and dmidecode files are missing and they only occur once).

Currently the StarMade Server is takes only a few seconds to create hundreds of megabytes of data.

A few technical details:


OS: Debian Wheezy (up-to-date)

Java: starmade_srv@brodowski:~/StarMade$ java -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)

VGA: n/a

Displayserver: n/a


I hope that you can help me.

Please note: I'm not a native speaker. I'm sorry for any spelling and gramma mistakes.

EDIT//

As a workaround I'm redirectiong nohup output to /dev/null and deleting logfiles using a cronjob(Just revoking write permissions to the log directory didn't work). However this is very bad practice and unfortunately I don't have to care about harddrive lifetime since the server is located in a datacenter and my agreemnet does cover such things. If this is a StarMade bug I can provide a login (for developers/staff only) to reproduce the errors.

EDIT2//

This bug can be solved by using screen instead of nohup.

Best regards,

Seoson

 

[Fishbreath]

I noticed that problem, too—it seems to be related to the use of nohup. Running the server with screen doesn\'t pile up the log messages, it doesn\'t look like.

 

[Seoson]

Sounds strange. I will give that a try next time I restart the server.

Thank you!

 

[Seoson]

O.K: That works. I have no clue why so I guess this is a StarMade Bug.

Maybe this should be moved to bugs and a not note should be added that currently StarMade is not compatible with nohup (which is the standard way of executing programms on userlevel in background).

 

[der_scheme]

This does also happen in SP. However, in my case it seems to be a client-side problem.


$ uname -a
Linux kenobi 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar 7 17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ java -version
java version \"1.7.0_51\"
OpenJDK Runtime Environment (fedora-2.4.5.1.fc20-x86_64 u51-b31)
OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)