Unbekannte Meldung im Screen.

Sound, Digitalkameras, TV+Video und Spiele.
Antworten
DebianGnu
Beiträge: 2
Registriert: 19.01.2019 15:55:25

Unbekannte Meldung im Screen.

Beitrag von DebianGnu » 19.01.2019 16:25:24

Hallo :-)

habe vor kurzen einen VServer eingerichtet, auf welchem Minecraft (Java-Version) läuft.

Außer wenigen Warnungen läuft es auch problemlos, aber darauf möchte ich jetzt nicht eingehen, es sei denn jemand weiss dafür ebenfalls die Ursache, dann kann das gerne hier geschildert werden. ;-)

Nun zum eigentlichen "Problem", wobei ich nicht sicher bin ob es überhaupt eins ist.^^

Nach dem ersten start und einigen neustarts des MC-Servers habe ich in der Screensitzung in dem ser MC-Server läuft die Tastenkombination Strg+^ gedrückt, weil ich eine Tastenkombination falsch Interpretiert hatte.

Dann wurde mir folgendes angezeigt:

Code: Alles auswählen

"C2 CompilerThread2" #7 daemon prio=9 os_prio=0 tid=0x00007f1ba420c000 nid=0x1a1 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread1" #6 daemon prio=9 os_prio=0 tid=0x00007f1ba420a800 nid=0x1a0 waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"C2 CompilerThread0" #5 daemon prio=9 os_prio=0 tid=0x00007f1ba4207800 nid=0x19f waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Signal Dispatcher" #4 daemon prio=9 os_prio=0 tid=0x00007f1ba4206000 nid=0x19e waiting on condition [0x0000000000000000]
   java.lang.Thread.State: RUNNABLE

"Finalizer" #3 daemon prio=8 os_prio=0 tid=0x00007f1ba41d3800 nid=0x19d in Object.wait() [0x00007f1b8dae1000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006c001d3a0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
        - locked <0x00000006c001d3a0> (a java.lang.ref.ReferenceQueue$Lock)
        at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)
        at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:216)

"Reference Handler" #2 daemon prio=10 os_prio=0 tid=0x00007f1ba41d1000 nid=0x19c in Object.wait() [0x00007f1b8dbe2000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000006c001d558> (a java.lang.ref.Reference$Lock)
        at java.lang.Object.wait(Object.java:502)
        at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
        - locked <0x00000006c001d558> (a java.lang.ref.Reference$Lock)
        at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)

"VM Thread" os_prio=0 tid=0x00007f1ba41c7800 nid=0x19b runnable

"GC task thread#0 (ParallelGC)" os_prio=0 tid=0x00007f1ba401f800 nid=0x193 runnable

"GC task thread#1 (ParallelGC)" os_prio=0 tid=0x00007f1ba4021800 nid=0x194 runnable

"GC task thread#2 (ParallelGC)" os_prio=0 tid=0x00007f1ba4023000 nid=0x195 runnable

"GC task thread#3 (ParallelGC)" os_prio=0 tid=0x00007f1ba4025000 nid=0x196 runnable

"GC task thread#4 (ParallelGC)" os_prio=0 tid=0x00007f1ba4026800 nid=0x197 runnable

"GC task thread#5 (ParallelGC)" os_prio=0 tid=0x00007f1ba4028800 nid=0x198 runnable

"GC task thread#6 (ParallelGC)" os_prio=0 tid=0x00007f1ba402a000 nid=0x199 runnable

"GC task thread#7 (ParallelGC)" os_prio=0 tid=0x00007f1ba402c000 nid=0x19a runnable

"VM Periodic Task Thread" os_prio=0 tid=0x00007f1ba421c000 nid=0x1a4 waiting on condition

JNI global references: 2502

Heap
 PSYoungGen      total 1327104K, used 404451K [0x000000076ab00000, 0x00000007c0000000, 0x00000007c0000000)
  eden space 1265664K, 28% used [0x000000076ab00000,0x0000000780a7c200,0x00000007b7f00000)
  from space 61440K, 72% used [0x00000007bc100000,0x00000007bec7ca28,0x00000007bfd00000)
  to   space 66048K, 0% used [0x00000007b7f00000,0x00000007b7f00000,0x00000007bbf80000)
 ParOldGen       total 699392K, used 85585K [0x00000006c0000000, 0x00000006eab00000, 0x000000076ab00000)
  object space 699392K, 12% used [0x00000006c0000000,0x00000006c5394458,0x00000006eab00000)
 Metaspace       used 41792K, capacity 44644K, committed 44888K, reserved 1087488K
  class space    used 5727K, capacity 6525K, committed 6528K, reserved 1048576K
Dann musste ich die Screensitzung beenden, und den MC-Server wieder starten.

Seitdem wird bei jedem starten/neustarten des MC-Servers immer folgendes angezeigt:

Code: Alles auswählen

Jan 19, 2019 3:59:26 PM io.netty.util.internal.MacAddressUtil defaultMachineId
Was ist hier passiert, und wie kann ich das beheben, bzw. muss das behoben werden?
Hab echt keinen plan.^^

Hier noch zwei logs des MC-Servers, jeweils eins vor und eins nach dem geschehen:

Vorher:

Code: Alles auswählen

[19:43:11] [main/WARN]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
[19:43:11] [main/WARN]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[19:43:11] [main/WARN]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
[19:43:11] [main/WARN]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
[19:43:11] [main/WARN]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[19:43:11] [main/INFO]: Loaded 0 recipes
[19:43:11] [main/INFO]: Loaded 0 advancements
[19:43:11] [Server thread/INFO]: Starting minecraft server version 1.13.2
[19:43:11] [Server thread/INFO]: Loading properties
[19:43:12] [Server thread/INFO]: Default game type: SURVIVAL
[19:43:12] [Server thread/INFO]: Generating keypair
[19:43:12] [Server thread/INFO]: Starting Minecraft server on 85.214.235.85:25565
[19:43:12] [Server thread/INFO]: Using epoll channel type
[19:43:12] [Server thread/INFO]: Preparing level "world"
[19:43:13] [Server thread/INFO]: Reloading ResourceManager: Default
[19:43:14] [Server thread/INFO]: Loaded 524 recipes
[19:43:14] [Server thread/INFO]: Loaded 571 advancements
[19:43:15] [Server thread/INFO]: Preparing start region for dimension minecraft:overworld
[19:43:15] [Server thread/INFO]: Preparing spawn area: 4%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 8%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 12%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 16%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 20%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 24%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 28%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 32%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 36%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 40%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 44%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 48%
[19:43:16] [Server thread/INFO]: Preparing spawn area: 52%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 56%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 60%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 64%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 68%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 72%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 76%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 80%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 84%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 88%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 92%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 96%
[19:43:17] [Server thread/INFO]: Preparing spawn area: 100%
[19:43:17] [Server thread/INFO]: Time elapsed: 2297 ms
[19:43:17] [Server thread/INFO]: Done (4.406s)! For help, type "help"

Nacher:

Code: Alles auswählen

[16:13:10] [main/WARN]: Ambiguity between arguments [teleport, destination] and [teleport, targets] with inputs: [Player, 0123, @e, dd12be42-52a9-4a91-a8a1-11c01849e498]
[16:13:10] [main/WARN]: Ambiguity between arguments [teleport, location] and [teleport, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[16:13:10] [main/WARN]: Ambiguity between arguments [teleport, location] and [teleport, targets] with inputs: [0.1 -0.5 .9, 0 0 0]
[16:13:10] [main/WARN]: Ambiguity between arguments [teleport, targets] and [teleport, destination] with inputs: [Player, 0123, dd12be42-52a9-4a91-a8a1-11c01849e498]
[16:13:10] [main/WARN]: Ambiguity between arguments [teleport, targets, location] and [teleport, targets, destination] with inputs: [0.1 -0.5 .9, 0 0 0]
[16:13:10] [main/INFO]: Loaded 0 recipes
[16:13:10] [main/INFO]: Loaded 0 advancements
[16:13:10] [Server thread/INFO]: Starting minecraft server version 1.13.2
[16:13:10] [Server thread/INFO]: Loading properties
[16:13:11] [Server thread/INFO]: Default game type: SURVIVAL
[16:13:11] [Server thread/INFO]: Generating keypair
[16:13:11] [Server thread/INFO]: Starting Minecraft server on *:25565
[16:13:11] [Server thread/INFO]: Using epoll channel type
Jan 19, 2019 4:13:11 PM io.netty.util.internal.MacAddressUtil defaultMachineId
WARNUNG: Failed to find a usable hardware address from the network interfaces; using random bytes: 74:6b:5a:08:a4:5f:28:aa
[16:13:11] [Server thread/INFO]: Preparing level "world"
[16:13:11] [Server thread/INFO]: Reloading ResourceManager: Default
[16:13:12] [Server thread/INFO]: Loaded 524 recipes
[16:13:13] [Server thread/INFO]: Loaded 571 advancements
[16:13:13] [Server thread/INFO]: Preparing start region for dimension minecraft:overworld
[16:13:13] [Server thread/INFO]: Preparing spawn area: 4%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 8%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 12%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 16%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 20%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 24%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 28%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 32%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 36%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 40%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 44%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 48%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 52%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 56%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 60%
[16:13:14] [Server thread/INFO]: Preparing spawn area: 64%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 68%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 72%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 76%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 80%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 84%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 88%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 92%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 96%
[16:13:15] [Server thread/INFO]: Preparing spawn area: 100%
[16:13:15] [Server thread/INFO]: Time elapsed: 1629 ms
[16:13:15] [Server thread/INFO]: Done (3.579s)! For help, type "help"

cronoik
Beiträge: 2049
Registriert: 18.03.2012 21:13:42
Lizenz eigener Beiträge: GNU Free Documentation License

Re: Unbekannte Meldung im Screen.

Beitrag von cronoik » 19.01.2019 17:16:30

Hi und willkommen im Forum,

grundsaetzlich solltest du dich vielleicht an ein Forum fuer Minecraft-Administratoren wenden. Wenn du die Warnung allerdings bei google nachschlaegst , dann kommst du zu diesem Bugreport [1] und der sagt das es nicht weiter schlimm ist. Ob jetzt deine gedrueckte Tastenkombination damit etwas zu tun hat, weis ich nicht da ich Minecraft nicht kenne.

[1] https://github.com/netty/netty/issues/6406
Hilf mit unser Wiki zu verbessern!

DebianGnu
Beiträge: 2
Registriert: 19.01.2019 15:55:25

Re: Unbekannte Meldung im Screen.

Beitrag von DebianGnu » 20.01.2019 10:58:56

Danke für die freundliche Begrüßung und deine Hilfe. :-)

Darauf bin ich auch schon gestoßen, nur machte es mich stutzig, das dies erst nach dem drücken der Tastenkombination immer wieder auftritt.
Ich dachte auch erst in einem MC-Forum zu posten, aber da diese Meldung wie gesagt erst kam nachdem ich diese Tastenkombination gedrückt hatte, glaube ich das es mehr mit Debian dem Screen und evtl. noch mit Java zu tun hat, als mit dem MC-Server selbst.

Probleme oder irgendwelche Nachteile konnte ich jedoch bis jetzt nicht feststellen, werd das einfach weiter beobachten.
Falls jemand noch einen Ansatz hat, zögert nicht diesen zu Posten, bin über jede Hilfe dankbar.

Antworten