pserv "connection refused" errors spamming its log file

Bug #1379636 reported by Julian Edwards
14
This bug affects 2 people
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,client] Event-loop 'maas:pid=23213' authenticated.
2014-10-10 15:13:22+1000 [ClusterClient,client] Event-loop 'maas:pid=23213' authenticated.
2014-10-10 15:13:22+1000 [ClusterClient,client] Event-loop 'maas:pid=23212' authenticated.
2014-10-10 15:13:22+1000 [ClusterClient,client] Event-loop 'maas:pid=23212' authenticated.

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.122.1: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.122.1:42097): Connection was refused by other side: 111: Connection refused.

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.

Tags: landscape
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Targeting to next since everything appears to actually work, but the log noise is a nuisance. Any ideas Gavin?

Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → next
Revision history for this message
Gavin Panella (allenap) wrote :

Did it shut up after about 5 minutes? If so, it's probably because the event-loops were not able to stop cleanly and remove their host:port entries from the database. This is bug 1350786.

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 1379636] Re: pserv "connection refused" errors spamming its log file

On Friday 10 Oct 2014 09:21:15 you wrote:
> Did it shut up after about 5 minutes? If so, it's probably because the
> event-loops were not able to stop cleanly and remove their host:port
> entries from the database. This is bug 1350786.

Oh I didn't check. I'll look again next time I run up my rig, please feel
free to dupe this if you're confident, I can easily undupe if necessary.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Also getting tons of these connection refused messages in the logs.

tags: added: landscape
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Un-duping from bug 1350786 as this seems to be a result of it trying to connect to 127.0.0.1 (and the link-local address, from memory).

Changed in maas:
milestone: next → 1.7.1
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.