[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #30703 [Internal Services/Services Admin Team]: How to modify Apache config on polyanthum?
#30703: How to modify Apache config on polyanthum?
-------------------------------------------------+-------------------------
Reporter: phw | Owner: phw
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Internal Services/Services Admin | Version:
Team |
Severity: Normal | Resolution: fixed
Keywords: | Actual Points:
Parent ID: #30472 | Points: 0.5
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Changes (by anarcat):
* status: assigned => closed
* resolution: => fixed
Comment:
so. er. there are actually *two* version control systems in there:
1. all of `/etc` is managed through git, by a tool called etckeeper which
does daily autocommits and has hooks that run after package installs and
so on
2. the `/etc/apache2/sites-available` directory, *on top of that* is
*also* managed through RCS
The last commit on that file in RCS is:
{{{
----------------------------
revision 1.15 locked by: root;
date: 2017/11/15 23:27:10; author: root; state: Exp; lines: +1 -0
update run by root(isis) at Wed, 15 Nov 2017 23:27:10 +0000 on
polyanthum.torproject.org
}}}
The diff is:
{{{
root@polyanthum:/etc/apache2/sites-available# rcsdiff -u -r1.14 -r1.15
./bridges.torproject.org.conf
===================================================================
RCS file: ./RCS/bridges.torproject.org.conf,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- ./bridges.torproject.org.conf 2017/04/27 00:57:53 1.14
+++ ./bridges.torproject.org.conf 2017/11/15 23:27:10 1.15
@@ -25,6 +25,7 @@
</Proxy>
ProxyPass /meek/ http://127.0.0.1:2000/
+ ProxyPass /moat/ http://127.0.0.1:3881/moat/
ProxyPass / http://127.0.0.1:3880/ retry=10
ProxyPassReverse / http://127.0.0.1:3880/
}}}
Those changes were *also* committed into git, through the daily
autocommit. Hilarious. :)
In any case, those files are only writable by root, so I guess you need to
ask me or other tpa to make changes.
So I just implemented your change. I grepped through the access log and it
seems the `/scan` prefix wasn't in use anywhere, so it's a safe bet. The
thing gives us a 404 right now, but I guess that's to be expected because
it doesn't seem like anything is running on port 4000. Here's the error
log in apache:
{{{
[Fri May 31 00:43:11.833004 2019] [proxy:error] [pid 17339:tid
140323233597184] (111)Connection refused: AH00957: HTTP: attempt to
connect to 127.0.0.1:4000 (127.0.0.1) failed
}}}
I've committed the change into RCS *and* git, for good measure.
Then I'll try to forget what I have seen here, for mental health reasons.
:p
I hope that helps!
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30703#comment:3>
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