> Errr... I thought that you know how to use the command...
> 'netstat -lpn --ip | grep 3050' will show you who listen the port.
>

sofia ~ # netstat -lpn --ip | grep 3050
tcp 0 0 0.0.0.0:3050 0.0.0.0:* LISTEN 6019/xinetd

>
> May be xinetd is listening indeed, but is unable to fork FB server
> process. In this case you must examine it's logs to find out the reason.
>
> SY, SD.
>

the output of /var/log/messages:
Jun 20 15:31:18 sofia xinetd[6019]: xinetd Version 2.3.14 started with libwrap loadavg options compiled in.
Jun 20 15:31:18 sofia xinetd[6019]: Started working: 1 available service
Jun 20 15:33:11 sofia xinetd[6019]: START: gds_db pid=6042 from=192.168.0.45
Jun 20 15:33:11 sofia xinetd[6042]: FAIL: gds_db address from=192.168.0.45
Jun 20 15:33:11 sofia xinetd[6019]: EXIT: gds_db status=0 pid=6042 duration=0(sec)
Jun 20 15:33:13 sofia xinetd[6019]: START: gds_db pid=6043 from=192.168.0.45
Jun 20 15:33:13 sofia xinetd[6043]: FAIL: gds_db address from=192.168.0.45
Jun 20 15:33:13 sofia xinetd[6019]: EXIT: gds_db status=0 pid=6043 duration=0(sec)

i can't understand from this log what happens. The FB Log is empty.