4.0.0b18: Error in python3 setup build

115 views
Skip to first unread message

Pat

unread,
Apr 13, 2020, 6:01:22 PM4/13/20
to weewx-development
Not sure why I'm seeing this today, I haven't seen it with other builds. weewx seems to be working fine regardless? 

root@nebula:~/weewx-4.0.0b18# python3 setup.py build
/usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
  warnings
.warn(msg)
running build
running build_py
running build_scripts



Then python3 setup.py install runs it's install

root@nebula:~/weewx-4.0.0b18# service weewx status
weewx.service - LSB: weewx weather system
   
Loaded: loaded (/etc/init.d/weewx; generated)
   
Active: active (running) since Mon 2020-04-13 17:58:05 EDT; 1min 53s ago
     
Docs: man:systemd-sysv-generator(8)
 
Process: 20137 ExecStop=/etc/init.d/weewx stop (code=exited, status=0/SUCCESS)
 
Process: 20159 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS)
   
Tasks: 8 (limit: 4702)
   
CGroup: /system.slice/weewx.service
           
└─20187 /usr/bin/python3 /home/weewx/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf


Apr 13 17:58:05 nebula weewx[20182] INFO __main__: Initializing weewx version 4.0.0b18
Apr 13 17:58:05 nebula weewx[20182] INFO __main__: Using Python 3.6.9 (default, Nov  7 2019, 10:44:02) #012[GCC 8.3.0]
Apr 13 17:58:05 nebula weewx[20182] INFO __main__: Platform Linux-4.15.0-96-generic-x86_64-with-Ubuntu-18.04-bionic
Apr 13 17:58:05 nebula weewx[20182] INFO __main__: Locale is 'C.UTF-8'
....
Apr
13 17:58:10 nebula /weewxd[20187]: restx: MQTT: desired unit system is US
Apr 13 17:58:10 nebula /weewxd[20187]: restx: MQTT: network encryption/authentication will be attempted
Apr 13 17:58:10 nebula /weewxd[20187]: restx: Windy: version is 0.31
Apr 13 17:58:10 nebula /weewxd[20187]: restx: Windy: Data will be uploaded to https://stations.windy.com/pws/update
Apr 13 17:58:10 nebula weewxd[20187]: weewx[20187] INFO __main__: Starting up weewx version 4.0.0b18
Apr 13 17:58:12 nebula weewxd[20187]: weewx[20187] INFO weewx.engine: Clock error is -0.11 seconds (positive is fast)
Apr 13 17:58:12 nebula weewxd[20187]: weewx[20187] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx'
Apr 13 17:58:12 nebula weewxd[20187]: weewx[20187] INFO weewx.manager: Starting backfill of daily summaries
Apr 13 17:58:14 nebula weewxd[20187]: weewx[20187] INFO weewx.engine: Starting main packet loop.

Something I should be concerned with?

Pat

unread,
Apr 13, 2020, 6:26:38 PM4/13/20
to weewx-development
Maybe things aren't working as they should. It's no longer archiving records on the archive interval. 

I'm sure this is isolated to me. Unsure how to fix it.

Vince Skahan

unread,
Apr 13, 2020, 7:18:23 PM4/13/20
to weewx-development
On Monday, April 13, 2020 at 3:26:38 PM UTC-7, Pat wrote:
Maybe things aren't working as they should. It's no longer archiving records on the archive interval. 

I'm sure this is isolated to me. Unsure how to fix it.



Impossible to know without a description of your system.  Is this ubuntu in a VM perhaps ?
(darn users :-)

Vince Skahan

unread,
Apr 13, 2020, 7:42:36 PM4/13/20
to weewx-development
Hey Pat - I can recreate the message you saw in 'python3 setup.py build' in a current ubuntu VM, but the VM 'does' work ok in Simulator mode FWIW.


Pat

unread,
Apr 13, 2020, 8:24:52 PM4/13/20
to weewx-development
Yeah, I was trying to do a little more recreation. I ended up deleting /home/weewx, deleting the build folder, downloading fresh and starting fresh. It seems to have worked this way. 

I'm still having an issue where the archive record is not being saved to the database. I thought maybe this was a Vantage Pro2 console error? So I did power it off, remove the batteries and wait. Here's my debug info below. 

