Comment 4 for bug 1554436

Cheryl,

Thanks for looking into this.

Regarding problem #2, the Canonical Cloud Reference Architecture we now follow for the BootStacks we build has nova-compute (therefore libvirt-bin et cetera) on all metal deployed by Juju. Each will have the default virt net (virbr0 with 192.168.122.1).

As you suggest, the Juju logs become very much filled with error messaging, and we see the several SYN_SENT state failed connections on all units, as noted in the bug description. From an operations view, these are both issues that can cloud troubleshooting (if you'll excuse the pun). There is really no such thing as 'harmless' error logging: if it says 'bad' it is, and it's dangerous to learn to ignore error messages and bad network connections, as I'm sure you'll appreciate.

I assume the failed connections to rsyslogd on the state servers are an issue for Juju, but you may be better placed to understand the impact than I am. Does this limit the usefulness of debug-log, for example?

Perhaps if the impact, from the Juju view, is not critical, the logging itself could be corrected too. The message says:

    ERROR juju.worker runner.go:223 exited "rsyslog": dial tcp <state server addr>:6514: connection refused

You'll note it does not tell us why this is critical, just that a connection has been refused and that this is important enough to be regarded as an error, rather than a warning.

The accuracy and usefulness of the log message is really a separate bug, though. Even if we knew more about the impact and severity from the log message, we still have erroneous attempts to connect to state servers, which need to be stopped.

Cheers,

Mick