-
Type:
Bug
-
Resolution: Invalid
-
Priority:
Minor
-
None
-
Affects Version/s: None
-
Environment:
AWS m3.large 2xCPU 7.5GB RAM running Ubuntu 18.04.2 LTS
openjdk version "1.8.0_191"
OpenJDK Runtime Environment (build 1.8.0_191-8u191-b12-2ubuntu0.18.04.1-b12)
OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)Arguments: -XX:+UseG1GC -Xmx4G -Xms4G -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
Plugins: GriefPrevention v16.7.1
AWS m3.large 2xCPU 7.5GB RAM running Ubuntu 18.04.2 LTS openjdk version "1.8.0_191" OpenJDK Runtime Environment (build 1.8.0_191-8u191-b12-2ubuntu0.18.04.1-b12) OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode) Arguments: -XX:+UseG1GC -Xmx4G -Xms4G -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Plugins: GriefPrevention v16.7.1
-
1.14-R0.1-SNAPSHOT
-
Yes
When launching the server from an AWS Ubuntu 18.04.02 VM command line in a screen session:
[14:44:55] [Server console handler/ERROR]: Exception handling console input java.io.IOException: Resource temporarily unavailable at java.io.FileInputStream.readBytes(Native Method) ~[?:1.8.0_191] at java.io.FileInputStream.read(FileInputStream.java:255) ~[?:1.8.0_191] at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) ~[?:1.8.0_191] at java.io.BufferedInputStream.read(BufferedInputStream.java:265) ~[?:1.8.0_191] at org.bukkit.craftbukkit.libs.jline.internal.NonBlockingInputStream.read(NonBlockingInputStream.java:169) ~[spigot-1.14.jar:git-Spigot-1eece4f-a584320] at org.bukkit.craftbukkit.libs.jline.internal.NonBlockingInputStream.read(NonBlockingInputStream.java:137) ~[spigot-1.14.jar:git-Spigot-1eece4f-a584320] at org.bukkit.craftbukkit.libs.jline.internal.NonBlockingInputStream.read(NonBlockingInputStream.java:246) ~[spigot-1.14.jar:git-Spigot-1eece4f-a584320] at org.bukkit.craftbukkit.libs.jline.internal.InputStreamReader.read(InputStreamReader.java:261) ~[spigot-1.14.jar:git-Spigot-1eece4f-a584320] at org.bukkit.craftbukkit.libs.jline.internal.InputStreamReader.read(InputStreamReader.java:198) ~[spigot-1.14.jar:git-Spigot-1eece4f-a584320] at org.bukkit.craftbukkit.libs.jline.console.ConsoleReader.readCharacter(ConsoleReader.java:2145) ~[spigot-1.14.jar:git-Spigot-1eece4f-a584320] at org.bukkit.craftbukkit.libs.jline.console.ConsoleReader.readLine(ConsoleReader.java:2349) ~[spigot-1.14.jar:git-Spigot-1eece4f-a584320] at net.minecraft.server.v1_14_R1.DedicatedServer$2.run(DedicatedServer.java:95) [spigot-1.14.jar:git-Spigot-1eece4f-a584320]
I am not able to reproduce this is anything other than this specific platform. I tried a regular Ubuntu 18.04.2 VM on my PC without issue, an Ubuntu 16.04.2 running Pufferpanel, and Windows, and it worked in all of them. It seems specific to the AWS flavor of Ubuntu, but not Ubuntu 16.04.2 which was working before I rebuilt the instance. I did look around to see if this was reported before, but I did not see it in previous bug reports (SPIGOT-3292) or web searches, so I apologize if it is known information. Disregard if so.
Thank you for your consideration.
Edit: Cleaned up the text formatting in the code.
[SPIGOT-4845] Server console handler/ERROR: Exception handling console input
Equilateral
added a comment - So I notice the part where it says BuildTools 81 and above will now apply the workaround, I'm using 101 to build with currently. But when I built this instance fresh, I did use the latest version of Oracle Java, but then thinking that might be the issue I removed it and installed OpekJDK 8. As far as I recall, the other places I used was just OpenJDK 8 straight from the get-go, so that probably makes sense, but for your consideration anyway in case someone else stumbles into the bar I did. 
Thank you.
Equilateral
added a comment - So I notice the part where it says BuildTools 81 and above will now apply the workaround, I'm using 101 to build with currently. But when I built this instance fresh, I did use the latest version of Oracle Java, but then thinking that might be the issue I removed it and installed OpekJDK 8. As far as I recall, the other places I used was just OpenJDK 8 straight from the get-go, so that probably makes sense, but for your consideration anyway in case someone else stumbles into the bar I did.
Thank you. 
Sorry my bad, linked the wrong thread.
https://www.spigotmc.org/threads/ubuntu-18-04-bad-kernel-update.357871
is the relevant thread