Yep, your right, Ubuntu 18.04 VM. 

I'm a little stumped why it's not saving to the archive? I wonder if I need to do a clear on the console. My output below looks similar to the corrupted station memory in the user guide.  



Apr 13 20:20:16 nebula weewx[4999] DEBUG weewx.drivers.vantage: Getting archive packets since 2020-04-13 12:50:00 EDT (1586796600)
Apr 13 20:20:16 nebula weewx[4999] DEBUG weewx.drivers.vantage: Gentle wake up of console successful
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.drivers.vantage: Retrieving 12 page(s); starting index= 0
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.drivers.vantage: DMPAFT complete: page timestamp 2020-04-04 15:35:00 EDT (1586028900) less than final timestamp 2020-04-13 12:50:00 EDT (1586796600)
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.drivers.vantage: Catch up complete.
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.reportengine: Running reports for latest time in the database.
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.drivers.vantage: Requesting 200 LOOP packets.
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.reportengine: Running report 'SeasonsReport'
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.reportengine: Found configuration file /home/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.cheetahgenerator: Using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Apr 13 20:20:18 nebula weewx[4999] DEBUG weewx.manager: Daily summary version is 1.0
Apr 13 20:20:19 nebula weewx[4999] DEBUG weewx.drivers.vantage: Gentle wake up of console successful
Apr 13 20:20:19 nebula weewx[4999] DEBUG weewx.manager: Daily summary version is 1.0
Apr 13 20:20:20 nebula weewx[4999] DEBUG weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping.
Apr 13 20:20:20 nebula weewx[4999] DEBUG weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
Apr 13 20:20:20 nebula weewx[4999] DEBUG weewx.reportengine: Report 'StandardReport' not enabled. Skipping.
Apr 13 20:20:20 nebula weewx[4999] DEBUG weewx.reportengine: Running report 'Belchertown'
Apr 13 20:20:20 nebula weewx[4999] DEBUG weewx.reportengine: Found configuration file /home/weewx/skins/Belchertown/skin.conf for report 'Belchertown'
Apr 13 20:20:20 nebula weewx[4999] DEBUG weewx.cheetahgenerator: Using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 'user.belchertown.getData']
Apr 13 20:20:20 nebula weewx[4999] DEBUG weewx.manager: Daily summary version is 1.0
Apr 13 20:20:20 nebula weewx[4999] INFO user.belchertown: version 1.1
Apr 13 20:20:20 nebula weewx[4999] INFO user.belchertown: New forecast file downloaded to /var/www/html/belchertownweather/json/darksky_forecast.json
Apr 13 20:20:20 nebula weewx[4999] DEBUG user.belchertown: Downloading earthquake data using urllib2 was successful
Apr 13 20:20:20 nebula weewx[4999] DEBUG user.belchertown: Earthquake data saved to /var/www/html/belchertownweather/json/earthquake.json
Apr 13 20:20:22 nebula weewx[4999] DEBUG weewx.manager: Daily summary version is 1.0
Apr 13 20:20:27 nebula weewx[4999] DEBUG weewx.reportengine: Report 'FTP' not enabled. Skipping.
Apr 13 20:20:27 nebula weewx[4999] DEBUG weewx.reportengine: Report 'RSYNC' not enabled. Skipping.

Thomas Keffer

unread,
Apr 13, 2020, 8:36:48 PM4/13/20
to weewx-development
You either don't have setuptools installed, or you have an old version.

python3 -m pip install --upgrade setuptools

Frankly, I'm finding setuptools more of a pain than a help and am thinking of abandoning it.

-tk

--
You received this message because you are subscribed to the Google Groups "weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/10a705db-4c93-423f-8f68-96fcbecfb9d7%40googlegroups.com.

Pat

unread,
Apr 13, 2020, 8:41:42 PM4/13/20
to weewx-development
I think we can close this out. I'm not sure what happened today but it seems I had a stale build folder, and corrupted station memory. Those 2 problems had me chasing ghosts a little bit. 

Deleting both the folder and the corrupted memory and starting fresh has me back where I need to be. 
Reply all
Reply to author
Forward
0 new messages