Hi, On Fri, 2009-07-31 at 09:50 -0300, Alexei Aliaev wrote:

Hi Balazs,

Thanks for fast reply :-)

I tried compiling and running syslog-ng from latest snapshot (which includes your commit). Looks like it starts now...

However, I noticed that it tries to establish connection to port 0 instead of specified port(514) and I get "Connection refused (111)" message.

From output: --- Syslog connection failed; fd='10', server='AF_INET6(fdab:228b:77af:6e7e:206:5bff:fef6:e2af:0)', error='Connection refused (111)', time_reopen='60' ----

Even though my destination is: tcp6("fdab:228b:77af:6e7e:206:5bff:fef6:e2af" port(514));

Is there something else wrong? Or am I just missing something?

Right, this was also wrong: commit d2158b87895fd7cc7a044af0bbad4df37db19015 Author: Balazs Scheidler <bazsi@balabit.hu> Date: Fri Jul 31 21:14:00 2009 +0200 don't reset the destination port number to 0 in ipv6 address resolution resolve_host() zeroes out the port number if an ipv6 address is resolved. I'll need to add the ipv6 specific cases to the functional test program. As it seems only very few people use syslog-ng in ipv6 environments, if any. I appreciate further testing in the area.

-- Alexey

-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Friday, July 31, 2009 7:46 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 destination host + port causes assertion failure in gsockaddr.h

Hi,

This is a regression, this patch fixes it for me.

commit 741dcea9e98fe4a7543f0ab705b3a52eab99332c Author: Balazs Scheidler <bazsi@balabit.hu> Date: Fri Jul 31 12:00:03 2009 +0200

fixed possible abort when using tcp6() destination

On Thu, 2009-07-30 at 11:06 -0300, Alexei Aliaev wrote:

...

Hi,

I am trying to solve an issue with syslog-ng 3.0.3 in IPv6 environment... I have a destination specified in my config file as such:

destination collector { tcp6("fdab:228b:77af:6e7e:206:5bff:fef6:e2af" port(514)); };

When I run syslog-ng, I get this:

file gsockaddr.h: line 86 (g_sockaddr_inet_get_sa): assertion failed: (g_sockaddr_inet_check(s)) Aborted

I tracked down that this is caused by the destination definition above.

The destination address is of the same box and port 514 is open and listening.

If I remove the port, everything seems to start-up fine but it tries to connect to the specified IP to port 0 and I keep getting connection refused messages.

Are there any known issues that could explain this?

-- Alexey

________________________________________________________________________ ______

...

Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html

-- Bazsi

Balazs, Is there any information on whether 3.0.4 syslog-ng OSE will be released (including those fixes)? and if so, when can it be expected? Thanks. -- Alexey -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu on behalf of Balazs Scheidler Sent: Fri 7/31/2009 4:15 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 destination host + port causes assertion failure in gsockaddr.h Hi, On Fri, 2009-07-31 at 09:50 -0300, Alexei Aliaev wrote:

Hi Balazs,

Thanks for fast reply :-)

I tried compiling and running syslog-ng from latest snapshot (which includes your commit). Looks like it starts now...

However, I noticed that it tries to establish connection to port 0 instead of specified port(514) and I get "Connection refused (111)" message.

From output: --- Syslog connection failed; fd='10', server='AF_INET6(fdab:228b:77af:6e7e:206:5bff:fef6:e2af:0)', error='Connection refused (111)', time_reopen='60' ----

Even though my destination is: tcp6("fdab:228b:77af:6e7e:206:5bff:fef6:e2af" port(514));

Is there something else wrong? Or am I just missing something?

Right, this was also wrong: commit d2158b87895fd7cc7a044af0bbad4df37db19015 Author: Balazs Scheidler <bazsi@balabit.hu> Date: Fri Jul 31 21:14:00 2009 +0200 don't reset the destination port number to 0 in ipv6 address resolution resolve_host() zeroes out the port number if an ipv6 address is resolved. I'll need to add the ipv6 specific cases to the functional test program. As it seems only very few people use syslog-ng in ipv6 environments, if any. I appreciate further testing in the area.

-- Alexey

-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Friday, July 31, 2009 7:46 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 destination host + port causes assertion failure in gsockaddr.h

Hi,

This is a regression, this patch fixes it for me.

commit 741dcea9e98fe4a7543f0ab705b3a52eab99332c Author: Balazs Scheidler <bazsi@balabit.hu> Date: Fri Jul 31 12:00:03 2009 +0200

fixed possible abort when using tcp6() destination

On Thu, 2009-07-30 at 11:06 -0300, Alexei Aliaev wrote:

...

Hi,

I am trying to solve an issue with syslog-ng 3.0.3 in IPv6 environment... I have a destination specified in my config file as such:

destination collector { tcp6("fdab:228b:77af:6e7e:206:5bff:fef6:e2af" port(514)); };

When I run syslog-ng, I get this:

file gsockaddr.h: line 86 (g_sockaddr_inet_get_sa): assertion failed: (g_sockaddr_inet_check(s)) Aborted

I tracked down that this is caused by the destination definition above.

The destination address is of the same box and port 514 is open and listening.

If I remove the port, everything seems to start-up fine but it tries to connect to the specified IP to port 0 and I keep getting connection refused messages.

Are there any known issues that could explain this?

-- Alexey

________________________________________________________________________ ______

...

Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html

-- Bazsi ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html

Perfect! Thanks Balazs. -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Wednesday, August 05, 2009 4:00 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 destination host + port causes assertion failure in gsockaddr.h On Tue, 2009-08-04 at 20:31 -0300, Alexei Aliaev wrote:

Balazs,

Is there any information on whether 3.0.4 syslog-ng OSE will be released (including those fixes)? and if so, when can it be expected?

I'm uploading a 3.0.4 release to our webserver right now. -- Bazsi ________________________________________________________________________ ______ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html