Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:02:02Zhttps://gitlab.torproject.org/legacy/trac/-/issues/34114Please give gk access to staticiforme and torwww groups2020-06-13T17:02:02ZMatthew FinkelPlease give gk access to staticiforme and torwww groups```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
This is reversing gk's permission removal in #32735.
Please allow gk access to staticiforme and the supplementary
groups, as described in that ticket.
Thanks!
Mon 04 May 2020 03:00:0...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
This is reversing gk's permission removal in #32735.
Please allow gk access to staticiforme and the supplementary
groups, as described in that ticket.
Thanks!
Mon 04 May 2020 03:00:00 PM GMT
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEo4znE8duGsmMUJcuHp029Ma9dU4FAl6wMDEACgkQHp029Ma9
dU5ilwgAv89nBWt1tIrdgaAWR1wQm9yeZDS6hyLk1ZXjVRn4+GO2RA6+zVHewkwk
Hp5nGF08bN1z27vKVw3wxGKD7U9VVl1pIwqgBhZVAagaN8Vd6OnDVFjjJdkf3nX2
/B8mRsLOh6fPyI4Nrmnl7WKfAkL6H28WD9R3wtObPcJaCZEMcwjiUYxIpOKP+/ll
kumoWR97KiIz92dXKUk3aZt3Qt8VySR5iRmR0Id13Af/LHenY6IV6q+6ks1SVD3E
d8fGnYJv8qnZOy2TSIix0QYkjjv+m1potwLI7Bs06uc9+/dUZ+EIrRoHS1GeUlNO
03KXCVLfdAuZLEN2smiFrnTh6ra0dg==
=D2Le
-----END PGP SIGNATURE-----
```
Ref: #32735anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/34098crm-int-01 running out of disk space2020-06-13T17:02:01Zanarcatcrm-int-01 running out of disk spaceWe're at 92% disk use on crm-int-01 suddenly... It seems that disk usage grew suddenly three days ago:
https://grafana.torproject.org/d/ER3U2cqmk/node-exporter-server-metrics?panelId=31&fullscreen&orgId=1&var-node=crm-ext-01.torproject....We're at 92% disk use on crm-int-01 suddenly... It seems that disk usage grew suddenly three days ago:
https://grafana.torproject.org/d/ER3U2cqmk/node-exporter-server-metrics?panelId=31&fullscreen&orgId=1&var-node=crm-ext-01.torproject.org:9100&var-node=crm-int-01.torproject.org:9100&from=1585834161059&to=1588426161060
The mariadb server was stopped this morning as well. It seems innodb crashes with the following assertion:
```
2020-05-02 9:08:31 41 [ERROR] InnoDB: preallocating 65536 bytes for file ./torcrm_prod/civicrm_acl_contact_cache.ibd failed with error 28
2020-05-02 9:08:31 41 [Warning] InnoDB: Cannot create table `torcrm_prod`.`civicrm_acl_contact_cache` because tablespace full
2020-05-02 09:08:31 0x7f6c50252700 InnoDB: Assertion failure in file /build/mariadb-10.3-qB78gy/mariadb-10.3-10.3.22/storage/innobase/dict/dict0dict.cc line 491
```
There are also warnings on startup:
```
2020-05-02 13:23:17 0 [Note] InnoDB: Ignoring data file './torcrm_prod/#sql-ib1158381.ibd' with space ID 1137566. Another data file called ./torcrm_prod/civicrm_acl_contact_cache.ibd exists with the same space ID.
2020-05-02 13:23:17 0 [Note] InnoDB: Ignoring data file './torcrm_prod/civicrm_acl_contact_cache.ibd' with space ID 1137566. Another data file called ./torcrm_prod/#sql-ib1158381.ibd exists with the same space ID.
```
We have ~1.5GB left on the server:
```
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 20G 18G 1.6G 92% /
```
Most of that 18G is in /var with 5GB split between the two databases:
```
2.4 GiB [##########] /torcrm_prod
2.3 GiB [######### ] /torcrm_staging
```
Here's the top 10 tables in disk usage:
```
528.0 MiB [##########] civicrm_mailing_event_queue.ibd
432.0 MiB [######## ] civicrm_mailing_recipients.ibd
340.0 MiB [###### ] civicrm_activity_contact.ibd
172.0 MiB [### ] civicrm_contact.ibd
168.0 MiB [### ] civicrm_log.ibd
148.0 MiB [## ] civicrm_mailing_event_delivered.ibd
80.0 MiB [# ] civicrm_activity.ibd
60.0 MiB [# ] civicrm_group_contact.ibd
52.0 MiB [ ] civicrm_subscription_history.ibd
52.0 MiB [ ] civicrm_email.ibd
```
Backups take up the most space, however, at about 10GB. I am not familiar with how the backup system works on that host, but there are about 7.5GB of SHA256-* files in there:
```
root@crm-int-01:/var/backups/local/mysql# du -sch SHA256-* | tail -1
7.6G total
```
Some of those are fairly old too:
```
root@crm-int-01:/var/backups/local/mysql# ls -alt SHA256-* | tail -2
-rw-r----- 2 root root 16130992 Feb 8 2019 SHA256-f6810ff0245807455347d88a1a0d7eaf29368e64188e7c1766b64c0cc143570e
-rw-r----- 2 root root 130308 Feb 8 2019 SHA256-c30b262677ed796d892b888f7f417690ca55dd83bf17fa421fdd32438ca2203a
```
It also seems that the database grew quite a bit -- doubled in size -- in the last few months, according to the backup sizes:
```
800.9 MiB [##########] 20200415-190301-torcrm_prod
670.4 MiB [######## ] 20200109-190301-torcrm_prod
398.9 MiB [#### ] 20191002-190301-torcrm_prod
```
Obviously, a database server running out of disk space is an... undesirable condition, to say the least. :) Should we expand the disk usage for that server (which I would rather avoid doing during the weekend) or is there something you can do on your end to clean stuff up?
Alternatively, maybe we should improve the backup system here so it doesn't take up twice as much disk space as the production server. Or, even better, not be on the same partition as the prod...anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/34074[RT-admin] Redirect email alias giving@ and newsletter@ to RT2020-06-13T17:01:57ZGus[RT-admin] Redirect email alias giving@ and newsletter@ to RTHi, Isa asked to redirect giving@ and newsletter@ to RT queues.
giving@ -> RT queue: giving
newsletter@ -> RT queue: newsletter
Thanks!Hi, Isa asked to redirect giving@ and newsletter@ to RT queues.
giving@ -> RT queue: giving
newsletter@ -> RT queue: newsletter
Thanks!anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/34056Please remove irl from gitolite LDAP group2020-06-13T17:01:55ZirlPlease remove irl from gitolite LDAP group```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
For trac.torproject.org 2020-04-29:
Please remove irl from the gitolite LDAP group.
I will file another ticket to remove myself from the
gitolite-admin group in the gitolite configur...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
For trac.torproject.org 2020-04-29:
Please remove irl from the gitolite LDAP group.
I will file another ticket to remove myself from the
gitolite-admin group in the gitolite configuration.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAl6pK+UACgkQF4mIfdjV
vF28lQ//fQnd2uDUtop9qMbDuvrapHYeDj8SWhHUEpO7VesU1Mtya88waxvQ1z98
NXjVRlcGoxB/+d296NNpiTFilO1ziC1+Ib22W0AVL8Ra8Q4EhYCpU8ck+JqXURTF
C3e94fiI7nq/Qj6b3tmVGTjOHGoT6vwP0Bg2T7WYcHL0Zt2+viASWaBcA0bev8fq
SqWGBfKb7q3SiCE/CCMyNsygXM/sKjmKm+r8/HFHL1bOTP1hPgOA9IyMtHtxsmt4
F79hyFZ7/PfkBfD5Bfk0RWxUDLoGeqoMQNXlIbWjYDyxgGiQXniWhQTWZJkOngpT
+tAWRyjK9V127h7SNttH3I0FH5jagWj+FMT92UW4nznwm8GrNDnX3DXxxE33XVNM
eYmyenXxqMSE/VbyHoghEDe5U7fUF8/hq0EocVJc/mLDKU2rf7sSrgOvCjDjVPHU
2tQOduWcEyk3uwSC8R9vJOsrMBFoy8EW4ykV8VGsHwwzpzwA47ea3K8H4CQDJNth
n9FfZxIQgzwscNNBcGam7RzKwW+Ug5v/cViHGV+3U8+JBQEsxO6u0xDvUg65TbTf
BZKMmkP7cSVc6gyZj8EEV3GPK6e6Hnkyjubp8WvT/sB08pfx3+sJ4E5BvwkZAUTL
kIdDN6ulvgqqWVa0VcrSMaDvfjmxmSFL4iGdlw66E1DjyW37tp8=
=9EI7
-----END PGP SIGNATURE-----
```anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/34047Allow sysrqb access to majus2020-06-13T17:01:55ZMatthew FinkelAllow sysrqb access to majusMaybe this is the `translation` ldap group?
Emmapeel, can you confim (and provide a signed message? :/ )
ThanksMaybe this is the `translation` ldap group?
Emmapeel, can you confim (and provide a signed message? :/ )
Thanksanarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/34020Please remove the DNS entry for op-ab.onionperf.torproject.net2020-06-13T17:01:53ZirlPlease remove the DNS entry for op-ab.onionperf.torproject.net#34018 removes this from CollecTor configuration, and the host is currently being shut down as I write this ticket.
I don't know if there's any question as to what to do about TLS certs issued to domain names. In an ideal world we'd tra...#34018 removes this from CollecTor configuration, and the host is currently being shut down as I write this ticket.
I don't know if there's any question as to what to do about TLS certs issued to domain names. In an ideal world we'd track these and not reuse names until we're sure the certs would be expired. There is a Lets Encrypt cert issued to this name that will also be in backups, destroying it would be difficult, but I can revoke the certs:
https://letsencrypt.org/docs/revoking/
I've done this for the two non-expired certs.anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/34019Please remove irl from groups2020-06-13T17:01:52ZirlPlease remove irl from groups```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
For trac.torproject.org 2020-04-27:
Please remove irl from the following LDAP groups:
1512(metrics)
1550(collector)
1546(exonerator)
1547(onionoo)
1532(tordnsel)
1505(gitweb)
1507(ch...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
For trac.torproject.org 2020-04-27:
Please remove irl from the following LDAP groups:
1512(metrics)
1550(collector)
1546(exonerator)
1547(onionoo)
1532(tordnsel)
1505(gitweb)
1507(check)
1577(torresearch)
1573(exonerator-web)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAl6mvTIACgkQF4mIfdjV
vF1+Bg/+K06u/k15Cyz8W6N/yer4/Fy5mPYDf4vCF3MCUGXMTSfs1kTptHxRmypv
gyGRjICSIOk28JI4tKsbHk7HtMdc5WYBqmq9/5NDooZdpN4BY+HAN0FFsAumhXPW
DVhI9wh86ejORPzjDMLgwBa9N4WbMbuTCd3hXsvNtj1cEsNPgCCj1rP7TRzq3mqy
EHtwOx+rDss+0xfoSWKO/4DSMptn7wXqp8E5GwcsuCP9i/ODDtlAbW4PmQd/dpAV
yuY2J+3jKWdtW3xlt/r4gfg/UFEFhOuCs0y5QJVKvbTtS2i3s+Y2uai/f9Oc5JZq
ITB9gGp5HcUh+YtVg6qqhmK2Bgip7togUaEpNQ1f6Lyt3mS2lz7TXm15NcWKtc5k
H1P5dSnOZhIKB4ewagpXhh4ZdeEee8/df1NI7T2cCgdDBd+y3hHVxO8bXnZcgOWM
QDxzJu/ZJ0pVK4Sjh8+UgfCh1A2zIMxc6YsT0YxD2QGs+qPtXYT5DdEws60YfXY1
5oeMpiloI6flwA0KNTc/7GLQfGB3o3VtIpcWQVfh4I6OBhxSJaTAAlVoCOSzQ8+Y
W2c6/Rx291K5bew0WlmFcba3DaERLkenczvHgjMxEC8ZH31ybYcV0Br24aHhq+uc
+4/ZdQAmT6iVrgU41jNQGUQE8KePPprqHtZK82x9frliw9W1qhs=
=cYgF
-----END PGP SIGNATURE-----
```anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/34016Please add DNS entries for new OnionPerf hosts2020-06-13T17:01:52ZKarsten LoesingPlease add DNS entries for new OnionPerf hostsCan you please put in DNS entries for the following new OnionPerf hosts?
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
37.218.241.56 op-us2.onionperf.torproject.net
37.218.247.100 op-nl2.onionperf.torproject.net
103.104.244....Can you please put in DNS entries for the following new OnionPerf hosts?
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
37.218.241.56 op-us2.onionperf.torproject.net
37.218.247.100 op-nl2.onionperf.torproject.net
103.104.244.142 op-hk2.onionperf.torproject.net
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEzBAEBCAAdFiEEn3LJwENUSMzBpDI57UASP+I0EckFAl6mr7wACgkQ7UASP+I0
Ecn8YQgAmXXd9A2jk2RSCoNDsxO2RFpkuB54qhffYccyHl+3DZMZgQ/taGIvOUQK
ikoIx4o+dHhUoww0oOwi7vSK7TShSknxpHdCtFfBet9U5YrmgeICDpVu6bbM/0Oa
vpUR//UeXNT3rZWUmCLQdxNbO9tN9Ad1A1v56xvOj6TUbnxbV4Z3Zc+eNvuMu9h0
n02akV8llBg6HuI8639hg9P3M3Qw8aKtB14yW398+eUm4KhgMyLMWgxnZE1algEb
Lta0unKp1qbDpysDL830ZpqTwBvyqTmJ50Uma7kg57Jx695mrqSl/+N6Ef5d/YJK
z0URVMddc4zGw/AtuVAcjoJMHGSJZA==
=+V9l
-----END PGP SIGNATURE-----
```
Later this week I'll ask you to remove three DNS entries for current OnionPerf hosts, but we should first have the new ones in place and running before turning the old ones off.
Thanks!anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33970Really remove irl from deb.tpo2020-06-13T17:01:49ZirlReally remove irl from deb.tpo#33940 only half did the job.
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
For trac.torproject.org on 2020-04-23:
Please remove irl from the tordebadm LDAP group.
Please also edit /srv/deb.torproject.org/reprepro/conf/trusted-...#33940 only half did the job.
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
For trac.torproject.org on 2020-04-23:
Please remove irl from the tordebadm LDAP group.
Please also edit /srv/deb.torproject.org/reprepro/conf/trusted-keys and remove
(or comment) the final line of the file which contains my signing subkey.
You can double check with gpg --list-key and the fingerprint to make sure
you're commenting out my key.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAl6hPcAACgkQF4mIfdjV
vF2juA/+J+HgcZNetYqfLcpKIRCU1ozRIllTQyemdjz1PPowq/wxyPHnrGj1qmSi
tmtCDFnobIxOD8j4d0gRbkxhrQZhyWfibA4JE9ecmulr2lnGw6bWGmDwNYh5BS+F
7hKbiHUTOx4RaJJQhsjGZdkrPedl3OH4vE0B/dt6IwHMijM8eFWyCZ+o47YVpRfG
l0a8IEBW65XrmLaUbiPzwWtKCs2x3DJcnjpgALxWp6QCwzxJTY5z4iUoj9aIhBtQ
hMCdD+Mow2Gom0FzUS8imR5l9s4Ktjj4YX3ezgLR200RWra3MRm9FpwBDta16azD
oRuNFW17xo+e8JRnFltBkFzewCJcH38Jc/j/KcyrYJpTFCWWWq8LxDj7mfrLcm1M
cEm4J0/Az83H7BVoSme00BoSqLnNoF9i/hkGJA+Woru3Rbqa02ynnbCRuk499yOS
Pg0PrSZeNpB2HLD6sS1y56nMSH6P6Nukvos8nmnrToTn3S/Ax+yO+iXqP3/QSDvX
uoDf7QsiHVS1QrX6i8m2MIIa27o9Lp5jlUjCw5xhtPxSUHsnEM1jBf0CvD61bSu9
k9A6zDeJNbb6HZi0mYa8Xm5glcSgfjt9lSiZco3VukC8PnQR3qCImJVVm3Odsi8r
z7wzwQR+ZYA6eGfuCuHLXTWTVHFFYqQJI1CzdaaLOKIr9iLH3sk=
=t/mD
-----END PGP SIGNATURE-----
```anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33967Add phw to tordnsel and check groups2020-06-13T17:01:48ZirlAdd phw to tordnsel and check groups```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please add phw to the tordnsel and check LDAP groups.
For trac.torproject.org on 2020-04-22.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAl6gXrMACgkQF...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please add phw to the tordnsel and check LDAP groups.
For trac.torproject.org on 2020-04-22.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAl6gXrMACgkQF4mIfdjV
vF1jzBAAudNFtzSTeNmhGX7CcJmoHensOaWbhf5MH4Ka2TT5vO7ANyAILv1JOAJE
/MRez7l6T/QGU2HsI1TvTv3lHYTAIiSdNwW/NGsI8nFM6YXwxvRQF6AK5QziLONd
XAVQWyeeTgsb/bYSD7n0b5018SY5VaqJ+Xf+JLYfI3nTmvyOxz3N2o3S8ccIEcJY
/5SebNZ41Gxn2+V97Ql8ybbi7d4cXVyVoG2JZdDV5JAZ02IvKswytp5OYF2PNRuo
Hfgp82CtPC8Gk+avSjTL5v22zVHFtTEnHuy5dzmxHyEJocz8A0ytmS47hwIB28tI
8QCbUe5xSff702N4qTRZbvFV/eKyuK2KKawnYDmzQn38SwjZTS1RRGTw1fp5X3Qu
dxA/6Xv4QjtfZgMNjsH6OGVKiW8YIqmtEBTVlzIcQ0njE6BEGAimA6MGR27fGYbP
ynAU/7LVVfC61m/KB6bMWn9L6324KQUmMs4S7/Y7PQf+9inFP5sfImgpSEESGo/A
m60oP5NQfuZlZcaPaVekKtYF5RmoVds7swt7wgFOYNMTVcE2HiCCvWEf6720NP+l
SC1fbMHDj6ru75HWe7axxVXrptYEAq0aCFWz3ijW2nTCHlzRCryKdT/nnR4osZXs
gAHdWughfn/tGXiC5ZTB+lQtISZOURVSR3PHAiFiYZgIU8Udgn0=
=v0iy
-----END PGP SIGNATURE-----
```anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33951mtail floods its logs with garbage2020-06-13T17:01:48Zanarcatmtail floods its logs with garbagewe seen ton of this garbage in the mtail logs:
```
I0421 18:43:02.307808 21142 file.go:168] file type does not support deadline
```
there's a lot to unpack here:
* weird log format: the first word is `IMMDD`, that is the above mess...we seen ton of this garbage in the mtail logs:
```
I0421 18:43:02.307808 21142 file.go:168] file type does not support deadline
```
there's a lot to unpack here:
* weird log format: the first word is `IMMDD`, that is the above message is from April 21st (the I is for "Irrelevant character", i guess?)
* 21142 is the pid
* `file type does not support deadline` is an error from the golang standard library and occurs when someone calls `SetReadDeadline` on a file that doesn't support it
This happens every minute or so. It gathers about a gigabyte of logs a month or two.
In later versions of mtail, this is fixed by making turning the "warning" (technically, it's an "Info" message, but those are displayed unconditionnally) into a "verbose" (technically `V(2)`) message that doesn't get shown by default.
The package from buster doesn't have that fix, but the current version in unstable (rc24) does have it.anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33940Please remove irl from tordeb LDAP group (and any other deb.tpo related group)2020-06-13T17:01:45ZirlPlease remove irl from tordeb LDAP group (and any other deb.tpo related group)```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
For trac.tpo at 08:46 on 2020-04-20:
Hi,
Please remove irl from the tordeb group.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAl6dYYEACgkQF4mIfdjV
vF1r...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
For trac.tpo at 08:46 on 2020-04-20:
Hi,
Please remove irl from the tordeb group.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/ps4MHN0fw3t6AudF4mIfdjVvF0FAl6dYYEACgkQF4mIfdjV
vF1r7w//QeffA+6t79Ktkb+KyYzHUSFBJwopMPrE30PPU+LDZ7J/5b4yBaAQR7ER
U+J2PHRWHcBHgiz6RvBe+V4NeHZgXpL2FQ6BVrrryjTgmft3sM+ioHbo09gNZ1rq
t5D4NAkHQHBOW4nSXi6xPP9ikMJFmsEum+cgpFyK8IOvEOP7EvvdLZSdkjfc5YlO
3xytoC8rW8Dt5Qw1Lmu3rEzuiengmJVEutitLTDSW0ttrLZsKNH95yncRFtq6+1h
AUVK8eoHwRopS0ZgMhFFqX76/voAbURhw067KCuoBcGuCawWNTiwNWJSC59CyUJa
WucDAQWAPXIq46yzmFfb4u3lMY8VflttGGdEe0/scH1bu54Vr7VX8cI32Wn6loBS
EGzFs47shHN7yj8XC7CH5W+etIL2eOSlLONsUgLy3pFpbSuaSUZLUbzZREiITBBg
O+tiypctR5tKcuwui/xlTqw4UFaDHbb5CPn761oA0Xq/HHDgncc3RyqoVbWn5jCa
BCl9He18EO6MZ22SFQWVUa7yVzNO+dwi8tH+SbLe38UoZXXzUL6CW/Pv7d/Yg4qm
GTH6zwu4nYRIdLNzl9tkRu3rgyyOCrrMYkT1gWY1YMzi1RKkCxcyCxCwnXkmDVud
zX6H7m4cr0H9NZ1LTOBxRDAK3TNwhtviq5iVkK/TY2IQ3Pw1aPs=
=nY0t
-----END PGP SIGNATURE-----
```anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33869update spreadsheet after migrations2020-06-13T17:01:38Zanarcatupdate spreadsheet after migrationsi just updated the docs for this, but not before i migrated a bunch of machines without updating the spreadsheet, which is probably missing a bunch of hosts in the gnt-fsn cluster now.i just updated the docs for this, but not before i migrated a bunch of machines without updating the spreadsheet, which is probably missing a bunch of hosts in the gnt-fsn cluster now.anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33868fabric (incorrectly) asumes User root ssh_config2020-06-13T17:01:37Zanarcatfabric (incorrectly) asumes User root ssh_configour fabric code assumes we have a `User root` block for all tpo hosts, which is incorrect: i actually deliberately set `User anarcat` on pauli, for example, so that I don't push as root.
this should be fixed with a fabric-specific config.our fabric code assumes we have a `User root` block for all tpo hosts, which is incorrect: i actually deliberately set `User anarcat` on pauli, for example, so that I don't push as root.
this should be fixed with a fabric-specific config.anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33829Please refresh my key certifications2020-06-13T17:01:35Zmicahmicah@torproject.orgPlease refresh my key certificationsThe openpgp key used for me on db.torproject.org needs to be refreshed from the keyservers.
==> <class 'userdir_exceptions.UDFormatError'>: UDFormatError: Signing key
(8CBF9A322861A790, Micah) has expiredThe openpgp key used for me on db.torproject.org needs to be refreshed from the keyservers.
==> <class 'userdir_exceptions.UDFormatError'>: UDFormatError: Signing key
(8CBF9A322861A790, Micah) has expiredanarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33823Can we block phishing emails when forwarding emails?2020-06-13T17:01:34ZteorCan we block phishing emails when forwarding emails?Recently, I have seen a few phishing emails at my torproject email address.
Some of them seem to have been specifically crafted for tor. Some of them are attempts to attack mailman. Others seem like generic spam.
Do we have email spam ...Recently, I have seen a few phishing emails at my torproject email address.
Some of them seem to have been specifically crafted for tor. Some of them are attempts to attack mailman. Others seem like generic spam.
Do we have email spam filters on our email forwarder?
If we do, is there a way to block more spam emails?
Can I send the full headers to someone?anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33776Please change email forwarding for jon@2020-06-13T17:01:30ZErin WyattPlease change email forwarding for jon@```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please forward jon@ to ewyatt@torproject.org, effective April 1st. Jon is aware of this change. Thanks.
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIzBAEB...```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Please forward jon@ to ewyatt@torproject.org, effective April 1st. Jon is aware of this change. Thanks.
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIzBAEBCgAdFiEENecqn2ZVRfkstmYkugyUAPgPkc4FAl6D9gAACgkQugyUAPgP
kc71oxAAnCjtM6ppw1jhgcOoQS0LJqKSEMtKJpYGMYZQtQMLi6CDfiWI7sbjaYbB
ws3TMOQL3j5DU3+/a6IIx7tTkQvCgkNV987la5SYJdPiFGxuKi+UTkdjaqBOv0Rp
R2fUzD65BiWoETSnHhCvAgnOedu8vZkevh5FW3GHyRCxRuB0Nhh6SYcWyE3ggzE7
CN/Gb8sze6byCpkTf+gj/FEH7Bn1UWpXvxGIEB4fGPZT0yBCabsmuEXNAJID8wrL
JZeDCxngrQVNnlPyV1suYPxM42ItRNVeOTELJvG++IHrCOHI+EwEQK+RBZO64GQ+
cgN8hPKdlCpJZO61oPEkvIosmYFQ44UUwFCETW+agGFkvENtgEhsLUD/7va8Pe/J
LWzgH/I1GQOOofMBoD0d5bWF0zauI57n0gJn2coWee5BkC1VeK42c4DlcSpuorun
u0abh1ozFIzMtfVgwK4gnby4mw4vCYkI0XxC7f/hwKPWzVdt88o9P+vbFX1k+01c
Mc+7PoT9IjPZtDwxZkQAmNC6+GQD077Fnlb1oGcyiRchQ5XD4uQqAfmFMA3Cq/bP
Pz8HiRwJDIYaWBxZmdsj5fB70uxRtu/7smOCS/OjqrN+bHbkFMeog1hj+SO1Njgo
uWaZoK5ThDaT12x5UtwvoXUWgU1nuCM5cZdBQEuS/IA1ZjD2Z7Q=
=1Iwk
-----END PGP SIGNATURE-----
```anarcatanarcathttps://gitlab.torproject.org/legacy/trac/-/issues/33539retire gitlab-012020-06-13T17:01:12Zanarcatretire gitlab-01after a week of tests of gitlab-02, retire host gitlab-01.
follow this procedure:
https://help.torproject.org/tsa/howto/retire-a-host/after a week of tests of gitlab-02, retire host gitlab-01.
follow this procedure:
https://help.torproject.org/tsa/howto/retire-a-host/HiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/33082decomission kvm3 AKA macrum, 7 VMs to migrate2020-06-13T17:00:37Zanarcatdecomission kvm3 AKA macrum, 7 VMs to migrate * [x] crm-ext-01.torproject.org (part of #32198) done at `116.202.120.186`
* [x] crm-int-01.torproject.org (also part of #32198) done at `116.202.120.190`
* [x] forrestii.torproject.org (fpcentral, #33729) server migrated to `116.202.... * [x] crm-ext-01.torproject.org (part of #32198) done at `116.202.120.186`
* [x] crm-int-01.torproject.org (also part of #32198) done at `116.202.120.190`
* [x] forrestii.torproject.org (fpcentral, #33729) server migrated to `116.202.120.185`
* [x] nevii.torproject.org (DNS master) - #33834
* [x] rude.torproject.org (RT) - migrated to `116.202.120.187`
* [x] troodi.torproject.org (Trac, #33731) - migrated to `116.202.120.188`
* [x] vineale.torproject.org (gitweb, #33730) - done, new IP is `116.202.120.189`
The CRM machines might have already been migrated by the time we start this, see #32198.
Will require a new Ganeti node (#33083).HiroHirohttps://gitlab.torproject.org/legacy/trac/-/issues/32275Close down tor-reports list, or at least remove the postfix lines2020-06-13T16:59:27ZRoger DingledineClose down tor-reports list, or at least remove the postfix linesRight now by far the most mailman owner traffic I get has to do with people trying to maliciously subscribe other people to the tor-reports list.
For context, there are 7462 pending tor-report subscription attempts currently. And there ...Right now by far the most mailman owner traffic I get has to do with people trying to maliciously subscribe other people to the tor-reports list.
For context, there are 7462 pending tor-report subscription attempts currently. And there are dozens of new ones each day.
(These are not real people. There are jerks on the internet who try to subscribe victims to mailing lists, and one of these groups of jerks picked the tor-reports list as one of the ways they do it. It's been going on for years.)
So, I can handle the extra mailman spam -- it's a bit of a nuisance, but whatever.
But I feel bad that dozens of new people each day around the internet are getting their first introduction to the tor project in the form of "are you sure? reply to confirm" mails from our mailman for a list they know and care nothing about.
I don't want to take away the archives from the world:
https://lists.torproject.org/pipermail/tor-reports/
because they are useful for posterity.
But I want to destroy everything else about the list.anarcatanarcat