Scalix Forums

Hi all,

I've just noticed that our PostgreSQL log file is full of the following error messages :

2007-07-23 00:55:50 EEST scalix scalix ERROR: current transaction is aborted, commands ignored until end of transaction block
2007-07-23 00:55:59 EEST scalix scalix ERROR: invalid byte sequence for encoding "UTF8": 0x00
2007-07-23 00:55:59 EEST scalix scalix 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".

We're running 11.1 version of Scalix on SuSe Enterprise Server. Any comment on that? Thanks in advance...

Yucel

See this: http://www.scalix.com/wiki/index.php?ti ... 03-PGCHARS

Thank you. Does recreating the DB affect old messages?

To be honest, I don't know. I would assume they are lost. But keep in mind that the stuff stored in the Postgres DB is for amenities, it's not the mail store. So, blowing it away shouldn't a big deal. But don't quote me on that. Perhaps someone else can give their thoughts.

The Postgres database is a cache, yes, not part of the mailstore. You can run the entire mailstore without installing it, if you wish (you will lose the platform API, though), but you can access mail perfectly.

If you blow away the cache and then use the API again, it should re-create the cache - including for old messages. For perfomance, you may want to prime the cache before users need it.

http://www.scalix.com/wiki/index.php?ti ... 03-PGCHARS
mentions sxpsql-recreatedb, which will re-build the complete cache.

Regards,
Gren.

Could you post the part of sxpsql-recreatedb that rebuilds the cache? Because I don't see anything in there appears to do that.

Oops. I should check my facts first! Sorry, I assumed the link was to something else I was aware of.
See :
http://www.scalix.com/wiki/index.php?ti ... PlatformDb

for a tool to populate the DB.

Regards,
Gren.

OK, gotcha. I thought maybe that is what you were talking about, but I decided to go with "I have to be missing something". Thanks.