On Thursday 11 October 2012, Daniel-Constantin Mierla wrote:
On 10/11/12 12:00 PM, Alex Hermann wrote:
On Thursday 11 October 2012, Daniel-Constantin Mierla wrote:
Do you get any other error/debug message before that can give an hint why is failing?
Unfortunately not.
Not even debug messages that could lead to failure point if running with debug=3?
Sorry, forgot about debug logs. Here they are:
DEBUG: <core> [dns_cache.c:567]: dns_hash_find([IPv6 Address](30), 1), h=707 DEBUG: <core> [resolve.c:727]: get_record: lookup([IPv6 Address], 1) failed DEBUG: <core> [dns_cache.c:895]: dns_cache_mk_bad_entry([IPv6 Address], 1, 60, 1) DEBUG: <core> [dns_cache.c:828]: dns_cache_add: adding [IPv6 Address](30) 1 (flags=1) at 707 ERROR: dispatcher [dispatch.c:325]: could not resolve [IPv6 Address] WARNING: <core> [mem/f_malloc.c:474]: WARNING:fm_free: free(0) called
Is dns_try_ipv6 parameter set to yes in configuration file?
I tried with and without it, same result.
Anyhow, the dns resolve is done for doing keepalives, if it is an ipv4 only, you will get some errors at runtime because there is no socket for ipv6. Perhaps the fix would require some coding in dispatcher module. An alternative is to use database views to make available only the groups you want in this ipv4 instance.
I'll see what i can do about it. Thanks