Alright, I think I'm good to go. I have no idea what happened, but here's what I did.
I did - sudo apt-get remove weewx - sudo apt-get remove --purge weewx I used the mlocate package to find all weewx files I could find, and deleted them - sudo updatedb - sudo locate wee I then re-installed weewx: - sudo apt-get install weewx Then I used a file diff utility and added my custom weewx.conf components for my custom driver and custom reports. I uploaded the skins to /etc/weewx/skins and the driver to /usr/share/weewx/user. I started weewx and I get this from sudo systemctl status weewx ● weewx.service - LSB: weewx weather system Loaded: loaded (/etc/init.d/weewx; bad; vendor preset: enabled) Active: active (running) since Sun 2017-07-09 18:17:53 EDT; 8s ago Docs: man:systemd-sysv-generator(8) Process: 8302 ExecStop=/etc/init.d/weewx stop (code=exited, status=0/ SUCCESS) Process: 8662 ExecStart=/etc/init.d/weewx start (code=exited, status=0/ SUCCESS) Tasks: 6 Memory: 12.4M CPU: 97ms CGroup: /system.slice/weewx.service └─8679 python /usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf Jul 09 18:17:53 example.com weewx[8679]: restx: PWSWeather: Data for station will be posted Jul 09 18:17:53 example.com weewx[8679]: restx: CWOP: Data for station will be posted Jul 09 18:17:53 example.com weewx[8679]: restx: WOW: Posting not enabled. Jul 09 18:17:53 example.com weewx[8679]: restx: AWEKAS: Posting not enabled. Jul 09 18:17:53 example.com weewx[8679]: restx: WeatherBug: service version is 0.6 Jul 09 18:17:53 example.com weewx[8679]: restx: WeatherBug: Data will be uploaded for station_number= publisher_id= Jul 09 18:17:53 example.com weewx[8679]: restx: WeatherCloud: service version is 0.10 Jul 09 18:17:53 example.com weewx[8679]: restx: WeatherCloud: Data will be uploaded for id= Jul 09 18:17:53 example.com weewx[8679]: engine: Starting up weewx version 3.7.1 Jul 09 18:17:53 example.com weewx[8679]: engine: Starting main packet loop. A few of things that stand out to me: 1. The status now shows active (running) whereas before it didn't 2. Before 'weewxd' was not in my PATH, so I had to manually specify /usr/ share/weewxd I can now just use 'weewxd'. 3. /usr/share had all of the weewx folders in the root of this path. So instead of everything being in /usr/share/weewx/[schemas|user|weecfg|weedb](etc), it was in the root of /usr/share. After reinstalling, everything is in the singular subfolder as it should be. So I think I'm all set now. The only thing I did differently was initially I installed as the user account performing "sudo apt-get install weewx". This time I did "sudo bash -login" to get a full root shell, then did "apt-get install weewx". Technically the sudo should have been all I needed the first time around. That's the only thing I've done different. No idea what went wrong. Thanks for the help vince! On Sunday, July 9, 2017 at 4:03:31 PM UTC-4, Pat wrote: > > Just tried this, and it explains why there's nothing to upgrade. apt > thinks it's already upgraded. Even though the debug has a wrong version. > > ubuntu@xenon:~$ sudo apt install weewx > Reading package lists... Done > Building dependency tree > Reading state information... Done > weewx is already the newest version (3.7.1-1). > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. > > Still lost on this one. Will try the other suggestion of going back to the > "dist" copies I made and slowly adding things in. > > > > On Sunday, July 9, 2017 at 3:57:53 PM UTC-4, Pat wrote: >> >> Strange, that's all I see in my syslog - no custom things going on with >> it either. This is a mostly-fresh install of Ubuntu 16.04. >> >> Here's the output of my apt settings. >> >> ubuntu@xenon:/var/lib/apt/lists$ ls -lgd weewx* >> -rw-r--r-- 1 root 2537 Mar 23 10:12 weewx. >> com_apt_dists_squeeze_InRelease >> -rw-r--r-- 1 root 12583 Mar 23 10:12 weewx. >> com_apt_dists_squeeze_main_binary-all_Packages >> >> ubuntu@xenon:/var/lib/apt/lists$ sha1sum weewx* >> e438785ed8f2d7bd8211145b3d160080f6b2656e weewx. >> com_apt_dists_squeeze_InRelease >> db54ea29a4565aa811096a19ff46bc1564c9e8c2 weewx. >> com_apt_dists_squeeze_main_binary-all_Packages >> >> 'sudo apt-get clean && sudo apt-get update && sudo apt-get upgrade' had 0 >> results for packages needing upgrading. I also noticed all other repo's say >> xenial, but weewx says squeeze. Would that matter? >> >> I'll download the deb package and install that and see what happens. >> >> >> On Sunday, July 9, 2017 at 3:05:53 PM UTC-4, vince wrote: >>> >>> On Sunday, July 9, 2017 at 9:49:26 AM UTC-7, Pat wrote: >>>> >>>> >>>> Debug mode is on: debug=1, and in syslog all I see is this: >>>> >>>> Jul 9 12:23:54 example systemd[1]: Starting LSB: weewx weather system >>>> ... >>>> Jul 9 12:23:54 example systemd[1]: Started LSB: weewx weather system. >>>> >>>> No other log information in syslog. Is there another weewx log? Running >>>> this command didn't find a specific weewx log. sudo find / -name weewx >>>> -print | grep log >>>> >>>> >>> That particular find command wouldn't do it, but no there isn't a >>> weewx-specific log unless you did something special in your syslog config >>> file. You should have a whole lot more than one line in /var/log/syslog >>> however, even if it blew up massively during initialization. >>> >>> >>> >>>> Perhaps I need to restore my "dist" backup copy, and manually copy my >>>> weewx.conf settings over? I don't see how that would change much though. >>>> >>>> >>> I would generally lean that way. FWIW, a long time ago I took the time >>> to make my extensions and skins installable via the extension installer, so >>> for me a clean build is just doing weewx (setup.py or package, doesn't >>> matter) and then running the extension installer a few times to add the >>> skins and extensions. No copying nor editing required. Granted, that took >>> some time to cook up of course. >>> >>> In this case, I'd start with vanilla weewx. Change your setup to use >>> mysql, with no extensions. Get the vanilla product to work with that >>> database, then gradually change things to put your customizations in one at >>> a time. >>> >>> >>> An interesting item: Initializing weewx version 3.6.2 - The latest >>>> version is 3.7.1. >>>> >>> >>> >>>> >>>> Performing a sudo apt-get update && sudo apt-get upgrade does not show >>>> an upgrade available for weewx 3.7.1 >>>> >>>> >>> Hmmm, can't explain that one. I did a clean install in vagrant and it >>> got 3.7.1 as the latest. >>> >>> >>>> Should I try a manual install of the deb package? >>>> >>>> >>> I'd lean toward yes, so you get all the bug fixes etc. >>> >>> I'm wondering if you forgot to get a root shell before doing 'apt-get >>> update' perhaps. If you cd to /var/lib/apt/lists you'll see the listings >>> of the various repos you have configured. Mine looks like: >>> >>> >>> ubuntu@ubuntu-xenial:/var/lib/apt/lists$ ls -lgd weewx* >>> -rw-r--r-- 1 root 2537 Mar 23 07:12 weewx. >>> com_apt_dists_squeeze_InRelease >>> -rw-r--r-- 1 root 12583 Mar 23 07:12 weewx. >>> com_apt_dists_squeeze_main_binary-all_Packages >>> >>> >>> ubuntu@ubuntu-xenial:/var/lib/apt/lists$ sha1sum weewx* >>> e438785ed8f2d7bd8211145b3d160080f6b2656e weewx. >>> com_apt_dists_squeeze_InRelease >>> db54ea29a4565aa811096a19ff46bc1564c9e8c2 weewx. >>> com_apt_dists_squeeze_main_binary-all_Packages >>> >>> >>> The top of the last file there should show a 3.7.1 version available if >>> your apt-get update worked ok. >>> >>> You might also try a 'apt-get clean' to clean the cache before you >>> 'apt-get update' to rebuild 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.