Conversion from ISO2022CN to ISO8859_1 not found. Meaning?

[kirberich]

When I enter omshowlog, I get these warning messages, can anybody tell me if they mean something bad is happening?

Code: Select all

WARNING                        Shared memory (Shared memory ) 26.06.07 16:44:40
[OM 24142] Conversion from SJIS to ISO8859_1 not found.


WARNING                        Shared memory (Shared memory ) 26.06.07 16:44:41
[OM 24142] Conversion from ISO2022CN to ISO8859_1 not found.


WARNING                        Remote Client (HTML Access   ) 26.06.07 18:59:50
[OM 8013] The name/mailnode contains invalid characters


        <- cvc_IsMappingAvail3
        <- uni_GetCharset
        <- cvc_IsMappingAvail2
        -> cvc_IsMappingAvail2
        -> uni_GetCharset
        -> cvc_IsMappingAvail3
        <- cvc_IsMappingAvail3
        <- uni_GetCharset
        <- cvc_IsMappingAvail2
        <- htuICE_SetProcessLang
        -> htuICE_ParseORNToTF
        -> htuICE_GetProfile
        -> htuICE_GetConfig
        <- htuICE_GetConfig
        <- htuICE_GetProfile
        <- /build/11.1.0/src/lib/ombase/cl/cl_parse.c:379[100,8013]


WARNING                        Remote Client (HTML Access   ) 26.06.07 19:02:11
[OM 8013] The name/mailnode contains invalid characters


        <- cvc_IsMappingAvail3
        <- uni_GetCharset
        <- cvc_IsMappingAvail2
        -> cvc_IsMappingAvail2
        -> uni_GetCharset
        -> cvc_IsMappingAvail3
        <- cvc_IsMappingAvail3
        <- uni_GetCharset
        <- cvc_IsMappingAvail2
        <- htuICE_SetProcessLang
        -> htuICE_ParseORNToTF
        -> htuICE_GetProfile
        -> htuICE_GetConfig
        <- htuICE_GetConfig
        <- htuICE_GetProfile
        <- /build/11.1.0/src/lib/ombase/cl/cl_parse.c:379[100,8013]


[KevinAnderson]

You can safely ignore them. They are not serious.

Kev.

[kirberich]

Thank you for the quick reply.

Is there a way to get rid of them? They blow up the log file to something fairly unreadable.

[gren]

Hi,

The [OM 24142] errors emitted by the Shared memory daemon should go away with the next release.

You can control what goes into omshowlog on a per-component basis using the
omconflvl command.

For instance, to lower the level for the shared memory daemon use :
omconflvl -a "Shared memory daemon" 4

You can see the existing levels using :
omshowlvl -a

The "Remote Client Interface" is more complicated as it can be set on a per-user basis using the UAL_TRACE_LEVEL setting in user.cfg files or in general.cfg.

However, note that either ways, you run the risk of missing genuine problems.

Regards,
Gren.