Problem: DSEE6 Install on RedHat ES 4
I installed DSEE6 with DSCC on RHES4, I had it running fine. Once I rebooted it could not restart. It is installed as a service and marked for startup in level 5. boot.log claims it was successful, but it was not.
The problem is that my initial install did NOT create file:
/etc/opt/sun/ds6/autostart.list
The startup script /etc/init.d/dsee_directory looks for this file and failing to find it, does "exit 0" - so that's why boot.log says it was successfully started.
DSEE6 was installed by RPM, and I do see directory /etc/opt/sun/ds6, so most of the install appears kosher.
What should I do to get that autostart.list file created?
[672 byte] By [
Glenn-Na] at [2007-11-27 1:21:09]
# 2
Thanks, that did the trick. Specifically:
My prior installation had already created /etc/init.d/dsee_directory
I created /etc/opt/sun/ds6/autostart.list
In this file I listed the DSEE instances. I only had created one:
/var/opt/sun/dsins1
Now when I boot system, the server is started, but not Java Web Console or cacao, but those two are not necessary to running DSEE, they're simply helpful for management.
To get Java Web Console running:
/usr/sbin/smcwebserver start
Now you can manage by https://localhost:6789
Login as localhost root user (or other local user), not admin!
Then click on dscc link and login as admin
If you need cacao:
/opt/sun/cacao/bin/cacaoadm start
# 3
When one create an instance, it is not automatically registered for starting up at boot time, although almost everything is in place for it.
The administrator must run the simple command:
> dsadm autostart </path/to/instance>
This allows to create other instances for test.
Also, when installing on Solaris 10, the rc scripts are not installed. Since Solaris 10 delivers SMF which obsoletes the rc scripts, the administrator can run the following command to register the instance in SMF and have it automatically started, and restarted on failure:
dsadm enable-service -T SMF </path/to/instance>
I believe that both Java Web Console and Cacao have rc scripts as well to be started at boot time.
Finally, DSCC creates a private Directory Server instance (nicknamed ads). This instance could be started automatically by the dsadm autostart /var/opt/sun/... command.
Regards,
Ludovic.
