Custom Query (25134 matches)


Show under each result:

Results (37 - 39 of 25134)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#32906 fixed GetTor email responder not working cohosh

I'm getting a response that reports an error in the process_email script:

This is the mail system at host

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<>: Command died with status 1: "python3
    /srv/". Command
    output: Traceback (most recent call last):   File
    "/srv/", line 52, in
    <module>     settings = options.parse_settings() TypeError:
    parse_settings() missing 2 required positional arguments: 'locale' and
#32903 fixed Install python3-pip on gettor-01 hiro cohosh

We need some python3 packages for the update_github script

#32902 fixed document the current install workflow visually hiro anarcat

After discussing the problem of automating installs with hiro, it became clear it would be quite useful to better understand the different workflows we currently have in place.

This could be done with a flowchart with the first decision point branching into the various install systems we have (hetzner cloud, hetzner robot, generic baremetal (say at cymru), ganeti).

The diagram should document every step taken by the various processes documented in the new-machine document. the first decision point would branch into the following pages:

In the first two cases, we should also expand the install scripts from tsa-misc, specifically:

  • tsa-misc/installer/tor-install-hetzner - for hetzner-cloud
  • tsa-misc/installer/tor-install-format-disks - for hetzner-robot
  • tsa-misc/installer/tor-install-luks-setup - for hetzner-robot

We should also cover new-machine-mandos somehow in there.

Bits that should/could be automated should eventually be created as sister tickets here, but for now this should focus on just documenting the actual process in a diagram.

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Note: See TracQuery for help on using queries.