Red Hat Bugzilla – Bug 132085
Error While Starting Listener
Last modified: 2007-11-30 17:10:48 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040809 Description of problem: When I launch gnomemeeting, I get the following error message: Error while starting the listener. Version-Release number of selected component (if applicable): gnomemeeting-1.0.2-8 How reproducible: Always Steps to Reproduce: 1. Click on gnomemeeting Actual Results: The error message below is displayed. Error while starting the listener You will not be able to receive incoming calls. Please check that no other program is already running on the port used by Gnomemeeting. Expected Results: Gnomemeeting should launch without any errors Additional info: nmap -sT -O localhost returned the following information with or without gnomemeeting active. Starting nmap 3.55 ( http://www.insecure.org/nmap/ ) at 2004-09-08 14:05 EDT sendto in send_ip_raw: sendto(4, packet, 28, 0, 127.0.0.1, 16) => Operation not permitted Interesting ports on XXXXX.XXXXXXXX.XXX (127.0.0.1): (The 1651 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 53/tcp open domain 111/tcp open rpcbind 139/tcp open netbios-ssn 445/tcp open microsoft-ds 631/tcp open ipp 953/tcp open rndc 1720/tcp open H.323/Q.931
Open a terminal and examine the output of (run as root): netstat -l -v -p -n This should show which process is listening on port 1720 (which is what gnomemeeting wants). If it is another instance of gnomemeeting, see if you can find where it is and either use that instance or kill it. If it is something else, you may need to shut it down. If it is something else and you think gnomemeeting and the other process shouldn't conflict with each other, feel free to reopen this and include the output of the netstat command (above). Thanks.
The output from the command showed that port 1720 was not used by anything. I'm not sure what caused this, but I rebooted the box and it cleared the port. Was it a bug??? If it was, it would probably be hard to track down the root cause. tcp 0 0 :::1720 :::* LISTEN -