Resolved - FreeRadius 0.15.7 Issue
-
@jimp maybe want to rollback from FreeRadius 0.15.7 in the packages.
FreeRadius nolonger seems to start since the update to 0.15.7.
This is also after a fresh install and also removing and reinstalling FreeRadius.
[2.4.4-RELEASE][admin@pfsense]/var/log: clog radius.log
Segmentation fault (core dumped)
[2.4.4-RELEASE][admin@pfsense]/var/log:Anyone else have issues with FreeRadius?
Just going to install of a test pfSense VM.
-
[2.4.4-RELEASE][admin@test.localdomain]/var/log: clog radius.log
Segmentation fault (core dumped)
[2.4.4-RELEASE][admin@test.localdomain]/var/log: ls -alg radius.log
-rw------- 1 freeradius freeradius 0 Apr 9 12:25 radius.log
[2.4.4-RELEASE][admin@test.localdomain]/var/log: -
Must be local to you or your config. That version has been up since November and it's working fine.
That particular log file isn't a clog file, so I wouldn't expect clog to work on it.
-
I've had the same FreeRadius config for ages.
I was seeing a update to FreeRadius yesterday, very odd.
I guess its me trying to do a clog on the file causing the core dump not the contents of the file.
-
radiusd -X works fine.
-
Looks like it may be down to /tmp/radiusd_start.lock
-
@NogBadTheBad said in FreeRadius 0.15.7 Issue:
Looks like it may be down to /tmp/radiusd_start.lock
Strange.
No such file in my /tmp/ folder.
My 0.15.7 is running for months now.Btw : as said above : the radius.log file isn't a regular clog file. It's a "normal" log file.
Which also implies that it grows .... and grows .... think about purging it if [disk space could be an issue](link url).
I advise you to stop FreeRadius in the GUI.
Enter console mode, option 8.
Check if it's really dead :ps -ax | grep 'radius'This line should not be there any more :
61958 - Ss 0:00.15 /usr/local/sbin/radiusd(if so, kill them all)
Execute a
tail -f /var/log/radius.logNow start radius in the GU again and see what happens.
-
Thanks for that, I couldn't actually start FreeRadius and there were no processes running.
After removing /tmp/radiusd_start.lock I could start / stop FreeRadius from the GUI.
FreeRadius showed as having an update yesterday as it showed in yellow in the Package Manager, Jimp mentioned there hasn't been an update since November, does this not show an update since then:-
I'm not a GitHub expert BTW.
-
That was for 2.5.0 snapshots, not 2.4.4
-
Github commits don't automatically mean that an package update, for us as end-users - follows.
Btw : this was the commit : https://github.com/pfsense/FreeBSD-ports/commit/e61234a30c724016242124035c770baf2abc64a8#diff-7d997af96a3fdf1e7d5a64104639abe8
The version is still the same. I guess the coders are preparing the packages for 2.something called "2.5.0" ;) -
Thanks @Jimp
I'm not running 2.5.0, odd that I saw it.
-
Then that wasn't what you saw. Even that update for 2.5.0 was from March, and it would have been 0.15.7_1, not 0.15.7.
Before anything else, make sure you are on 2.4.4-p2, and that everything else is up-to-date.
-
Everything was up to date and all the patches, something hosed my config and I had to ask support for the latest non CE image.
Ticket #INC-25105
https://forum.netgate.com/topic/142381/solved-need-to-redownload-non-ce-image-for-sg-4860.
The issue occured after a fresh install and recovery from yesterdays backup.
-
@NogBadTheBad said in Resolved - FreeRadius 0.15.7 Issue:
https://forum.netgate.com/topic/142381/solved-need-to-redownload-non-ce-image-for-sg-4860.
I saw your question (see URL) - and I was bit surprised.
Netgate's devices needs "special" pfSense builds, not the "throw it on a 64-bits compatible Intel/AMD (clone)" and you'll be good. Devices like the 4860 are ARM processors, and need a special build - for the ARM.
These versions can be obtained using the support page, activated when you "register" your crevice.
From what I know, support from the Netgate's support page is ultra fast.PS : Very soon now I will own also a device from Netgate, so I speak "without have it done myself". Please correct me if I was wrong.
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
There was a report recently where FreeRADIUS would fail to start the first time after installing fresh, or something like that, but I don't see the thread or redmine issue now. It was some time ago.
Do you see any errors when you run:
$ /usr/local/etc/rc.d/radiusd.sh restartRemember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!
Need help fast? Netgate Global Support!
Do not Chat/PM for help!
-
@Gertjan said in Resolved - FreeRadius 0.15.7 Issue:
Devices like the 4860 are ARM processors, and need a special build - for the ARM.
4860 isn't ARM. The SG-1000, SG-1100, and SG-3100 are ARM. Most other devices can run CE or Factory, only other major exception is the 7100 since the switch code is only in factory.
-
Based on the output in that other thread, though, I'd say you were on 2.4.3 or earlier and not 2.4.4, and somehow managed to nudge that out-of-date box into downloading a newer package, which then blew things up. That wouldn't have any effect after the install, though.
It's also possible that the package was not reinstalled during the restore, and the 'update' on the screen was actually showing that it wasn't installed properly, and needed to be reinstalled (that would show red, update would be yellow)
-
@jimp said in Resolved - FreeRadius 0.15.7 Issue:
/usr/local/etc/rc.d/radiusd.sh restart
Wasn't sure exactly how it was started so I was doing it from the GUI.
-
@NogBadTheBad said in Resolved - FreeRadius 0.15.7 Issue:
@jimp said in Resolved - FreeRadius 0.15.7 Issue:
/usr/local/etc/rc.d/radiusd.sh restart
Wasn't sure exactly how it was started so I was doing it from the GUI.
That's essentially what the GUI does, but if you run it at the shell you might see an error that the GUI doesn't display
