[HECnet] Re: auto launching pydecnet at boot?

On Jul 8, 2024, at 4:57 PM, Mike Kostersitz &lt;mikekostersitz(a)gmail.com <mailto:mikekostersitz@gmail.com>> wrote: It starts if I launch it with my startup script. I did upgrade from T1.1 which was working before, I used the build/install flow before that and it always started automatically. this is my launch.sh ``` cd /home/pi/.local/bin sudo pydecnet --daemon --log-config /home/pi/dev-logging.json /home/pi/theark.conf /home/pi/http.conf ``` This is my http.conf ``` # Enable HTTP server (no HTTPS) as well as API (default socket name) http -4 --http-port 8000 --https-port 8443 --certificate /etc/letsencrypt/live/the-ark.ddns.net/fullchain.pem <http://the-ark.ddns.net/fullchain.pem> api ``` Nothing happens on boot. The log file is simply not written. Nothing in dmesg. Yes I did update Python as well but in place with all packages as well. Packages seem to be in place ``` pi@rpi-theark:~ $ pip3 install python-daemon Looking in indexes: https://pypi.org/simple <https://pypi.org/simple>, https://www.piwheels.org/simple <https://www.piwheels.org/simple> Requirement already satisfied: python-daemon in /usr/lib/python3/dist-packages (2.2.3) pi@rpi-theark:~ $ pip3 --version pip 18.1 from /usr/lib/python3/dist-packages/pip (python 3.7) ``` Mike From: Paul Koning &lt;paulkoning(a)comcast.net <mailto:paulkoning@comcast.net>> Sent: Monday, July 8, 2024 1:13 PM To: The Hobbyist DECnet mailing list &lt;hecnet(a)lists.dfupdate.se <mailto:hecnet@lists.dfupdate.se>> Subject: [HECnet] Re: auto launching pydecnet at boot? Does it not even try to start, or does it try and then fail at startup? Presumably you have a startup script for this, and these days that would typically be a systemd type of script. So the question would be: what does your systemd script to in order to start up pydecnet? Did you specify a log file? What's in the log file? Also: did you upgrade from V1.0 or from T1.1? There are some config differences between 1.0 and 1.1, described in the README.txt file. The one that could prevent startup is this one, introduced during the T1.1 beta cycle: f. The --api and --insecure-api switches on the "http" configuration line have been removed. Instead, API control is via a new "api" line. See doc/config.txt for details. One more possibility: did you switch to a newer Python? If so, did you install any library packages needed for your config? For example, if you want to start pydecnet with the --daemon switch you have to have python-daemon installed on whatever python version you're now running. Anything you install with "pip" -- any of those optional Python packages -- is installed for a particular version, whichever is the default Python version at that time or the specific one you referred to. For example "pip3.10 install ..." will install something for your python3.10; it won't be seen by any other python version you might have installed. paul _______________________________________________ HECnet mailing list -- hecnet(a)lists.dfupdate.se <mailto:hecnet@lists.dfupdate.se> To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se <mailto:hecnet-leave@lists.dfupdate.se>