Re: [Ejbca-develop] Install.sh hangs

[<Thu...@ao...>]

Also the superadmin.p12 file is not being re-created.

In a message dated 5/23/2004 11:58:51 PM Eastern Daylight Time, Thuffman00 
writes:

> I've installed the beta 3, removed the tomcat.jks and \\foo.crt from bin, 
> re-ran the ./install.sh and I'm now able to get to completion of the script. 
> But now the \\foo.crt and tomcat.jks file are not being created and I'm 
> getting a java.io.FileNotFoundException. 
> 
> 
> In a message dated 5/22/2004 5:31:03 AM Eastern Daylight Time, 
> to...@pr... writes:
> 
> >> This is a bug that was fixed in ejbca 3.0Beta3.
>> 
>> Cheers,
>> Tomas
>> 
>> 
>> Thu...@ao... wrote:
>> 
>> >I've been unsuccessful solving this problem. What's occuring is that 
>> >when ever I runt the install.sh, the process hangs with nothing 
>> >indicating why. The parameters I'm usig are:
>> >
>> >*/You have entered the following data :
>> >
>> >CA short name : AdminCA1
>> >Distinguished Name CA : cn=AdminCA1,o=Biosensor,c=US
>> >Keysize of the CA :  2048
>> >Validity in days for the CA : 3650
>> >Policy id of the CA : 2.5.29.32.0
>> >Computer name of CA server : localhost
>> >Distinguished Name of the SSL server certificate : 
>> >cn=localhost,o=Biosensor,c=US
>> >Password for the super administrators keystore : changeit
>> >Is this correct ( Yes/No/Exit ) :Yes
>> >
>> >The installation will now start, please wait .....
>> >
>> >
>> >Initializing CA
>> >Generating rootCA keystore:
>> >DN: CN=AdminCA1,O=Biosensor,C=US
>> >Keysize: 2048
>> >Validity (days): 3650
>> >Policy ID: 2.5.29.32.0
>> >Initalizing Temporary Authorization Module.
>> >Creating CA...
>> >CAId for created CA: 870865990
>> >-Created and published initial CRL.
>> >CA initialized
>> >
>> >
>> >Setup of Administration Web Interface have started, this will take a 
>> >minute to complete ....
>> >/*
>> >Once I reach this point, the system hangs. All the step for security 
>> >has been followed. This includes the JDK policy upgrade for 'Unlimited 
>> >Strength Jurisdiction Policy Files'.
>> >
>> >I get one error in the JBoss log the indicates the adn=min group was 
>> >not remove as expected, but the exceptions handle and everything 
>> >appears to proceed. The following is an snippet of the log:
>> >*/
>> >/*
>> >*/system_functionality
>> >2004-05-19 23:17:07,606 DEBUG 
>> >[se.anatom.ejbca.authorization.AccessRulesDataBean] Created accessrule 
>> >: /hardtoken_functionality
>> >2004-05-19 23:17:07,613 DEBUG 
>> >[se.anatom.ejbca.authorization.AccessRulesDataBean] Created accessrule 
>> >: /ca
>> >2004-05-19 23:17:07,619 DEBUG 
>> >[se.anatom.ejbca.authorization.AccessRulesDataBean] Created accessrule 
>> >: /endentityprofilesrules
>> >2004-05-19 23:17:07,645 ERROR 
>> >[se.anatom.ejbca.authorization.LocalAuthorizationSessionBean] 
>> >RemoveAdminGroup: javax.ejb.ObjectNotFoundException: No such entity!
>> >2004-05-19 23:17:07,659 ERROR [se.anatom.ejbca.log.Log4jLogDevice] May 
>> >19, 2004 11:17:07 PM EDT, CAId : 0, RA, 
>> >EVENT_ERROR_EDITEDADMINISTRATORPRIVILEGES, Administrator : CACMDLINE, 
>> >User : No User Involved, Certificate : No Certificate Involved, 
>> >Comment : Error removing administratorgroup Public Web Users.
>> >2004-05-19 23:17:07,696 DEBUG 
>> >[se.anatom.ejbca.authorization.AdminGroupDataBean] Created admingroup 
>> >: Public Web Users
>> >2004-05-19 23:17:07,721 DEBUG 
>> >[se.anatom.ejbca.authorization.AdminEntityDataBean] Created admin 
>> >entity null
>> >2004-05-19 23:17:07,726 DEBUG 
>> >[se.anatom.ejbca.authorization.AccessRulesDataBean] Created accessrule :
>> >
>> >*Has anyone else ran across this problem? 
>> 
>> 
>> 
>> 
> 
>