Welcome to the Cumulus Support forum.

Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025

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

If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080

Error encountered during custom seconds MYSQL operation

Topics about the Beta trials up to Build 3043, the last build by Cumulus's founder Steve Loft. It was by this time way out of Beta but Steve wanted to keep it that way until he made a decision on his and Cumulus's future.

Moderator: mcrossley

Locked
bosschafj
Posts: 4
Joined: Fri 30 Dec 2016 3:03 pm
Weather Station: WH0101
Operating System: Raspberry Pi 3
Contact:

Error encountered during custom seconds MYSQL operation

Post by bosschafj »

Sorry is this topic is already mentioned in this forum, but I have not nog found is.

I'm running CumulusMX om my raspberry pi 3 now for a couple of days noticed the following problem:

CumulusMX is running (Cumulus MX v.3.0.0 build 3041)
CumulusMX is listening on TCP Port: 8998 (http://192.168.20.89:8998)
ProcessID (PID) of CumulusMX is: 12115
CumulusMX Version is: Cumulus MX v.3.0.0 build 3041
System Uptime of FjB_PI_01 is: 20 hours 18 minutes
CumulusMX is running since: 2017-01-03 08:40
Path to CumulusMX is: /home/pi/CumulusMX

startup:
12362 ? Ss 0:00 SCREEN -dmS CumulusMX -amds bash mono /home/pi/CumulusMX/CumulusMX.exe -port 8998 -lang en
12366 pts/0 Ssl+ 0:50 mono /home/pi/CumulusMX/CumulusMX.exe -port 8998 -lang en-GB

In my MXdiags file if found the following lines:

2017-01-03 08:46:06.277 CommandText property has not been initialized.
2017-01-03 08:46:16.277 Error encountered during custom seconds MySQL operation.
2017-01-03 08:46:16.278 CommandText property has not been initialized.
2017-01-03 08:46:26.277 Error encountered during custom seconds MySQL operation.
2017-01-03 08:46:26.278 CommandText property has not been initialized.
2017-01-03 08:46:36.277 Error encountered during custom seconds MySQL operation.
2017-01-03 08:46:36.278 CommandText property has not been initialized.
2017-01-03 08:46:46.277 Error encountered during custom seconds MySQL operation.
2017-01-03 08:46:46.282 CommandText property has not been initialized.
2017-01-03 08:46:56.278 Error encountered during custom seconds MySQL operation.
2017-01-03 08:46:56.279 CommandText property has not been initialized.
2017-01-03 08:47:00.796 New monthly record, month = 1: 2017-01-03 08:47 0.816 "High daily windrun" 2017-01-03 08:46 0.654
2017-01-03 08:47:00.865 Writing log entry for 03/01/2017 08:47:00
2017-01-03 08:47:00.867 Written log entry for 03/01/2017 08:47:00
2017-01-03 08:47:00.872 Writing today.ini, LastUpdateTime = 03/01/2017 08:47:00 raindaystart = 18 rain counter = 18.9
2017-01-03 08:47:00.872 Latest reading: 1010: 02 2E D3 00 5C 3A 00 E5 27 1B 22 00 0E 3F 00 00
2017-01-03 08:47:00.874 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('17-01-03 08:47',5.8,92,4.6,9.7,19.4,292,0.0,0.9,999.1,18.9,21.1,46,12.2,3.7,5.8,0.0,0,0.00,0.00,2.7,322,0.0,315,0.0,0.9,'WNW','NW')
2017-01-03 08:47:00.912 MySQL: 1 rows were affected.
2017-01-03 08:47:06.278 Error encountered during custom seconds MySQL operation.
2017-01-03 08:47:06.279 CommandText property has not been initialized.
2017-01-03 08:47:16.277 Error encountered during custom seconds MySQL operation.
2017-01-03 08:47:16.278 CommandText property has not been initialized.
2017-01-03 08:47:26.278 Error encountered during custom seconds MySQL operation.
2017-01-03 08:47:26.278 CommandText property has not been initialized.
2017-01-03 08:47:36.278 Error encountered during custom seconds MySQL operation.
2017-01-03 08:47:36.278 CommandText property has not been initialized.
2017-01-03 08:47:46.029 New monthly record, month = 1: 2017-01-03 08:47 999.000 "Low barometer" 2017-01-03 08:43 999.100
2017-01-03 08:47:46.279 Error encountered during custom seconds MySQL operation.
2017-01-03 08:47:46.279 CommandText property has not been initialized.
2017-01-03 08:47:56.278 Error encountered during custom seconds MySQL operation.
2017-01-03 08:47:56.278 CommandText property has not been initialized.
2017-01-03 08:48:00.799 New monthly record, month = 1: 2017-01-03 08:48 0.960 "High daily windrun" 2017-01-03 08:47 0.816
2017-01-03 08:48:00.867 Writing log entry for 03/01/2017 08:48:00
2017-01-03 08:48:00.869 Written log entry for 03/01/2017 08:48:00
2017-01-03 08:48:00.873 Writing today.ini, LastUpdateTime = 03/01/2017 08:48:00 raindaystart = 18 rain counter = 18.9
2017-01-03 08:48:00.873 Latest reading: 1010: 03 2E D3 00 5C 3A 00 E4 27 18 22 00 0C 3F 00 00
2017-01-03 08:48:00.875 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('17-01-03 08:48',5.8,92,4.6,8.6,19.4,293,0.0,0.9,999.0,18.9,21.1,46,12.2,3.9,5.8,0.0,0,0.00,0.00,2.9,326,0.0,270,0.0,0.9,'WNW','W')

I hope someone can help me.

thanks, Freerk
User avatar
steve
Cumulus Author
Posts: 26672
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Error encountered during custom seconds MYSQL operation

Post by steve »

bosschafj wrote:2017-01-03 08:46:06.277 CommandText property has not been initialized.
2017-01-03 08:46:16.277 Error encountered during custom seconds MySQL operation.
It looks like you have enabled a "Custom seconds" SQL update without supplying the SQL update command that you want to use.
Steve
bosschafj
Posts: 4
Joined: Fri 30 Dec 2016 3:03 pm
Weather Station: WH0101
Operating System: Raspberry Pi 3
Contact:

Re: Error encountered during custom seconds MYSQL operation

Post by bosschafj »

Steve, thanks for your reply.

That was the issue. I disabled these options and the "problem" is gone.
Locked