Difference between revisions of "RADIUS server failed to start"
m (1 revision imported) |
|
(No difference)
|
Latest revision as of 12:52, 11 May 2017
Contents
Overview
RADIUS server failed to start, error: message is seen in the PINsafe logs. For further information see the RADIUS How To Guide
Prerequisites
PINsafe 3.x
Symptoms
RADIUS server failed to start, error: com.theorem.radserver3.RADIUSServerException: RADIUS authentication server receiver thread failed to start: Failed to create RADIUS server socket on port 1812: java.net.BindException: Cannot assign requested address.
RADIUS server failed to start, error: com.theorem.radserver3.RADIUSServerException: RADIUS authentication server receiver thread failed to start: Failed to create RADIUS server socket on port 1812: java.net.BindException: Address already in use.
RADIUS: Failed to create RADIUS server socket on port 1812: java.net.BindException: Address already in use
Solution
If seen after an upgrade restart Tomcat.
The RADIUS server has failed to start up. Ensure that the PINsafe server IP address matches the RADIUS server IP address, or is blank (blank will accept any request to the PINsafe servers IP addresses and is useful where multiple interfaces are present on the PINsafe server).
Do not use the VIP address as the RADIUS server address, see VIP on PINsafe Appliances.
Ensure that the RADIUS ports are not already being used by another RADIUS server. The following command allows to see which process is using the port. Typically this is seen on Windows Test servers with other applications such as IAS server.
netstat -abn
Check to ensure that there is not another instance of PINsafe running in the webapps folder. If a pinsafe backup or copy exists in the PINsafe folder this may also be running RADIUS. See Copies of PINsafe in Webapps folder