- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: unable to get me_dserv listen on port 9898
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2002 03:39 AM
10-02-2002 03:39 AM
unable to get me_dserv listen on port 9898
"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 ???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2002 03:44 AM
10-02-2002 03:44 AM
Re: unable to get me_dserv listen on port 9898
get lsof and quit using netstat -a
http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.64/
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2002 03:56 AM
10-02-2002 03:56 AM
Re: unable to get me_dserv listen on port 9898
we are working with HP-UX 10.20, so we cannot use LSOF.
Any other solutions ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2002 04:32 AM
10-02-2002 04:32 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2002 05:00 AM
10-02-2002 05:00 AM
Re: unable to get me_dserv listen on port 9898
This is still no answer for us !!!
Did we do anything wrong in the files descriped above ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2002 03:11 PM
10-02-2002 03:11 PM
Re: unable to get me_dserv listen on port 9898
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2002 10:17 PM
10-03-2002 10:17 PM
Re: unable to get me_dserv listen on port 9898
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