pserv "connection refused" errors spamming its log file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
High
|
Unassigned |
Bug Description
I installed upgraded packages and after the installation finished, pserv was reporting:
2014-10-10 15:13:22+1000 [ClusterClient,
2014-10-10 15:13:22+1000 [ClusterClient,
2014-10-10 15:13:22+1000 [ClusterClient,
2014-10-10 15:13:22+1000 [ClusterClient,
Followed by:
2014-10-10 15:13:23+1000 [Uninitialized] Event-loop maas:pid=22266 (127.0.0.1:42097): Connection was refused by other side: 111: Connection refused.
2014-10-10 15:13:23+1000 [Uninitialized] Event-loop maas:pid=22266 (127.0.0.1:42097): Connection was refused by other side: 111: Connection refused.
2014-10-10 15:13:23+1000 [Uninitialized] Event-loop maas:pid=22266 (10.0.0.9:42097): Connection was refused by other side: 111: Connection refused.
2014-10-10 15:13:23+1000 [Uninitialized] Event-loop maas:pid=22266 (10.0.0.9:42097): Connection was refused by other side: 111: Connection refused.
2014-10-10 15:13:23+1000 [Uninitialized] Event-loop maas:pid=22266 (192.168.
2014-10-10 15:13:23+1000 [Uninitialized] Event-loop maas:pid=22266 (192.168.
The latter opes here repeating over and over.
Note that 10.0.0.9 is the actual IP address of my maas host. The UI reports that the cluster is connected OK.
Changed in maas: | |
milestone: | 1.7.1 → 1.7.2 |
Changed in maas: | |
milestone: | 1.7.2 → 1.7.3 |
Changed in maas: | |
status: | Triaged → Won't Fix |
Targeting to next since everything appears to actually work, but the log noise is a nuisance. Any ideas Gavin?