Note ¯ 
If no action is recommended, do the following before you contact Lucent InterNetworking Systems Technical Support: Write down the error message exactly and record the output of radiusd -v and uname -a .
Note ¯
If no action is recommended, do the following before you contact Lucent InterNetworking Systems Technical Support: Write down the error message exactly and record the output of radiusd -v and uname -a .
RADIUS received an accounting packet with an invalid Request-Authenticator on port Portnumber from a RADIUS client at Ipaddress.
Check that the shared secret on the client and the server are exactly the same. Case is significant. If the secrets match, next check the version of ComOS on the client if it is a PortMaster. Lucent InterNetworking Systems recommends that you run ComOS 3.3.1 or later with RADIUS 2.1 accounting. If any of your PortMaster clients are running ComOS 3.3 or earlier, run radiusd with the -o option. If this message results from a client that is not a PortMaster, then the client is not compliant with RFC 2139.
RADIUS was not able to add additional information to the end of the accounting detail file, Filename.
Check permissions and ownership of the detail file and its directory. Verify that the hard disk has not run out of available storage space.
An accounting packet was received from a network access server (NAS) that is not identified in the clients file.
Add client to clients file if appropriate. Otherwise, apply a filter to prevent access requests from the NAS.
At startup, radiusd was unable to bind RADIUS accounting on UDP socket 1646 and returned an error message.
Verify that radiusd is not already running. Use netstat -a to determine whether UDP port 1646 is in use by some other process. Kill the process that bound the port and restart radiusd .
At startup, radiusd was unable to open RADIUS accounting UDP socket 1646 and returned an error message.
Verify that radiusd is not already running. Use netstat -a to determine whether UDP port 1646 is in use by some other process. Kill the process that bound the port and restart radiusd .
An operating system error prevented RADIUS from starting the accounting daemon from radiusd .
Consult your system administrator or the UNIX man pages.
RADIUS did not authenticate user Username attempting access from server NAS at IP address Ipaddress.
RADIUS received an access request with no username from server NAS. this message can result from a malformed authentication request or from the dial-up software.
RADIUS ignored an access-request by user Username from server NAS. Any request coming from a NAS not specifically configured in the clients file is ignored.
Add the NAS hostname or IP address to the clients file if appropriate. Otherwise, apply a filter to prevent access requests from the NAS.
At startup, radiusd was unable to bind RADIUS authentication on UDP socket 1645 and returned an error message.
Verify that radiusd is not already running. Use netstat -a to determine whether UDP port 1645 is in use by some other process. Kill the process that bound the port and restart radiusd .
At startup, radiusd was unable to open RADIUS authentication UDP socket 1645 and returned an error message.
Verify that radiusd is not already running. Use netstat -a to determine whether UDP port 1645 is in use by some other process. Kill the process that bound the port and restart radiusd .
RADIUS dropped packet Idnumber from server NAS. Each request contains an ID number. This message is generated if RADIUS receives a request with an ID to which it has already responded in the last five seconds.
RADIUS is dropping the request for ID Idnumber because the queue has grown too large. Number indicates the number of requests already in the queue.
RADIUS ran out of memory while receiving a packet and shut down.
RADIUS received a packet from client Client that was reported to be Number of bytes in length but was Number2 of bytes instead.
Check client; this message can result from a malformed or corrupted packet.
Child process ID Number was not found.
RADIUS dropped an authentication request with ID Number because it had responded to an earlier request with this ID within the last five seconds. A NAS sends duplicate requests if it does not receive a response within three seconds.
RADIUS received a request from Ipaddress2 in response to an access-challenge sent to Ipaddress, but the addresses do not match.
The msgget function for the authentication key with a hexadecimal value of Hexvalue for packet ID Number failed and returned error message Number.
The msgsend function for the authentication key with a hexadecimal value of Hexvalue for packet ID Number failed and returned error message Number.
RADIUS failed to get the group name Group from UNIX for user Username.
RADIUS failed to get the password name from UNIX for user Username.
During the authentication process, the msgctl function for message ID Number returned an error message.
During the authentication process, the msgget function for the authentication key with a hexadecimal value of Hexvalue for packet ID Number failed and returned an error message.
During the authentication process, the msgrcv function for message ID Number returned an error message.
The IP address Ipaddress for a client NAS was not found in the client cache that is generated from the clients file.
Verify that clients file contains this client's IP address.
A syntax error occurred in the clients file for the client Client.
RADIUS could not resolve Hostname found in the clients file into an IP address, or there are multiple entries in the clients file for the same client.
Remove duplicate hosts from the clients file.
RADIUS could not find the clients file Filename, which is read into memory and cached whenever it changes.
RADIUS could not create a temporary client cache file Filename.
Verify that radiusd has write permission to /etc/raddb (or the directory specified with the -d option) and that the hard disk has not run out of available storage space.
RADIUS cannot open the clients file Filename for reading.
Check the permissions on the clients file.
When parsing the dictionary file Filename, RADIUS found an attribute that did not have an associated number on line Number of the dictionary.
Correct the attribute in the dictionary.
When parsing the dictionary file Filename, RADIUS found an unrecognizable attribute line Number of the dictionary.
Correct the attribute in the dictionary.
When parsing the dictionary file Filename, RADIUS found an attribute name on line Number of the dictionary that was more that 31 characters long.
Correct the attribute name in the dictionary.
RADIUS could not open the dictionary file Filename for reading.
Check permissions for the dictionary file.
When parsing the dictionary file Filename, RADIUS found an invalid attribute on line Number of the dictionary.
Check for syntax errors in the dictionary file. Download the latest dictionary file from ftp://ftp.livingston.com/pub/le/radius/dictionary .
When parsing the dictionary file Filename, RADIUS found an invalid value for an attribute on line Number of the dictionary.
Check for syntax errors in the dictionary file. Download the latest dictionary file from ftp://ftp.livingston.com/pub/le/radius/dictionary .
RADIUS ran out of memory after reading line Number of the dictionary file Filename.
Either exit any non-RADIUS processes running on the RADIUS server or upgrade server memory.
When parsing the dictionary file Filename, RADIUS found a nonnumeric value on line Number of the dictionary.
When parsing the dictionary file Filename, RADIUS found a value that was more that 31 characters long on line Number of the dictionary.
RADIUS had trouble analyzing the data found in the menu file Filename.
RADIUS quit because a fatal error occurred on signal number Number.
RADIUS terminated the child process ID Number because the process had not exited.
Run radiusd -s to force RADIUS to run in single-process mode.
The operating system hosting the RADIUS server does not have enough memory for RADIUS to run.
Either exit any non-RADIUS processes running on the RADIUS server or upgrade server memory.
RADIUS is unable to fork a process during startup.
RADIUS ignored a request from server NAS because it could not identify the request type Number.
RADIUS could not connect to the SecurID server.
The SecurID configuration file could not be opened for reading
The SecurID server returned an unknown code Number for user Username.
Use the SecurID documentation to identify the unknown code.
The State attribute sent in the access-request does not match the one sent in the access-challenge. Most likely the client is doing something wrong.
RADIUS found a syntax error in the first line of the user profile in the users file for either user Username or the user who attempted access immediately before Username.
Do the following in the user profile for Username and the previous user:
RADIUS found a syntax error in the first line of the user profile for user Username in the DBM database generated from the users file.
RADIUS found a syntax error in the reply items of the user profile for user Username in the DBM database generated from the users file.
RADIUS found a syntax error in the reply items of the user profile in the users file for user Username.
Do the following in the reply items in the user profile for Username:
The user profile in the users file for user Username is Number characters in size and exceeds the maximum number of characters Max allowed for the profile.
RADIUS rejected a username with no characters.
RADIUS could not open the DBM users database Filename for reading.
RADIUS could not open the users file Filename for reading.
RADIUS ran out of memory while parsing the user profile.