17 Aug
2020
17 Aug
'20
3:09 a.m.
Same here, and my log files still show up/down
events.
i wonder if the issue isn't related to the line i added for Paul, but rather some
behavioral change between 488 and 526 which requires some config update?
i've never had any line in my config in relation to debug or informational logs - just
the log file definition on the daemon startup script.
previously when i started PyDECnet i used to get lines like:
2020-07-12 14:25:28.891: A35RTR: Starting DECnet/Python DECnet/Python V1.0-488
2020-07-12 14:25:28.897: A35RTR: Running as daemon
2020-07-12 14:25:28.902: A35RTR: Event type 2.0, Local node state change
From node 35.1023 (A35RTR), occurred 12-Jul-2020 14:25:28.902
Reason = Operator command
Old state = Off
New state = On
2020-07-12 14:25:29.967: A35RTR: Event type 4.15, Adjacency up
From node 35.1023 (A35RTR), occurred 12-Jul-2020 14:25:29.967
Circuit = GRE-12
Adjacent node = 12.1023 (A12RTR)
2020-07-12 14:25:30.351: A35RTR: Event type 4.15, Adjacency up
From node 35.1023 (A35RTR), occurred 12-Jul-2020 14:25:30.351
Circuit = GRE-31
Adjacent node = 31.1023 (IMPRTR)
and the various up/down notifications as areas go up and down as expected.
but now all i get is:
2020-08-17 10:06:24.616: A35RTR: Starting DECnet/Python DECnet/Python V1.0-526
2020-08-17 10:06:24.624: A35RTR: Logging configuration reloaded
2020-08-17 10:06:24.624: A35RTR: Now running as daemon
is there something i require in my pydecnet.conf or when i'm running the daemon that i
might be missing?
cheers, Wiz!!
________________________________
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> on behalf of
Robert Armstrong <bob at jfcl.com>
Sent: Monday, 17 August 2020 10:40:17 AM
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] HECnet mapper -- request to backbone node operators
David Moylan <djm at wiz.net.au> wrote:
as per Keith, i also had to make the changes to TapEth so i could speak to /dev/net/tun.
FWIW, I just use pcap to talk to a tap device. Works fine, and no patches to pyDECnet
required.
i run PyDECnet as a daemon and normally my local log
files show up/down route visibility.
i assume with the "logging monitor" line that this functionality is changed?
Same here, and my log files still show up/down events.
Say, Paul ? now that we have the HECnet status reported to a single point, how about a
way for anybody to subscribe to network events? Perhaps by email or SMS??
Bob