Monitor crashed

[AccelerateServers]

Our monitor on one of our remote boxes crashed today with this error:

Code: Select all

9/3/2015 3:47:54 PM	n/a (0)	CHI2 (13)	n/a (0)	monitor	0	Remote thread error: Invalid arguments at System.Net.Sockets.Socket.Accept () [0x00000] in :0 at System.Net.Sockets.TcpListener.AcceptTcpClient () [0x00000] in :0 at UGCCMon.UGCCMon.remote () [0x00000] in :0 

[Masher]

That's a really weird place to crash, that area is protected from errors and should've kept running. Is there anything in /var/log/messages or syslog?

[AccelerateServers]

this is what I can find in syslog

Code: Select all

Sep  3 15:47:54 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

[Masher]

That's probably what caused it to crash. I'll put some better error management into that area of the code for the next update.

[AccelerateServers]

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.

[AccelerateServers]

This seems to be occurring when a user is transferring files. I am going to test this now and see. Will update.

[AccelerateServers]

I transferred about 600 out of 1000 files to the same folder logged in as the same user around the time of the crash (as shown by ftp.log) and the monitor crashed. I will wait a while to see if it crashes again, then retry my test to see if it is, in fact, ftp activity making it crash.

[AccelerateServers]

The monitor on server #1 just crashed with this in the syslog:

Code: Select all

Sep  7 18:30:56 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

[AccelerateServers]

Both panels are now crashing, this is getting excessive.

server #1 syslog:

Code: Select all

Sep  7 18:48:31 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

server #2 syslog:

Code: Select all

Sep  7 18:45:58 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 18:57:24 chi2 mono: ugccmonsvc.exe: Lock file already exists: /tmp/ugccmonsvc.exe.lock
Sep  7 18:58:42 chi2 mono: ugccmonsvc.exe: Lock file already exists: /tmp/ugccmonsvc.exe.lock
Sep  7 18:59:52 chi2 mono: ugccmonsvc.exe: Lock file already exists: /tmp/ugccmonsvc.exe.lock
Sep  7 19:00:19 chi2 mono: ugccmonsvc.exe: Lock file already exists: /tmp/ugccmonsvc.exe.lock