On Monday 20 July 2020 at 08:48:39, Alexander Malysh wrote:
> Hi,
>
> Kannel always take the first IP from DNS response. Therefore you have to
> make sure IPV4 address is the first address,
Er, you can't do that with DNS. Records are returned from the resolver in a
random order on each request, in a deliberate effort to spread out the load on
servers.
On Monday 20 July 2020 at 09:07:15, Alexander Malysh wrote:
> Hmm, looking into the code Kannel should connect just fine even DNS
> resolves to IPV4 and IPV6.
>
> Please check in your logs in debug mode for:
>
> Connecting to <%s>
>
> AND
>
> connect to <%s> failed
I see no "Connecting to" messages for the hostname in question.
I do see:
2020-07-20 09:18:19 [6053] [0] ERROR: MYSQL: Can't connect to MySQL server on
'server.example.com' (111 "Connection refused")
2020-07-20 09:18:19 [6053] [0] PANIC: SQLBOX: MySQL: database pool has no
connections!
2020-07-20 09:18:19 [6143] [0] ERROR: MYSQL: can not connect to database!
Now, the "connection refused" part puzzled me - it looked like kannel was
connecting to MySQL but MySQL was saying "go away", so I set up tshark to
capture packets to/from port 3306, and what I see is that an *IPv6* connection
*is being made* between the two servers, there's a login request, an 'OK'
response and then the connection gets closed.
I'm going to investigate this a bit more to see exactly what query and
response are being exchanged, once I can spend a bt of time with a broken
system again.
Thanks for the assistance,
Antony.
--
A few words to be cautious of between American and English:
- momentarily
- suspenders
- chips
- pants
- jelly
- pavement
- vest
- pint (and gallon)
- pissed
Please reply to the list;
please *don't* CC me.
