On 2013/08/21 06:32, Bogdan Andu wrote: > [Switching to thread 1027726] > 0x0000029e250da81a in kevent () at <stdin>:2 > 2 <stdin>: No such file or directory. > in <stdin> > Current language: auto; currently asm > (gdb)
oh, I forgot, you will need to "continue" here ;) > > launched qualys scan and now waiting for crash to occur - will take 2 > hours. > > Unfortunately the relayd patch branch failed with the same error, and > that is why I tried relayd -current > > I'll come back with crash results > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ > From: Stuart Henderson <s...@spacehopper.org> > To: misc@openbsd.org > Sent: Wednesday, August 21, 2013 3:51 PM > Subject: Re: relayd crash > > On 2013-08-21, Bogdan Andu <bo...@yahoo.com> wrote: > > I tried relayd -current and crashed with the error: > > pwd: > > /usr/src/usr.sbin/relayd > > > > $ sudo ./relayd -f /etc/relayd.conf -d > > ..... A LOT > > OF LOGS ................ > > relay www_ssl, session 1368 (1 active), 0, > > 64.39.111.90 -> :0, SSL accept error > > relay www_ssl, session 1369 (1 active), > > 0, 64.39.111.90 -> 127.0.0.1:8080, done > > pfe exiting, pid 8360 > > lost child: > > relay terminated; signal 11 > > hce exiting, pid 18726 > > parent terminating, pid > > 2704 > > Build it with debug symbols (make clean, make DEBUG=-g install) > and re-run it, then you can attach gdb to the pfe process (use ps > to find the correct pid and 'gdb /usr/sbin/relayd' and 'attach <pid>'. > Now when you trigger the crash you should be able to get a backtrace.
