Minor 3.10 debian packaging bug
Tested on ubuntu trusty, /etc/init.d/freeradius looks for pid file on /var/run/freeradius/freeradius.pid, yet by default the server writes /var/run/radiusd/radius.pid. This cause the init script to always thinks freeradius is not running, making "service freeradius status" return the wrong information, and "service freeradius restart" fails. Editing radiusd.conf from name = radiusd to name = freeradius fixed this issue. -- Fajar
Hi, one day they wont rename the server name on debian/ubuntu - after all, the radiusd they avoid clashing with is pretty much ancient and noone uses it alan
On Tue, Oct 06, 2015 at 11:04:50AM +0700, Fajar A. Nugraha wrote:
Tested on ubuntu trusty, /etc/init.d/freeradius looks for pid file on /var/run/freeradius/freeradius.pid, yet by default the server writes ...
Editing radiusd.conf from
name = radiusd
to
name = freeradius
Please check you've installed the latest version (and latest config files). This is patched as part of the debian packaging. https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/debian/patches/r... It works here with a clean install on Debian jessie: $ dpkg-deb -x freeradius-config_3.0.10+git_amd64.deb /tmp/y $ grep ^name /tmp/y/etc/freeradius/radiusd.conf name = freeradius $ # apt-get install yadda yadda # grep ^name /etc/freeradius/radiusd.conf name = freeradius # # service freeradius start # # service freeradius status ● freeradius.service - LSB: Radius Daemon Loaded: loaded (/etc/init.d/freeradius) Active: active (running) since Tue 2015-10-06 11:13:24 BST; 2s ago Process: 98702 ExecStop=/etc/init.d/freeradius stop (code=exited, status=0/SUCCESS) Process: 122196 ExecStart=/etc/init.d/freeradius start (code=exited, status=0/SUCCESS) CGroup: /system.slice/freeradius.service └─122200 /usr/sbin/freeradius Oct 06 11:13:24 ellipse freeradius[122196]: Starting FreeRADIUS daemon: freeradius. Oct 06 11:13:24 ellipse systemd[1]: Started LSB: Radius Daemon. # # service freeradius restart # service freeradius stop # Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
On Tue, Oct 6, 2015 at 5:18 PM, Matthew Newton <mcn4@leicester.ac.uk> wrote:
On Tue, Oct 06, 2015 at 11:04:50AM +0700, Fajar A. Nugraha wrote:
Tested on ubuntu trusty, /etc/init.d/freeradius looks for pid file on /var/run/freeradius/freeradius.pid, yet by default the server writes ...
Editing radiusd.conf from
name = radiusd
to
name = freeradius
Please check you've installed the latest version (and latest config files). This is patched as part of the debian packaging.
https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/debian/patches/r...
It works here with a clean install on Debian jessie:
$ dpkg-deb -x freeradius-config_3.0.10+git_amd64.deb /tmp/y $ grep ^name /tmp/y/etc/freeradius/radiusd.conf name = freeradius $
I think I found the culprit. I used ubuntu ppa for building, basically by only editing the changelog (so that my key can be used to sign the source) and upload the source to ppa. However from the build log on https://launchpadlibrarian.net/220364056/buildlog_ubuntu-trusty-amd64.freera... , after "dpkg-buildpackage" line, I see that it calls fakeroot debian/rules clean debian/rules build-arch while if I tried to build it locally with dpkg-buildpackage (as normal user) it calls fakeroot debian/rules clean debian/rules build And from debian/rules: build: patch build-arch build-indep build-arch: build-arch-stamp patch build-arch-stamp: config.status $(MAKE) touch $@ So on the ppa, the patch didn't get called in time, raddb/radiusd.conf.in is patched AFTER configure and make step, leading to the unpatched radiusd.conf that I have. Not sure why the ppa didn't call debian/rules build (bug on their end?) but it looks like editing build-arch line on debian/rules should do the trick. Will try this later. -- Fajar
On Tue, Oct 06, 2015 at 06:23:11PM +0700, Fajar A. Nugraha wrote:
fakeroot debian/rules clean debian/rules build-arch
while if I tried to build it locally with dpkg-buildpackage (as normal user) it calls
fakeroot debian/rules clean debian/rules build ... Not sure why the ppa didn't call debian/rules build (bug on their end?) but it looks like editing build-arch line on debian/rules should do the trick. Will try this later.
It's sbuild - I've reproduced it. Will have a look to see if there's a sensible fix that I can see. Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
On Tue, Oct 06, 2015 at 12:40:37PM +0100, Matthew Newton wrote:
On Tue, Oct 06, 2015 at 06:23:11PM +0700, Fajar A. Nugraha wrote:
fakeroot debian/rules clean debian/rules build-arch
while if I tried to build it locally with dpkg-buildpackage (as normal user) it calls
fakeroot debian/rules clean debian/rules build ... Not sure why the ppa didn't call debian/rules build (bug on their end?) but it looks like editing build-arch line on debian/rules should do the trick. Will try this later.
It's sbuild - I've reproduced it. Will have a look to see if there's a sensible fix that I can see.
PR incoming. Thanks for the bug analysis. Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
participants (3)
-
A.L.M.Buxey＠lboro.ac.uk -
Fajar A. Nugraha -
Matthew Newton