Subject | Re: [firebird-support] Re: Firebird 2.5.4 - CentOS - mon$remote_address 0.0.0.0 |
---|---|
Author | Thomas Steinmaurer |
Post date | 2015-06-10T06:32:10Z |
> Hello ,Is this a real remote connection from a remote client or an attachment locally on the server?
>
> So Dmitry suggested it , we have disabled IPV6 on our server CentOS 7 (Firebird
> 2.5.4 Classic server (I forgot to mention it in my first mail)).
> By following the centos FAQ :
> http://wiki.centos.org/FAQ/CentOS7#head-8984faf811faccca74c7bcdd74de7467f2fcd8ee
> Rebooting the server.
> But even after this modification the mon$remote_address is still giving
> 0.0.0.0
>
> Any ideas are welcome.
--
With regards,
Thomas Steinmaurer
http://www.upscene.com
Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.
> Marianne
>
> De : firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
> Envoyé : lundi 8 juin 2015 12:47
> À : firebird-support@yahoogroups.com
> Objet : [firebird-support] Re: Firebird 2.5.4 - CentOS - mon$remote_address
> 0.0.0.0
>
>
>
> 08.06.2015 10:02, Marianne Castel wrote:
>>
>> We were working with Firebird 2.5.2 on Debian . At that time, in the
>> monitoring table MON$ATTACHEMENTS I could see the IP address of the
>> client connected to a database.
>>
>> Now our administrators have decided to work with CentOS and the last
>> available packages thus Firebird 2.5.4, and now in the databases on
>> that server in the table MON$ATTACHEMENTS table the field
>> mon$remote_address always contains : 0.0.0.0
>>
>> May be that the server is different too (network connection?) …
>>
>> Any idea why the IP address is no more reported ? How could we have the
>> IP address again in the monitoring table ?
>
> Interesting. One possible explanation can be found here:
>
> http://stackoverflow.com/questions/17220006/in-what-conditions-getpeername-returns-ipport-0-0-0-00
>
> Firebird 2.x does not support IPv6 and always listens on a AF_INET (i.e.
> v4) socket, but maybe it could be related somehow. Have you tried to
> disable IPv6 on the new server box?
>
> Dmitry
>
>