I logged in and saw that the monitor for both of my remote servers has crashed. After starting the monitor on both servers, it seems server #2's monitor keeps crashing, what seems to be randomly. First was an hour between crashing, then 10 minutes, then 5.
This is from var/log/syslog on server #1:
Code: Select all
Sep 7 12:41:19 chi1 logger: UGCC Monitor: The socket is not connected : at System.Net.Sockets.Socket.get_RemoteEndPoint () [0x00000] in <filename unknown>:0 at BrainlessFtpServer.FTPServer.start () [0x00000] in <filename unknown>:0 at System.Threading.Thread.StartInternal () [0x00000] in <filename unknown>:0
this is from server #2.
Code: Select all
Sep 7 05:38:19 chi2 logger: UGCC Monitor: The socket is not connected : at System.Net.Sockets.Socket.get_RemoteEndPoint () [0x00000] in <filename unknown>:0 at BrainlessFtpServer.FTPServer.start () [0x00000] in <filename unknown>:0 at System.Threading.Thread.StartInternal () [0x00000] in <filename unknown>:0
Sep 7 17:29:07 chi2 logger: UGCC Monitor: The socket is not connected : at System.Net.Sockets.Socket.get_RemoteEndPoint () [0x00000] in <filename unknown>:0 at BrainlessFtpServer.FTPServer.start () [0x00000] in <filename unknown>:0 at System.Threading.Thread.StartInternal () [0x00000] in <filename unknown>:0
Sep 7 17:29:37 chi2 crash_20150907172936_11.dmp[14801]: Uploading dump (out-of-process)#012/tmp/dumps/crash_20150907172936_11.dmp
Sep 7 17:29:38 chi2 crash_20150907172936_11.dmp[14801]: Finished uploading minidump (out-of-process): success = yes
Sep 7 17:29:38 chi2 crash_20150907172936_11.dmp[14801]: response: Discarded=1
Sep 7 17:29:38 chi2 crash_20150907172936_11.dmp[14801]: file ''/tmp/dumps/crash_20150907172936_11.dmp'', upload yes: ''Discarded=1''
-----
These have also been spamming the logs for days now, but seem to be harmless I gathered (from the Ignoring part) (on both remote monitors)
This is from ugccmon.log
Code: Select all
9/7/2015 5:55:22 PM (Warning) Ignoring invalid time stamp (replay attack) for remote command from address 192.223.26.242. Please ensure your timezone and time/date are accurate.
9/7/2015 5:55:22 PM (Warning) Ignoring invalid time stamp (replay attack) for remote command from address 192.223.26.242. Please ensure your timezone and time/date are accurate.
9/7/2015 5:55:22 PM (Warning) Ignoring invalid time stamp (replay attack) for remote command from address 192.223.26.242. Please ensure your timezone and time/date are accurate.
9/7/2015 5:55:22 PM (Warning) Ignoring invalid time stamp (replay attack) for remote command from address 192.223.26.242. Please ensure your timezone and time/date are accurate.