| To: | Jie Xu <jxu004@xxxxxxxxxx> |
|---|---|
| Subject: | Re: connection refused to a remote PMCD |
| From: | Kevin Wang <kjw@xxxxxxxxxxxxx> |
| Date: | Tue, 10 Feb 2004 23:23:45 -0800 |
| Cc: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1076483051.4029d3ebd042b@webmail.LaTech.edu> |
| References: | <ED373A183611D311A6220060943F134C08784D7B@eag-eaga002e--n.americas.sgi.com> <1076483051.4029d3ebd042b@webmail.LaTech.edu> |
| Sender: | pcp-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
From Jie Xu > The log says no route to the host, connection refused. > eg. From host haoscar, type following command: > #pminfo -h oscarnode1 kernel If you're getting a 'no route to host' error, that typically means you can't ping the host either. connection refused typically means that the pmcd isn't listening on the network. You can verify that it is listening on the network (on the server half) with "netstat -na | grep LISTEN | grep :4321 " where port 4321 is the default pmcd port number. - Kevin |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | connection refused to a remote PMCD, Jie Xu |
|---|---|
| Next by Date: | Re: connection refused to a remote PMCD, Max Matveev |
| Previous by Thread: | connection refused to a remote PMCD, Jie Xu |
| Next by Thread: | Re: connection refused to a remote PMCD, Jie Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |