cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1574
Views
0
Helpful
2
Replies
Beginner

FM5.07 unable to bind Syslog port...

Dear All,

we have Fabric Manager 5.07 installed on Windows Server 2008. Everything is working fine without this little problem:

Every time I start FM I get this Error message:

FM standalone was unable to bind to Syslog port as It was already in use, this may mean another instance of the application is already running.

But there is no other instance running and since now I wasn't able to overcome this problem...

Does anybody have any Idea how to resolve this problem? Which ports to check or where can I configure which ports FM will use for syslog?

best regards

Werner

Everyone's tags (6)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

FM5.07 unable to bind Syslog port...

Hi Werner,

SYSLOG is UDP port 514.  Normally this means that some other program is running and using port 514.

Some of the TFTP servers are also SYSLOG servers and will "listen" on this port.

You can see if port 514 is listening with Fabric Manager not running.

To find out what is using port 514:

(a)     Open a command prompt window.  From Start / Run enter: cmd

(b)     From the command prompt enter: netstat -ano

(c)      Note the PID (process identifier) associated with the ports you are  concerned about.  (Also note the Local Address, Foreign Address,  Protocol and State.)

(d)     Then do ctrl-alt-del to bring up the Windows Task Manager.

(e)     In Windows Task Manager, select the Processes tab.

(f)      Look for the PID you noted when you did the netstat in step (c).  Look  to left to the image name and that tells you which process has that PID.

- If you dont see a PID column, click on View / Select Columns.  Make sure PID is selected.  Click OK.

- Make sure Show processes from all users is selected.

Now you can see what process is using port 514.  FM would be listed as javaw.exe ( java exec without a console window ).

Best regards,

Jim

View solution in original post

2 REPLIES 2
Highlighted
Cisco Employee

FM5.07 unable to bind Syslog port...

Hi Werner,

SYSLOG is UDP port 514.  Normally this means that some other program is running and using port 514.

Some of the TFTP servers are also SYSLOG servers and will "listen" on this port.

You can see if port 514 is listening with Fabric Manager not running.

To find out what is using port 514:

(a)     Open a command prompt window.  From Start / Run enter: cmd

(b)     From the command prompt enter: netstat -ano

(c)      Note the PID (process identifier) associated with the ports you are  concerned about.  (Also note the Local Address, Foreign Address,  Protocol and State.)

(d)     Then do ctrl-alt-del to bring up the Windows Task Manager.

(e)     In Windows Task Manager, select the Processes tab.

(f)      Look for the PID you noted when you did the netstat in step (c).  Look  to left to the image name and that tells you which process has that PID.

- If you dont see a PID column, click on View / Select Columns.  Make sure PID is selected.  Click OK.

- Make sure Show processes from all users is selected.

Now you can see what process is using port 514.  FM would be listed as javaw.exe ( java exec without a console window ).

Best regards,

Jim

View solution in original post

Highlighted
Beginner

FM5.07 unable to bind Syslog port...

Thanks to your very clear and perfekt troubleshooting lesson, Jim:-)

A tftp server which was also configured for syslog was causing the problem. After disableing this syslog-service FM starts without any problem. 

Thanks you very much!

Best regards

Werner

CreatePlease to create content
This widget could not be displayed.