When you get this crypto shell error, do a ps ax and kill
any openca process.  Then redo openca_start.  Ignore the
change group error for now.  A ps ax should show
openca running.


Message: 3
Date: Mon, 15 Dec 2003 15:27:14 +0200
From: Alexei Chetroi <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [Openca-Users] openca_start starting problem
Reply-To: [EMAIL PROTECTED]

 Hi,

 I'm completly confused with openca_start. It doesn't like at all
usernames "www-data". With it openca_start 1st start attempt fails with

</HTML>
OpenCA: Error Trapped: Cannot initialize Crypto Shell
(/usr/bin/openssl)!No default token specified. at
/usr/share/perl5/OpenCA/UI/HTML.pm line 140.
Compilation failed in require at ./openca_start line 49.

 But there remains one openca_start proccess:
cosstel:/etc/openca# ps -ef|grep openca
www-data 28081     1  0 15:15 pts/0    00:00:00 /usr/bin/perl
./openca_start

 Second start attempt fails with:
cosstel:/etc/openca# ./openca_start
Process Backgrounded
2003/12/15-15:16:03 OpenCA::Server (type Net::Server::Fork) starting!
pid(28084)
Binding to UNIX socket file /var/lib/openca/tmp/openca_socket using
SOCK_STREAM
2003/12/15-15:16:03 Invalid group "www-data"
  at line 411 in file /usr/share/perl5/Net/Server.pm
2003/12/15-15:16:03 Server closing!

 With httpd_user like cawww 1st start attempt fails in the same way, but
second attempt complains about setuid:

cosstel:/etc/openca# ./openca_start
Process Backgrounded
2003/12/15-15:20:26 OpenCA::Server (type Net::Server::Fork) starting!
pid(28101)
Binding to UNIX socket file /var/lib/openca/tmp/openca_socket using
SOCK_STREAM
Setting gid to "104 104"
Setting uid to "102"
Couldn't POSIX::setuid to "102" []
cosstel:/etc/openca# ps -ef|grep openca
cawww    28097     1  1 15:20 pts/0    00:00:00 /usr/bin/perl
./openca_start
cawww    28101     1  0 15:20 pts/0    00:00:00 /usr/bin/perl
./openca_start
cosstel:/etc/openca# 

 So the big question: What do I do wrong? Is there any posibility to
increase verbosity of openca_start and cgi-bin/ca ?

<<winmail.dat>>

Reply via email to