Debian Bug report logs - #602552
Listener failed with error: socket() for [[(null)]:10050]

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Harald Dunkel <harri@afaics.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Listener failed with error: socket() for [[(null)]:10050]

Date: Fri, 05 Nov 2010 20:44:39 +0100

[Message part 1 (text/plain, inline)]

Package: zabbix-agent
Version: 1:1.8.3-2

On i386 the zabbix agentd doesn't start. Instead there is an error
message in the log file saying

  3174:20101105:203153.820 Zabbix Agent started. Zabbix 1.8.3 (revision 13928).
  3174:20101105:203153.824 Listener failed with error: socket() for [[(null)]:10050] failed with error 97: Address family not supported by protocol.

Using _exactly_ the same (md5sum!) zabbix_agentd.conf on amd64
there is no problem.

This is a severe problem, because I cannot monitor my i386
hosts.

Please mail if I can help to track this down.


Regards

Harri

[zabbix_agentd.conf (text/plain, attachment)]

[signature.asc (application/pgp-signature, attachment)]

Message #10 received at 602552@bugs.debian.org (full text, mbox, reply):

From: Christoph Haas <email@christoph-haas.de>

To: Harald Dunkel <harri@afaics.de>, 602552@bugs.debian.org

Subject: Re: Bug#602552: Listener failed with error: socket() for [[(null)]:10050]

Date: Sat, 06 Nov 2010 13:19:40 +0100

Please try:

Server=10.10.10.9,::ffff::10.10.10.9

instead of

Server=10.10.10.9

because I suspect it may rather be connected to IPv6 support than the 
architecture (i386 versus amd64).

 Christoph


Am 05.11.2010 20:44, schrieb Harald Dunkel:
> Package: zabbix-agent
> Version: 1:1.8.3-2
>
> On i386 the zabbix agentd doesn't start. Instead there is an error
> message in the log file saying
>
>    3174:20101105:203153.820 Zabbix Agent started. Zabbix 1.8.3 (revision 13928).
>    3174:20101105:203153.824 Listener failed with error: socket() for [[(null)]:10050] failed with error 97: Address family not supported by protocol.
>
> Using _exactly_ the same (md5sum!) zabbix_agentd.conf on amd64
> there is no problem.
>
> This is a severe problem, because I cannot monitor my i386
> hosts.
>
> Please mail if I can help to track this down.
>
>
> Regards
>
> Harri

Message #15 received at 602552@bugs.debian.org (full text, mbox, reply):

From: Harald Dunkel <harri@afaics.de>

To: 602552@bugs.debian.org

Subject: Re: Bug#602552: Listener failed with error: socket() for [[(null)]:10050]

Date: Tue, 09 Nov 2010 07:15:53 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/06/10 13:19, Christoph Haas wrote:
> Please try:
> 
> Server=10.10.10.9,::ffff::10.10.10.9
> 

I tried, but it didn't help. I still got

  2813:20101109:070422.372 Zabbix Agent started. Zabbix 1.8.3 (revision 13928).
  2813:20101109:070422.380 Listener failed with error: socket() for [[(null)]:10050] failed with error 97: Address family not supported by protocol.

Switching off ipv6 in /etc/modprobe.d/aliases.conf

	alias net-pf-10 off

didn't help, either. ifconfig showed no inet6 address,
but the error message is still there.


Regards

Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzY5xQACgkQUTlbRTxpHjf4gACfdFuWpj/L1/jWbQTrPBfJtwYC
ewMAn2iv7o5NmZSU5RzJM5LVrSaXskyK
=ufHY
-----END PGP SIGNATURE-----

Message #22 received at 602552@bugs.debian.org (full text, mbox, reply):

From: Christoph Haas <email@christoph-haas.de>

To: 602552@bugs.debian.org

Subject: Amazon EC2?

Date: Sat, 06 Aug 2011 00:41:22 +0200

I recently found the same issue on 32-bit Amazon EC2 instances.
Compiling the Zabbix package without IPv6 support worked there. The
actual reason is not yet clear to me. If anyone has an idea about the
cause I welcome it.

 Christoph

Message #27 received at 602552-done@bugs.debian.org (full text, mbox, reply):

From: Dmitry Smirnov <onlyjob@member.fsf.org>

To: 602552-done@bugs.debian.org

Subject: Done: Listener failed with error: socket() for [[(null)]:10050]

Date: Tue, 7 Aug 2012 00:13:41 +1000

Package: zabbix-agent
Version: 1:1.8.4-1

The very same problem has been reported for the same version of zabbix on 
Fedora: 

  https://bugzilla.redhat.com/show_bug.cgi?id=664639

Where commenter suggested that the problem may have been fixed in 1.8.4rc2.

