[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #4015 [Torflow]: BwAuthority postgres scanner freezes with changes from #3679 TorCtl Event Parsing Rewrite
#4015: BwAuthority postgres scanner freezes with changes from #3679 TorCtl Event
Parsing Rewrite
---------------------+------------------------------------------------------
Reporter: aagbsn | Owner: mikeperry
Type: defect | Status: new
Priority: major | Milestone:
Component: Torflow | Version:
Keywords: | Parent: #3679
Points: | Actualpoints:
---------------------+------------------------------------------------------
Comment(by mikeperry):
Replying to [comment:2 mikeperry]:
> Thoughts on ways to force a traceback/logs out of this piece of shit:
>
> kill -SIGINT child_pid # To cause a KeyboardInterrupt traceback in a
random python thread
> kill -SIGKILL tor_pid # To generate a traceback inside the read loop
due to closed control port
> kill -SIGHUP tor_pid # To cause tor to send some random control port
events during re-init
>
> Any others we can try?
ps -eLf will give us the thread ids of the bw scanner children. We can try
sending SIGINT, SIGALRM.
We could also try attaching gdb and running "thread apply all backtrace"
to get the actual python backtraces. Maybe those will yield clues.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4015#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs