Comment 1:

Labels changed: added go1.3maybe.

Comment 2:

Labels changed: added priority-later, packagebug, removed priority-triage.

Comment 3:

Labels changed: added release-none, removed go1.3maybe.

Comment 4:

Labels changed: added repo-main.

Comment 5:

I have a simple patch available for this problem at
Jimdo/periodicnoise@672a225
and even a very crude test available here
Jimdo/periodicnoise@c670de2
which shows the hang due to hanging listeners quite nicely.
I have this in production since about a month without any problems. Are you guys
interested in my polishing this up?
My problem in production there have been missing timeouts in the unix domain socket log
listeners.

Comment 6:

I'm not able to reproduce this running on tip.
My test environment:
rsyslog (running on a separate host)
nc (running on a separate host)
go tip (changeset:   18948:94165b19719e)
Ubuntu 13.10
Using the code from http://play.golang.org/p/ADb0RmfVYI  with a slight modification to
connect to a different host running rsyslog and nc I get the following behavior:
When running rsyslog on a remote host:
go run main.go 
2014/01/27 02:41:39 sent msg: <nil>
2014/01/27 02:41:40 sent msg: <nil>
2014/01/27 02:41:41 sent msg: <nil>
2014/01/27 02:41:42 sent msg: <nil>
2014/01/27 02:41:43 sent msg: <nil>
2014/01/27 02:41:44 sent msg: <nil>
2014/01/27 02:41:45 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:46 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:47 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:48 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:49 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:50 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:51 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:52 sent msg: <nil>
2014/01/27 02:41:53 sent msg: <nil>
2014/01/27 02:41:54 sent msg: <nil>
2014/01/27 02:41:55 sent msg: <nil>
2014/01/27 02:41:56 sent msg: <nil>
2014/01/27 02:41:57 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:58 sent msg: dial tcp 192.168.12.151:514: connection refused
2014/01/27 02:41:59 sent msg: dial tcp 192.168.12.151:514: connection refused
Starting and stopping the rsyslog server results in the expected behavior -- errors are
generated when rsyslog is down and the connection is restored  when rsyslog is restarted.
I get the exact same results against the a remote host running nc -ls 514.

Comment 7 by phmmnd:

I think this bug is actually a duplicate of 5541 and so was fixed in commit
8d5f80a6d6db6a076f5e429f45e26ac602c25c5e (which was in 1.2 but not in the 1.1.1 I was
using when I reported the issue).

Comment 8:

Status changed to Retracted.