Anonymous_User Absent Member.
Absent Member.
306 views

Linux Fan-out driver SSL connection error


Hi,

I'm trying to connect a Linux system(Debian) to a Identity Manager 4.02
running on OES11SP1. I installed and configured the Core Driver as per
documentation(I hope..) the service is listening on 3451 port. I
installed the Platform services on the connected system(Debian) but when
I have to configure SSL i get the folowing error: Error in SSL connect;
check address and port
I activated a trace log on the connected system:
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_connect: starting
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_connect: host = srv11.viki.ro
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_connect: port = 3451
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_connect: appears to be a hostname
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) attempting
to dup socket
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) Got new
socket descriptor, socket=256
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_select: selecting for time_out=19999574
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_connect: select returned
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_connect: connected
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_select: selecting for time_out=19996796
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_connect: could not make SSL connect (unclean shutdown), error =
1
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) Printing SSL
error queue:
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09E086:FIPS routines:FIPS_digestfinal:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09E086:FIPS routines:FIPS_digestfinal:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09E086:FIPS routines:FIPS_digestfinal:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
error:2D09E086:FIPS routines:FIPS_digestfinal:selftest failed
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_close: starting
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_close: ending
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_valid_socket: invalid socket number=-1
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_destroy: starting
2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
tcp_ssl_destroy: ending, errno = 11

Because I found nothing relevant about the errors I activated the
debug.log on Core Driver:

2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
tcp_ssl_accept: starting
2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl) attempting
to dup socket
2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl) Got new
socket descriptor, socket=1027
2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
network_connection_tcpip_ssl_create: starting
2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
network_connection_tcpip_ssl_create: ending
2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
tcp_ssl_accept: ending
2014-08-11 08:12:38 [21687@2888537856]: (listener)
listener_accept_connections: true
2014-08-11 08:12:38 [21687@2888537856]: (listener)
listener_work_task_execute: starting
2014-08-11 08:12:38 [21687@2888537856]: (os_pthread) os_start_task:
name=SSL HTTP Worker Thread
2014-08-11 08:12:38 [21687@2888537856]: (pthread) pthread_start_task:
name=SSL HTTP Worker Thread
2014-08-11 08:12:38 [21687@2888537856]: (pthread) pthread_start_task:
new task id=-1406970112
2014-08-11 08:12:38 [21687@2888537856]: (listener)
listener_work_task_execute: giving task to 18446744072302581504
2014-08-11 08:12:38 [21687@2888537856]: (listener) listener_poll_tasks:
task 18446744072302581504 (ac235700) is active
2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
tcp_ssl_select: selecting for time_out=60000000
2014-08-11 08:12:38 [21687@2887997184]: (http_server_task)
http_server_execute: running SSL HTTP Worker Thread (22)
2014-08-11 08:12:38 [21687@2887997184]: (http_server_task)
http_server_execute: starting
2014-08-11 08:12:38 [21687@2887997184]: (listener_subtask)
listener_subtask_init: starting
2014-08-11 08:12:38 [21687@2887997184]: (listener_subtask)
listener_subtask_init: after os_take_connection_from_task
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_select: selecting for time_out=20000000
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_accept_final: could not make SSL accept (clean shutdown), error
= 5
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_accept_final: SSL syscall error, errno = 0
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl) Printing
SSL error queue:
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_get_peer_info: starting
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_get_peer_info: could not get peer name, errno=107
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_get_peer_info: ending
.....
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl) Printing
SSL error queue:
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl) SSL
error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure
2014-08-11 08:12:38 [21687@2887997184]: (http_common) http_read_line:
http_read failed
2014-08-11 08:12:38 [21687@2887997184]: (http_server)
http_read_request_line: read error, len=-1 (0)
2014-08-11 08:12:38 [21687@2887997184]: (http_server) http_get_request:
http_read_request_line failed
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_close: starting
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_close: ending
2014-08-11 08:12:38 [21687@2887997184]: (http_server_task)
http_server_execute: get request failed
2014-08-11 08:12:38 [21687@2887997184]: (http_common) http_terminate:
starting
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_close: starting
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_close: could not close, errno=9
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_destroy: starting
2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
tcp_ssl_destroy: ending, errno = 9

The error I see is "could not get peer name, errno=107" but when I do
nslookup on both Core Driver and Platform service the names of the
systems are resolvables.

I tried openssl s_client command and it connects on the same port:
openssl s_client -connect srv11.viki.ro:3451

Can someone help me please to figure out what is wrong ?

Thanks,
Viki


