CumulusMX Errors on Raspberry Pi

[itstheburns]

I've done a bit of searching without success. While searching, the forum just stops loading and I give up so here's my post.

I'm running the latest build as of January 10, 2020 (3.3.0 build 3063) on a RPi 3b+ running raspbian 10

CumulusMX stops reporting to a few weather outlets (Windy, WeatherCloud, Wunderground, etc) after a few days, sometimes hours. I look in the logs and the 2 errors I'm seeing "loop data not received" and Unable to write data to the transport connection: connection reset by peer" and on some logs "Data input appears to have stopped" Below is a 2 hour partial from todays log. A partial from the end of the log is below that.

2020-02-13 14:00:00.327 Hour changed:14
2020-02-13 14:00:00.327 Calculating sunrise and sunset times
2020-02-13 14:00:00.328 Sunrise: 07:00:06
2020-02-13 14:00:00.328 Sunset : 17:33:01
2020-02-13 14:00:00.328 Tomorrow sunrise: 06:58:47
2020-02-13 14:00:00.329 Tomorrow sunset : 17:34:15
2020-02-13 14:00:00.331 Writing log entry for 2/13/2020 2:00:00 PM
2020-02-13 14:00:00.333 Written log entry for 2/13/2020 2:00:00 PM
2020-02-13 14:00:00.336 Writing today.ini, LastUpdateTime = 2/13/2020 2:00:00 PM raindaystart = 2.24 rain counter = 2.58
2020-02-13 14:00:00.600 Windy Response: OK: SUCCESS
2020-02-13 14:00:00.759 WeatherCloud Response: OK: 200
2020-02-13 14:10:01.167 Windy Response: OK: SUCCESS
2020-02-13 14:10:01.931 WeatherCloud Response: OK: 200
2020-02-13 14:17:39.960 !!! loop data not received
2020-02-13 14:17:40.966 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:20:00.592 Windy Response: OK: SUCCESS
2020-02-13 14:20:01.038 WeatherCloud Response: OK: 200
2020-02-13 14:30:00.823 Writing log entry for 2/13/2020 2:30:00 PM
2020-02-13 14:30:00.824 Written log entry for 2/13/2020 2:30:00 PM
2020-02-13 14:30:00.827 Writing today.ini, LastUpdateTime = 2/13/2020 2:30:00 PM raindaystart = 2.24 rain counter = 2.58
2020-02-13 14:30:01.120 Windy Response: OK: SUCCESS
2020-02-13 14:30:01.885 WeatherCloud Response: OK: 200
2020-02-13 14:40:00.698 Windy Response: OK: SUCCESS
2020-02-13 14:40:00.779 WeatherCloud Response: OK: 200
2020-02-13 14:46:40.091 !!! loop data not received
2020-02-13 14:46:41.098 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:47:18.166 !!! loop data not received
2020-02-13 14:47:19.173 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:47:53.933 !!! loop data not received
2020-02-13 14:49:00.076 !!! loop data not received
2020-02-13 14:49:00.803 *** Data input appears to have stopped
2020-02-13 14:49:19.891 !!! loop2 data not received
2020-02-13 14:50:00.850 *** Data input appears to have stopped
2020-02-13 14:50:41.998 !!! loop data not received
2020-02-13 14:51:40.400 !!! loop data not received
2020-02-13 14:53:00.985 *** Data input appears to have stopped
2020-02-13 14:53:38.157 Error sending LOOP command [LOOP 50]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:53:41.161 Error sending LOOP command [LPS 2 1]: The operation is not allowed on non-connected sockets.
2020-02-13 14:54:29.978 !!! loop data not received
2020-02-13 14:54:30.984 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:55:05.943 !!! loop data not received
2020-02-13 14:55:06.950 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:55:41.869 !!! loop data not received
2020-02-13 14:55:42.875 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:56:15.830 !!! loop data not received
2020-02-13 14:56:16.836 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:56:52.095 !!! loop data not received
2020-02-13 14:56:53.101 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:57:27.881 !!! loop data not received
2020-02-13 14:57:28.887 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:58:03.843 !!! loop data not received
2020-02-13 14:58:04.849 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:58:37.901 !!! loop data not received
2020-02-13 14:58:38.907 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:59:13.668 !!! loop data not received
2020-02-13 14:59:14.674 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 14:59:48.127 !!! loop data not received
2020-02-13 14:59:49.132 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:00:00.358 Hour changed:15
2020-02-13 15:00:00.359 Calculating sunrise and sunset times
2020-02-13 15:00:00.359 Sunrise: 07:00:06
2020-02-13 15:00:00.359 Sunset : 17:33:01
2020-02-13 15:00:00.360 Tomorrow sunrise: 06:58:47
2020-02-13 15:00:00.360 Tomorrow sunset : 17:34:15
2020-02-13 15:00:00.363 Writing log entry for 2/13/2020 3:00:00 PM
2020-02-13 15:00:00.364 Written log entry for 2/13/2020 3:00:00 PM
2020-02-13 15:00:00.367 Writing today.ini, LastUpdateTime = 2/13/2020 3:00:00 PM raindaystart = 2.24 rain counter = 2.58
2020-02-13 15:00:00.624 Windy Response: OK: SUCCESS
2020-02-13 15:00:00.771 WeatherCloud Response: OK: 200
2020-02-13 15:00:23.911 !!! loop data not received
2020-02-13 15:00:24.918 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:00:59.919 !!! loop data not received
2020-02-13 15:01:00.927 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:01:33.778 !!! loop data not received
2020-02-13 15:01:34.785 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:02:09.723 !!! loop data not received
2020-02-13 15:02:10.730 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:02:43.782 !!! loop data not received
2020-02-13 15:02:44.787 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:03:20.133 !!! loop data not received
2020-02-13 15:03:21.139 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:03:55.957 !!! loop data not received
2020-02-13 15:03:56.963 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:04:29.815 !!! loop data not received
2020-02-13 15:04:30.822 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:05:05.966 !!! loop data not received
2020-02-13 15:05:06.972 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:05:40.264 !!! loop data not received
2020-02-13 15:05:41.270 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:06:16.030 !!! loop data not received
2020-02-13 15:06:17.037 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:06:52.177 !!! loop data not received
2020-02-13 15:06:53.184 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:07:26.035 !!! loop data not received
2020-02-13 15:07:27.041 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:08:01.960 !!! loop data not received
2020-02-13 15:08:02.967 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:08:37.726 !!! loop data not received
2020-02-13 15:08:38.734 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:09:12.186 !!! loop data not received
2020-02-13 15:09:13.193 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:09:47.835 !!! loop data not received
2020-02-13 15:09:48.841 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:10:01.175 Windy Response: OK: SUCCESS
2020-02-13 15:10:01.301 WeatherCloud Response: OK: 200
2020-02-13 15:10:25.730 !!! loop data not received
2020-02-13 15:10:26.736 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:11:00.207 !!! loop data not received
2020-02-13 15:11:01.214 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:11:36.074 !!! loop data not received
2020-02-13 15:11:37.080 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:12:10.115 !!! loop data not received
2020-02-13 15:12:11.122 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:12:47.671 !!! loop data not received
2020-02-13 15:12:48.678 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:13:22.110 !!! loop data not received
2020-02-13 15:13:23.117 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:13:57.756 !!! loop data not received
2020-02-13 15:13:58.763 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:14:34.223 !!! loop data not received
2020-02-13 15:14:35.230 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:15:07.982 !!! loop data not received
2020-02-13 15:15:08.988 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:15:43.928 !!! loop data not received
2020-02-13 15:15:44.935 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:16:19.974 !!! loop data not received
2020-02-13 15:16:20.981 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:16:53.733 !!! loop data not received
2020-02-13 15:16:54.741 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:17:29.802 !!! loop data not received
2020-02-13 15:17:30.809 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:18:04.161 !!! loop data not received
2020-02-13 15:18:05.167 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:18:22.753 Error sending LOOP command [LOOP 50]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:19:16.084 !!! loop data not received
2020-02-13 15:19:17.092 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:19:51.952 !!! loop data not received
2020-02-13 15:19:52.959 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:20:00.627 Windy Response: OK: SUCCESS
2020-02-13 15:20:00.741 WeatherCloud Response: OK: 200
2020-02-13 15:20:26.008 !!! loop data not received
2020-02-13 15:20:27.015 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:21:01.774 !!! loop data not received
2020-02-13 15:21:02.781 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:21:39.647 !!! loop data not received
2020-02-13 15:21:40.654 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:22:14.094 !!! loop data not received
2020-02-13 15:22:15.101 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:22:49.762 !!! loop data not received
2020-02-13 15:22:50.767 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:23:26.027 !!! loop data not received
2020-02-13 15:23:27.034 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:24:01.795 !!! loop data not received
2020-02-13 15:24:02.801 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:24:39.751 !!! loop data not received
2020-02-13 15:24:40.758 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:25:11.805 !!! loop data not received
2020-02-13 15:25:12.811 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:25:46.164 !!! loop data not received
2020-02-13 15:25:47.171 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:26:22.139 !!! loop data not received
2020-02-13 15:26:23.146 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:26:55.898 !!! loop data not received
2020-02-13 15:26:56.903 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:27:31.964 !!! loop data not received
2020-02-13 15:27:32.971 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:28:06.223 !!! loop data not received
2020-02-13 15:28:07.230 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:28:41.889 !!! loop data not received
2020-02-13 15:28:42.896 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:29:17.774 !!! loop data not received
2020-02-13 15:29:18.780 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:29:51.812 !!! loop data not received
2020-02-13 15:29:52.819 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:30:00.683 Writing log entry for 2/13/2020 3:30:00 PM
2020-02-13 15:30:00.685 Written log entry for 2/13/2020 3:30:00 PM
2020-02-13 15:30:00.688 Writing today.ini, LastUpdateTime = 2/13/2020 3:30:00 PM raindaystart = 2.24 rain counter = 2.58
2020-02-13 15:30:00.976 Windy Response: OK: SUCCESS
2020-02-13 15:30:01.402 WeatherCloud Response: OK: 200
2020-02-13 15:30:28.179 !!! loop data not received
2020-02-13 15:30:29.185 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:31:01.979 !!! loop data not received
2020-02-13 15:31:02.986 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:31:37.955 !!! loop data not received
2020-02-13 15:31:38.962 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:32:15.831 !!! loop data not received
2020-02-13 15:32:16.837 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:32:47.881 !!! loop data not received
2020-02-13 15:32:48.888 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:33:22.218 !!! loop data not received
2020-02-13 15:33:23.224 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:33:58.085 !!! loop data not received
2020-02-13 15:33:59.092 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:34:31.983 !!! loop data not received
2020-02-13 15:34:32.991 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:35:07.852 !!! loop data not received
2020-02-13 15:35:08.859 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:35:43.801 !!! loop data not received
2020-02-13 15:35:44.808 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:36:19.868 !!! loop data not received
2020-02-13 15:36:20.875 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:36:54.207 !!! loop data not received
2020-02-13 15:36:55.213 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:37:30.033 !!! loop data not received
2020-02-13 15:37:31.039 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:38:03.892 !!! loop data not received
2020-02-13 15:38:04.899 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:38:39.860 !!! loop data not received
2020-02-13 15:38:40.867 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:39:13.919 !!! loop data not received
2020-02-13 15:39:14.925 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:39:50.285 !!! loop data not received
2020-02-13 15:39:51.292 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:40:00.609 Windy Response: OK: SUCCESS
2020-02-13 15:40:02.854 WeatherCloud Response: OK: 200
2020-02-13 15:40:24.079 !!! loop data not received
2020-02-13 15:40:25.086 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:40:59.745 !!! loop data not received
2020-02-13 15:41:00.751 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:41:35.789 !!! loop data not received
2020-02-13 15:41:36.796 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:42:10.168 !!! loop data not received
2020-02-13 15:42:11.174 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:42:45.818 !!! loop data not received
2020-02-13 15:42:46.825 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:43:22.065 !!! loop data not received
2020-02-13 15:43:23.072 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:43:57.833 !!! loop data not received
2020-02-13 15:43:58.840 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:44:31.693 !!! loop data not received
2020-02-13 15:44:32.700 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:45:07.826 !!! loop data not received
2020-02-13 15:45:08.833 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:45:44.193 !!! loop data not received
2020-02-13 15:45:45.199 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:46:18.131 !!! loop data not received
2020-02-13 15:46:19.138 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:46:53.880 !!! loop data not received
2020-02-13 15:46:54.887 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:47:27.802 !!! loop data not received
2020-02-13 15:47:28.809 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:48:04.309 !!! loop data not received
2020-02-13 15:48:05.315 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:48:42.113 !!! loop data not received
2020-02-13 15:48:43.120 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:49:14.164 !!! loop data not received
2020-02-13 15:49:15.171 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:49:48.103 !!! loop data not received
2020-02-13 15:49:49.111 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:50:01.061 Windy Response: OK: SUCCESS
2020-02-13 15:50:01.361 WeatherCloud Response: OK: 200
2020-02-13 15:50:23.872 !!! loop data not received
2020-02-13 15:50:24.878 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:50:59.718 !!! loop data not received
2020-02-13 15:51:00.725 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:51:33.798 !!! loop data not received
2020-02-13 15:51:34.804 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:52:08.139 !!! loop data not received
2020-02-13 15:52:09.146 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:52:43.984 !!! loop data not received
2020-02-13 15:52:44.991 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:53:18.125 !!! loop data not received
2020-02-13 15:53:19.131 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:53:53.788 !!! loop data not received
2020-02-13 15:53:54.794 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:54:29.732 !!! loop data not received
2020-02-13 15:54:30.741 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:55:04.153 !!! loop data not received
2020-02-13 15:55:05.160 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:55:39.821 !!! loop data not received
2020-02-13 15:55:40.827 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:56:15.867 !!! loop data not received
2020-02-13 15:56:16.873 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:56:54.043 !!! loop data not received
2020-02-13 15:56:55.050 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:57:26.216 !!! loop data not received
2020-02-13 15:57:27.223 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:58:00.077 !!! loop data not received
2020-02-13 15:58:01.084 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:58:36.065 !!! loop data not received
2020-02-13 15:58:37.072 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:59:09.763 !!! loop data not received
2020-02-13 15:59:10.770 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 15:59:45.828 !!! loop data not received
2020-02-13 15:59:46.834 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2020-02-13 16:00:00.235 Hour changed:16

