Monday Aug 17, 2009

Setting up ssoAdminTools fails with: /opensso/bootstrap (No such file or directory)

I was trying to install ssoadm commandline tool on a lab system that had opensso installed previously.

 I unzipped the  ssoAdminTools.zip to a directory and as per the instructions in the file README.setup I set the java path and then ran the setup command.  

The setup did not complete successfully, it complained about  not finding the bootstap file.

# export JAVA_HOME=/usr/jdk/jdk1.5.0_17
# ./setup
Path to config files of OpenSSO server (example: /opensso):/opensso
Debug Directory:/opensso/opensso/debug
Log Directory:/opensso/opensso/log
/opensso/bootstrap (No such file or directory)


I looked at the debug logs and found the following exception in the file:
/opensso/opensso/debug/Configuration

amSetupServlet:08/16/2009 11:42:25:705 PM EST: Thread[smIdmThreadPool,5,main]
ERROR: ServerConfigXMLObserver.notifyChanges
com.sun.identity.common.configuration.ConfigurationException: Not enough space
        at com.sun.identity.setup.BootstrapCreator.update(BootstrapCreator.java:112)

        at com.sun.identity.setup.BootstrapCreator.updateBootstrap(BootstrapCreator.java:79)        at com.sun.identity.common.configuration.ServerConfigXMLObserver.update(ServerConfigXMLObserver.java:100)
        at com.sun.identity.common.configuration.ServerConfigXMLObserver.notifyChanges(ServerConfigXMLObserver.java:80)
        at com.sun.identity.common.configuration.ConfigurationObserver.notifies(ConfigurationObserver.java:190)
        at com.sun.identity.common.configuration.ConfigurationObserver.globalConfigChanged(ConfigurationObserver.java:158)
        at com.sun.identity.sm.ServiceConfigManagerImpl.notifyGlobalConfigChange(ServiceConfigManagerImpl.java:464)
        at com.sun.identity.sm.ServiceConfigManagerImpl.objectChanged(ServiceConfigManagerImpl.java:436)
        at com.sun.identity.sm.SMSNotificationManager.sendNotifications(SMSNotificationManager.java:282)
        at com.sun.identity.sm.SMSNotificationManager$LocalChangeNotifcationTask.run(SMSNotificationManager.java:348)
        at com.iplanet.am.util.ThreadPool$WorkerThread.run(ThreadPool.java:306)

This meant that the opensso configurator was not successful in creating the bootstrap file and I came to know of this only when I tried to setup ssoadm command line tool.

When I last ran the opensso configurator, I remeber reading the message "configuration complete proceed to login" and I was able to login to opensso console as amadmin without any issues.

Is this a bug in the configurator ? Can I construct a bootstap file manually to include datastore information to workaround this ? I am not too sure on this, for now I just decided to use a different system to get going.

I'll make another entry in my blog if I find answers to the above questions.

About

Hema

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today