Thanks Graham. I read that killing the install process will mess up the install at a minimum and possibly corrupt the system. Is there a way to get back to the install script from the D option?
On Thursday, July 30, 2020 at 11:55:39 PM UTC-7, Graham Eddy wrote: > > ctl-Z stop just means you have paused the command and placed it in > background - it is still there, waiting, but paused (and holding the lock). > bring it back to foreground to resume and interact with it by $ fg > > then kill it with ctl-C > (or use some other method to kill it gently such as $ kill %1 ) > then try the command again. > cheers > > On 31 Jul 2020, at 3:24 pm, brisguy foo <iams...@gmail.com <javascript:>> > wrote: > > Sorry, that was a typo. I did run apt-get update (not upgrade). It seemed > to run successfully but I just now noticed the following: > > E: Repository 'http://weewx.com/apt squeeze InRelease' changed its > 'Origin' value from '. squeeze' to 'python2 squeeze' > E: Repository 'http://weewx.com/apt squeeze InRelease' changed its > 'Label' value from '. squeeze' to 'python2 squeeze' > N: This must be accepted explicitly before updates for this repository can > be applied. See apt-secure(8) manpage for details. > > Turns out there was an error when I tried to do the update. I got around > this by rerunning the commands to trust weewx repository and configure > python 3. Did not do this before because the user's guide says you only > need to do it once upon first install. > > Anyway, during the weewx install it told me it was going to replace > skins.conf and allowed me the D option to see the differences, but I could > not figure out how to get out of it. After trying several things, I used > CTL-Z which stopped the install process (I knew I would screw it up !). > Tried running install afterwards, but it won't run - saying the process is > locked. > > E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource > temporarily unavailable) > E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), > is another process using it? > > Is there any was to recover from this? > > On Thursday, July 30, 2020 at 6:14:08 PM UTC-7, Kevin Davis wrote: >> >> Do an “apt-get update” first to update the package manager so it’s aware >> of the newest version numbers. >> >> >> On Jul 30, 2020, at 6:04 PM, brisguy foo <iams...@gmail.com> wrote: >> >> >> Ah, thanks for that. Should have been able to figure that out myself. >> >> However, I just tried to upgrade using these commands: >> sudo apt-get upgrade >> sudo apt-get install weewx >> >> And was informed that 3.9.2 is the latest version! >> >> Does this mean I have to download the .tar and do it manually? I'm not >> too confident I can pull that off... >> >> On Thursday, July 30, 2020 at 4:16:29 PM UTC-7, Tom Keffer wrote: >>> >>> See the Upgrade Guide. http://www.weewx.com/docs/upgrading.htm >>> >>> On Thu, Jul 30, 2020 at 3:25 PM brisguy foo <iams...@gmail.com> wrote: >>> >>>> I was about to for that anyway. However, now that I am ready, I am not >>>> sure how to proceed. I see some info on installing and some on removing >>>> but >>>> none on upgrading. Do I need to uninstall first? Or is there an apt-get >>>> upgrade command? >>>> >>>> Thanks again. >>>> >>>> On Thursday, July 30, 2020 at 11:54:01 AM UTC-7, Tom Keffer wrote: >>>>> >>>>> Found the problem. You're using V3.9.2, but support for the LOOP2 >>>>> format was not introduced until V4.0.0. You'll need to upgrade to do this. >>>>> >>>>> I was misled because the change log (wrongly) said that support for >>>>> LOOP2 packets was introduced in V3.7.0, so I assumed support was there >>>>> --- >>>>> I never bothered to check the actual code base. The log was fixed in >>>>> commit >>>>> 56ebe96 >>>>> <https://github.com/weewx/weewx/commit/56ebe963e55c73b030492be9ecb6ad84d6885e2a> >>>>> >>>>> Sorry for the confusion. >>>>> >>>>> -tk >>>>> >>>>> On Thu, Jul 30, 2020 at 10:39 AM brisguy foo <iams...@gmail.com> >>>>> wrote: >>>>> >>>>>> I suppose that is possible, but remember, I started the program >>>>>> directly, using the /etc/weewx/weewx.conf as the conf file. That is the >>>>>> file I sent to this thread. >>>>>> >>>>>> Here is the syslog file. Sorry, it is a bit busy since I found that >>>>>> the daemon did not restart yesterday when I thought it did (still don't >>>>>> know why - no error message and the terminal indicated success) and >>>>>> would >>>>>> not start from the command line today so when I ran it directly again, >>>>>> there were lots of records to catch up. >>>>>> >>>>>> On Wednesday, July 29, 2020 at 4:43:44 PM UTC-7, Tom Keffer wrote: >>>>>>> >>>>>>> On a side note, when I tried running weewx directly without a config >>>>>>>> file argument, it would not run, even though my config file is located >>>>>>>> at >>>>>>>> /etc/weewx/weewx.conf. Is that a bug? >>>>>>>> >>>>>>> >>>>>>> No, but it suggests that you may not be editing the weewx.conf file >>>>>>> that weewxd is actually using. >>>>>>> >>>>>>> At this point, I have to ask for a log. Restart weewx, let it run >>>>>>> through the first reporting cycle. Post the resultant log. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>> >>>>>> -- >>>>>> 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...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/weewx-user/0cd14da1-7635-44c5-a13b-197d45725537o%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/weewx-user/0cd14da1-7635-44c5-a13b-197d45725537o%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...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/38fa16ae-b22e-4611-8d81-053989827c96o%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/38fa16ae-b22e-4611-8d81-053989827c96o%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...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/ddd2e056-605d-4038-9aad-7e8112a40cf8o%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/ddd2e056-605d-4038-9aad-7e8112a40cf8o%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...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/03ac4a7f-931d-4913-8c3d-fbb4116efb63o%40googlegroups.com > > <https://groups.google.com/d/msgid/weewx-user/03ac4a7f-931d-4913-8c3d-fbb4116efb63o%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/ae259149-16f5-46a2-a871-7329d22ace86o%40googlegroups.com.
