is there anything relevant showing in regiond.log when you curl and it
returns connection refused?
(note that from the previous curl command, the 5240 port is missing)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
We had this issue using the maas 3.0 snap in the new SQA lab
curling the address came back with a long delayed "connection refused"
and nothing else.
I was able to get everything back in working order by restarting maas.
Another odd symptom was that I could loop calls where i would connect
via t
I can't find anything obvious in the log files.
It would be good it you could provide the output of:
curl http://10.230.56.2/MAAS/rpc/
from the rackd that is having problems. Both when it's working, and when
you see this problem.
** Changed in: maas
Status: Triaged => Incomplete
--
Y
Last time we saw a a bug very much like this
(https://bugs.launchpad.net/maas/+bug/1707971), it was fixed in the 2.2
release range. The error logs look almost identical, so I'm going to
take a chance and triage this as if it were a regression. Someone can
swat me if they prove me wrong, no worrie
attached just those log files, we also have older rotated regiond.log
files
** Changed in: maas
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914807
Title:
rack ca
** Attachment added: "logs.tar.bz2"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1914807/+attachment/5472847/+files/logs.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914807
Title:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914807
Title:
rack can't contact region, deployments fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1914807/+
Can you please attach maas.log, regiond.log an rackd.log?
The error doesn't provide much clues as to why this is happening.
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914807
Title:
rack can't contact region, deployments fails
To manage notifications a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914807
Title:
rack
We are resorting to rebooting maas every day just so we can avoid
hitting this and having deployments fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914807
Title:
rack can't contact region, de
11 matches
Mail list logo