(I couldn't find anything related in upstream bug tracker)

At the moment I'm closing this issue as it is appears to be no longer a 
problem.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 602552@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Regards,
Dmitry.

Message #32 received at 602552@bugs.debian.org (full text, mbox, reply):

From: Harald Dunkel <harri@afaics.de>

To: 602552@bugs.debian.org, Dmitry Smirnov <onlyjob@member.fsf.org>

Cc: Christoph Haas <haas@debian.org>

Subject: Re: Bug#602552 closed by Dmitry Smirnov <onlyjob@member.fsf.org> (Done: Listener failed with error: socket() for [[(null)]:10050])

Date: Sat, 18 Aug 2012 11:00:25 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There is no Zabbix version 1.8.4 in Squeeze or its updates,
nor is there a newer version on debian-backports, so why do
you close this bug report pointing to Fedora? Do you suggest
I should switch to another distro?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlAvWaQACgkQUTlbRTxpHjfUKQCfYIfz2Ll0BOQWM0qJfK8YmEfR
TVwAn3MXk5RBL2KIgvHBTDJ8RjyQiImd
=+I2z
-----END PGP SIGNATURE-----

Message #37 received at 602552@bugs.debian.org (full text, mbox, reply):

From: Dmitry Smirnov <onlyjob@member.fsf.org>

To: Harald Dunkel <harri@afaics.de>

Cc: 602552@bugs.debian.org, Christoph Haas <haas@debian.org>

Subject: Re: Bug#602552 (Done: Listener failed with error: socket() for [[(null)]:10050])

Date: Sat, 18 Aug 2012 20:01:53 +1000

Dear Harald,

Usually we don't close bugs by uploading to backports.
Instead it is normal practice to close the bug when the problem is addressed 
in later version which may not necessary available in the particular Debian 
release that you're using. 
Often it is only possible to close bug in newer software release which will 
never be available for stable Debian release. If we keep all such bugs opened 
many of them would never be closed.

There was nothing in my message that suggest you to switch distro. Frankly I 
would be very happy if you stay with us.

But what can I do if the evidence suggests that the problem is fixed in later 
zabbix version long time ago? Let me assure you it is not reproducible in 
later versions. Fedora specifically mention the very problem you experienced 
and suggest that is was already fixed.

I you want us to make newer zabbix release available from backports I'll take 
it as request but I can't make any promises.

Regards,
Dmitry.

On Sat, 18 Aug 2012 19:00:25 Harald Dunkel wrote:
> There is no Zabbix version 1.8.4 in Squeeze or its updates,
> nor is there a newer version on debian-backports, so why do
> you close this bug report pointing to Fedora? Do you suggest
> I should switch to another distro?

Message #42 received at 602552@bugs.debian.org (full text, mbox, reply):

From: Harald Dunkel <harri@afaics.de>

To: Dmitry Smirnov <onlyjob@member.fsf.org>

Cc: 602552@bugs.debian.org, Christoph Haas <haas@debian.org>

Subject: Re: Bug#602552 (Done: Listener failed with error: socket() for [[(null)]:10050])

Date: Sun, 19 Aug 2012 11:05:52 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Dmitry,

On 08/18/12 12:01, Dmitry Smirnov wrote:
> Often it is only possible to close bug in newer software release which will never be available for stable Debian release. If we keep all such bugs opened many of them would never be closed.
> 

The purpose of the bug tracker is to provide information about
known problems. If you close a bug report without fixing it,
just to get rid of it, then you just hide the problem. Bad idea,
IMHO.

> There was nothing in my message that suggest you to switch distro. Frankly I would be very happy if you stay with us.
> 

Don't worry, I am on Debian since Hamm, even though I was never
found worthy to become a DM.

> I you want us to make newer zabbix release available from backports I'll take it as request but I can't make any promises.
> 

I had backported sid's zabbix 1.8.9-1 to squeeze. Since then I am
upgrading these packages to new Zabbix versions when they come out
(1.18.x, of course). Its running in my setup watching >80 clients
(Linux, Windows, Solaris, UPS), some of them via a proxy. I can
push these packages to mentors, if you are interested?


Regards

Harri

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlAwrHAACgkQUTlbRTxpHjfZ+ACeOaRFa4nNOG8I46VMc21x+vUC
IdkAn0TvN2FV1BsxKu6BefmEWRLh9gl8
=OqMA
-----END PGP SIGNATURE-----

Message #47 received at 602552@bugs.debian.org (full text, mbox, reply):

From: Dmitry Smirnov <onlyjob@member.fsf.org>

To: Harald Dunkel <harri@afaics.de>

Cc: 602552@bugs.debian.org, Christoph Haas <haas@debian.org>

Subject: Re: Bug#602552 (Done: Listener failed with error: socket() for [[(null)]:10050])

Date: Mon, 20 Aug 2012 11:23:05 +1000

On Sun, 19 Aug 2012 19:05:52 Harald Dunkel wrote:
> The purpose of the bug tracker is to provide information about
> known problems. If you close a bug report without fixing it,
> just to get rid of it, then you just hide the problem. Bad idea,
> IMHO.

The information we put into this bug report will be available even after 
close. If you treat opened bug reports as entries in TODO list there will be 
clear that there is nothing to do regarding this issue apart from packaging 
new version which is already packaged and available from 'testing' and 
'unstable' where the problem is fixed. Therefore I believe I have legitimate 
reason to close this - there is nothing I can do about it anyway as long as I 
can't make new zabbix version available in squeeze.
Sorry If I gave you the wrong impression but this bug was investigated and its 
closure will help to focus on more important issues where there might be 
something for maintainer to do. I don't see how keeping this bug opened could 
help anything but if you insist we can reopen and leave it opened until 
Squeeze will become 'oldstable'.


> I had backported sid's zabbix 1.8.9-1 to squeeze. Since then I am
> upgrading these packages to new Zabbix versions when they come out
> (1.18.x, of course). Its running in my setup watching >80 clients
> (Linux, Windows, Solaris, UPS), some of them via a proxy.

I see. So you've already fixed the issue by backporting...
Sorry that I couldn't do it for you.


> I can push these packages to mentors, if you are interested?

Not quite, thank you. I put so much effort into packaging 2.0.x so I already 
upgraded my server, proxy and frontend. 

But of course you can upload for those who might follow your steps.

If time allows I'll try to make a version for backports but it will likely to 
be 2.0.x which we did with backports in mind: although I didn't try, it should 
build on squeeze without any modifications.

All the best,
Dmitry.

Send a report that this bug log contains spam.