Re: [Ejbca-develop] driving me nuts....

[Tomas G. <to...@pr...>]

It sounds as if the ca-cert did not get installed in javas truststore. 
The 'keytool' command on setup-adminweb.sh is what is needed for this.
This is also where the hanging occured in beta2 since the keytool 
command prompted for input which java suppressed.
Try to import the ca-cert in the java truststore and the restart JBoss, 
then the adminWeb might work.

/Tomas

Ken Gunderson wrote:

>On Wednesday 26 May 2004 12:29 am, Tomas Gustavsson wrote:
>  
>
>>Dou you have execute permissions on all .sh files? This would hang
>>things on Linux.
>>    
>>
>
>Yep.  Ran find . -name "*.sh" -maxdepth 1 | xargs chmod 755.....  Also 
>sed /bin/sh to /usr/local/bin/bash.
>
>  
>
>>What happens if you run setup-adminweb.sh manually? Manual run should
>>give more information which is otherwise suppressed by java.
>>Just running setup-adminweb.sh should give you a list of arguments so
>>you could figure them out.
>>    
>>
>
>setup-adminweb.sh seems to be what's hanging, but maybe I didn't have 
>all the params correct.  
>
>Apparently the install.sh script hangs on the adminweb set up part??  
>The tomcat.jks gets created, then stops.  install.sh is supposed to run 
>some tests and then copy the appropriate jboss-service.xml file.  This 
>is not happening though.  Also, looks like the paths to the keystore 
>might not be correct.
>
>I've manually configured everything and have now at least gotten to the 
>admin interface on port 8443, but then it doesn't accept my cert and I 
>get auth denied.  Bummer.  Noticed someone else was having probs w/ 
>Konqueror, so I'll try it on a M$ machine.
>
>Just did.  Same deal.  Boo hiss!!
>
>  
>
>>A manual install should consist of something like:
>>ca.sh init ...
>>    
>>
>
>Done deal...;-)
>
>  
>
>>setup-adminweb.sh ...
>>    
>>
>
>Forewent the setup-admin and worked through it all manually.  I've been 
>able to get all the scripts to work individually, but not 
>setup-adminweb.sh
>
>  
>
>>A wipe of the database could be good if you get some more information
>>after running the above.
>>    
>>
>
>After I recharge my batteries a bit I'll cat /dev/null to the logs, drop 
>the db, and start over with more systematic trouble shooting now that I 
>have pretty good knowledge of what the scripts are supposed to do.
>
>Anybody running AIX, Solaris, HP-U, etc. haven't run into similar 
>issues?
>
>  
>