New 2.0.8 abort with use_dns(persist_only);
I had been running 2.0.7 fine. When I install and start the new 2.0.8 version I get the following error and fails to actually start if I use the the options use_dns(persist_only); and dns_cache_hosts(/etc/hosts); Syslog connection established; from='AF_INET(0.0.0.0:0)', to='AF_INET(192.168.176.3:514)' syslog-ng starting up; version='2.0.8' Incoming log entry; line='<134>id=firewall sn=00XXXXXXXX time="2008-02-05 08:34:52" fw=1.1.1.1 pri=6 c=1024 m=98 n=133049021 src=192.168.184.83:25753:HomePort proto=icmp/8 rcvd=52 \x0d\x0a' file dnscache.c: line 100 (dns_cache_key_hash): should not be reached Abort With the use_dns(no); option it runs fine. bug? thanks, marc
On Wed, 2008-02-06 at 12:38 -0500, Marc Wiatrowski wrote:
I had been running 2.0.7 fine. When I install and start the new 2.0.8 version I get the following error and fails to actually start if I use the the options use_dns(persist_only); and dns_cache_hosts(/etc/hosts);
Syslog connection established; from='AF_INET(0.0.0.0:0)', to='AF_INET(192.168.176.3:514)' syslog-ng starting up; version='2.0.8' Incoming log entry; line='<134>id=firewall sn=00XXXXXXXX time="2008-02-05 08:34:52" fw=1.1.1.1 pri=6 c=1024 m=98 n=133049021 src=192.168.184.83:25753:HomePort proto=icmp/8 rcvd=52 \x0d\x0a' file dnscache.c: line 100 (dns_cache_key_hash): should not be reached Abort
With the use_dns(no); option it runs fine.
Hmm... it does not abort for me, so there must be something else in your environment that causes the abort. The abort itself says that the DNS cache encountered an address family that is not know to it (not AF_INET and neither AF_INET6). The from address is somewhat funny too: 0.0.0.0:0 -- Bazsi
On Wed, 2008-02-06 at 21:25 +0100, Balazs Scheidler wrote:
On Wed, 2008-02-06 at 12:38 -0500, Marc Wiatrowski wrote:
I had been running 2.0.7 fine. When I install and start the new 2.0.8 version I get the following error and fails to actually start if I use the the options use_dns(persist_only); and dns_cache_hosts(/etc/hosts);
Syslog connection established; from='AF_INET(0.0.0.0:0)', to='AF_INET(192.168.176.3:514)' syslog-ng starting up; version='2.0.8' Incoming log entry; line='<134>id=firewall sn=00XXXXXXXX time="2008-02-05 08:34:52" fw=1.1.1.1 pri=6 c=1024 m=98 n=133049021 src=192.168.184.83:25753:HomePort proto=icmp/8 rcvd=52 \x0d\x0a' file dnscache.c: line 100 (dns_cache_key_hash): should not be reached Abort
With the use_dns(no); option it runs fine.
Hmm... it does not abort for me, so there must be something else in your environment that causes the abort.
The abort itself says that the DNS cache encountered an address family that is not know to it (not AF_INET and neither AF_INET6).
The from address is somewhat funny too: 0.0.0.0:0
To diagnose the problem further I'd need a core file and a binary, possibly with debug symbols. -- Bazsi
On Wed, 2008-02-06 at 21:29 +0100, Balazs Scheidler wrote:
On Wed, 2008-02-06 at 21:25 +0100, Balazs Scheidler wrote:
On Wed, 2008-02-06 at 12:38 -0500, Marc Wiatrowski wrote:
I had been running 2.0.7 fine. When I install and start the new 2.0.8 version I get the following error and fails to actually start if I use the the options use_dns(persist_only); and dns_cache_hosts(/etc/hosts);
Syslog connection established; from='AF_INET(0.0.0.0:0)', to='AF_INET(192.168.176.3:514)' syslog-ng starting up; version='2.0.8' Incoming log entry; line='<134>id=firewall sn=00XXXXXXXX time="2008-02-05 08:34:52" fw=1.1.1.1 pri=6 c=1024 m=98 n=133049021 src=192.168.184.83:25753:HomePort proto=icmp/8 rcvd=52 \x0d\x0a' file dnscache.c: line 100 (dns_cache_key_hash): should not be reached Abort
With the use_dns(no); option it runs fine.
Hmm... it does not abort for me, so there must be something else in your environment that causes the abort.
The abort itself says that the DNS cache encountered an address family that is not know to it (not AF_INET and neither AF_INET6).
The from address is somewhat funny too: 0.0.0.0:0
To diagnose the problem further I'd need a core file and a binary, possibly with debug symbols.
This fix resolves this issue for me: http://git.balabit.hu/?p=bazsi/syslog-ng-2.0.git;a=commit;h=e49b43b6ab8ca8cd... The problem is triggered if you have multiple entries with the same IP address in your /etc/hosts file (not on the same line, in separate lines). Tomorrow's snapshot is going to have the fix. -- Bazsi
participants (2)
-
Balazs Scheidler
-
Marc Wiatrowski