Support Center

Troubleshooting Port Conflicts (Only one usage of each socket address is normally permitted)

Last Updated: Jun 13, 2019 08:24PM PDT
If you see the error "Only one usage of each socket address (protocol/network address/port) is normally permitted" in Settings | Sources, this indicates that you have a port conflict on the Fastvue machine for the port you are using to listen for syslog messages (most likely the default port 514).

To find out whether there is a port conflict on the Fastvue Reporter machine for port 514, open a command prompt and enter:
 
netstat -ano | find "514"

This will list all the processes on the machine using port 514 (it may also include other processes that have a substring of 514). You have a port conflict if there is more than one unique Process ID listed as using the port.

Note the Process ID(s), and then open Task Manager and go to the Services tab. You should be able to identify the other process by looking for the matching Process ID (PID).

Checking for Port Conflicts on the Fastvue Reporter server

Solution

The easiest solution is to change the syslog port being used on both your FortiGate and in your Fastvue Reporter source.

Changing the Syslog Port on your FortiGate needs to be done using the CLI. The following commands change the port to 50514:

 
config log syslogd setting
    set port 50514
    end
 

Once this has been changed, go to your Fastvue Reporter interface and go to Settings | Sources. Edit your FortiGate source, and change the Port to match your newly specified Syslog Port (50514 in the above example).

The 'Records Per Second' and 'Number of Records' values should soon start increasing. If not, repeat the steps above to ensure the new port is not conflicting, or see our checklist on troubleshooting other data import issues.

Contact Us

  • Post a Public Question
  • Email Us
  • Chat with us

    Call Us @ 888.885.6711
support@fastvue.co
http://assets0.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete