Re: [weewx-user] Pipe errors etc

[hind...@gmail.com]

Still no further forward with this problem, but by setting loop_on_it=1 as 
Tom K suggested, I do at least have a working weather station website, 
albeit with repeated periods where it is not "live" and where graphs etc 
are always an hour or so out of date.

I have put the most recent log below, in case anyone has any more 
brainwaves that might solve this.

In the meantime, I am having trouble stopping weewx - not sure if this is 
related to my ongoing pipe errors or not.  When I type 

ps -aux|grep weewx

I get

root   535  5.6  6.1 117524 58128 ?Sl   10:16   2:42 python2 
/usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid 
/etc/weewx/weewx.conf
pi2130  0.0  0.0   4368   564 pts/0S+   11:04   0:00 grep 
--color=auto weewx

And, then typing 

sudo /etc/init.d/weewx stop

produces

 Stopping weewx (via systemctl): weewx.service.

but then repeating the grep command, still shows the 535 process still 
running?

How do I stop weewx - do I have to use kill 535 perhaps?

Thanks

David.


Log of weewx from syslog

Dec 16 10:57:10 raspberrypi weewx[535] INFO __main__: Starting up weewx 
version 4.10.2
Dec 16 10:57:10 raspberrypi weewx[535] DEBUG weewx.manager: Daily summary 
version is 4.0
Dec 16 10:57:10 raspberrypi weewx[535] DEBUG weewx.manager: Daily summary 
version is 4.0
Dec 16 10:57:10 raspberrypi weewx[535] DEBUG weewx.manager: Daily summary 
version is 4.0
Dec 16 10:57:10 raspberrypi weewx[535] DEBUG weewx.manager: Daily summary 
version is 4.0
Dec 16 10:57:12 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Dec 16 10:57:13 raspberrypi weewx[535] INFO weewx.engine: Clock error is 
1.42 seconds (positive is fast)
Dec 16 10:57:13 raspberrypi weewx[535] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Dec 16 10:57:13 raspberrypi weewx[535] INFO weewx.manager: Starting 
backfill of daily summaries
Dec 16 10:57:13 raspberrypi weewx[535] INFO weewx.manager: Daily summaries 
up to date
Dec 16 10:57:13 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2023-12-16 10:55:00 GMT (1702724100)
Dec 16 10:57:16 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Dec 16 10:57:18 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Retrieving 0 page(s); starting index= 0
Dec 16 10:57:18 raspberrypi weewx[535] INFO weewx.engine: Starting main 
packet loop.
Dec 16 10:57:20 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Dec 16 10:57:21 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Requesting 200 LOOP packets.
Dec 16 10:57:24 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Dec 16 10:57:25 raspberrypi weewx[535] ERROR weewx.drivers.vantage: 
send_data: no  received from Vantage console
Dec 16 10:57:25 raspberrypi weewx[535] ERROR weewx.drivers.vantage: LOOP 
batch try #1; error: No  received from Vantage console
Dec 16 10:57:32 raspberrypi weewx[535] ERROR weewx.drivers.vantage: ip-read 
error: timed out
Dec 16 10:57:32 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 1 failed. Exception: timed out
Dec 16 10:57:32 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#1 unable to wake up console... sleeping
Dec 16 10:57:41 raspberrypi weewx[535] ERROR weewx.drivers.vantage: ip-read 
error: timed out
Dec 16 10:57:41 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 2 failed. Exception: timed out
Dec 16 10:57:41 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#2 unable to wake up console... sleeping
Dec 16 10:57:50 raspberrypi weewx[535] ERROR weewx.drivers.vantage: ip-read 
error: timed out
Dec 16 10:57:50 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 3 failed. Exception: timed out
Dec 16 10:57:50 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#3 unable to wake up console... sleeping
Dec 16 10:57:58 raspberrypi weewx[535] ERROR weewx.drivers.vantage: ip-read 
error: timed out
Dec 16 10:57:58 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 4 failed. Exception: timed out
Dec 16 10:57:58 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#4 unable to wake up console... sleeping
Dec 16 10:57:59 raspberrypi weewx[535] ERROR weewx.drivers.vantage: Unable 
to wake up Vantage console
Dec 16 10:57:59 raspberrypi weewx[535] ERROR weewx.drivers.vantage: LOOP 
batch try #2; error: Unable to wake up Vantage console
Dec 16 10:58:01 raspberrypi weewx[535] ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe
Dec 16 10:58:01 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Wake up 
try 1 failed. Exception: [Errno 32] Broken pipe
Dec 16 10:58:01 raspberrypi weewx[535] DEBUG weewx.drivers.vantage: Retry 
#1 unable to wake up console... sleeping
Dec 16 10:58:02 raspberrypi weewx[535] ERROR weewx.drivers.vantage: 
ip-write error: [Errno 32] Broken pipe
Dec 16 10:58:02 

