Better information on what is using a port comes from lsof.
- rick warner
On Thu, 12 Oct 2000, Warren Melnick wrote:
> Try doing a netstat and seeing what process is attaching to this port.
>
> Warren
> -----Original Message-----
> From: Kevin Tyle [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 12, 2000 3:38 PM
> To: [EMAIL PROTECTED]
> Subject: bind:address already in use (WAS: Multicast Question)
>
> OK, I understand what you're saying about Multicast, thanks.
>
> Then, let me turn to the 2nd paragraph. Perhaps coincidentally,
> around the time I began ingesting said data on Multicast, I began
> noticing "bind:address already in use" errors when restarting services
> that bind to particular TCP ports--such as 4559 (hylafax). The only
> way I've found thus far to restart the services without the
> bind error is to reboot.
>
> What can I try to fix this?
>
> Could it somehow be due to the Multicast feed? I don't see how,
> but the coincidence is very hard to ignore.
>
> Thanks,
>
> Kevin
>
> ---------------------------------------------------------------
>
> Kevin Tyle <[EMAIL PROTECTED]>
> MESO, Inc.
> Troy, NY
>
> ---------------------------------------------------------------
>
> Warren Melnick writes:
>
> >In a word: No. The whole idea of multicast is to have every packet hit
> >every machine so that a single stream of data can be received
> >(watched/listened to) by everyone.
> >
> >
> >Warren
>
> >>Hi,
> >>
> >>We recently installed a satellite data receiver which transmits
> >>data over a Multicast address (224.10.10.10). I have assigned
> >>the receiver an IP address on our Class C address, and it is
> >>attached to our network switch.
> >>
> >>While this configuration allows any of our Linux machines to
> >>receive and process the data, I have found that the receiver's
> >>packets are being received by all of our systems on the network,
> >>according to tcpdump. This may also be responsible to some strange
> >>instances of "bind:address already in use" when I attempt to restart
> >>some network services, such as HylaFAX.
> >>
> >>Can anyone give me advice as to how to restrict the Multicast packets
> >>being sent on 224.10.10.10 so that they don't hit all the machines--only
> >>the two or so that I want? I don't really understand much about
> >>Multicast so I'd welcome any assistance.
> >>
> >>The receiver is preconfigured by the vendor to use Multicast so
> >>reconfiguring it locally is not an option.
> >>
> >>Thanks!
> >>
> >>--Kevin
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
