[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #10609 [Torflow]: aggregate.py unhappy with input data

#10609: aggregate.py unhappy with input data
-------------------------+--------------------
     Reporter:  ln5      |      Owner:  aagbsn
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Torflow  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+--------------------

Comment (by micah):

 I included also the information about which scanner directory was in play,
 by adding:

 {{{
 print("slicenum: "+slicenum)
 }}}

 that showed me:

 {{{
 ValueError on file: bws-41.4:42.1-done-2015-01-21-17:03:13
 slicenum:
 /home/bwscanner/torflow/NetworkScanners/BwAuthority/data/scanner.3/scan-
 data/
 }}}

 and so looking at that file, I found:

 {{{
 bwscanner@longclaw:~/torflow/NetworkScanners/BwAuthority/data/scanner.3
 /scan-data$ ls -l bws-41.4:42.1-done-2015-01-21-17:03:13
 -rw-r--r-- 1 bwscanner bwscanner 0 Jan 21 17:03
 bws-41.4:42.1-done-2015-01-21-17:03:13
 }}}

 aha! Its zero bytes... probably was truncated before it was written when
 the system was rebooted.

 I removed that file and now I get no cron errors. So perhaps the code
 should be a little smarter here about dealing with zero byte files?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10609#comment:9>
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