Serverprobleme (Juni 2016)

[CyD]

Seit letztem Wochenende scheint irgendwas mit dem Minecraftservice nicht mehr zu stimmen. Jeden Tag kommen einige an Crash-Reports dazu: 

Code:

crash-2016-01-26_16.19.46-server.txt
crash-2016-02-01_07.53.54-server.txt
crash-2016-02-05_19.05.51-server.txt
crash-2016-06-01_04.45.33-server.txt
crash-2016-06-05_11.03.12-server.txt
crash-2016-06-09_02.44.47-server.txt
crash-2016-06-09_09.47.07-server.txt
crash-2016-06-26_21.40.39-server.txt
crash-2016-06-27_00.34.25-server.txt
crash-2016-06-27_10.53.34-server.txt
crash-2016-06-27_23.55.09-server.txt
crash-2016-06-28_20.01.27-server.txt
crash-2016-06-28_21.44.44-server.txt
crash-2016-06-29_00.39.36-server.txt
crash-2016-06-29_19.19.55-server.txt
crash-2016-06-29_21.37.34-server.txt
crash-2016-06-29_23.05.16-server.txt
crash-2016-06-30_00.35.07-server.txt

Ich hab den Server bereits aktualisiert und neu gestartet, jedoch bleibt der Fehler wohl weiterhin bestehen.

Hier der letzte Crashreport: 

Code:

---- Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.

Time: 30.06.16 00:35
Description: Watching Server

java.lang.Error
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.PrintStream.write(PrintStream.java:482)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
at java.io.PrintStream.write(PrintStream.java:527)
at java.io.PrintStream.print(PrintStream.java:669)
at java.io.PrintStream.println(PrintStream.java:823)
at java.lang.Throwable$WrappedPrintStream.println(Throwable.java:748)
at java.lang.Throwable.printStackTrace(Throwable.java:658)
at java.lang.Throwable.printStackTrace(Throwable.java:643)
at java.lang.Throwable.printStackTrace(Throwable.java:634)
at azy.a(SourceFile:137)
at azv.a(SourceFile:45)
at ls.a(SourceFile:926)
at ls.a(SourceFile:879)
at net.minecraft.server.MinecraftServer.a(SourceFile:372)
at net.minecraft.server.MinecraftServer.C(SourceFile:572)
at net.minecraft.server.MinecraftServer.run(SourceFile:458)
at java.lang.Thread.run(Thread.java:745)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Server Watchdog
Stacktrace:
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.PrintStream.write(PrintStream.java:482)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
at java.io.PrintStream.write(PrintStream.java:527)
at java.io.PrintStream.print(PrintStream.java:669)
at java.io.PrintStream.println(PrintStream.java:823)
at java.lang.Throwable$WrappedPrintStream.println(Throwable.java:748)
at java.lang.Throwable.printStackTrace(Throwable.java:658)
at java.lang.Throwable.printStackTrace(Throwable.java:643)
at java.lang.Throwable.printStackTrace(Throwable.java:634)
at azy.a(SourceFile:137)
at azv.a(SourceFile:45)
at ls.a(SourceFile:926)
at ls.a(SourceFile:879)
at net.minecraft.server.MinecraftServer.a(SourceFile:372)
at net.minecraft.server.MinecraftServer.C(SourceFile:572)

-- Thread Dump --
Details:
Threads: "Netty Epoll Server IO #7" Id=26 RUNNABLE (in native)
at io.netty.channel.epoll.Native.epollWait(Native Method)
at io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:194)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:219)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)


"Netty Epoll Server IO #6" Id=25 RUNNABLE (in native)
at io.netty.channel.epoll.Native.epollWait(Native Method)
at io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:194)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:219)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)


"Netty Epoll Server IO #5" Id=24 RUNNABLE (in native)
at io.netty.channel.epoll.Native.epollWait(Native Method)
at io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:194)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:219)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)


"Netty Epoll Server IO #4" Id=23 RUNNABLE (in native)
at io.netty.channel.epoll.Native.epollWait(Native Method)
at io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:194)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:219)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)


"File IO Thread" Id=37 TIMED_WAITING
at java.lang.Thread.sleep(Native Method)
at bbu.c(SourceFile:51)
at bbu.run(SourceFile:30)
at java.lang.Thread.run(Thread.java:745)


"Netty Epoll Server IO #3" Id=22 RUNNABLE (in native)
at io.netty.channel.epoll.Native.epollWait(Native Method)
at io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:194)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:219)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)


