Hi All,
A couple of times in the last few weeks Cumulus appears to have "stopped" and the only way to recover is to re-boot the Pi. I am not sure if its just not uploading to my website or if stopped completely. I am currently working away from home so dont have as much acces as I would like to the Pi and Cumulus.
I did manage to get hold of the MX diags file and see this at the end of them from when I believe the issue occurred. Its only just started happening recently so am trying to understand why. I have a Fineoffset weather station and dont seem to suffer from the known USB issues. Everything before this in the diags file seems normal
Any help appreciated. Here is the error:
2018-11-23 09:40:39.773 System.Net.Sockets.SocketException: The socket is not connected
at System.Net.Sockets.Socket.get_RemoteEndPoint () [0x00000] in <filename unknown>:0
at Alchemy.Classes.Context..ctor (Alchemy.WebSocketServer server, System.Net.Sockets.TcpClient connection) [0x00000] in <filename unknown>:0
at Alchemy.WebSocketServer.OnRunClient (System.Object data) [0x00000] in <filename unknown>:0
2018-11-23 09:40:39.967 System.ObjectDisposedException: The object was used after being disposed.
at System.IO.FileStream.Write (System.Byte[] array, Int32 offset, Int32 count) [0x00000] in <filename unknown>:0
at System.IO.StreamWriter.FlushBytes () [0x00000] in <filename unknown>:0
at System.IO.StreamWriter.FlushCore () [0x00000] in <filename unknown>:0
at System.IO.StreamWriter.Flush () [0x00000] in <filename unknown>:0
at System.Diagnostics.TextWriterTraceListener.Flush () [0x00000] in <filename unknown>:0
at System.Net.FtpClient.FtpTrace.Write (System.String message) [0x00000] in <filename unknown>:0
at System.Net.FtpClient.FtpTrace.WriteLine (System.String message) [0x00000] in <filename unknown>:0
at System.Net.FtpClient.FtpClient.Dispose () [0x00000] in <filename unknown>:0
at System.Net.FtpClient.FtpClient.Finalize () [0x00000] in <filename unknown>:0
Thanks
Andy
Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.0.0 (build 4022) - 11 May 2024
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V4 release 4.0.0 (build 4022) - 11 May 2024
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
MX Randomly "stops" on Pi3
Moderator: mcrossley
- mcrossley
- Posts: 12846
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: MX Randomly "stops" on Pi3
The WebSocket component is used to drive the "Admin" interface for MX. Are you leaving a browser connected this interface?
-
- Posts: 265
- Joined: Tue 10 Sep 2013 8:40 pm
- Weather Station: Ecowitt GW1003 (GW1000)
- Operating System: Raspbian 10 (Buster) / Mono 6.12
- Location: Freiston, Lincolnshire, UK
- Contact:
Re: MX Randomly "stops" on Pi3
Hi Mark,
Thanks for the reply and apologies in the delay getting back.
I rarely use the interface of MX (I assume you mean logging into the local MX on port 8998) and the last time it occurred I was actually away and didnt have access to it.
It hasnt happened again since, so I will just monitor it for the time being and avoid accessing MX directly and see what happens.
Andy
Thanks for the reply and apologies in the delay getting back.
I rarely use the interface of MX (I assume you mean logging into the local MX on port 8998) and the last time it occurred I was actually away and didnt have access to it.
It hasnt happened again since, so I will just monitor it for the time being and avoid accessing MX directly and see what happens.
Andy