Hello. I see a lot of 1401 errors in radiusd.log. But they does not lead to core dumps. Radiusd performs correctly. These errors come when users supply incorrect usernames those are longer than the username column size. We work on SPARC Solaris 2.8, gcc 3.3, Oracle 9.2.0.5, freeradius-1.0.0..
> Kostas Zorbadelos <[EMAIL PROTECTED]> wrote: > > My environment is Solaris 2.8, gcc 2.95.3, Oracle 8.1.7. > > Freeradius crashes (and core dumps) after an sql query causes an error > > with an Oracle backend database. > > Yuck. > > > First of all in oraclesql.conf there is a typo in > > accounting_start_query_alt query: > > Fixed, thanks. > > > Secondly, I caused the crash by sending an accounting start packet > > with very large acct-session-id, that caused an ORA-01401(: inserted > > value too large for column) error. > > Ok. The server *should* be robust in the face of such errors. > > > Should I submit a bug report in bugs.freeradius.org? > > Please. > > > For anything else you might need to trace the error, please let me > > know. > > A gdb 'bt', so we can see where/when the error occured. > > If you have access to a Linux box, you can try running it under > "valgrind", which should give you more information about the invalid > memory accesses. > > Alan DeKok. > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
