Fatal error "iconv.cs" in Server 11.3

[obrodkin]

Just installed 11.3 server while migrating store from previous version (11.0.2). All services are running fine, however keep getting this messages in s/logs/fatal:

Code: Select all


ERROR                   Internet Mail (Incoming      ) Sun Jan 27 08:58:38 2008
[OM 24071] Event logging for Admin use :
Failed to read iconv.cs: /var/opt/scalix/v2/s/sys/iconv.cs
Pid of logging process: 9225


BTW, s/logs/log.0 complains about the same issues with iconv.cs but with some unreadable characters here and there.

Thanks

Oleg B

[obrodkin]

so am I only one who have this problem? how special....

[Mouseclone]

No you are not the only one that is having this problem.

I came in this morning to find pop3 service down. I tried to stop and start the scalix services and see what was going on and ended up having to reboot the server.

I don't know if these messages caused my failier yet or not. but there are plenty of them. Any one have any idea what they are about?

-----

Edit

Dig some digging around and I don't have - /var/opt/scalix/bw/s/sys/iconv.cs. Wonder if I need it or not. I'm going to keep digging.

[Valerion]

Mm ... I do have a iconv.cs, so maybe you should re-create it. Not sure what it's used for, but it looks related to character set mappings.

-r--r--r-- 1 scalix scalix 1182 Dec 16 23:20 iconv.cs

Code: Select all

# Configuration file to define external mappings for ICONV Equivalent charsets
# and ICONV Superset charsets. They complement the corresponding internal mappings
# configured for Scalix/ICONV Equivalent/Superset charsets. This file enables
# an ICONV charset conversion to replace or superceed another to be configured.
#
# Each line should consist of at least 3 columns separated by space(s) or tab(s).
# Column 1 should be 'E' or 'S' for Equivalent or Supertest mapping type, column
# 2 should be the normal charset (no space), column 3 should be the Equivalent
# or Superset charset (no space). Further columns are reserved for possible MAPI
# and IMAP client mappings.
#
# Note the charset in column 3 is checked at loading time for an ICONV conversion
# to UTF8 and the mapping will be ignored if such conversion is not available. This
# means additional ICONV libraries must be installed for the charset to be accepted.
# A server warning message will be logged when an unsupported charset is detected.
#
# Mapping format:
# E  <normal-charset>    <equivalent-charset>
# S  <normal-charset>    <superset-charset>

S   ISO-2022-JP     ISO-2022-JP-MS
S   ISO-8859-1      CP1252

[Mouseclone]

I found one in /opt/scalix/template/release.sys/iconv.cs

It contains the same data that you post here. I created a symlink to it

Code: Select all

ln -s /opt/scalix/template/release.sys/iconv.cs /var/opt/scalix/xx/s/sys/iconv.cs

This seemed to have stopped the errors in the logs

[Valerion]

Instead of a symlink I would recommend you copy the file to your sys directory. In case something removes it again. Also, then if needed you can edit the file.

[obrodkin]

copying the file stopped the error. Thanks

[tommes]

Hi,

I have the same problem with 'iconv.cs'. When doing an 'omshowlog' it says:

'Unsupported Charset2 [ISO-2022-JP-MS] in /var/opt/scalix/sx/s/sys/iconv.cs'

I checked the file and it looks like the same as the one found in /opt/scalix/template/release.sys/. So I can't see a problem here. However I copied this one to the destination but with no success.

The error stills occurs, so I would be pleased if someone could help me. Thanks a lot!

Tommes