I did what you said and it's still happening.  This was taken from
apache error log:

[root@cert httpd]# tail -200 ca-error_log
 -engine e      use engine e, possibly a hardware device
 -subject       output the request's subject
 -passin        private key password source
 -key file      use the private key contained in file
 -keyform arg   key file format
 -keyout arg    file to send the key to
 -rand file:file:...
                load the file (or the files in the directory) into
                the random number generator
 -newkey rsa:bits generate a new RSA key of 'bits' in size
 -newkey dsa:file generate a new DSA key, parameters taken from CA in
'file'
 -[digest]      Digest to sign with (md5, sha1, md2, mdc2, md4)
 -config file   request template file.
 -subj arg      set or modify request subject
 -new           new request.
 -batch         do not ask anything during request generation
 -x509          output a x509 structure instead of a cert. req.
 -days          number of days a certificate generated by -x509 is valid
for.
 -set_serial    serial number to use for a certificate generated by
-x509.
 -newhdr        output "NEW" in the header lines
 -asn1-kludge   Output the 'request' in a format that is wrong but some
CA's
                have been reported as requiring
 -extensions .. specify certificate extension section (override value in
config file)
 -reqexts ..    specify request extension section (override value in
config file)
 -utf8          input characters are UTF8 (default ASCII)
Using configuration from
/home/httpd/OpenCA/OpenCA/etc/openssl/openssl.cnf
Using configuration from
/home/httpd/OpenCA/OpenCA/etc/openssl/openssl.cnf
Using configuration from
/home/httpd/OpenCA/OpenCA/etc/openssl/openssl.cnf
Using configuration from
/home/httpd/OpenCA/OpenCA/etc/openssl/openssl.cnf
unknown option -pubkey
unknown option -pubkey
req [options] <infile >outfile
where options  are
 -inform arg    input format - DER or PEM
 -outform arg   output format - DER or PEM
 -in arg        input file
 -out arg       output file
 -text          text form of request
 -noout         do not output REQ
 -verify        verify signature on REQ
 -modulus       RSA modulus
 -nodes         don't encrypt the output key
 -engine e      use engine e, possibly a hardware device
 -subject       output the request's subject
 -passin        private key password source
 -key file      use the private key contained in file
 -keyform arg   key file format
 -keyout arg    file to send the key to
 -rand file:file:...
                load the file (or the files in the directory) into
                the random number generator
 -newkey rsa:bits generate a new RSA key of 'bits' in size
 -newkey dsa:file generate a new DSA key, parameters taken from CA in
'file'
 -[digest]      Digest to sign with (md5, sha1, md2, mdc2, md4)
 -config file   request template file.
 -subj arg      set or modify request subject
 -new           new request.
 -batch         do not ask anything during request generation
 -x509          output a x509 structure instead of a cert. req.
 -days          number of days a certificate generated by -x509 is valid
for.
 -set_serial    serial number to use for a certificate generated by
-x509.
 -newhdr        output "NEW" in the header lines
 -asn1-kludge   Output the 'request' in a format that is wrong but some
CA's
                have been reported as requiring
 -extensions .. specify certificate extension section (override value in
config file)
 -reqexts ..    specify request extension section (override value in
config file)
 -utf8          input characters are UTF8 (default ASCII)
Using configuration from
/home/httpd/OpenCA/OpenCA/etc/openssl/openssl.cnf
Error Trapped: Request not present in DB or the status of the request
was changed! at /home/httpd/OpenCA/OpenCA/lib/functions/misc-utils.lib
line 20, <FD> line 31.
Compilation failed in require at /home/httpd/OpenCA/cgi-bin/ca/ca line
193, <FD> line 31.


On Mon, 2002-04-15 at 13:08, Michael Bell wrote:
> "Ziemowit (Chris) Pierzycki" schrieb:
> > 
> > Just finished generating the CA certificate, submitted the admin
> > certificate request and got this error:
> > 
> > Error 690
> > Configuration Error. Request not present in DB or the status of the
> > request was changed!
> 
> Before you start testing again you must initialize the DB again. If you
> forget to reinitialize the database then you try to access the old
> request which has of course another status (ARCHIVED). The new request
> for the initial admin has the status PENDING but if you forget to
> initialize the DB then admin request has not the serial 1.
> 
> Michael
> -- 
> -------------------------------------------------------------------
> Michael Bell                   Email (private): [EMAIL PROTECTED]
> Rechenzentrum - Datacenter     Email:  [EMAIL PROTECTED]
> Humboldt-University of Berlin  Tel.: +49 (0)30-2093 2482
> Unter den Linden 6             Fax:  +49 (0)30-2093 2959
> 10099 Berlin
> Germany                                       http://www.openca.org
> 
> _______________________________________________
> Openca-Users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/openca-users



_______________________________________________
Openca-Users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-users

Reply via email to