Hello, I keep having issues now and then with radsqlrelay. Sometimes we get some accounting records which miss attributes or come with too unexpected values - the resulting SQL queries then sometimes are bogus. My last instance of this generated in radsqlrelay: Incorrect integer value: '' for column 'AcctSessionTime' at row 1 Incorrect integer value: '' for column 'AcctSessionTime' at row 1 Incorrect integer value: '' for column 'AcctSessionTime' at row 1 Incorrect integer value: '' for column 'AcctSessionTime' at row 1 Incorrect integer value: '' for column 'AcctSessionTime' at row 1 radsqlrelay keeps being excited over the query in question *forever* and retries to eternity. The query doesn't get any better over time though - it just makes the whole relaying process come to a grinding halt. Can't radqlrelay be a bit more clever about this, like try three times, and if the query is consistently rejected, save it to a ".reject" file and move on? I can't be the only one who falls into this, am I? Greetings, Stefan Winter -- Stefan WINTER Ingenieur de Recherche Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg Tel: +352 424409 1 Fax: +352 422473 PGP key updated to 4096 Bit RSA - I will encrypt all mails if the recipient's key is known to me http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0DE6A358A39DC66