Bug #12412

Adjust to Tor 0.3.x logging to syslog

Added by intrigeri 2017-03-30 10:27:15 . Updated 2017-05-23 09:05:44 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.0~rc1
Start date:
2017-03-30
Due date:
% Done:

100%

Feature Branch:
feature/12485-tor-0.3.x
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

http://metadata.ftp-master.debian.org/changelogs/main/t/tor/tor_0.3.0.4-rc-1_changelog says:

  * Change default log target to syslog.  We still keep /var/log/tor and
    the logrotation configuration around in case the admin prefers normal
    log files.  Also update README.Debian accordingly.  (closes: #852716).

I think this explains why https://jenkins.tails.boum.org/view/RM/job/test_Tails_ISO_feature-tor-nightly-master/ fails a lot.

Maybe tor_bootstrap_progress should read the Journal (unless we truncate the Tor log?), or use the control port (if that’s repaired)?

As a first stop-gap step, we should probably simply re-enable /var/log/tor/log.

Subtasks

History

#1 Updated by intrigeri 2017-04-27 08:09:26

  • Target version changed from Tails_3.0 to Tails_3.0~rc1
  • Parent task set to Bug #12485

#2 Updated by intrigeri 2017-05-16 18:18:55

#3 Updated by intrigeri 2017-05-16 18:22:11

#4 Updated by intrigeri 2017-05-19 07:43:34

  • Assignee changed from anonym to intrigeri
  • Feature Branch set to feature/12485-tor-0.3.x

#5 Updated by intrigeri 2017-05-19 11:27:45

  • Status changed from Confirmed to In Progress

#6 Updated by intrigeri 2017-05-19 11:29:44

  • % Done changed from 0 to 10

#7 Updated by intrigeri 2017-05-19 19:46:53

  • Assignee changed from intrigeri to anonym
  • QA Check set to Ready for QA

#8 Updated by anonym 2017-05-20 07:59:07

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 10 to 100
  • QA Check changed from Ready for QA to Pass

#9 Updated by intrigeri 2017-05-23 09:05:44

  • Status changed from Fix committed to Resolved