After 7 years, we better start from scratch, so marking this bug as NEW.
** Changed in: apache2 (Ubuntu)
Assignee: Chuck Short (zulcss) => (unassigned)
** Changed in: apache2 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
S
I'm not sure this is coming from cinder - the dependency chain is
python-oauth2client -> python-googleapi -> resource-agents (Recommends).
** Package changed: python-oauth2client (Ubuntu) => resource-agents
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server,
@Th - I think you're probably correct in that this is a load issue,
rather than a specific rabbitmq software issue. It looks like the
system is so loaded you're hitting some sort of 90 second timeout at
which point systemd just gives up:
/etc/systemd/system.conf: DefaultTimeoutStartSec=90s
you
Dropped googleapi to Suggests, avoiding the need for this MIR
** Changed in: resource-agents (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to resource-agents in Ubuntu.
https://bugs.launchpad.net/bugs/1
*** This bug is a duplicate of bug 1731502 ***
https://bugs.launchpad.net/bugs/1731502
Thanks for filing this bug in Ubuntu.
This seems to be a duplicate of bug #1731502, where there was no network
available when nmbd was restarted:
Status: "nmbd: No local IPv4 non-loopback interfaces ava