"Netty Epoll Server IO #2" Id=21 RUNNABLE
at io.netty.channel.epoll.Native.epollWait(Native Method)
at io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:194)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:219)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)


"Java2D Disposer" Id=32 WAITING on java.lang.ref.ReferenceQueue$Lock@7262b2ba
at java.lang.Object.wait(Native Method)
-  waiting on java.lang.ref.ReferenceQueue$Lock@7262b2ba
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at sun.java2d.Disposer.run(Disposer.java:145)
at java.lang.Thread.run(Thread.java:745)


"Server Watchdog" Id=31 RUNNABLE
at sun.management.ThreadImpl.dumpThreads0(Native Method)
at sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:446)
at le.run(SourceFile:43)
at java.lang.Thread.run(Thread.java:745)


"Netty Epoll Server IO #1" Id=20 RUNNABLE (in native)
at io.netty.channel.epoll.Native.epollWait(Native Method)
at io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:194)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:219)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)


"Netty Epoll Server IO #0" Id=19 RUNNABLE (in native)
at io.netty.channel.epoll.Native.epollWait(Native Method)
at io.netty.channel.epoll.EpollEventLoop.epollWait(EpollEventLoop.java:194)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:219)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116)
at java.lang.Thread.run(Thread.java:745)


"Server console handler" Id=16 RUNNABLE (in native)
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)
-  locked java.io.BufferedInputStream@2dc40c01
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)
-  locked java.io.InputStreamReader@1f22a148
at java.io.InputStreamReader.read(InputStreamReader.java:184)
...


"DestroyJavaVM" Id=15 RUNNABLE


"Server thread" Id=13 RUNNABLE (in native)
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:345)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
-  locked java.io.BufferedOutputStream@1a8a8df0
at java.io.PrintStream.write(PrintStream.java:482)
-  locked java.io.PrintStream@7e6c952c
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
-  locked java.io.OutputStreamWriter@ab5bc8c
...


"Server Infinisleeper" Id=12 TIMED_WAITING
at java.lang.Thread.sleep(Native Method)
at ld$1.run(SourceFile:79)


"Snooper Timer" Id=11 TIMED_WAITING on java.util.TaskQueue@216d90d2
at java.lang.Object.wait(Native Method)
-  waiting on java.util.TaskQueue@216d90d2
at java.util.TimerThread.mainLoop(Timer.java:552)
at java.util.TimerThread.run(Timer.java:505)


"Signal Dispatcher" Id=5 RUNNABLE


"Finalizer" Id=3 WAITING on java.lang.ref.ReferenceQueue$Lock@203edc23
at java.lang.Object.wait(Native Method)
-  waiting on java.lang.ref.ReferenceQueue$Lock@203edc23
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)


"Reference Handler" Id=2 WAITING on java.lang.ref.Reference$Lock@7ee68e5e
at java.lang.Object.wait(Native Method)
-  waiting on java.lang.ref.Reference$Lock@7ee68e5e
at java.lang.Object.wait(Object.java:503)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)



Stacktrace:
at le.run(SourceFile:59)
at java.lang.Thread.run(Thread.java:745)

