acnetd doesn't recover when booting without network
Kevin Martin reported that
acnetd doesn't recover properly when it's started without a working network. If the network outage is brief, it seems to recover and starts-up properly. If the network is missing for a few minutes, it doesn't recover.
The correct start-up behavior is:
- Allocate resources
- Multicast (to
nodesd) a request for the node table
- The highest priority
nodesdtask sets the node table through Level II functions
- Once the table is fully populated,
acnetdgoes into the background (at this point, a script starting
acnetd will multicast the request every 10 seconds until it gets its node table filled. Until this happens, the script will appear to hang. A prolonged absence of the network seems to break this algorithm.
#1 Updated by Richard Neswold about 3 years ago
Kevin Martin reported the problem occurred again. This time, we were able to get more information.
We've recently had a series of power outages. All three
nodesd services weren't responding, so Kevin's node never got its node table populated. Kevin noticed in the ACNET log that it somehow got it trunk and node correctly, but then reassigned its trunk and node to
$9EE, which is the ACNET address for
DNLDD! It is not obvious why this happened.
We did learn that part of diagnosing this problem is to remove all