which skin is aborting on me ?

66 views
Skip to first unread message

vince

unread,
Apr 2, 2021, 5:08:17 PM4/2/21
to weewx-user
I notice in my syslog that I have one skin aborting every run:

Apr  2 14:00:29 debian weewx[8936] INFO weewx.cheetahgenerator: Generated 9 files for report vds-local in 7.99 seconds
Apr  2 14:00:29 debian weewx[8936] INFO weewx.reportengine: Copied 0 files to /home/weewx/public_html
Apr  2 14:00:30 debian weewx[8936] DEBUG weewx.manager: Daily summary version is 4.0
Apr  2 14:00:31 debian weewx[8936] DEBUG weewx.manager: Daily summary version is 1.0
Apr  2 14:00:33 debian weewx[8936] DEBUG weewx.manager: Daily summary version is 4.0
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine: Caught unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****  outTemp
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****  Traceback (most recent call last):
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/reportengine.py", line 196, in run
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****      obj.start()
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/reportengine.py", line 281, in start
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****      self.run()
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/imagegenerator.py", line 41, in run
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****      self.genImages(self.gen_ts)
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/imagegenerator.py", line 177, in genImages
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****      start_vec_t, stop_vec_t ,data_vec_t = weewx.xtypes.get_series(var_type,
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/xtypes.py", line 94, in get_series
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****      raise weewx.UnknownType(obs_type)
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****  weewx.UnknownType: outTemp
Apr  2 14:00:51 debian weewx[8936] ERROR weewx.reportengine:         ****  Generator terminated
Apr  2 14:00:51 debian weewx[8936] DEBUG weewx.reportengine: Running report 'lastrain'
Apr  2 14:00:52 debian weewx[8936] DEBUG weewx.reportengine: Found configuration file /home/weewx/skins/lastrain/skin.conf for report 'lastrain'
Apr  2 14:00:52 debian weewx[8936] DEBUG weewx.cheetahgenerator: Using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.JSONHelpers', 'user.lastrain.vdsLastRainTags']
Apr  2 14:00:52 debian weewx[8936] DEBUG weewx.manager: Daily summary version is 4.0
Apr  2 14:00:52 debian weewx[8936] INFO weewx.cheetahgenerator: Generated 1 files for report lastrain in 0.13 seconds


What I can't figure out is 'which' skin has the issue.  Other than disabling them all and reenabling one at a time, is there a way to tell which skin is aborting ?

(note - this is 'not' 4.5.x related, I just had not noticed the syslog messages previously)

gjr80

unread,
Apr 2, 2021, 5:55:19 PM4/2/21
to weewx-user
Perhaps vds-local?

Gary

gjr80

unread,
Apr 2, 2021, 5:57:47 PM4/2/21
to weewx-user
Or alternatively, the report in weewx.conf immediately before lastrain.

Gary

vince

unread,
Apr 2, 2021, 5:59:09 PM4/2/21
to weewx-user
I'm leaning that way, but might be a custom extension I cooked up years ago.   I'm bleeding through reenabling them one by one to figure it out.

My more general question is whether there's a way to log which skin was being processed when an abort like this happened.   That might be a nice feature addition if it doesn't already exist.


On Friday, April 2, 2021 at 2:55:19 PM UTC-7 gjr80 wrote:
Perhaps vds-local?
 

Gary Roderick

unread,
Apr 2, 2021, 6:06:25 PM4/2/21
to weewx...@googlegroups.com
Tracking down the skin should be easy with debug = 1, you simply look for the line containing:

Found configuration file /home/weewx/skins/xxxxxx/skin.conf for report 'yyyyy'

immediately before the error, the problem skin will be xxxxxx and the problem report (in weewx.conf) will be yyyyy. In your case the issue is with the WeeWX image generator so would be looking at the plots in the problem skin.

Agree it would be good to see skin or report in debug=0 logs, did look at that some time ago and left it, can’t remember why (too hard, detail that is not available, not sure.

Gary

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/vjOV4j6PVRc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/996f7c5b-4b68-402a-9978-5365757fcf50n%40googlegroups.com.
--

Gary

vince

unread,
Apr 2, 2021, 6:16:23 PM4/2/21
to weewx-user
On Friday, April 2, 2021 at 3:06:25 PM UTC-7 gjr80 wrote:
Tracking down the skin should be easy with debug = 1, you simply look for the line containing:

Found configuration file /home/weewx/skins/xxxxxx/skin.conf for report 'yyyyy'

immediately before the error, the problem skin will be xxxxxx and the problem report (in weewx.conf) will be yyyyy. In your case the issue is with the WeeWX image generator so would be looking at the plots in the problem skin.


That's plenty good enough to figure it out.  Thanks.

Where it gets interesting is "weewx.UnknownAggregation: historical_max('outTemp')" in the logs, when outTemp is kinda well known.   Wondering if I found a bug in Tom's xaggs 0.6 extension.  I'll poke around.
 

vince

unread,
Apr 2, 2021, 6:52:01 PM4/2/21
to weewx-user
Think I found a bug...
No way it was my edits...
Oops, yup it was me...
     - weewx-user bug report haiku

Found it.  What was happening is I was trying to generate some images from a one-time test of the 'historical' extension that I disabled a long time ago, but neglected to comment the images out in skin.conf

Thanks for the help.

Reply all
Reply to author
Forward
0 new messages