Problems with listen { type="detail" } related to ownership of listen { filename=".." } #1398

Closed
jpereira opened this Issue Nov 25, 2015 · 0 comments

Projects

None yet

1 participant

@jpereira
Contributor

If we have an old "detail.work" file with an ownership different of username used by radiusd. they will be ignored and nothing else is showed during starting.

# ls -l /var/log/freeradius/radacct/buffered/
total 1938368
-rw------- 1 jpereira jpereira 1984882938 Ago  1 23:59 detail.work
# freeradius -XXXxxx
............
Wed Nov 25 14:08:03 2015 : Debug: Listening on command file /var/run/freeradius/freeradius.sock
Wed Nov 25 14:08:03 2015 : Debug: Listening on auth address * port 1812 bound to server default_authentication
Wed Nov 25 14:08:03 2015 : Debug: Listening on acct address * port 1813 bound to server default_accounting
Wed Nov 25 14:08:03 2015 : Debug: Listening on detail file /var/log/freeradius/radacct/buffered/detail-* as server buffered-accounting
Wed Nov 25 14:08:03 2015 : Debug: Listening on coa address * port 3799 bound to server coa
Wed Nov 25 14:08:03 2015 : Debug: Listening on status address 127.0.0.1 port 18121 bound to server status
Wed Nov 25 14:08:03 2015 : Debug: Opened new proxy socket 'proxy address * port 42955'
Wed Nov 25 14:08:03 2015 : Debug: Listening on proxy address * port 42955
Wed Nov 25 14:08:03 2015 : Info: Ready to process requests
Wed Nov 25 14:08:03 2015 : Debug: detail (/var/log/freeradius/radacct/buffered/detail-*): Polling for detail file
Wed Nov 25 14:08:03 2015 : Debug: detail (/var/log/freeradius/radacct/buffered/detail-*): Detail listener state unopened waiting 0.795675 sec
> Ctrl+C

The files are processed only with correct ownership. (this case, same of radiusd)

# chown -R freerad.  /var/log/freeradius/radacct/buffered/
# freeradius -XXXxxx
.......... started and processed with normally.
@alandekok alandekok closed this in ee94eae Nov 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment