Error logs

Known bugs reported by PacsOne users
Post Reply
midician
Posts:27
Joined:Wed Jun 07, 2006 12:44 pm
Error logs

Post by midician » Tue Jan 29, 2008 5:24 am

Hi All,

I get this error periodically:

ERROR - Cannot bind() socket to port: 104, Error: 98

What does this mean?


M

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Tue Jan 29, 2008 4:38 pm

The error usually means the port was busy (already in-use by another application), the error code 98 is the errno if you are running Linux/MacOS, or the last error number if you are running Windows.

midician
Posts:27
Joined:Wed Jun 07, 2006 12:44 pm

Port

Post by midician » Tue Jan 29, 2008 10:19 pm

I have all modalities running on port 104- would it be better to change some to a different port?

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Wed Jan 30, 2008 12:04 am

To check if port 104 is available on the server where PacsOne is installed, you can use the netstat command before PacsOne is installed (or when it's stopped):

Code: Select all

C:\>netstat -aon -p tcp
If you see 0.0.0.0:104 shows up at the 2nd column in the output of the above command, then port 104 is being used by another program on the same server. If this is the case, you should configure PacsOne to listen to a different port to avoid such conflicts.

Post Reply