Bug #11912

acnetd doesn't recover when booting without network

Added by Richard Neswold over 4 years ago. Updated about 2 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


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 nodesd task sets the node table through Level II functions
  • Once the table is fully populated, acnetd goes into the background (at this point, a script starting acnetd will proceed.)

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.

Related issues

Related to ACNET Service - Feature #16707: Find an alternate to 'nodesd'New05/30/2017


#1 Updated by Richard Neswold over 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 nodesd services.

#2 Updated by Richard Neswold over 3 years ago

#3 Updated by Richard Neswold about 2 years ago

  • Category set to acnetd
  • Status changed from Assigned to Closed

Kevin recently had problems booting several acnetd nodes. The problem was, again, nodesd. I'm closing out this issue since the solution will be found when #16707 gets resolved.

Also available in: Atom PDF