[weewx-user] Where does the error output go, when there is a parse error parsing weewx.conf?

['michael.k...@gmx.at' via weewx-user]

When I have an erroneous weewx.conf and start weewx using
systemctl start weewx
there is nothing in my log file, nor in /var/log/syslog . I am on Debian 
using rsyslog and have the logging configured like so in weewx.conf:
[Logging]
version = 1
disable_existing_loggers = False

# Root logger
[[root]]
level = INFO
handlers = rotate,

# Additional loggers would go in the following section. This is useful 
for tailoring logging
# for individual modules.
[[loggers]]

# Definitions of possible logging destinations
[[handlers]]

# Log to a set of rotating files
[[[rotate]]]
level = INFO
formatter = verbose
class = logging.handlers.RotatingFileHandler
filename = /var/log/weewxd.log
maxBytes = 1000
backupCount = 4

When I start weewxd manually, the error output is shown, any I ideas where 
the output is stored (if it is stored) or how to set up logging, that this 
output is stored in the weewxd.log file?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/61b4b425-4ded-46be-b0e5-160ae648ea78n%40googlegroups.com.

[weewx-user] Failed MQTT Server Install

[Mark Sanchez]

Hello all,

I attempted to install MQTT for real time data of my weather station using 
this guide. However, it doesn't want to connect to the server and I wanted 
to disable it for the time being. I commented out all the lines associated 
with it but when I run wee_reports I get the following error. I'm wondering 
what I need to do to restore my weather station's status as now I just see 
that it can't connect to it on the webpage.

Traceback (most recent call last):
  File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
obj.start()
  File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
self.run()
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 169, in run
ngen = self.generate(gen_dict[section_name], section_name, self.gen_ts)
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate
ngen += self.generate(section[subsection], subsection, gen_ts)
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate
ngen += self.generate(section[subsection], subsection, gen_ts)
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 321, in generate
searchList = self._getSearchList(encoding, timespan,
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 415, in 
_getSearchList
search_list += obj.get_extension_list(timespan, db_lookup)
  File "/usr/share/weewx/user/belchertown.py", line 2015, in 
get_extension_list
if self.generator.skin_dict["Extras"]["mqtt_websockets_host_kiosk"] != 
"":
  File "/usr/lib/python3/dist-packages/configobj.py", line 554, in 
__getitem__
val = dict.__getitem__(self, key)
KeyError: 'mqtt_websockets_host_kiosk'

How can I get rid of the mqtt_websockers_host_kiosk?
Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/35daa585-c236-44a6-ae5c-746f65e8faa3n%40googlegroups.com.

[weewx-user] Re: Where does the error output go, when there is a parse error parsing weewx.conf?

[vince]

If you have rsyslog installed and running, it's using that,  but without 
seeing your error output, hard to say.

I'd try "sudo journalctl -u weewx" and see if anything is returned of any 
value.

Which debian version might help a little too.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0159b2f4-d3c5-4650-9790-fb020610d8bfn%40googlegroups.com.

[weewx-user] Re: Where does the error output go, when there is a parse error parsing weewx.conf?

['michael.k...@gmx.at' via weewx-user]

cat /etc/debian_version
11.7

journalctl isn't installed

Oops, I deleted the original message this was it:

When I have an erroneous weewx.conf and start weewx using
systemctl start weewx
there is nothing in my log file, nor in /var/log/syslog . I am on Debian 
using rsyslog and have the logging configured like so in weewx.conf:
[Logging]
version = 1
disable_existing_loggers = False
   
# Root logger
[[root]]
level = INFO
handlers = rotate,
   
# Additional loggers would go in the following section. This is useful 
for tailoring logging
# for individual modules.
[[loggers]]
   
# Definitions of possible logging destinations
[[handlers]]
   
# Log to a set of rotating files
[[[rotate]]]
level = INFO
formatter = verbose
class = logging.handlers.RotatingFileHandler
filename = /var/log/weewxd.log
maxBytes = 1000
backupCount = 4

When I start weewxd manually, the error output is shown, any I ideas where 
the output is stored (if it is stored) or how to set up logging, that this 
output is stored in the weewxd.log file?

vince schrieb am Samstag, 16. Dezember 2023 um 19:41:12 UTC+1:

> If you have rsyslog installed and running, it's using that,  but without 
> seeing your error output, hard to say.
>
> I'd try "sudo journalctl -u weewx" and see if anything is returned of any 
> value.
>
> Which debian version might help a little too.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/87629405-f30c-4ed6-b99c-b4fa07db329fn%40googlegroups.com.

[weewx-user] Re: Where does the error output go, when there is a parse error parsing weewx.conf?

['michael.k...@gmx.at' via weewx-user]

 found it:  /var/log/journal/weewx.log

michael.k...@gmx.at schrieb am Samstag, 16. Dezember 2023 um 19:48:04 UTC+1:

> cat /etc/debian_version
> 11.7
>
> journalctl isn't installed
>
> Oops, I deleted the original message this was it:
>
> When I have an erroneous weewx.conf and start weewx using
> systemctl start weewx
> there is nothing in my log file, nor in /var/log/syslog . I am on Debian 
> using rsyslog and have the logging configured like so in weewx.conf:
> [Logging]
> version = 1
> disable_existing_loggers = False
>
> # Root logger
> [[root]]
> level = INFO
> handlers = rotate,
>
> # Additional loggers would go in the following section. This is useful 
> for tailoring logging
> # for individual modules.
> [[loggers]]
>
> # Definitions of possible logging destinations
> [[handlers]]
>
> # Log to a set of rotating files
> [[[rotate]]]
> level = INFO
> formatter = verbose
> class = logging.handlers.RotatingFileHandler
> filename = /var/log/weewxd.log
> maxBytes = 1000
> backupCount = 4
>
> When I start weewxd manually, the error output is shown, any I ideas where 
> the output is stored (if it is stored) or how to set up logging, that this 
> output is stored in the weewxd.log file?
>
> vince schrieb am Samstag, 16. Dezember 2023 um 19:41:12 UTC+1:
>
>> If you have rsyslog installed and running, it's using that,  but without 
>> seeing your error output, hard to say.
>>
>> I'd try "sudo journalctl -u weewx" and see if anything is returned of any 
>> value.
>>
>> Which debian version might help a little too.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/80cbccd1-d4c2-4227-84d5-6a2ad47cc43an%40googlegroups.com.

[weewx-user] Re: Where does the error output go, when there is a parse error parsing weewx.conf?

[vince]

Yup.  That's where systemd writes logs.

On Saturday, December 16, 2023 at 10:57:40 AM UTC-8 michael.k...@gmx.at 
wrote:

>  found it:  /var/log/journal/weewx.log
>
> michael.k...@gmx.at schrieb am Samstag, 16. Dezember 2023 um 19:48:04 
> UTC+1:
>
>> cat /etc/debian_version
>> 11.7
>>
>> journalctl isn't installed
>>
>> Oops, I deleted the original message this was it:
>>
>> When I have an erroneous weewx.conf and start weewx using
>> systemctl start weewx
>> there is nothing in my log file, nor in /var/log/syslog . I am on Debian 
>> using rsyslog and have the logging configured like so in weewx.conf:
>> [Logging]
>> version = 1
>> disable_existing_loggers = False
>>
>> # Root logger
>> [[root]]
>> level = INFO
>> handlers = rotate,
>>
>> # Additional loggers would go in the following section. This is 
>> useful for tailoring logging
>> # for individual modules.
>> [[loggers]]
>>
>> # Definitions of possible logging destinations
>> [[handlers]]
>>
>> # Log to a set of rotating files
>> [[[rotate]]]
>> level = INFO
>> formatter = verbose
>> class = logging.handlers.RotatingFileHandler
>> filename = /var/log/weewxd.log
>> maxBytes = 1000
>> backupCount = 4
>>
>> When I start weewxd manually, the error output is shown, any I ideas 
>> where the output is stored (if it is stored) or how to set up logging, that 
>> this output is stored in the weewxd.log file?
>>
>> vince schrieb am Samstag, 16. Dezember 2023 um 19:41:12 UTC+1:
>>
>>> If you have rsyslog installed and running, it's using that,  but without 
>>> seeing your error output, hard to say.
>>>
>>> I'd try "sudo journalctl -u weewx" and see if anything is returned of 
>>> any value.
>>>
>>> Which debian version might help a little too.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/16f9d80f-e99f-45fe-9a56-0577dc53b56dn%40googlegroups.com.

[weewx-user] Re: Failed MQTT Server Install

[vince]

Just turn it off in your skin configuration in weewx.conf

 [[Belchertown]]
[[[Extras]]]
mqtt_websockets_enabled = 0


On Saturday, December 16, 2023 at 10:40:46 AM UTC-8 Mark Sanchez wrote:

> Hello all,
>
> I attempted to install MQTT for real time data of my weather station using 
> this guide. However, it doesn't want to connect to the server and I wanted 
> to disable it for the time being. I commented out all the lines associated 
> with it but when I run wee_reports I get the following error. I'm wondering 
> what I need to do to restore my weather station's status as now I just see 
> that it can't connect to it on the webpage.
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
> obj.start()
>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
> self.run()
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 169, in run
> ngen = self.generate(gen_dict[section_name], section_name, self.gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate
> ngen += self.generate(section[subsection], subsection, gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate
> ngen += self.generate(section[subsection], subsection, gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 321, in generate
> searchList = self._getSearchList(encoding, timespan,
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 415, in 
> _getSearchList
> search_list += obj.get_extension_list(timespan, db_lookup)
>   File "/usr/share/weewx/user/belchertown.py", line 2015, in 
> get_extension_list
> if self.generator.skin_dict["Extras"]["mqtt_websockets_host_kiosk"] != 
> "":
>   File "/usr/lib/python3/dist-packages/configobj.py", line 554, in 
> __getitem__
> val = dict.__getitem__(self, key)
> KeyError: 'mqtt_websockets_host_kiosk'
>
> How can I get rid of the mqtt_websockers_host_kiosk?
> Thanks.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b06246d3-62d9-4423-ab74-c2c8700f66ffn%40googlegroups.com.

Re: [weewx-user] Pipe errors etc

[vince]

Sorry - we can't fix your network.  Lots of legacy embedded type 2.4GHz 
wifi things have issues staying on the network and stable.   I'd suggest 
you try to see if your wifi is being interfered with from a neighbor 
perhaps.  Maybe you can switch which channel your wifi is on.

FWIW, we have too many neighbors here with misconfigured wifi to even 
count, depending on who moves in/out and who visits them occasionally. 
 What I eventually needed to do was (a) move everything in the house that 
could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and basically 
try to out-radiate the neighbors.  Problem went away at that point.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%40googlegroups.com.

[weewx-user] weewx - mariadb high read and cpu utilization....

['Christian Peters' via weewx-user]

Hi all,

i just updated my weewx vm and noticed high cpu load since end of October 
(average was 20% cpu load, now 80%cpu load).  
Maybe this is my fault as I added some features but I can't remember what 
could cause this? Maybe a typo in weewx.conf. 
I did an iotop -o and get this, even if weewx is idle and did all things in 
the 1min interval. :

  694 be/4 mysql  25.99 M/s0.00 B/s mariadbd

So there is a constant sending of the database I think? 
I'm not very experienced but I google a littel bit and did this:
login into mysql and did a 
> SHOW PROCESSLIST;

I do this many times and I see if weewx runs at 15sec after full minute to 
45sec it query the data and send  it into the database. 
But I see all the time this one line sending data...:

| 121 | weewx | localhost | weewx_new | Query   |1 | Sending data | 
SELECT sum(  CASEWHEN `outTemp`>1000.0 THEN 0.0WHEN `outTemp`>86.0 
THEN 36.0WHEN `outTem |0.000 |

What could be the reason for this!? This line never dropped, seems to cause 
the high read and  cpu!?

Any idea howto debug this...?

Thanks in advance...

Regards,

Christian 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d9bc381f-cca8-4f0d-8128-612513aa96e6n%40googlegroups.com.

Re: [weewx-user] Re: Failed MQTT Server Install

[Mark Sanchez]

Yeah. That hasn't worked. It's still trying to call on it from the script.
Might have to go in to the Belchertown script and comment out any mqtt
stuff.

On Sat, Dec 16, 2023, 11:24 AM vince  wrote:

> Just turn it off in your skin configuration in weewx.conf
>
>  [[Belchertown]]
> [[[Extras]]]
> mqtt_websockets_enabled = 0
>
>
> On Saturday, December 16, 2023 at 10:40:46 AM UTC-8 Mark Sanchez wrote:
>
>> Hello all,
>>
>> I attempted to install MQTT for real time data of my weather station
>> using this guide. However, it doesn't want to connect to the server and I
>> wanted to disable it for the time being. I commented out all the lines
>> associated with it but when I run wee_reports I get the following error.
>> I'm wondering what I need to do to restore my weather station's status as
>> now I just see that it can't connect to it on the webpage.
>>
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> obj.start()
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> self.run()
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 169, in run
>> ngen = self.generate(gen_dict[section_name], section_name,
>> self.gen_ts)
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate
>> ngen += self.generate(section[subsection], subsection, gen_ts)
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate
>> ngen += self.generate(section[subsection], subsection, gen_ts)
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 321, in generate
>> searchList = self._getSearchList(encoding, timespan,
>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 415, in
>> _getSearchList
>> search_list += obj.get_extension_list(timespan, db_lookup)
>>   File "/usr/share/weewx/user/belchertown.py", line 2015, in
>> get_extension_list
>> if self.generator.skin_dict["Extras"]["mqtt_websockets_host_kiosk"]
>> != "":
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 554, in
>> __getitem__
>> val = dict.__getitem__(self, key)
>> KeyError: 'mqtt_websockets_host_kiosk'
>>
>> How can I get rid of the mqtt_websockers_host_kiosk?
>> Thanks.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/b06246d3-62d9-4423-ab74-c2c8700f66ffn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CA%2BCc0BEcf3S9LjuvyJAndMJocV52TeLLBipP5jHBSKQmZoypwA%40mail.gmail.com.

[weewx-user] Re: weewx - mariadb high read and cpu utilization....

['Christian Peters' via weewx-user]

...ok...I tracked it down: I updated the * weewx-GTS 
 * xtype extension in October. 
I disabled the xtype_service *user.GTS.GTSService * and the querys and high 
load and I/O is gone. 
Will ask Karen K.

Regards,

Christian 


Christian Peters schrieb am Samstag, 16. Dezember 2023 um 20:42:30 UTC+1:

> Hi all,
>
> i just updated my weewx vm and noticed high cpu load since end of October 
> (average was 20% cpu load, now 80%cpu load).  
> Maybe this is my fault as I added some features but I can't remember what 
> could cause this? Maybe a typo in weewx.conf. 
> I did an iotop -o and get this, even if weewx is idle and did all things 
> in the 1min interval. :
>
>   694 be/4 mysql  25.99 M/s0.00 B/s mariadbd
>
> So there is a constant sending of the database I think? 
> I'm not very experienced but I google a littel bit and did this:
> login into mysql and did a 
> > SHOW PROCESSLIST;
>
> I do this many times and I see if weewx runs at 15sec after full minute to 
> 45sec it query the data and send  it into the database. 
> But I see all the time this one line sending data...:
>
> | 121 | weewx | localhost | weewx_new | Query   |1 | Sending data | 
> SELECT sum(  CASEWHEN `outTemp`>1000.0 THEN 0.0WHEN `outTemp`>86.0 
> THEN 36.0WHEN `outTem |0.000 |
>
> What could be the reason for this!? This line never dropped, seems to 
> cause the high read and  cpu!?
>
> Any idea howto debug this...?
>
> Thanks in advance...
>
> Regards,
>
> Christian 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c5707797-67e1-4774-b913-b9c1c44cc039n%40googlegroups.com.

Re: [weewx-user] Re: Failed MQTT Server Install

[vince]

you need to stop+restart weewx if you edit weewx.conf

On Saturday, December 16, 2023 at 11:45:17 AM UTC-8 Mark Sanchez wrote:

> Yeah. That hasn't worked. It's still trying to call on it from the script. 
> Might have to go in to the Belchertown script and comment out any mqtt 
> stuff. 
>
> On Sat, Dec 16, 2023, 11:24 AM vince  wrote:
>
>> Just turn it off in your skin configuration in weewx.conf
>>
>>  [[Belchertown]]
>> [[[Extras]]]
>> mqtt_websockets_enabled = 0
>>
>>
>> On Saturday, December 16, 2023 at 10:40:46 AM UTC-8 Mark Sanchez wrote:
>>
>>> Hello all,
>>>
>>> I attempted to install MQTT for real time data of my weather station 
>>> using this guide. However, it doesn't want to connect to the server and I 
>>> wanted to disable it for the time being. I commented out all the lines 
>>> associated with it but when I run wee_reports I get the following error. 
>>> I'm wondering what I need to do to restore my weather station's status as 
>>> now I just see that it can't connect to it on the webpage.
>>>
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>>> obj.start()
>>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>>> self.run()
>>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 169, in run
>>> ngen = self.generate(gen_dict[section_name], section_name, 
>>> self.gen_ts)
>>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in 
>>> generate
>>> ngen += self.generate(section[subsection], subsection, gen_ts)
>>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in 
>>> generate
>>> ngen += self.generate(section[subsection], subsection, gen_ts)
>>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 321, in 
>>> generate
>>> searchList = self._getSearchList(encoding, timespan,
>>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 415, in 
>>> _getSearchList
>>> search_list += obj.get_extension_list(timespan, db_lookup)
>>>   File "/usr/share/weewx/user/belchertown.py", line 2015, in 
>>> get_extension_list
>>> if self.generator.skin_dict["Extras"]["mqtt_websockets_host_kiosk"] 
>>> != "":
>>>   File "/usr/lib/python3/dist-packages/configobj.py", line 554, in 
>>> __getitem__
>>> val = dict.__getitem__(self, key)
>>> KeyError: 'mqtt_websockets_host_kiosk'
>>>
>>> How can I get rid of the mqtt_websockers_host_kiosk?
>>> Thanks.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b06246d3-62d9-4423-ab74-c2c8700f66ffn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a58fcd9f-a272-41ff-8f61-1f8204091aa4n%40googlegroups.com.

Re: [weewx-user] interceptor stops my station

['Rainer Lang' via weewx-user]

interesting, but as you didn't give us more context, you're likely not 
to receive a satisfactory reply


1. it is good practice to post a _*complete*_ syslog protocol from a 
weewx start to at least one archiving and reporting cycle (unless it 
doesn't reach it)
2. you should tell us about your context - what weather station are you 
talking about, what console do you use, did you change anything in your 
console (added a sensor, changed a configuration etc.)


without that you expect us reading a crystal ball - what we are not 
proficient in


On 14.12.2023 21:22, enu...@gmail.com wrote:

today, i got this error
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__: Caught 
unrecoverable exception:
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:  
 'totalrainin'
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:  
 Traceback (most recent call last):
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:     File 
"/usr/share/weewx/weewxd", line 154, in main
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:      
 engine.run()
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:     File 
"/usr/share/weewx/weewx/engine.py", line 208, in run
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:      
 for packet in self.console.genLoopPackets():
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:     File 
"/usr/share/weewx/user/interceptor.py", line 2558, in genLoopPackets
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:      
 pkt = self._device.parser.parse(data)
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:     File 
"/usr/share/weewx/user/interceptor.py", line 2398, in parse
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:      
 self.LABEL_MAP.pop('totalrainin')
Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:  
 KeyError: 'totalrainin'

Dec 14 15:32:57 raspberrypi weewx[756] CRITICAL __main__:   Exiting.
I don't know because sudendly stop weewx and i had reset it hours later.
--
You received this message because you are subscribed to the Google 
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5e0bacdf-f9f4-4af5-b7d1-079cec62eefdn%40googlegroups.com 
.


--
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8dc1ba54-e80f-421a-92f5-7eb1847baf0c%40gmail.com.

[weewx-user] Re: Keep losing nameserver on ubuntu 22.04

[cric...@pobox.com]

I get tired of trying to figure out all the various ways /etc/resolve.conf 
can get modified, for all my static hosts,
if it's a link, I replace it with the file with the contents I want, then 
run:
chattr +i /etc/resolve/conf
That prevents any further messing with the file.  It does mean you are on 
the hook for any needed updates.
The alternative is figuring out who (which process(es)) is maintaining the 
file and get the configs to those files
straightened out.  I manage my own DNS and DHCP servers so I know what 
resolve.conf needs to have, but the
various OS's drive me nuts, so I remove their ability to screw things up.

Chris

On Friday, December 15, 2023 at 7:48:22 AM UTC-7 WindnFog wrote:

> I wouldn't touch /etc/resolv.conf as the O/S manages this.  I use the 
> Ubuntu Gnome GUI to set my DNS servers. Under the network icon on the top 
> left, select Settings and beside "Wired," again, pick Settings.  I pick the 
> IPv4 tab and select Manual . . . I'm using a static IP on my LAN.  At the 
> bottom, there is a DNS slot.  Turn off Automatic and put in your DNS 
> servers separated by commas. Use the DNS servers your ISP specifies, or go 
> with proven public ones like Google (8.8.8.8. 8.8.4.4), Cloudflare 
> (1.1.1.1, 1.0.0.1), OpenDNS (208.67.222.222, 208.67.220.220), etc.
>
> I don't see how weeWX could be changing these. It's almost certainly a 
> Ubuntu issue.
>
> On Friday, December 15, 2023 at 8:54:06 AM UTC-4 bgra...@umw.edu wrote:
>
>> Hello,
>> Weewx 4.10.2 has been running fine but suddenly stopped FTPing to the 
>> main site. After checking, I found that my dns servers were missing. After 
>> putting them back, it ran normally for a few hours and then FTP stopped 
>> again because dns had disappeared. Not sure what is happening here as weewx 
>> is running fine. Resolv.conf seems to be a simlink to something else and 
>> can’t be edited. Using webmin to reset the dns servers only works for a 
>> short while.
>> I realize this probably isn’t a weewx problem but I’m completely stumped 
>> as to how to fix the problem. Any help or suggestions would be greatly 
>> appreciated. Thanks in advance.
>> Cheers,
>> Bob
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bebc8bfe-dec8-459b-b990-3da90c61f2e3n%40googlegroups.com.