Hello,
I guess this is not a common problem, but I believe I was able to resolve this issue. I am posting my resolution incase others are encountering the same problem. CentOS 7 now uses systemd instead of init, I had to look at the corresponding configuration files for firebird. The systemd configuration files for firebird, [email protected] & firebird-classic.socket are located in /usr/lib/systemd/system. #cat firebird-classic.socket [Unit] Description=Firebird Classic Activation Socket [Socket] ListenStream=3050 I changed the ListenStream to ListenStream=0.0.0.0:3050 and restarted the service and now firebird is listening on 0.0.0.0:3050 and not :::3050, which means it is listening on IPV4 protocol. I was able to verify that the REMOTE IP ADDRESS is returning correctly on the MON$ATTACHMENTS table. Thank you, Ed Mendez From: [email protected] [mailto:[email protected]] Sent: Monday, November 2, 2015 10:11 AM To: [email protected] Subject: RE: [firebird-support] MON$ATTACHMENTS.MON$REMOTE_ADDRESS showing as 0.0.0.0 in FIREBIRD 2.5.4 on CENTOS 7 Hello, I have an issue with the MON$REMOTE_ADDRESS column in the MON$ATTACHMENTS table. The IP Address is coming back as 0.0.0.0. The server is running LI-V6.3.4.26856 Firebird 2.5.4 And it is running 64 bit CENTOS 7 all patched up. I have disabled IPV6 and rebooted and the problem still persists. I also want to mention that we have FIREBIRD 2.5.4 running on a CENTOS 6.7 and that is working correctly. So the issue seems something with CENTOS 7. I came across the following thread that details this issue, but it doesn’t seem to have a resolution. <https://www.mail-archive.com/[email protected]/msg12297.html> https://www.mail-archive.com/[email protected]/msg12297.html Any feedback would be greatly appreciated. Thank you, Ed Mendez
