- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: coda port (381) is not LISTEN
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
Discussions
Discussions
Forums
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
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
тАО02-04-2008 01:47 PM
тАО02-04-2008 01:47 PM
coda port (381) is not LISTEN
i have a problem one of the linux node communicationg to my OVPM server.
2.4.9-e.57smp
Red Hat Linux Advanced Server release 2.1AS (Pensacola)
it is a vmware guest server
# ps -ef|grep -i vmware
root 379 1 0 2007 ? 00:25:15 /usr/sbin/vmware-guestd --backgr
Not sure how to this port open. While port 383 (llbserver) is LISTEN state
tcp 0 0 0.0.0.0:383 0.0.0.0:* LISTEN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2008 02:00 PM
тАО02-04-2008 02:00 PM
Re: coda port (381) is not LISTEN
#telnet adela133p 381
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
not sure if there a restriction going through 127.0.0.1?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2008 11:41 AM
тАО02-11-2008 11:41 AM
Re: coda port (381) is not LISTEN
ovconfchg -ns coda.comm -set SERVER_PORT 381
ovc -restart
netstat -an |grep 381/telnet to 381 will confirm.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-25-2008 10:24 AM
тАО02-25-2008 10:24 AM
Re: coda port (381) is not LISTEN
telnet adedd61p 381
Trying...
telnet: Unable to connect to remote host: Connection refused
adedd61p:root [/opt/OV/bin] telnet adedd61p 383
Trying...
Connected to adedd61p.ami.alcoa.com.
Escape character is '^]'.
telnet> close
Connection closed.
adedd61p:root [/opt/OV/bin] netstat -an|grep LISTEN|egrep -i "383|381"
tcp 0 0 *.383 *.* LISTEN
But how my other clients are not reporting any problem like this and showing LISTEN state for both for 381 and 383?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2008 01:36 AM
тАО02-26-2008 01:36 AM
Re: coda port (381) is not LISTEN
Compare the results in different nodes, and you can identify the process that should be using the port 381 but isn't.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-01-2008 10:44 PM
тАО03-01-2008 10:44 PM
Re: coda port (381) is not LISTEN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2008 06:45 PM
тАО03-05-2008 06:45 PM