After running radiusd with -xxyz -l stdout, and logging it, this was the
last output I received before it segfaulted:
Reloading configuration files.
reread_config: reading radiusd.conf
Config: including file: //etc/raddb/proxy.conf
Config: including file: //etc/raddb/clients.conf
Config: including file: //etc/raddb/snmp.conf
Config: including file: //etc/raddb/sql.conf
main: prefix = "/"
main: localstatedir = "//var"
main: logdir = "/var/log/radiusd-freeradius"
main: libdir = "/usr/lib/freeradius"
main: radacctdir = "/var/log/radiusd-freeradius/radacct"
main: hostname_lookups = no
read_config_files: reading dictionary
read_config_files: reading clients
read_config_files: reading realms
read_config_files: reading naslist
main: max_request_time = 30
main: cleanup_delay = 5
main: max_requests = 1024
main: delete_blocked_requests = 0
main: port = 0
main: allow_core_dumps = no
main: log_stripped_names = no
main: log_auth = yes
main: log_auth_badpass = yes
main: log_auth_goodpass = no
main: pidfile = "//var/run/radiusd/radiusd.pid"
main: user = "freerad"
main: group = "shadow"
main: usercollide = no
main: lower_user = "after"
main: lower_pass = "no"
main: nospace_user = "after"
main: nospace_pass = "no"
main: proxy_requests = yes
proxy: retry_delay = 5
proxy: retry_count = 3
proxy: synchronous = no
proxy: default_fallback = yes
proxy: dead_time = 120
security: max_attributes = 200
security: reject_delay = 0
main: debug_level = 0
... I'm assuming this means it failed after receiving a -HUP signal?
(It's given one every 15 minutes to rehash our config files and usernames)
If so, I can deal with that, I'll just rewrite our scripts to completely
kill and completely restart it.
Regards,
Justin Wheeler
-- Computer programmer (n): Red-eyed mammal capable of communicating with
electronics and inanimate equipment.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