After a few hours, it appears to have gone back to normal and then at the end of the file, there is this:

2020-02-14 06:00:00.873 Hour changed:6
2020-02-14 06:00:00.874 Calculating sunrise and sunset times
2020-02-14 06:00:00.875 Sunrise: 06:58:47
2020-02-14 06:00:00.875 Sunset : 17:34:15
2020-02-14 06:00:00.877 Tomorrow sunrise: 06:57:27
2020-02-14 06:00:00.877 Tomorrow sunset : 17:35:30
2020-02-14 06:00:00.882 Writing log entry for 2/14/2020 6:00:00 AM
2020-02-14 06:00:00.884 Written log entry for 2/14/2020 6:00:00 AM
2020-02-14 06:00:00.890 Writing today.ini, LastUpdateTime = 2/14/2020 6:00:00 AM raindaystart = 2.58 rain counter = 2.58
2020-02-14 06:00:01.245 Windy Response: OK: SUCCESS
2020-02-14 06:00:01.743 WeatherCloud Response: OK: 200
2020-02-14 06:10:00.741 Windy Response: OK: SUCCESS
2020-02-14 06:10:01.034 WeatherCloud Response: OK: 200
2020-02-14 06:20:01.257 Windy Response: OK: SUCCESS
2020-02-14 06:20:01.875 WeatherCloud Response: OK: 200
2020-02-14 06:30:00.626 Writing log entry for 2/14/2020 6:30:00 AM
2020-02-14 06:30:00.630 Written log entry for 2/14/2020 6:30:00 AM
2020-02-14 06:30:00.634 Writing today.ini, LastUpdateTime = 2/14/2020 6:30:00 AM raindaystart = 2.58 rain counter = 2.58
2020-02-14 06:30:01.018 Windy Response: OK: SUCCESS
2020-02-14 06:30:05.719 WeatherCloud Response: OK: 200
2020-02-14 06:40:00.400 Windy Response: OK: SUCCESS
2020-02-14 06:40:01.202 WeatherCloud Response: OK: 200
2020-02-14 06:42:45.497 !!! loop data not received
2020-02-14 06:44:00.305 *** Data input appears to have stopped
2020-02-14 06:45:00.354 *** Data input appears to have stopped
2020-02-14 06:46:00.385 *** Data input appears to have stopped
2020-02-14 06:47:00.429 *** Data input appears to have stopped
2020-02-14 06:48:00.452 *** Data input appears to have stopped
2020-02-14 06:49:00.492 *** Data input appears to have stopped
2020-02-14 06:50:00.537 *** Data input appears to have stopped
2020-02-14 06:51:00.636 *** Data input appears to have stopped
2020-02-14 06:52:00.662 *** Data input appears to have stopped
2020-02-14 06:53:00.688 *** Data input appears to have stopped
2020-02-14 06:54:00.765 *** Data input appears to have stopped
2020-02-14 06:55:00.809 *** Data input appears to have stopped
2020-02-14 06:56:00.863 *** Data input appears to have stopped
2020-02-14 06:57:00.954 *** Data input appears to have stopped
2020-02-14 06:58:00.039 *** Data input appears to have stopped
2020-02-14 06:59:00.082 *** Data input appears to have stopped
2020-02-14 07:00:00.137 Hour changed:7
2020-02-14 07:00:00.137 Calculating sunrise and sunset times
2020-02-14 07:00:00.138 Sunrise: 06:58:47
2020-02-14 07:00:00.138 Sunset : 17:34:15
2020-02-14 07:00:00.139 Tomorrow sunrise: 06:57:27
2020-02-14 07:00:00.139 Tomorrow sunset : 17:35:30
2020-02-14 07:00:00.140 *** Data input appears to have stopped
2020-02-14 07:01:00.200 *** Data input appears to have stopped
2020-02-14 07:02:00.271 *** Data input appears to have stopped
2020-02-14 07:03:00.291 *** Data input appears to have stopped
2020-02-14 07:04:00.313 *** Data input appears to have stopped
2020-02-14 07:05:00.348 *** Data input appears to have stopped
2020-02-14 07:06:00.390 *** Data input appears to have stopped
2020-02-14 07:07:00.439 *** Data input appears to have stopped
2020-02-14 07:08:00.463 *** Data input appears to have stopped
2020-02-14 07:09:00.526 *** Data input appears to have stopped
2020-02-14 07:10:00.554 *** Data input appears to have stopped
2020-02-14 07:11:00.606 *** Data input appears to have stopped
2020-02-14 07:12:00.676 *** Data input appears to have stopped
2020-02-14 07:13:00.749 *** Data input appears to have stopped
2020-02-14 07:14:00.804 *** Data input appears to have stopped
2020-02-14 07:15:00.851 *** Data input appears to have stopped
2020-02-14 07:16:00.883 *** Data input appears to have stopped
2020-02-14 07:17:00.935 *** Data input appears to have stopped
2020-02-14 07:18:00.987 *** Data input appears to have stopped
2020-02-14 07:19:00.063 *** Data input appears to have stopped
2020-02-14 07:20:00.094 *** Data input appears to have stopped
2020-02-14 07:21:00.127 *** Data input appears to have stopped
2020-02-14 07:22:00.173 *** Data input appears to have stopped
2020-02-14 07:23:00.237 *** Data input appears to have stopped
2020-02-14 07:24:00.285 *** Data input appears to have stopped
2020-02-14 07:25:00.339 *** Data input appears to have stopped
2020-02-14 07:26:00.399 *** Data input appears to have stopped
2020-02-14 07:27:00.427 *** Data input appears to have stopped
2020-02-14 07:28:00.463 *** Data input appears to have stopped
2020-02-14 07:29:00.506 *** Data input appears to have stopped
2020-02-14 07:30:00.584 *** Data input appears to have stopped
2020-02-14 07:31:00.639 *** Data input appears to have stopped
2020-02-14 07:32:00.675 *** Data input appears to have stopped
2020-02-14 07:33:00.710 *** Data input appears to have stopped
2020-02-14 07:34:00.749 *** Data input appears to have stopped
2020-02-14 07:35:00.802 *** Data input appears to have stopped
2020-02-14 07:36:00.861 *** Data input appears to have stopped
2020-02-14 07:37:00.887 *** Data input appears to have stopped
2020-02-14 07:38:00.927 *** Data input appears to have stopped
2020-02-14 07:39:00.970 *** Data input appears to have stopped
2020-02-14 07:40:01.007 *** Data input appears to have stopped
2020-02-14 07:41:00.039 *** Data input appears to have stopped
2020-02-14 07:42:00.066 *** Data input appears to have stopped
2020-02-14 07:43:00.113 *** Data input appears to have stopped
2020-02-14 07:44:00.143 *** Data input appears to have stopped
2020-02-14 07:45:00.180 *** Data input appears to have stopped
2020-02-14 07:46:00.229 *** Data input appears to have stopped
2020-02-14 07:47:00.273 *** Data input appears to have stopped
2020-02-14 07:48:00.311 *** Data input appears to have stopped
2020-02-14 07:49:00.350 *** Data input appears to have stopped
2020-02-14 07:50:00.406 *** Data input appears to have stopped
2020-02-14 07:51:00.440 *** Data input appears to have stopped
2020-02-14 07:52:00.484 *** Data input appears to have stopped
2020-02-14 07:53:00.556 *** Data input appears to have stopped
2020-02-14 07:54:00.640 *** Data input appears to have stopped
2020-02-14 07:55:00.696 *** Data input appears to have stopped
2020-02-14 07:56:00.765 *** Data input appears to have stopped
2020-02-14 07:57:00.802 *** Data input appears to have stopped
2020-02-14 07:58:00.873 *** Data input appears to have stopped
2020-02-14 07:59:00.958 *** Data input appears to have stopped
2020-02-14 08:00:00.994 Hour changed:8
2020-02-14 08:00:00.995 Calculating sunrise and sunset times
2020-02-14 08:00:00.996 Sunrise: 06:58:47
2020-02-14 08:00:00.996 Sunset : 17:34:15
2020-02-14 08:00:00.997 Tomorrow sunrise: 06:57:27
2020-02-14 08:00:00.998 Tomorrow sunset : 17:35:30
2020-02-14 08:00:01.000 *** Data input appears to have stopped
2020-02-14 08:01:00.035 *** Data input appears to have stopped
2020-02-14 08:02:00.096 *** Data input appears to have stopped
2020-02-14 08:03:00.146 *** Data input appears to have stopped
2020-02-14 08:04:00.198 *** Data input appears to have stopped
2020-02-14 08:05:00.252 *** Data input appears to have stopped
2020-02-14 08:06:00.297 *** Data input appears to have stopped
2020-02-14 08:07:00.331 *** Data input appears to have stopped
2020-02-14 08:08:00.373 *** Data input appears to have stopped
2020-02-14 08:09:00.406 *** Data input appears to have stopped
2020-02-14 08:10:00.489 *** Data input appears to have stopped
2020-02-14 08:11:00.535 *** Data input appears to have stopped
2020-02-14 08:12:00.595 *** Data input appears to have stopped
2020-02-14 08:13:00.650 *** Data input appears to have stopped
2020-02-14 08:14:00.708 *** Data input appears to have stopped
2020-02-14 08:15:00.757 *** Data input appears to have stopped
2020-02-14 08:16:00.812 *** Data input appears to have stopped
2020-02-14 08:17:00.861 *** Data input appears to have stopped
2020-02-14 08:18:00.895 *** Data input appears to have stopped
2020-02-14 08:19:00.926 *** Data input appears to have stopped
2020-02-14 08:20:00.975 *** Data input appears to have stopped
2020-02-14 08:21:00.030 *** Data input appears to have stopped
2020-02-14 08:22:00.088 *** Data input appears to have stopped
2020-02-14 08:23:00.113 *** Data input appears to have stopped
2020-02-14 08:24:00.149 *** Data input appears to have stopped
2020-02-14 08:25:00.225 *** Data input appears to have stopped
2020-02-14 08:26:00.300 *** Data input appears to have stopped
2020-02-14 08:27:00.355 *** Data input appears to have stopped
2020-02-14 08:28:00.404 *** Data input appears to have stopped
2020-02-14 08:29:00.421 *** Data input appears to have stopped

Once I try to view the CumulusMX webpage on the Pi, it shows the last station update time to be behind the CumulusMX update time. I usually login with VNC-Viewer, CTRL-C and restart CumulusMX. Sometimes it will be fine for almost a week, then sometimes only a few hours. I'm not really sure what to look for or what else I can provide but some insight as to why this is happening would be great! Thank you for your time!!!

Kevin

[ExperiMentor]

Your log shows 2 different problems going on simultaneously.

The first is: "Data input appears to have stopped"
I think this is a Cumulus message, repeated every minute, meaning that receipt of data from your weather station has stopped. Check physical wires, that batteries are not flat etc. If the station connects via WiFi, might indicate a problem with your local network (station to router or router to RPi)

The second is: "Unable to write data to the transport connection: Connection reset by peer."
This is a Linux error which means that the RPi has 'found' the remote server (Windy, Wunderground), but the connection has not been successful, maybe rejected by the far end.
This error usually means that the target [remote server] machine is running, but the service that you're trying to connect to is not available. (Either it stopped, crashed, or is busy with another request.) Other causes might be: wrong password? unable to negotiate correct transfer protocol? some other network problem?
But as these are commercial servers, it's most likely that the issue is at YOUR end. And as it sometimes works OK, some causes can be eliminated (eg password).

Common between these 2 lists is some kind of local network connection issue? So some questions and what I would try:

1. Tell us if this problem just started when you upgraded to Build 3063. If so, which build were you using previously? I just noticed that the updates in Build 3063 included changes to FTP sections, so I'll be deferring updating for a while ...
2. You may have already done this, but have not said so explicitly: Reboot the RPi [sudo reboot] and restart Cumulus.
RPi (and indeed most computers) are not designed for continuous running and cumulating errors can give rise to strange things like this if a stack somewhere gets a wrong byte. Suggest a scheduled daily reboot using Crontab.
3. Reboot your network router and modem
4. Check wires and change battery in weather station. Does it use a WiFi connection?

If no joy from these, we should wait to see what Mark Crossley thinks.

[itstheburns]

Hello!

Thank you for the reply. I wasn't sure if this software was still in development or being abandoned.

Both my Pi and weather station are Ethernet connected, no wifi. The weather station is a Davis VantageVue using the IP datalogger, if that helps. Both are plugged into mains power and the Davis console is receiving data from the sensors as normal. As for when I noticed this issue, I just recently started using CumulusMX on a regular basis. I have not used any other builds in this manner so no previous long-term basis for reliability. The previous version I messed with was back when CumulusMX first launched and I ran it on windows 7 for about a week to see what was different but that's about it. Previous to that was Cumulus 1.9.4 and that worked 96% flawlessly. I really only went to CumulusMX so I could run it on a Pi and not leave a PC on 24/7.

I checked my router logs for any errors related to cumulus not receiving data and there are no errors reported (pfsense router os). The Pi and the vantagevue are assigned static IPs from pfSense and are on their own vlan with internet access only. A few rules to allow internet access and allow my pc to see the webpage and vnc into the Pi, but nothing more. I have restarted pfsense with no change in behavior. I've had uptimes of 30+ days with no negative effects on my network or internet connectivity. Regardless of uptime on pfsense or cable modem, this issue seems to be random. I have rebooted both the pi and weather station console multiple times with no change or frequency in behavior. When cumulus stops receiving data, i reboot the pi and restart cumulus manually hoping it would resolve the issue.

I have also put the weather station and Pi on their own, wide open network with unlimited access, full DMZ to see if I botched something with my pfSense settings. This had no change on behavior.

The connection to the remote services (Weather Underground, WeatherCloud, etc) are not critical. I mostly wanted to have better access to my weather station's data. Those services only seem to stop when cumulus stops receiving data from the weather station. The only way I know this happens is when I'm notified by those services that data has stopped. This is when I remove into the pi via VNC and restart it and cumulus. I can confirm data has stopped by viewing the CumulusMX built in weather page. The most annoying part is not knowing why it stopped receiving data since its so random (its really not annoying, just confusing, if you know what I mean). I can still access the webpage, change settings, save, etc when it stops reporting, if that helps any.

