Operating System - HP-UX
1834608 Members
3081 Online
110069 Solutions
New Discussion

Re: unable to get me_dserv listen on port 9898

 
Robert Pieters
Occasional Advisor

unable to get me_dserv listen on port 9898

On a HP-UX D380 we installed allbase and HP-DMS. In order to get the me_dserv working we had to add the following lines in /etc/services:
"me_dserv 9898/tcp # HP-DMS"
and in /etc/inetd.conf:
"me_dserv stream tcp nowait medmgr /opt/dbms_server/me_dserv me_dserv -e LANG=C"

Afterwards we stopped and started inetd and did a netstat -a|grep me. The me_dserv is not in the LISTEN-state.

What's wrong ???

6 REPLIES 6
harry d brown jr
Honored Contributor

Re: unable to get me_dserv listen on port 9898

INETD is the listener, NOT me_dserv.

get lsof and quit using netstat -a

http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.64/

live free or die
harry

Live Free or Die
Robert Pieters
Occasional Advisor

Re: unable to get me_dserv listen on port 9898

Maybe I descriped the "LISTEN" part wrong but
we are working with HP-UX 10.20, so we cannot use LSOF.

Any other solutions ??
harry d brown jr
Honored Contributor

Re: unable to get me_dserv listen on port 9898


Well you have about 8 months left for 10.20.

of course the answer is still the same. Inetd is the listener.

live free or die
harry
Live Free or Die
Robert Pieters
Occasional Advisor

Re: unable to get me_dserv listen on port 9898

Harry,

This is still no answer for us !!!

Did we do anything wrong in the files descriped above ??
harry d brown jr
Honored Contributor

Re: unable to get me_dserv listen on port 9898

Robert,

The service isn't going to be started until you have someone hit pot 9898 or until you manually start the application.

live free or die
harry
Live Free or Die
U.SivaKumar_2
Honored Contributor

Re: unable to get me_dserv listen on port 9898

Hi,
Does user medmgr exists ?. Does me_dserv have
proper execute permissions for user medmgr to
execute it. After restarting inetd have you
gone through /var/adm/syslog/syslog.log file
for any errors ?
Open two terminal windows in that server.
Give this command in one window.
#telnet 127.0.0.1 9898
Does it say any error ?. Or the telnet just connects with no messages ?
In another window.
#netstat -a | grep me
Does it show anything ?

Harry , IMHO , the author is right about the
LISTEN state . Inetd listens on open ports with port name defined in /etc/services and
/etc/inetd.conf . For example , telnet .

/etc/inetd.conf
telnet stream tcp nowait
root /usr/sbin/telnetd

/etc/services
telnet 23/tcp

Now if you give
#netstat -a | grep telnet

You can see telnet (But actually inetd) entry in LISTEN state.

regards,
U.SivaKumar








Innovations are made when conventions are broken