27 Jun
2024
27 Jun
'24
11:56 a.m.
With new version available, I decided to get the secure monitoring web
server up (never tried this before)
I expect to see both ports 8000 and 8443 show up as listening in netstat ,
but I see only 8000
Any thoughts? I'll attach the trace file, but if that does not survive
posting:
grep -E "Starting|Listening" /var/log/on*trace
2024-06-27 11:27:52.337: MainThread: Starting DECnet/Python V1.1.0rc1
2024-06-27 11:28:07.579: ONAPI4: Starting node ONAPI4
2024-06-27 11:28:07.579: ONAPI4: Starting timer subsystem
2024-06-27 11:28:07.579: ONAPI4: Starting datalink layer
2024-06-27 11:28:07.583: ONAPI4: Starting MOP layer
2024-06-27 11:28:07.583: ONAPI4: Starting mop for _TapEth TAP-1
2024-06-27 11:28:07.585: ONAPI4: Starting Routing layer
2024-06-27 11:28:07.590: ONAPI4: Starting NSP
2024-06-27 11:28:07.590: ONAPI4: Starting Session Control
2024-06-27 11:28:07.591: ONAPI4: Starting DMC-2-1023
2024-06-27 11:28:07.593: ONAPI4: Starting DMC-29-2
2024-06-27 11:28:07.593: https: Starting https server on port 8443
2024-06-27 11:28:07.593: ONAPI4: Starting http server on port 8000
2024-06-27 11:28:07.594: https: Listening at *:8443
2024-06-27 11:28:07.594: ONAPI4: Listening at *:8000
2024-06-27 11:28:07.595: ONAPI4: Starting DMC-29-420
2024-06-27 11:28:07.596: ONAPI4: Starting DMC-29-700
2024-06-27 11:28:07.597: ONAPI4: Starting DMC-31-3
2024-06-27 11:28:07.598: ONAPI4: Starting MUL-1-1023
2024-06-27 11:28:07.598: ONAPI4: Starting MUL-27-1
2024-06-27 11:28:07.599: ONAPI4: Starting MUL-30-15
2024-06-27 11:28:07.601: ONAPI4: Listening at *:9601
2024-06-27 11:28:07.603: ONAPI4: Listening at *:9651
2024-06-27 11:28:07.607: ONAPI4: Listening at *:9621
2024-06-27 11:28:07.613: ONAPI4: Listening at *:8887
2024-06-27 11:28:07.615: ONAPI4: Listening at *:9641
2024-06-27 11:28:12.045: ONAPI4: starting object 25 (MIRROR)
pi@raspi4 ~ $ netstat -l --numeric-ports
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN
tcp 0 0 localhost:631 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8887 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:33685 0.0.0.0:* LISTEN
[etc, no 8443]
Command line:
/usr/local/bin/pydecnet --daemon --log-file /var/log/onapi4.log --keep 3
--log-level TRACE /opt/onapi4.conf /opt/http.conf
http.conf:
http -4 --http-port 8000 --https-port 8443 --certificate /home/pi/raspi4.pem
api
raspi4.pem is a self-signed certificate for now
Wilm
-----Original Message-----
From: Paul Koning <paulkoning(a)comcast.net>
Sent: Monday, June 24, 2024 6:56 PM
To: The Hobbyist DECnet mailing list <hecnet(a)lists.dfupdate.se>
Subject: [HECnet] DECnet/Python V1.1 release candidate
Gentlepeople,
I figured it was about time to move PyDECnet past the "beta 1.1" stage. I
sorted through the various bugfixes I had not yet commmitted and did so, the
built kits called "release candidate 1". The code is currently running on
node PYTHON, and kits can be found on the downloads page at
http://akdesign.dyndns.org:8080/resources/public/index.html
I'd like to get the "real" release out soon, so it would be great if some
of
you could take this version for a test drive. I'd also like to hear if
there were any bugfixes I was supposed to do that I missed.
By the way, this version requires Python 3.7 or later.
Last but not least, I moved the source control to GitHub:
https://github.com/pkoning2/pydecnet . The Subversion repository is now
obsolete; I will take it off line soon. The full history should be in the
Git version (it was converted from the Subversion repository).
paul
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se To unsubscribe send an email
to hecnet-leave(a)lists.dfupdate.se