--
vdusnoki
------------------------------------------------------------------------
vdusnoki's Profile: https://forums.netiq.com/member.php?userid=5728
View this thread: https://forums.netiq.com/showthread.php?t=51495

Labels (1)
0 Likes
9 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


You may have mismatched versions of the Platform Services and the Core
Driver.

It looks like Platform Services is 4.0.2b and the Core Driver is older.

To get the Platform Services version: asamrcvr -v

To get the Core Driver version: asamcdrv -v

Are they mismatched?


--
Zygomax
------------------------------------------------------------------------
Zygomax's Profile: https://forums.netiq.com/member.php?userid=215
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


Hi,

I will check. Because this is our test environment I already started to
reinstall everything hoping that I did something wrong in the first
place. I will return with an update after I finish this.

Thanks,

Viki


--
vdusnoki
------------------------------------------------------------------------
vdusnoki's Profile: https://forums.netiq.com/member.php?userid=5728
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


Hi,
I have checked:
../asamrcvr -v
Version: 3.6.1.22
Build Date: 140415

srv11:/usr/local/ASAM/bin/CoreDriver # ./asamcdrv -v
Novell Identity Manager Fan-Out Driver
Version 4.0.2
Build Date 140415

I don't know if this is a problem. I installed Platform Services from
the latest
Integration Module 4.02b and the Core Driver from the same kit!.

Thanks,
Viki
Zygomax;247453 Wrote:
> You may have mismatched versions of the Platform Services and the Core
> Driver.
>
> It looks like Platform Services is 4.0.2b and the Core Driver is older.
>
> To get the Platform Services version: asamrcvr -v
>
> To get the Core Driver version: asamcdrv -v
>
> Are they mismatched?



--
vdusnoki
------------------------------------------------------------------------
vdusnoki's Profile: https://forums.netiq.com/member.php?userid=5728
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


Those versions are fine.

This build added FIPS support with OpenSSL, for additional security. It
appears from the first log that FIPS is having issues.

What version of Debian are you running? What is printed from "uname -a"
on that system?


--
Zygomax
------------------------------------------------------------------------
Zygomax's Profile: https://forums.netiq.com/member.php?userid=215
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


Hi,
The version is:

root@TestIDM:~# uname -a
Linux TestIDM 3.2.0-4-686-pae #1 SMP Debian 3.2.60-1+deb7u3 i686
GNU/Linux

Thanks,
Viki


--
vdusnoki
------------------------------------------------------------------------
vdusnoki's Profile: https://forums.netiq.com/member.php?userid=5728
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


From the platform services side, was anything from the asamrcvr logged
to syslog? Also, is this problem isolated to Debian?


