Need a little more information. Did you run "weectl station create" before attempting to run weewxd? It creates weewx.conf so, without it, there isn't any configuration file to be found.
If you ran it without any parameters it will put the file in ~/weewx-data, which, in this case, would be /root/weewx-data. If you ran it with a file path, it will set it up at that path. Let me know what you did. -tk On Fri, Jan 27, 2023 at 6:14 PM G Hammer <[email protected]> wrote: > I will start fresh and document what I see sometime over the weekend. > However, root user running directly, would need the entire path to the > config passed. Attempting simply weewxd results in a failure to find > weewx.conf. > See weewx5-root.txt > > > > > On Friday, January 27, 2023 at 8:31:58 PM UTC-5 Tom Keffer wrote: > >> The warning only happened because pip did a path check after it had been >> invoked using 'sudo', so it would not see anything that was not in >> secure_path. >> >> When it comes time to actually run weewxd, you most likely would not >> be using 'sudo', but rather simply run a daemon as the root user. The root >> user probably has /usr/local/bin in its path, if not simply add it in >> .profile (or equivalent). >> >> End result: it's probably a false warning that can be ignored. >> >> Wanted to ask you: earlier you said that the pip install instructions are >> "incomplete." I'm too close to this thing, so it's good to have some other >> eyes take a look. Anything in particular that you found incomplete or >> confusing? >> >> -tk >> >> On Fri, Jan 27, 2023 at 5:19 PM G Hammer <[email protected]> wrote: >> >>> As this is a container, I will reset and incorporate the lessons learned >>> today, wheel, etc. >>> You are correct, the path does not contain /usr/local/bin when using >>> sudo. >>> secure_path=/sbin\:/bin\:/usr/sbin\:/usr/bin >>> >>> I imagine visudo could solve that. But, are there other possibilities? >>> >>> >>> On Friday, January 27, 2023 at 5:18:04 PM UTC-5 Tom Keffer wrote: >>> >>>> Thanks for that! >>>> >>>> The error "Using legacy 'setup.py install' for pyephem, since package >>>> 'wheel' is not installed." is exactly that. You need to install >>>> 'wheel' before using pip: >>>> >>>> *sudo pip install wheel.* >>>> >>>> >>>> That little detail should really be in the quickstart guide. >>>> >>>> I suspect the "PATH" warning is because the path when running 'sudo' is >>>> different from the path without. Try >>>> >>>> *sudo -l* >>>> >>>> >>>> and see if "secure_path" is set for your user and, if so, whether it >>>> includes /usr/local/bin. >>>> >>>> >>>> >>>> >>>> On Fri, Jan 27, 2023 at 1:30 PM G Hammer <[email protected]> wrote: >>>> >>>>> I spun up a clean Rocky Linux 9.1 container on Proxmox today to give >>>>> v5 install a shot. >>>>> I created a user so as to not be installing as root, though I am going >>>>> to use sudo, so... >>>>> I used a variety of resources to get the general flow. >>>>> This one was good, but didn't hold your hand. >>>>> https://github.com/weewx/weewx/wiki/pip-install-strategies >>>>> This one had a bit more handholding, but was incomplete and was debian >>>>> oriented. >>>>> https://github.com/weewx/weewx/blob/V5/docs/quickstarts/pip.md >>>>> >>>>> Between the two, I thought I had enough to install. >>>>> sudo python3 -m pip install weewx >>>>> >>>>> That resulted in a good install, but a few items were not done with >>>>> pip as they needed wheel to be available. >>>>> There were also PATH warnings that look to be in error as the >>>>> directories are in the path. Plus, weewxd and utilities ran fine without >>>>> explicit full paths. >>>>> >>>>> I'm attaching the output from the install as weewx5-install.txt mainly >>>>> to show these items. >>>>> >>>>> I have installed weewx-mqtt and weewx-weatherlink-live, reconfigured >>>>> for these and all is running fine. >>>>> >>>>> Next I will add the systemd service file and enable it. >>>>> >>>>> I was kinda hesitant to go down the pip path. For no reason it seems. >>>>> This was easier than my traditional setup.py install. >>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/weewx-development/98edb954-2e38-490c-850c-a90f01f785fdn%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/weewx-development/98edb954-2e38-490c-850c-a90f01f785fdn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> 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 [email protected]. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-development/97464335-dcf9-4f12-af83-0351e5f6dbcan%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-development/97464335-dcf9-4f12-af83-0351e5f6dbcan%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-development/af039e68-4514-4773-894f-581b3fe940c5n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-development/af039e68-4514-4773-894f-581b3fe940c5n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/CAPq0zEBPcsMNGzz%2B3eRvQ5x4wLs1jy7mBxJEh%3DS_yZnfbH0GKw%40mail.gmail.com.
