I was mistaken, when i use --daemon it crashes - always The import serial thing, i did that on the cmd line. I removed StdPrint and --daemon and it works without excess logging I am in the process of upgrading to 4.7 now
On Wednesday, March 2, 2022 at 9:52:33 AM UTC-8 tke...@gmail.com wrote: > I'm glad things are working, but just for my edification, what did we fix? > I thought the --daemon flag fixed the problem of LOOP packet data appearing > in the log. Why was it necessary to comment out StdPrint? > > And, what fixed the problem with the importation of "serial"? > > On Wed, Mar 2, 2022 at 9:28 AM Cat22 <erben...@gmail.com> wrote: > >> python3 -c "import serial" >> that works, return code is 0 (echo $?) >> >> On Wednesday, March 2, 2022 at 9:26:20 AM UTC-8 Cat22 wrote: >> >>> I made this change and it worked! At least it looks like it worked, I >>> need to watch it for awhile to be sure >>> #report_services = *weewx.engine.StdPrint*, weewx.engine.StdReport, >>> user.lowBattery.BatteryAlarm >>> report_services = weewx.engine.StdReport, user.lowBattery.BatteryAlarm >>> >>> On Wednesday, March 2, 2022 at 9:04:04 AM UTC-8 Cat22 wrote: >>> >>>> That's basically what i did. When i add --daemon and restart i see this: >>>> Mar 02 08:53:52 pc2 systemd[1]: weewx.service: Current command vanished >>>> from the unit file, execution of the command list won't be resumed. >>>> followed by some weather data then this: >>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: >>>> Initializing weewx version 4.0.0 >>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Using >>>> Python 3.8.8 (default, Feb 19 2021, 16:53:21) [GCC] >>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Platform >>>> Linux-5.8.11-x86_64-with-glibc2.2.5 >>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Locale >>>> is 'en_US.UTF-8' >>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: PID file >>>> is /var/run/weewx.pid >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Using >>>> configuration file /usr/local/bin/weewx/weewx.conf >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO weewx.engine: >>>> Loading station type Vantage (weewx.drivers.vantage) >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Received >>>> signal TERM (15). >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] ERROR weewx.engine: >>>> Import of driver failed: (<class '__main__.Terminate'>) >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** Traceback (most recent call last): >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "/usr/local/bin/weewx/bin/weewx/engine.py", line 103, in >>>> setupStation >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** self.console = loader_function(config_dict, self) >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line >>>> 39, in loader >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** return VantageService(engine, config_dict) >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line >>>> 1897, in __init__ >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** Vantage.__init__(self, **config_dict[DRIVER_NAME]) >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line >>>> 511, in __init__ >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** self.port.openPort() >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line >>>> 305, in openPort >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** import serial >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "/usr/lib/python3.8/site-packages/serial/__init__.py", >>>> line 14, in <module> >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** from serial.serialutil import * >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "<frozen importlib._bootstrap>", line 991, in >>>> _find_and_load >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "<frozen importlib._bootstrap>", line 975, in >>>> _find_and_load_unlocked >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "<frozen importlib._bootstrap>", line 657, in >>>> _load_unlocked >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "<frozen importlib._bootstrap>", line 562, in >>>> module_from_spec >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "<frozen importlib._bootstrap>", line 481, in >>>> _init_module_attrs >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** File "/usr/local/bin/weewx/bin/weewxd", line 257, in >>>> sigTERMhandler >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** raise Terminate >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: >>>> **** Terminate >>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL __main__: >>>> Unable to load driver: >>>> On Wednesday, March 2, 2022 at 8:47:31 AM UTC-8 tke...@gmail.com wrote: >>>> >>>>> "weewx crashed" doesn't give us very much information. >>>>> >>>>> There are other command line flags that are normally used in a systemd >>>>> file. >>>>> >>>>> Why not use the weewx.service that comes with WeeWX? It's in the >>>>> util/systemd directory. Modify as required. >>>>> >>>>> On Wed, Mar 2, 2022 at 8:30 AM Cat22 <erben...@gmail.com> wrote: >>>>> >>>>>> Seems like the --daemon option fixed things >>>>>> my service file looks like this (in part() >>>>>> [Service] >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ExecStart=/usr/local/bin/weewx/bin/weewxd >>>>>> /usr/local/bin/weewx/weewx.conf --daemon >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ExecReload=/usr/bin/killall -TERM $MAINPID >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Type=simple >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Restart=on-failure >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> RestartSec=100s >>>>>> >>>>>> Good grief this google thing here is hard to use! >>>>>> >>>>>> ok, i just checked before posting and weewx crashed - it never does >>>>>> tthat but the --daemon opt was the only thing that changed >>>>>> >>>>>> On Wednesday, March 2, 2022 at 8:23:51 AM UTC-8 Cat22 wrote: >>>>>> >>>>>>> I thought systemd asked services not to demonize as systemd does >>>>>>> that for them. Ami right about this? >>>>>>> However, I will try it. >>>>>>> >>>>>>> On Wednesday, March 2, 2022 at 8:20:32 AM UTC-8 Cat22 wrote: >>>>>>> >>>>>>>> weewx version 4.0.0 >>>>>>>> I am having trouble posting here, my posts seem to just disappear. >>>>>>>> Hopefully this one will make it. >>>>>>>> I found log_success in 2 places in weewx.conf I set that to False >>>>>>>> also, but it doesnt make a bit of differrence >>>>>>>> >>>>>>>> Here is a sample: >>>>>>>> Mar 02 08:18:20 pc2 weewxd[14910]: LOOP: 2022-03-02 08:18:19 PST >>>>>>>> (1646237899) altimeter etc etc, the line is very long >>>>>>>> On Wednesday, March 2, 2022 at 8:15:48 AM UTC-8 tke...@gmail.com >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Thanks, i just tried that and restarted wewx but it's still >>>>>>>>>> printing that loop data. >>>>>>>>> >>>>>>>>> >>>>>>>>> I'm not sure what you mean by "printing that loop data." Are we >>>>>>>>> talking about the log? Or, printing to a console through standard >>>>>>>>> output? >>>>>>>>> >>>>>>>>> If the former, the Vantage driver logs no data in the system log >>>>>>>>> --- only control information. StdArchive does log successful and >>>>>>>>> unsuccessful insertions into the database, but these should be >>>>>>>>> controlled >>>>>>>>> by log_success and log_failure, respectively, at least on modern >>>>>>>>> versions >>>>>>>>> of WeeWX (what version are you using?). >>>>>>>>> >>>>>>>>> If the latter (printing to the console), then you shouldn't see >>>>>>>>> this if you are running weewxd as a daemon. >>>>>>>>> >>>>>>>>> Perhaps an excerpt of the log so we can see what you're concerned >>>>>>>>> about? >>>>>>>>> >>>>>>>>> On Wed, Mar 2, 2022 at 7:55 AM Tom Keffer <tke...@gmail.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Just set option log_success >>>>>>>>>> <http://www.weewx.com/docs/usersguide.htm#General> to False. >>>>>>>>>> >>>>>>>>>> On Wed, Mar 2, 2022 at 7:50 AM Cat22 <erben...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> debug=0 but weewx writes over a thousand lines to the systemd >>>>>>>>>>> journal. Its writing the data it read from the Vantage Pro II >>>>>>>>>>> mostly LOOP: >>>>>>>>>>> lines. I would rather it didn't do that. None of it is error data. >>>>>>>>>>> Any idea how to prevent it? >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> 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/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%40googlegroups.com >>>>>>>>>>> >>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>>> . >>>>>>>>>>> >>>>>>>>>> -- >>>>>> 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/5c5be090-439b-4fcd-9b23-b7172e606515n%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/weewx-user/5c5be090-439b-4fcd-9b23-b7172e606515n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >> 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/56130b42-b4a2-4594-87f3-25681860c018n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/56130b42-b4a2-4594-87f3-25681860c018n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/a18a43dc-9c99-47bb-b375-bb20bc22ca2fn%40googlegroups.com.
