cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to start SBR on Linux server.

SOLVED
Highlighted
Contributor

Re: Unable to start SBR on Linux server.

Do you have the startup log?  (20130226.log)

 

That'll give you an idea as to what's failing to load and what needs to be fixed in order to get radius to start.

 

Highlighted
Occasional Contributor

Re: Unable to start SBR on Linux server.

Here is the log of when I tried to start.

 

02/27/2013 10:45:04: Licenses enable this server to:
02/27/2013 10:45:04: Run
02/27/2013 10:45:04: Licensed for Steel-Belted Radius Carrier
02/27/2013 10:45:04: Not licensed for Concurrency
02/27/2013 10:45:04: No IP address configured
02/27/2013 10:45:04: Initialized dbclusterlocal referenced in dbclusterlocal.gen
02/27/2013 10:45:04: dbclusterlocal: INITIALIZE SUCCESS
02/27/2013 10:45:04: Initialized Persistence plug-in "LOCAL"
02/27/2013 10:45:04: Attribute Editing enabled
02/27/2013 10:45:04: 3gpp2: Unable to determine local IP address
02/27/2013 10:45:04: 3gpp2: Initialization failed.
02/27/2013 10:45:04: Unable to initialize 3GPP2 Mobile IP
02/27/2013 10:45:07: Failed to initialize Radius administration infrastructure

Highlighted
Contributor

Re: Unable to start SBR on Linux server.

Make sure the hostname can resolve to the interface addresses.  I've seen something similar before where the hostname resolution fails and adding an entry in /etc/hosts allow's SBR to start.

 

 

Highlighted
Occasional Contributor

Re: Unable to start SBR on Linux server.

I have already done that and the hostname is resolvable. 

Contributor

Re: Unable to start SBR on Linux server.

Does it resolve localhost and the configured IP?

Highlighted
Occasional Contributor

Re: Unable to start SBR on Linux server.

There was a typo on the hosts file, had the hostname wrong, fixed it and the service started Smiley Very Happy 

 

Thanks! 

Highlighted
Occasional Contributor

Re: Unable to start SBR on Linux server.

02/27/2013 06:10:33: DCF system started
02/27/2013 06:10:33: Initialized Radius socket address 172.16.0.98 port 1646 (receive buffer size 229376 bytes)
02/27/2013 06:10:33: Initialized Radius socket address 172.16.0.98 port 1813 (receive buffer size 229376 bytes)
02/27/2013 06:10:33: Initialized Radius socket address 172.16.0.99 port 1646 (receive buffer size 229376 bytes)
02/27/2013 06:10:33: Initialized Radius socket address 172.16.0.99 port 1813 (receive buffer size 229376 bytes)
02/27/2013 06:10:33: Initialized Radius socket address 172.16.0.98 port 1645 (receive buffer size 229376 bytes)
02/27/2013 06:10:33: Initialized Radius socket address 172.16.0.98 port 1812 (receive buffer size 229376 bytes)
02/27/2013 06:10:33: Initialized Radius socket address 172.16.0.99 port 1645 (receive buffer size 229376 bytes)
02/27/2013 06:10:33: Initialized Radius socket address 172.16.0.99 port 1812 (receive buffer size 229376 bytes)
02/27/2013 06:10:33: LatencyLogger is Disabled
02/27/2013 06:10:33: Radius Authentication Server started ...
02/27/2013 06:10:33: Radius Accounting Server started ...
02/27/2013 06:10:33: Extended Proxy: No [Processing] section in /opt/JNPRsbr/radius/proxy.ini
02/27/2013 06:10:33: Extended Proxy: Default proxy identification processing enabled
02/27/2013 06:10:33: Number of Authentication Plugin : 0, Number of Accounting Plugin : 0
02/27/2013 06:10:33: Steel-Belted Radius is operational.