Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#10855 closed defect (invalid)

Arm crashes when run remotely

Reported by: atagar Owned by: atagar
Priority: Very Low Milestone:
Component: Archived/Nyx Version:
Severity: Keywords: remote
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Filing on behalf of johnakabean...

Traceback (most recent call last):
  File "/usr/share/arm/", line 578, in <module>
    cli.controller.startTorMonitor(time.time() - initTime)
  File "/usr/share/arm/cli/", line 700, in
    curses.wrapper(drawTorMonitor, startTime)
  File "/usr/lib/python2.7/curses/", line 43, in wrapper
    return func(stdscr, *args, **kwds)
  File "/usr/share/arm/cli/", line 720, in
    initController(stdscr, startTime)
  File "/usr/share/arm/cli/", line 86, in initController
expandedEvents, config))
  File "/usr/share/arm/cli/", line 652, in __init__
  File "/usr/share/arm/cli/", line 696, in
    torEventBacklog = getLogFileEntries(setRunlevels, readLimit,
addLimit, self._config)
  File "/usr/share/arm/cli/", line 251, in
    sIndex = runlevels.index(loggingTypes)
ValueError: '[HTTP,OR,PROTOCOL,EDGE,APP,CIRC]NOTICE' is not in list

If you connect to tor's console remotely, of course ARM is unable to
read the log. I see by the python that its supposed to say, in this
case, "unable to read tor's logfile" but, instead, it crashes with the
above. The workaround is to disable it executing this part of pything,
by putting, in the armrc, " false"

Child Tickets

Change History (2)

comment:1 Changed 7 years ago by johnakabean

Keywords: remote added
Priority: normaltrivial
Resolution: invalid
Status: newclosed

comment:2 Changed 7 years ago by johnakabean

my apologies, this bug does exist but with a different result that I will remake new bug report with the correct details. The bug I reported to you, sir, was a result of my misconfiguration of armrc. However, not being able to read the log file locally, arm does crash with the --gui option, where I am remaking this bug report to include the details.

I copied the sample armrc over the existing and only modified the connect host and port, to verify the bug above doesn't exist with the shell based arm. Sorry for the confusion.

Note: See TracTickets for help on using tickets.