Hi Jan,
Thanks for the quick response!
I found that issue in the voms-admin log and already fixed that.
But I noticed it was looking the config dir at //etc/voms-admin/, and I
thought it causes another issue so I removed the initial / from the
config path in the /etc/sysconfig/voms-admin file.
Now I write it back and everything working fine.
Sorry for the noise.
Regards,
Peter
On 04/30/2014 01:05 PM, Jan Svec wrote:
> Hi Peter,
>
> I had the same problem, you should check the ownership and permissions of server key and certificate.
>
> Cheers
> Jan
>
> On 30. 4. 2014, at 12:58, Peter Kotcauer <[log in to unmask]> wrote:
>
>> Dear All,
>>
>> I've just upgraded our voms server to EMI-3, but the clients can't
>> connect to the server.
>>
>> I can see the following in the VO's log file:
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19505]:
>> msg="LOG_INFO:REQUEST:logconnection (ipv6sock.cc:123):Received
>> connection from: xxx."
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19547]:
>> msg="LOG_DEBUG:REQUEST:AcceptGSIAuthentication (Server.cpp:378):Select
>> status: 2"
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19547]:
>> msg="LOG_DEBUG:REQUEST:AcceptGSIAuthentication (Server.cpp:403):Accept
>> status: -1"
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19547]:
>> msg="LOG_DEBUG:REQUEST:AcceptGSIAuthentication (Server.cpp:404):Error
>> code: 1"
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19547]:
>> msg="LOG_DEBUG:REQUEST:AcceptGSIAuthentication
>> (Server.cpp:405):SSL_WANT_READ: 2, SSL_WANT_WRITE: 3"
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19547]:
>> msg="LOG_INFO:REQUEST:AcceptGSIAuthentication (Server.cpp:431):Error
>> enstabilishing SSL context."
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19547]: msg="LOG_INFO:REQUEST:Run
>> (vomsd.cc:746):Failed to authenticate peer."
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19547]: msg="LOG_INFO:REQUEST:Run
>> (vomsd.cc:747):OpenSSL error: SSL Handshake error:error:1408A0C1:SSL
>> routines:SSL3_GET_CLIENT_HELLO:no shared cipher"
>> Wed Apr 30 12:37:24 2014:voms:vomsd[19505]: msg="LOG_INFO:REQUEST:Run
>> (vomsd.cc:738):Started child executor with pid = xxxx"
>>
>> Has anyone experienced this issue before?
>>
>> Thanks is advance,
>> Peter
|