Hello Oliver -
On Tue, 24 Aug 1999, O Stockhammer wrote:
> >%_Hello,
> We are currently getting two sets of errors reported at Log level
> 4. The first set has to do with our dictionary file, they read:
>
> on Aug 23 10:41:05 1999: ERR: Attribute number 11 (vendor 311) is not
> defined in your dictionary
> Mon Aug 23 10:41:06 1999: ERR: Attribute number 1 (vendor 311) is not
> defined in your dictionary
> Mon Aug 23 10:47:19 1999: ERR: Attribute number 11 (vendor 311) is not
> defined in your dictionary
> Mon Aug 23 10:47:19 1999: ERR: Attribute number 1 (vendor 311) is not
> defined in your dictionary
> Mon Aug 23 10:57:00 1999: ERR: Attribute number 11 (vendor 311) is not
> defined in your dictionary
> Mon Aug 23 10:57:00 1999: ERR: Attribute number 1 (vendor 311) is not
> defined in your dictionary
>
This is due to the Attributes listed above not being in your dictionary. If you
would like to send the definitions to us we will be happy to include them.
> And the second set seem to be with the MySQL DBM module when it tries to
> query the database:
>
> DBD::mysql::db do failed: You have an error in your SQL syntax near
> 'Realm='',
> 'Aug 21, 1999 12:35')' at line 2 at
> /usr/local/lib/perl5/site_perl/5.005/Radius/SqlDb.pm line 189.
> DBD::mysql::db do failed: You have an error in your SQL syntax near
> 'Realm='',
> 'Aug 21, 1999 12:35')' at line 2 at
> /usr/local/lib/perl5/site_perl/5.005/Radius/SqlDb.pm line 189.
> DBD::mysql::db do failed: You have an error in your SQL syntax near 'PPP',
> '4evryng', '', 'Async', '207.240.215.217', 'ccittV42bi' at line 2 at
> /usr/local/lib/perl5/site_perl/5.005/Radius/SqlDb.pm line 189.
>
I note in your configuration file that you have redefined your SQL accounting.
The above errors are due to missing values as indicated by the " ,'', " strings
in the debug messages. If you could send us the corresponding debug output we
will see what packets (and values) are causing the problems.
> This are both very mysterious reporting errors to us. It seems that
> radiator is also crashing quite frequently (once every two days at least).
> We do not get anything logged when it dies. It does take a restart to get
> it going again. We where wondering if it might be better to run Radiator
> out of inetd? Again, this is for our main authentication server. Any
> insight would be appreciated. I have attached a copy of our radius.cfg as
> well (with all passwords commented out).
Again - debug traces at level 4 will assist greatly in identifying the source
of any problems.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
