On Mon, Nov 27, 2017 at 11:11:59PM +0100, Alexander Bluhm wrote: > On Mon, Nov 27, 2017 at 11:04:49PM +0100, Alexander Bluhm wrote: > > And I am waiting for my loop to fail ... > > Now I have got a different error: > > execute: ssh ot2 perl -I /usr/src/regress/usr.sbin/relayd > /usr/src/regress/usr.sbin/relayd/remote.pl copy 10.188.81.22 10.188.81.21 > 37198 /usr/src/regress/usr.sbin/relayd/args-https-inspect.pl > execute: relayd -dvv -f /usr/src/regress/usr.sbin/relayd/relayd.conf > startup > relay_load_certfiles: using ca certificate ca.crt > pfe: filter init done > relay_load_certfiles: using ca key ca.key > relay_load_certfiles: using certificate /etc/ssl/10.188.81.22.crt > relay_load_certfiles: using private key /etc/ssl/private/10.188.81.22.key > parent_tls_ticket_rekey: rekeying tickets > relay_privinit: adding relay relay-args-https-inspect.pl > protocol 1: name proto-args-https-inspect.pl > flags: used, relay flags: tls, tls client, tls inspect > tcp flags: no splice > tls flags: tlsv1.2, cipher-server-preference > tls session tickets: disabled > type: http > match request header log "foo" value "*" > match response header log "bar" value "*" > socket_rlimit: max open files 1024 > socket_rlimit: max open files 1024 > ca_engine_init: using RSA privsep engine > ca_engine_init: using RSA privsep engine > relay_tls_ctx_create: loading certificate > failed to load tls certificate: Invalid argument > relay: relay_launch: failed to create TLS context > lost child: pid 77881 exited abnormally > hce exiting, pid 50562 > pfe exiting, pid 83847 > ca exiting, pid 16315 > parent terminating, pid 52245 > listen sock: 10.188.81.22 11154 > stdin closed >
So relay_load_fd() fails. The code is trashing errno so that may not be a real EINVAL. Guess this is another change to do. -- :wq Claudio
