At 06:56 PM 11/8/2001 -0500, you wrote:
> I'd say there's a serious problem on your system somewhere. Have
>you installed the server multiple times, from multiple versions? If
>so, then the rlm_FOO may access data structures which no longer
>exists.
>
> Delete all binaries, and re-install.
I did just this on 2 different systems. It worked on the second system, so
as your and in Chris's email suggest I removed all files, and reinstalled
fresh and new. I am no longer receiving segfaults. =) Thanks guys.
On to the next issue. I am trying to execute external scripts on both
Start and Stop status types. The Start works; however, the Stop seems to
be skipped entirely.
My users file looks like this for the start and stop:
DEFAULT Acct-Status-Type := Start
Exec-Program-Wait = "/etc/raddb/test.sh START",
Fall-Through = 1
DEFAULT Acct-Status-Type := Stop
Exec-Program-Wait = "/etc/raddb/test.sh STOP",
Fall-Through = 1
My test.sh program simply logs to a file to show if it has run or not. It
does run properly on Start, but not on stop. Here is the debug output of
the session:
Thread 3 assigned to request 2
--- Walking the entire request list ---
Threads: total/active/spare threads = 5/1/4
Thread 3 handling request 2, (1 handled so far)
<<<<CHOPPED ATTRIBUTES TO SHORTEN EMAIL HERE>>>>
modcall: entering group preacct
modcall[preacct]: module "suffix" returns ok
modcall[preacct]: module "files" returns noop
modcall[preacct]: module "preprocess" returns noop
modcall: group preacct returns ok
modcall: entering group accounting
radius_xlat: '/var/log/radacct/208.8.184.16/detail'
rlm_detail: /var/log/radacct/%{Client-IP-Address}/detail expands to
/var/log/radacct/208.8.184.16/detail
modcall[accounting]: module "detail" returns ok
modcall[accounting]: module "unix" returns ok
radius_xlat: '[EMAIL PROTECTED]'
modcall[accounting]: module "radutmp" returns ok
modcall: group accounting returns ok
Sending Accounting-Response of id 136 to 208.8.184.16:1647
Proxy-State = 0x313435
Finished request 2
Going to the next request
Thread 3 waiting to be assigned a request
--- Walking the entire request list ---
Threads: total/active/spare threads = 5/0/5
Cleaning up request 2 ID 136 with timestamp 3bec8227
Nothing to do. Sleeping until we see a request.
It seems at the end it "cleans" up request 2 because it never found the
stop packet, therefore never executed the stop script?
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
