Subject | Re: Can't connect to CentOS 7 service port 3050 from network |
---|---|
Author | Philippe Makowski |
Post date | 2014-09-17T11:40:59Z |
Le 16/09/14 18:21, duque.hernando@... [firebird-support] a écrit :
if you got Firebird from EPEL repositories, there is a README file that
explain that (/usr/share/doc/firebird-2.5.3.26778.0/README.Fedora) :
* According to Fedora packaging rules, firebird service is not started
automatically. You need to start it, as root :
for SuperServer :
systemctl start firebird-superserver.service
for SuperClassic :
systemctl start firebird-superclassic.service
for Classic :
systemctl start firebird-classic.socket
If you want to have firebird started at each boot, as root :
for SuperServer :
systemctl enable firebird-superserver.service
for SuperClassic :
systemctl enable firebird-superclassic.service
for Classic :
systemctl enable firebird-classic.socket
> Hi to alldid you started the service ?
>
>
> I've just installed Firebird 2.5 SuperClassic on a new Linux CentOS 7
> box. I tested local connections and are working fine. SELinux is
> disabled and firewall service is down.
>
>
> But when I try to connect from a workstation using "telnet my-server
> 3050", is not responding. Neither I can see the 3050 port if I do
> "lsof | grep 3050" on the host.
>
>
> Is there I've missed?
>
if you got Firebird from EPEL repositories, there is a README file that
explain that (/usr/share/doc/firebird-2.5.3.26778.0/README.Fedora) :
* According to Fedora packaging rules, firebird service is not started
automatically. You need to start it, as root :
for SuperServer :
systemctl start firebird-superserver.service
for SuperClassic :
systemctl start firebird-superclassic.service
for Classic :
systemctl start firebird-classic.socket
If you want to have firebird started at each boot, as root :
for SuperServer :
systemctl enable firebird-superserver.service
for SuperClassic :
systemctl enable firebird-superclassic.service
for Classic :
systemctl enable firebird-classic.socket