[OpenIndiana-discuss] Openindiana and Sun DSEE 6.3.1+

[Jim Klimov]

FWIW, this seems to have been fixed by one or more of the following:

1) Copy certificate bundles from old OS to new OS in /etc/certs
    and /etc/crypto/certs (this alone did not help, at least)

2) Rename the new /usr/lib/mps into a backup location and effectively
    replace with one from the antique installation

Now upon the OS (local zone) restart there are no complaints from the
DSEE server as well as no dmesg errors, and no other SMF services
complain either. Also, the DPS instance that was found to complain
about inability to decypher some of its configuration passwords,
no longer seems to complain about this either.

Hope this helps someone sometime in the future ;)

Thought I'd prefer to use the "proper" configuration, including the
stock up-to-date mps libraries, apparently they have obsoleted
something that DSEE wants...

//Jim

On 2013-12-23 20:01, Jim Klimov wrote:
> Hello all,
>
>    We had a POC recently to see if an old Solaris 10 server can be
> migrated into OI with its tasks and packages (as native OI zones
> with some porting of older packages for vendor software), and the
> project was quite successful in terms of functional equivalence.
>
>    However, one of the old installation's tasks was to run the Sun
> DSEE server stack, stuck at 6.3.1 as seems to have been the last
> release available from Sun at free-to-use demo-project licensing.
> After migration into the new OS the server seems to work, but the
> logs of its LDAP DS instance are filled with errors like these:
>
> [13/Dec/2013:07:16:13 +0400] - ERROR<4112> - Bootstrap config  - conn=-1
> op=-1 msgId=-1 - Configuration error  Plugin cn=Binary
> Syntax,cn=plugins,cn=config has an invalid signature -- Could not verify
> signature
> [13/Dec/2013:07:16:14 +0400] - ERROR<4112> - Bootstrap config  - conn=-1
> op=-1 msgId=-1 - Configuration error  Plugin cn=Boolean
> Syntax,cn=plugins,cn=config has an invalid signature -- Could not verify
> signature
>
> I am not sure what to make of dozens of such lines, since things
> just work. Maybe some (Sun?) certificate got obsoleted or absent
> from the system repositories? Or we missed some package with some
> certificates or whatever? :)
>
> Did anyone encounter this or have an opinion - how to fix, should
> it be a worry at all, etc.?