Grrr, Updating the VMs made the problem go away. (this just leaves the problem of logging going missing) Andrew
On Sat, 26 Oct 2019 at 10:01, Andrew Cagney <[email protected]> wrote: > > One of my test environments was failing in > nss-cert-09-notyetvalid-initiator-ikev2, yet not testing.libreswan.org > and not other environments. The command being run is: > > faketime -f +370d ipsec pluto --config /etc/ipsec.conf > > and pluto.log contains the totally unhelpful: > > [...] > Initializing libevent in pthreads mode: headers: 2.1.8-stable > (2010800); library: 2.1.8-stable (2010800) > | libevent_malloc: new ptr-libevent@0x7f1f55e5afd0 size 40 > | libevent_malloc: new ptr-libevent@0x7f1f55e5cfd0 size 40 > | libevent_malloc: new ptr-libevent@0x7f1f55e5efd0 size 40 > | creating event base > | libevent_malloc: new ptr-libevent@0x7f1f55e60fc0 size 56 > | libevent_malloc: new ptr-libevent@0x7f1f55e62d60 size 664 > > with the help of ftrace -f I turned up: > > write(3, "| libevent_malloc: new ptr-libev"..., 60) = 60 > getuid() = 0 > geteuid() = 0 > getgid() = 0 > getegid() = 0 > fstat(1, {st_mode=S_IFCHR|0666, st_rdev=makedev(0x1, 0x3), ...}) = 0 > ioctl(1, TCGETS, 0x7ffc9c7672a0) = -1 ENOTTY (Inappropriate > ioctl for device) > munmap(0x7f1f58f13000, 8) = 0 > munmap(0x7f1f59149000, 32) = 0 > write(1, "Invalid clock_id for clock_getti"..., 37) = -1 EBADF (Bad > file descriptor) > exit_group(1) = ? > +++ exited with 1 +++ > (END) > > any ideas? > > (as an aside, the message didn't make it to the log file; wonder where > FD-1 is pointing; and we currently have problems getting early log > messages out) _______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