-- System Details --
Details:
Minecraft Version: 1.10.2
Operating System: Linux (amd64) version 3.2.0-4-amd64
Java Version: 1.7.0_79, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 625120736 bytes (596 MB) / 1038876672 bytes (990 MB) up to 6407585792 bytes (6110 MB)
JVM Flags: 11 total; -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -XX:+UseGCOverheadLimit -XX:-UseParallelGC -XX:ParallelGCThreads=4 -XX:+AggressiveOpts -XX:LargePageSizeInBytes=4m -XX:+UseLargePages -Xms1G -Xmx6G
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Profiler Position: N/A (disabled)
Player Count: 0 / 20; []
Is Modded: Unknown (can't tell)
Type: Dedicated Server (map_server.txt)

Ich hab keine Ahnung warum der Service selbst bei 0 Spielern nicht hinterher kommt. 
Was eventuell zu testen wäre: 
- Downgrade auf eine ältere Version (mit dem mvst zu machen wie mit einem update)
- Den Kartenstand vor dem Wochenende mal einspielen

Wenn jemand weitere Ideen hat, immer her damit.

Edit: 
Ich hab ein kleines Skript runtergehackt, welches des Server startet, sofern er nicht schon läuft. Das Skript wird alle halbe Stunde ausgeführt.

[S3l33ngrab]

Hm.. vlt sollten wir das mal bei dem Mojang Bug Tracker einwerfen? Evt haben die ne antwort drauf..

[CyD]

Hab vorhin mal ein downgrade auf 1.10 vollzogen

[BloxKilla]

(30.06.2016, 13:09)CyD schrieb: Hab vorhin mal ein downgrade auf 1.10 vollzogen

Searge hatte ja getwittert, dass es derartige Probleme in der 1.10.1 gegeben hat. in der 1.10.2 sollten die Crashes behoben sein, allerdings sollte auch das noch bestehende Problem im End behoben sein, dass man den Drachen nicht mehr respawnen kann.
Es wäre echt nicht schlecht wenn Du einen Bugreport beim Bugtracker einreichen würdest CyD
Gruß Stephan

[BloxKilla]

Nachdem ich nun schon mehrmals dabei war, wenn der Server crashte kann ich mit Sicherheit sagen, dass es wohl am Wetter liegt. Jedes mal nach dem einloggen regnete/schneite/gewitterte es

[S3l33ngrab]

Hats auch vor dem crash gewettert?

[BloxKilla]

Nein, aber bem einloggen schneite es bei mir, hab aber eben auch schon gehabt, dass es ganz ohne Crash angefangen hat zu schneien.
Da es vorher mit der 1.10 ohne Crash funktioniert hat und wir nun wieder auf 1.10 sind liegt es vielleicht an was anderem.
CyD, hast Du denn in den letzten beiden Wochen was an der Hardware/Software des Servers verändert?

[Kalmidrion]

kann das von blox soweit bestätigen wenn der Server weggecrashed ist dann gab es nach dem einloggen meist
regen/gewitter/Schneefall wo vorher nichts war.

Ich vermute das in der 1.10.X irgendwo ein fauler sein muss was das... sagen wir mal verhalten des Servers beim einsetzen des
wetters beeinflusst

[CyD]

Also das Downgrade scheint auch nichts zu bringen. Da ich ja seit gestern einen "watchdog" laufen habe, welcher alle 30mins schaut ob der Service noch läuft, habe ich von dem schon ein paar Logs sammeln können:

Code:

2016-06-30_16:00 WATCHDOG: status ok
2016-06-30_16:30 WATCHDOG: status ok
2016-06-30_17:00 WATCHDOG: status ok
2016-06-30_17:30 WATCHDOG: starting the server ( 0.05 0.08 0.06 3/228 26733 )
2016-06-30_18:00 WATCHDOG: status ok
2016-06-30_18:30 WATCHDOG: status ok
2016-06-30_19:00 WATCHDOG: starting the server ( 0.03 0.09 0.08 3/233 28599 )
2016-06-30_19:30 WATCHDOG: status ok
2016-06-30_20:00 WATCHDOG: status ok
2016-06-30_20:30 WATCHDOG: starting the server ( 0.00 0.02 0.05 3/226 30292 )
2016-06-30_21:00 WATCHDOG: status ok
2016-06-30_21:30 WATCHDOG: status ok
2016-06-30_22:00 WATCHDOG: starting the server ( 0.08 0.04 0.05 4/231 32052 )
2016-06-30_22:30 WATCHDOG: status ok
2016-06-30_23:00 WATCHDOG: status ok
2016-06-30_23:30 WATCHDOG: starting the server ( 0.01 0.28 0.52 3/227 1288 )
2016-07-01_00:00 WATCHDOG: status ok
2016-07-01_00:30 WATCHDOG: status ok
2016-07-01_01:00 WATCHDOG: starting the server ( 0.06 0.24 0.47 5/231 3180 )
2016-07-01_01:30 WATCHDOG: status ok
2016-07-01_02:00 WATCHDOG: status ok
2016-07-01_02:30 WATCHDOG: starting the server ( 0.03 0.04 0.11 3/226 4937 )
2016-07-01_03:00 WATCHDOG: status ok
2016-07-01_03:30 WATCHDOG: status ok
2016-07-01_04:00 WATCHDOG: starting the server ( 0.06 0.09 0.13 3/228 6619 )
2016-07-01_04:30 WATCHDOG: status ok
2016-07-01_05:00 WATCHDOG: status ok
2016-07-01_05:30 WATCHDOG: starting the server ( 0.02 0.06 0.05 3/228 8250 )
2016-07-01_06:00 WATCHDOG: status ok
2016-07-01_06:30 WATCHDOG: status ok
2016-07-01_07:00 WATCHDOG: starting the server ( 0.00 0.06 0.07 4/229 10102 )
2016-07-01_07:30 WATCHDOG: status ok
2016-07-01_08:00 WATCHDOG: status ok
2016-07-01_08:30 WATCHDOG: starting the server ( 0.01 0.02 0.05 3/226 11726 )
2016-07-01_09:00 WATCHDOG: status ok
2016-07-01_09:30 WATCHDOG: status ok
2016-07-01_10:00 WATCHDOG: starting the server ( 0.01 0.14 0.33 3/228 13421 )
2016-07-01_10:30 WATCHDOG: status ok
2016-07-01_11:00 WATCHDOG: status ok
2016-07-01_11:30 WATCHDOG: starting the server ( 0.00 0.03 0.07 2/220 15035 )
2016-07-01_12:00 WATCHDOG: status ok
2016-07-01_12:30 WATCHDOG: status ok
2016-07-01_13:00 WATCHDOG: starting the server ( 0.00 0.02 0.11 3/226 16733 )
2016-07-01_13:30 WATCHDOG: status ok
2016-07-01_14:00 WATCHDOG: status ok
2016-07-01_14:30 WATCHDOG: starting the server ( 0.01 0.05 0.05 2/223 18340 )
2016-07-01_15:00 WATCHDOG: status ok
2016-07-01_15:30 WATCHDOG: status ok
2016-07-01_16:00 WATCHDOG: starting the server ( 0.04 0.08 0.14 3/231 20061 )
2016-07-01_16:30 WATCHDOG: status ok
2016-07-01_17:00 WATCHDOG: status ok
2016-07-01_17:30 WATCHDOG: starting the server ( 0.00 0.03 0.05 4/229 21774 )

Der Code von dem Ding ist nichts anderes als:

Code:

#!/bin/sh

/home/minecraft/bin/minecraftd.sh status
r=$?
d=$(date +%F_%R)
log=/home/minecraft/logs/watchdog.log

if [ "$r" -gt 0 ]
then
        la=$(cat /proc/loadavg)
        echo "$d WATCHDOG: starting the server ( $la )" >> $log
        /home/minecraft/bin/minecraftd.sh start
else
        echo "$d WATCHDOG: status ok" >> $log
fi

Der Server scheint in den 15 Minuten davor wirklich kein bisschen Ausgelastet zu sein. In Klammern beim starting steht u.a. der load average.

Dann dachte ich, dass der Service vllt kurz nach dem Watchdog oder so abstürzt... und jetzt wirds interessant!
Immer wenn der Service sich abschaltet, printet er vorher eine Meldung, dass er sich jetzt gewaltsam beendet. Ich hab die mal aus dem Log gefiltert, achtet mal auf die Minuten:

Code:

$ grep -e "crashed" ../logs/mvst_default.log | tail -n 40
2015-12-20 23:27:07,442|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-01-26 16:19:44,399|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-02-01 07:51:19,463|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-02-05 19:05:51,097|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-01 04:45:29,914|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-05 11:02:17,810|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-09 02:44:47,404|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-09 09:47:07,277|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-26 21:40:39,323|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-27 00:34:24,849|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-27 10:53:33,841|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-27 23:55:09,537|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-28 20:01:27,056|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-28 21:44:44,350|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-29 00:39:36,063|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-29 19:19:55,319|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-29 21:37:34,328|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-29 23:05:15,889|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 00:35:06,795|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 09:11:06,471|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 10:57:20,931|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 12:27:20,669|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 14:32:00,817|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 17:11:02,499|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 18:56:36,432|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 20:27:24,693|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 21:56:37,354|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-06-30 23:27:23,888|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 00:56:38,578|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 02:27:26,361|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 03:56:36,322|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 05:27:21,730|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 06:56:35,636|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 08:27:20,348|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 09:56:36,109|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 11:27:22,545|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 12:56:37,118|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 14:27:22,768|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 15:56:36,679|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.
2016-07-01 17:27:23,393|Wrapper|INFO|Server: Considering it to be crashed, server will forcibly shutdown.

Als ob da alle 1,5h irgendwas wäre. (Ob es Niederschlag ist, kann ich leider nicht rauslesen).

[Kalmidrion]

es ist einfach nur mysterious ... sollten das mal wenn zeit ist im teamspeak genauer erörten...

aber ist lustig das es seit neustem immer die 27 und 56 sind