Freeradus service goes down
Dear, I have a Freeradius server running OK, authenticating against an AD. The Debian package is 2.1.12+dfsg-1.2 version. The problem is that the service goes down 2 o 3 times a week, and I can't know tha cause. I see the /var/log/freeradius/radisu.log but there is nothing important I think. When I start the service in this way "service freeradius start", today the service didn't start, and I have started it with "freeradius -X" and it runs OK now. How can I find the origin of the problem the service goes up frequently??? Do you recommend to me start the service with "service freeradius start" or "freeradius -X"??? Thanks in advance. Roberto
Roberto Carna wrote:
Dear, I have a Freeradius server running OK, authenticating against an AD. The Debian package is 2.1.12+dfsg-1.2 version.
The problem is that the service goes down 2 o 3 times a week, and I can't know tha cause. I see the /var/log/freeradius/radisu.log but there is nothing important I think.
Upgrade. We'll be releasing version 2.2.2 tomorrow. Alan DeKok.
On 10/28/2013 04:14 PM, Alan DeKok wrote:
Roberto Carna wrote:
Dear, I have a Freeradius server running OK, authenticating against an AD. The Debian package is 2.1.12+dfsg-1.2 version.
The problem is that the service goes down 2 o 3 times a week, and I can't know tha cause. I see the /var/log/freeradius/radisu.log but there is nothing important I think. Upgrade. We'll be releasing version 2.2.2 tomorrow.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html One thing I will be testing tomorrow is a more recent version of Samba 3.x. There are a number of bugs relating to winbind that might be causing some of these (if you are using RHEL in some form, the versions are always slow to move).
Some of the bugs that I reviewed in the changelogs are: Given that RHEL is always way behind on versioning, I took a minute to glance at the changelogs for more recent versions of Samba then available via RHN. The current version of RHN is topped at 3.6.9 I have found repositories that will allow us to upgrade (fairly easily since I did it on devel in 5 minutes) to 3.6.19 Here are a few bugs that might have some bearing in our environment * 3.6.19 - BUG 9994: s3-winbind: Do not delete an existing valid credential cache. * 3.6.15 - BUG 9854: Fix crash bug in Winbindd (considered a major enhancement) * 3.6.14 - BUG 9735: Fix Winbind separator in upn to username conversion. * 3.6.13 - BUG 9684: Fix two resource leaks in winbindd. (considered a major enhancement) * 3.6.10 - BUG 9367: Use work around for 'winbind use default domain' only if it is set. (unsure) * 3.6.10 - BUG 9386: Winbind: Failover if netlogon pipe is not available. (unsure) The problems we are seeing only occur under load. I am hopefully that 2.2.2 will help mitigate some of these, but just sharing what I found. I will know more in a week of this helps our situation. We will definitely be upgrading to 2.2.2 but the samba upgrades will be done first just to rule out any of the above bugs. http://www.mavinerc.com/home/2012/04/30/howto-update-samba-to-the-latest-bui... - John Douglass
On 28/10/2013 20:38, John Douglass wrote:
* 3.6.10 - BUG 9367: Use work around for 'winbind use default domain' only if it is set. (unsure) * 3.6.10 - BUG 9386: Winbind: Failover if netlogon pipe is not available. (unsure)
FWIW at least one of these - samba #9386, above - is backported to the RHEL6 RPM, and I think #9367 too. This is not to say I'm happy with the laggy samba package on RHEL6, but worth noting. Of course, it's very difficult to follow the RHEL "samba" RPM changelog, as the bugs are all private, undoubtedly for the usual nonsense reason of "might possibly contain 3 bytes of customer info". Sigh.
Ok, I've try to upgrade today but there is nothing to do at the momento, no new packages. But in order to know the procedure, how can I do to monitor/analyze the cause that Freeradius service goes down ??? Some file to inspect inside /var/log or what ??? Thanks a lot. Roberto 2013/10/28 Phil Mayers <p.mayers@imperial.ac.uk>:
On 28/10/2013 20:38, John Douglass wrote:
* 3.6.10 - BUG 9367: Use work around for 'winbind use default domain' only if it is set. (unsure) * 3.6.10 - BUG 9386: Winbind: Failover if netlogon pipe is not available. (unsure)
FWIW at least one of these - samba #9386, above - is backported to the RHEL6 RPM, and I think #9367 too.
This is not to say I'm happy with the laggy samba package on RHEL6, but worth noting.
Of course, it's very difficult to follow the RHEL "samba" RPM changelog, as the bugs are all private, undoubtedly for the usual nonsense reason of "might possibly contain 3 bytes of customer info". Sigh.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Roberto Carna wrote:
Ok, I've try to upgrade today but there is nothing to do at the momento, no new packages.
That's a Debian issue. You *can* create your own Debian packages. See the Wiki.
But in order to know the procedure, how can I do to monitor/analyze the cause that Freeradius service goes down ??? Some file to inspect inside /var/log or what ???
The system should be set up to monitor that. Alan DeKok.
OK, but how do I should setup the system to monitor that please ??? THanks again. 2013/10/31 Alan DeKok <aland@deployingradius.com>:
Roberto Carna wrote:
Ok, I've try to upgrade today but there is nothing to do at the momento, no new packages.
That's a Debian issue. You *can* create your own Debian packages. See the Wiki.
But in order to know the procedure, how can I do to monitor/analyze the cause that Freeradius service goes down ??? Some file to inspect inside /var/log or what ???
The system should be set up to monitor that.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Roberto Carna wrote:
OK, but how do I should setup the system to monitor that please ???
Use monitoring tools on your system? Read the debian documentation. Look for monitoring tools. This isn't a list for end-to-end Debian support. We presume you have some ability to administer a Unix system. Alan DeKok.
On 31 Oct 2013, at 14:58, Alan DeKok <aland@deployingradius.com> wrote:
Roberto Carna wrote:
OK, but how do I should setup the system to monitor that please ???
Use monitoring tools on your system?
Read the debian documentation. Look for monitoring tools.
This isn't a list for end-to-end Debian support. We presume you have some ability to administer a Unix system.
scripts for monit are included in the scripts directory. Suggest that'd be a good place to start. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
participants (5)
-
Alan DeKok -
Arran Cudbard-Bell -
John Douglass -
Phil Mayers -
Roberto Carna