On Tue, 12 Oct 2010 09:40:27 +0200, Morten Brekkevold morten.brekkevold@uninett.no wrote:
On Mon, Oct 11, 2010 at 07:59:41PM +0200, Sigurd Mytting wrote:
I'm also getting a lot of errors in ipdevpoll.log, just one examle:
[snip]
"/var/lib/python-support/python2.5/django/db/models/sql/query.py", line 1734, in execute_sql cursor.execute(sql, params) DataError: invalid byte sequence for encoding "UTF8": 0xe56b65 HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encoding".
Is there any way I can avoid putting non latin-1 characters into the database as a workaround?
Well, this error has avoided it for you ;-)
Yeah, I kind of got that after poking around in the code after I'd sent the reply ;-) What I should have asked is how to remove all non ASCII at the time data is fetched from the box.
Apparently, you've set the description of Gi1/0/17 on 12a-sw-vts to "Temperatur Overvåker", using a latin-1 encoding.
It's almost unavoidable when having more than 800 devices on 240 different locations all over the country and more than 30 people doing this their own way. I would of course never even dream of using anything other than ASCII (one of the perks with growing up with the DOS codepage-hell in the 1980s.. ;)
Please report this to the bugtracker, and we'll try to fix it in 3.6.1 (scheduled next week, but possibly delayed over the weekend due to some saved-up vacation time).
Reported.
Cheers,
-Sigurd