Syslogd may not associate messages with new nodes without a restart

Don't have time at the moment to give a ton of detail, but in a nutshell:

• Configure Syslogd to recognize messages and make events from them
• With no nodes in the system, send some syslog messages. Verify that they become events with null nodeid.
• Synchronize a requisition that contains the nodes sending the syslog messages. Let it run for a few hours.

Expected result: syslog-derived events received after synchronizing the requisition are associated with the correct node

Actual result: all syslog-derived events continue to have a null nodeid. After a restart, subsequent syslog-derived events are correctly associated.

Hypothesis: Syslogd maybe not correctly dealing with nodeAdded / nodeGainedInterface / similar events. Could be something specific to requisition or general Provisiond behavior versus auto-provisioned or general Capsd behavior.