Opened 6 years ago

Closed 2 years ago

#11640 closed defect (user disappeared)

bwauth, aggregate.py fails on freebsd

Reported by: phobos Owned by: aagbsn
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Blocker Keywords: torflow, python, freebsd, torctl
Cc: mikeperry Actual Points:
Parent ID: #24088 Points:
Reviewer: Sponsor:

Description

bwauth is up and running, but aggregate fails to run. It returns the following error:

./cron-mine.sh 
ERROR[Mon Apr 28 19:24:08 2014]:Exception during aggregate: No section: 'TorCtl'
Traceback (most recent call last):
  File "/usr/home/torflow/torflow/NetworkScanners/BwAuthority/aggregate.py", line 876, in <module>
    main(sys.argv)
  File "/usr/home/torflow/torflow/NetworkScanners/BwAuthority/aggregate.py", line 364, in main
    TorUtil.read_config(argv[1]+"/scanner.1/bwauthority.cfg")
  File "../../TorCtl/TorUtil.py", line 119, in read_config
    tor_port = config.getint('TorCtl', 'tor_port')
  File "/usr/local/lib/python2.7/ConfigParser.py", line 359, in getint
    return self._get(section, int, option)
  File "/usr/local/lib/python2.7/ConfigParser.py", line 356, in _get
    return conv(self.get(section, option))
  File "/usr/local/lib/python2.7/ConfigParser.py", line 607, in get
    raise NoSectionError(section)
NoSectionError: No section: 'TorCtl'

Child Tickets

Change History (3)

comment:1 Changed 6 years ago by phobos

cron-mine.sh is

#!/bin/sh

SCANNER_DIR=/usr/home/torflow/torflow/NetworkScanners/BwAuthority

TIMESTAMP=`date +%Y%m%d-%H%M`
ARCHIVE=$SCANNER_DIR/data/bwscan.${TIMESTAMP}
OUTPUT=$SCANNER_DIR/bwscan.V3BandwidthsFile

cd $SCANNER_DIR # Needed for import to work properly.
$SCANNER_DIR/aggregate.py $SCANNER_DIR/data $OUTPUT

if [ $? = 0 ]
then
 cp $OUTPUT $ARCHIVE
 #scp $OUTPUT bwscan@torauthority.org:/var/lib/tor.scans/bwscan > /dev/null
fi

SCANNER_DIR is the correct path.

comment:2 Changed 5 years ago by cypherpunks

is TorCtl here: /usr/home/torflow/torflow/TorCtl ?

comment:3 Changed 2 years ago by teor

Parent ID: #24088
Resolution: user disappeared
Severity: Blocker
Status: newclosed

This is apparently a setup issue, not a torflow issue.
In either case, we are removing setup.sh in #24088, because it leads to issues like this.

Note: See TracTickets for help on using tickets.