If there are any files I can provide that would help, I would be more than happy to upload them for you.

[mcrossley]

It does appear to be a lost network connection to your IP logger, and maybe it isn't recovering from it very gracefully. With no data coming in, Cumulus will not upload to the external websites.

I'm afraid I do not have an IP logger to test and develop against, I did add some more code to try and recover when the IP connection is lost, and is does in some circumstances, but not this one it seems.

[billy]

For what it's worth - which may be nothing - this seems awfully similar to a problem I had about 2 months ago after I had done an upgrade to 3059. I haven't kept the mxdiags file so can't be certain. I went away soon after and couldn't deal with it for a few weeks. When I did get an opportunity, the solution that worked for me was another upgrade to the latest version available then (3062). At first I thought it must have been a bug in 3059 but no-one else reported it as far as I know, and I came to the conclusion that it was probably a corrupt install of 3059. So maybe a fresh re-install of 3063 might help?

[billy]

Oh, and I need to change my station on the forum info - it is a Davis VP2+

[mcrossley]

So maybe a fresh re-install of 3063 might help?

Possibly, but I'm sceptical.

[billy]

You are correct to be sceptical

I was able to recover the mxdiag file from one of the instances. It does not have any "Unable to write data to the transport connection" messages. It has some "!!! loop data not received" messages that increase in frequency over time and are interspersed with a handful of "!!! VP2 Not woken". Then eventually ""*** Data input appears to have stopped".

[f4phlyer]

I too, had a similar problem. I didn't look at any of the log files but the symptom was that my data would not update. A restart would start everything up again. As Mark mentioned I finally identified the issue as Cumulus not recovering from a temporary network interruption of Cumulus and the logger. I suspected a power interruption of the network switch that my VP II console and were on. I had a UPS on everything else so I added a UPS to the switch and I've not had a problem since. FWIW

[ConligWX]

I think I may have suffered something of a similar nature with Cumulsmx today and previously last week.

Using Nano SD as the data logger and CumulsMX collects data on port 22222. however if this stops I get an error:

Code: Select all

2020-07-28 14:14:08.230 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: The socket has been shut down.
2020-07-28 14:14:08.230 Error sending LOOP command [LOOP 50]: Unable to write data to the transport connection: The socket has been shut down.
2020-07-28 14:14:08.230 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: The socket has been shut down.
2020-07-28 14:14:08.231 Error sending LOOP command [LOOP 50]: Unable to write data to the transport connection: The socket has been shut down.
2020-07-28 14:14:08.231 Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: The socket has been shut down.

it continues until my hard disk was full last week with over 28Gb of MXDiag file. today it was only 4.8gb as I restarted CumulusMX. I take it Cumulus does not stop trying to connect? maybe a pause of 5 minutes before a retry for a new connection perhaps? I think My Nano had a reboot last week when this occurred. and I may have inadvertently, done something on the network so that the Nano dropped off the network for a few minutes today. I guess it could also be the Nano's fault too.

[mcrossley]

Next time you see this happening could you switch on debug logging and let it run a minute before restarting MX? I'd like to see the log file.

But I agree, ideally it should back off and only retry periodically on a persistent failure.