vdusnoki;247411 Wrote:
> Hi,
>
> I'm trying to connect a Linux system(Debian) to a Identity Manager 4.02
> running on OES11SP1. I installed and configured the Core Driver as per
> documentation(I hope..) the service is listening on 3451 port. I
> installed the Platform services on the connected system(Debian) but when
> I have to configure SSL i get the folowing error: Error in SSL connect;
> check address and port
> I activated a trace log on the connected system:
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_connect: starting
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_connect: host = srv11.viki.ro
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_connect: port = 3451
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_connect: appears to be a hostname
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) attempting
> to dup socket
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) Got new
> socket descriptor, socket=256
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_select: selecting for time_out=19999574
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_connect: select returned
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_connect: connected
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_select: selecting for time_out=19996796
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_connect: could not make SSL connect (unclean shutdown), error =
> 1
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) Printing SSL
> error queue:
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09E086:FIPS routines:FIPS_digestfinal:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09E086:FIPS routines:FIPS_digestfinal:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09E086:FIPS routines:FIPS_digestfinal:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09F086:FIPS routines:FIPS_digestupdate:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl) SSL
> error:2D09E086:FIPS routines:FIPS_digestfinal:selftest failed
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_close: starting
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_close: ending
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_valid_socket: invalid socket number=-1
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_destroy: starting
> 2014-08-11 08:12:24 [8290@3076421312]: (network_tcpip_ssl)
> tcp_ssl_destroy: ending, errno = 11
>
> Because I found nothing relevant about the errors I activated the
> debug.log on Core Driver:
>
> 2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
> tcp_ssl_accept: starting
> 2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl) attempting
> to dup socket
> 2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl) Got new
> socket descriptor, socket=1027
> 2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
> network_connection_tcpip_ssl_create: starting
> 2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
> network_connection_tcpip_ssl_create: ending
> 2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
> tcp_ssl_accept: ending
> 2014-08-11 08:12:38 [21687@2888537856]: (listener)
> listener_accept_connections: true
> 2014-08-11 08:12:38 [21687@2888537856]: (listener)
> listener_work_task_execute: starting
> 2014-08-11 08:12:38 [21687@2888537856]: (os_pthread) os_start_task:
> name=SSL HTTP Worker Thread
> 2014-08-11 08:12:38 [21687@2888537856]: (pthread) pthread_start_task:
> name=SSL HTTP Worker Thread
> 2014-08-11 08:12:38 [21687@2888537856]: (pthread) pthread_start_task:
> new task id=-1406970112
> 2014-08-11 08:12:38 [21687@2888537856]: (listener)
> listener_work_task_execute: giving task to 18446744072302581504
> 2014-08-11 08:12:38 [21687@2888537856]: (listener) listener_poll_tasks:
> task 18446744072302581504 (ac235700) is active
> 2014-08-11 08:12:38 [21687@2888537856]: (network_tcpip_ssl)
> tcp_ssl_select: selecting for time_out=60000000
> 2014-08-11 08:12:38 [21687@2887997184]: (http_server_task)
> http_server_execute: running SSL HTTP Worker Thread (22)
> 2014-08-11 08:12:38 [21687@2887997184]: (http_server_task)
> http_server_execute: starting
> 2014-08-11 08:12:38 [21687@2887997184]: (listener_subtask)
> listener_subtask_init: starting
> 2014-08-11 08:12:38 [21687@2887997184]: (listener_subtask)
> listener_subtask_init: after os_take_connection_from_task
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_select: selecting for time_out=20000000
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_accept_final: could not make SSL accept (clean shutdown), error
> = 5
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_accept_final: SSL syscall error, errno = 0
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl) Printing
> SSL error queue:
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_get_peer_info: starting
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_get_peer_info: could not get peer name, errno=107
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_get_peer_info: ending
> ....
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl) Printing
> SSL error queue:
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl) SSL
> error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure
> 2014-08-11 08:12:38 [21687@2887997184]: (http_common) http_read_line:
> http_read failed
> 2014-08-11 08:12:38 [21687@2887997184]: (http_server)
> http_read_request_line: read error, len=-1 (0)
> 2014-08-11 08:12:38 [21687@2887997184]: (http_server) http_get_request:
> http_read_request_line failed
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_close: starting
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_close: ending
> 2014-08-11 08:12:38 [21687@2887997184]: (http_server_task)
> http_server_execute: get request failed
> 2014-08-11 08:12:38 [21687@2887997184]: (http_common) http_terminate:
> starting
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_close: starting
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_close: could not close, errno=9
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_destroy: starting
> 2014-08-11 08:12:38 [21687@2887997184]: (network_tcpip_ssl)
> tcp_ssl_destroy: ending, errno = 9
>
> The error I see is "could not get peer name, errno=107" but when I do
> nslookup on both Core Driver and Platform service the names of the
> systems are resolvables.
>
> I tried openssl s_client command and it connects on the same port:
> openssl s_client -connect srv11.viki.ro:3451
>
> Can someone help me please to figure out what is wrong ?
>
> Thanks,
> Viki



--
jgrieshop
------------------------------------------------------------------------
jgrieshop's Profile: https://forums.netiq.com/member.php?userid=483
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


Hi,

Nothing in the /var/log/messages. And yes, only on Debian, we only have
AD driver that was working before we implemented the Linux Driver.
Thanks,

Viki


--
vdusnoki
------------------------------------------------------------------------
vdusnoki's Profile: https://forums.netiq.com/member.php?userid=5728
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


Viki, can you give this installer a try?

http://tinyurl.com/pech3dm



vdusnoki;247797 Wrote:
> Hi,
>
> Nothing in the /var/log/messages. And yes, only on Debian, we only have
> AD driver that was working before we implemented the Linux Driver.
> Thanks,
>
> Viki



--
jgrieshop
------------------------------------------------------------------------
jgrieshop's Profile: https://forums.netiq.com/member.php?userid=483
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Linux Fan-out driver SSL connection error


Hi,

Yes I will but the file type is SIT and I don't know how to extract the
bin from inside.
And I have to finish the reinstallation of the environment.

Thanks,
Viki


--
vdusnoki
------------------------------------------------------------------------
vdusnoki's Profile: https://forums.netiq.com/member.php?userid=5728
View this thread: https://forums.netiq.com/showthread.php?t=51495

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.