tcp_mgr

Mogamat — Fri, 24 Feb 2006 05:01:44 GMT

Hi There,

ftp was on port 21 and 20.

Moved to port 10121 and 10120 by changing in /etc/services and stopping and restarting inetd.

ftp-data 10120/tcp # File Transfer Protocol (Data)

ftp 10121/tcp # File Transfer Protocol (Control)

Application configured to run as follows:

Application services file:

FTPdata,S,gwsae02,dataftp,

FTPctrl,S,gwsae02,ctrlftp,

Resolves to the below in /etc/services:

ctrlftp 21/tcp # new ftp facility - open with port no.

dataftp 20/tcp # new ftp facility

start application:

entftps -c FTPctrl -e stnetr -s Parser -p FTPdata -d 10 -g m -by > logfiles/logftp 2>&1

APP DEBUG OUTPUT

Feb 24 09:52:17 [015950]: entftps: Command line interpreted as:

Extended logging level: 10.

E/S entserver Service ID: 'stnetr'.

E/S entparser Service ID: 'Parser'.

FTP Control Service ID: 'FTPctrl'.

FTP Data Service ID: 'FTPdata'.

Log filename: '/users2/editest/logfiles/entftps.log'.

Daemon path: '.'

Delay time in second(s) upon failed logon: 1.

Get option: multiple.

Feb 24 09:52:17 [015952]: ftps_driver: TMPDIR_: /users2/editest

Feb 24 09:52:17 [015952]: tcp_mgr: Cannot bind to socket. Permission denied.

Feb 24 09:52:17 [015952]: tcp_mgr: Couldn't close fd 3: Bad file number.

Check socket:

gwsae02:editest:/users2/editest $ netstat -anf inet | grep 21

tcp 0 0 196.38.104.55.80 196.38.104.211.1233 FIN_WAIT_2

tcp 0 0 196.38.104.55.1414 10.34.49.77.3217 ESTABLISHED

tcp 0 52 196.38.104.55.22 10.34.49.82.1211 ESTABLISHED

tcp 0 0 196.38.104.55.1416 195.75.132.14.2140 ESTABLISHED

tcp 0 0 196.38.104.55.1414 195.75.132.15.2175 ESTABLISHED

tcp 0 0 196.38.104.55.1414 195.75.132.15.2158 ESTABLISHED

tcp 0 0 *.10121 *.* LISTEN

tcp 0 0 *.2148 *.* LISTEN

tcp 0 0 *.2121 *.* LISTEN

udp 0 0 *.49212 *.*

udp 0 0 *.2121 *.*

udp 0 0 *.49214 *.*

udp 0 0 *.49211 *.*

udp 0 0 *.49215 *.*

udp 0 0 *.49210 *.*

udp 0 0 *.2148 *.*

and

gwsae02:editest:/users2/editest $ lsof -i tcp:21

gwsae02:editest:/users2/editest $

This is a vary tricky system to reboot, so if there is any way of identify and releasing the lock on the socket, the would be great.

Re: tcp_mgr

Hemmetter — Fri, 24 Feb 2006 05:19:19 GMT

Hi Mogamat,

Is your tcp_mgr running as "root"? Port numbers lower than 1024 are privileged ports. These ports can only opend by root-processes.

mfg
HGH

topic tcp_mgr in Operating System - HP-UX

tcp_mgr

Re: tcp_mgr