Fwd: Welcome to the "Psychology-club" mailing list
I was just subscribed to this one by somebody! ---------- Forwarded message --------- From: <psychology-club-request@psych.colorado.edu> Date: Tue, May 17, 2022 at 1:18 PM Subject: Welcome to the "Psychology-club" mailing list To: <gmkarl@gmail.com> Welcome to the Psychology-club@psych.Colorado.EDU mailing list! To post to this list, send your message to: psychology-club@psych.Colorado.EDU General information about the mailing list is at: http://psych.colorado.edu/mailman/listinfo/psychology-club If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://psych.colorado.edu/mailman/options/psychology-club/gmkarl%40gmail.com You can also make such adjustments via email by sending a message to: Psychology-club-request@psych.Colorado.EDU with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe without confirmation. It is: awutmoog Normally, Mailman will remind you of your psych.Colorado.EDU mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you. <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_source=signature> I'm using Inbox When Ready <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_source=signature> to protect my focus.
i have made progress on bisecting the issue i posted. the host is behind cloudflare :/ . that seems like a big possible related factor. the error does not happen when i run curl simultaneously to the failing request (prior, terminates after start, or after, terminates before end). so big suspects include triggering on headers, personal hallucination, system compromise. as it try to diagnose it my muscles contract and begin kind of vibrating, in ways that pull me away from what i'm doing. my body constantly tries to make errors that harm my work: i already ctrl-c'd one long-running process when i was trying to just rerun a test without ctrl-c'ing anything. i'd really like to video or eeg these weird personal misbehaviors. log storage first, though, or i'll just delete the log!
i'm not sure where to put this to find it again, and am putting it here. this command is working for me: { echo -e "GET /tx_anchor HTTP/1.1\r\nHost: arweave.net\r\n\r\n"; sleep 5; } | openssl s_client -quiet -connect arweave.net:443 i did not find python code that would make that request successfully, yet. i am instead trying other gateways, and making sure i have some work started to run a local gateway in a normative manner.
note: thinking of asking policeman if i am experiencing network misbehaviors from american infrastructure how do i know when it is a dangerous thing that i need to report to authorities and if it is authorised, how do i relate around it to resolve issues i run into?
i'm trying to run a local gateway and running into this weirdness: user@archival:/media/extradisk/src/vartex$ sudo systemctl start docker user@archival:/media/extradisk/src/vartex$ sudo systemctl status docker|cat ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-05-18 03:12:32 EDT; 5s ago TriggeredBy: ● docker.socket Docs: https://docs.docker.com Main PID: 1569105 (dockerd) Tasks: 24 Memory: 42.4M CGroup: /system.slice/docker.service └─1569105 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock May 18 03:12:31 archival dockerd[1569105]: time="2022-05-18T03:12:31.308680229-04:00" level=warning msg="Your kernel does not support CPU realtime scheduler" May 18 03:12:31 archival dockerd[1569105]: time="2022-05-18T03:12:31.308687898-04:00" level=warning msg="Your kernel does not support cgroup blkio weight" May 18 03:12:31 archival dockerd[1569105]: time="2022-05-18T03:12:31.308697447-04:00" level=warning msg="Your kernel does not support cgroup blkio weight_device" May 18 03:12:31 archival dockerd[1569105]: time="2022-05-18T03:12:31.308844551-04:00" level=info msg="Loading containers: start." May 18 03:12:31 archival dockerd[1569105]: time="2022-05-18T03:12:31.473029737-04:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" May 18 03:12:31 archival dockerd[1569105]: time="2022-05-18T03:12:31.549835210-04:00" level=info msg="Loading containers: done." May 18 03:12:32 archival dockerd[1569105]: time="2022-05-18T03:12:32.562570544-04:00" level=info msg="Docker daemon" commit=f756502 graphdriver(s)=overlay2 version=20.10.16 May 18 03:12:32 archival dockerd[1569105]: time="2022-05-18T03:12:32.562644977-04:00" level=info msg="Daemon has completed initialization" May 18 03:12:32 archival systemd[1]: Started Docker Application Container Engine. May 18 03:12:32 archival dockerd[1569105]: time="2022-05-18T03:12:32.718125787-04:00" level=info msg="API listen on /run/docker.sock" user@archival:/media/extradisk/src/vartex$ ls /run/docker.sock ls: cannot access '/run/docker.sock': No such file or directory
0327 ET this last pasted issue was possibly a quirk of systemd. stopping docker.service, then stopping docker.socket, then restarting docker.socket regenerated the file. i was switching from snap to apt and reinstalling things, and likely the .socket file got deleted in an uninstallation while the .socket service was running. 0338 omigod i am running a local arweave gateway and things are working and i am syncing a local node !!! i followed https://arweave.news/improve-decentralization-permaweb/ .
0343 this is not actually working. my vartex gateway is not showing transactions. this makes some sense, is i think it would need to process them all to do that. 0421 i found a type comparison error in vartex, i'm rather confused
i'm running it outside the docker image, with the latest version of cassandra, which only runs on ubuntu if you set the default jvm to 11 or 8. it is busy syncing. the syncing could be why it wasn't working earlier. 0505 0523 i submitted a fix for the type comparison error. i suspect there are more. there's a chance it resyncs from genesis every boot. it looks like it takes about 2 weeks to sync, if it continues at the rate it starts at. maybe a cool side project.
0535 i've found that one can specify DEVELOPMENT_SYNC_LENGTH on the environment to set a starting sync height, possibly radically speeding syncing for tasks that don't need to access old data. 0542 i've found that vartex is hardcoded to only requests 2 blocks at once, but coded in a generic way so it's easy to up that number. top 1000 blocks sync time drops from 1-2 hours to 15-20 minutes, with pulling many blocks at once. src/database/sync.ts around line 355
0828 it turns out this code doesn't support the transaction types i'm using. i found them supported on a branch. this branch looks more mature in some ways: it has the parallelisation parameterised already, for example. 0904 i've been trying to make the gateway work, but in the meantime i found that configuring the upload to use my local node as a gateway is working. the local node can't confirm the bundled uploads that can be sent for free the way the uploader does, but for some reason it looks like it's no longer checking them, and just resending them or something. seems that's working for now. it looks like i also have a loop, retrying when the timeout error is hit.
in two different tmux windows, i got two different docker updates first window: user@archival:~/src/termux-packages$ scripts/update-docker.sh Using default tag: latest latest: Pulling from termux/package-builder 940122ec7d0c: Pull complete 72eac69c115e: Pull complete 0ce93801a2ac: Pull complete f4d7ee9010f1: Pull complete 465b346ea08f: Downloading [==================================================>] 2.867GB/2.867GB 3fc97082f970: Download complete local error: tls: bad record MAC second window: user@archival:~/src/termux-packages$ scripts/update-docker.sh Using default tag: latest latest: Pulling from termux/package-builder 940122ec7d0c: Pull complete 72eac69c115e: Pull complete 0ce93801a2ac: Pull complete f4d7ee9010f1: Pull complete 465b346ea08f: Downloading [> ] 11.32MB/3.487GB 3fc97082f970: Download complete The downloads of 465b346ea08f take a lot of tries, restarting themselves repeatedly after just a little bit of transfer. The weirdness is that the two downloads have different total sizes, and the same hash. I got an SSL version error in another window for an arweave server, which resolved with retrying.
okay, my understanding is that this clearly indicates that something is tampering with the network of this system: user@archival:~/src/termux-packages$ docker pull termux/package-builder:latest latest: Pulling from termux/package-builder 940122ec7d0c: Pull complete 72eac69c115e: Pull complete 0ce93801a2ac: Pull complete f4d7ee9010f1: Pull complete 465b346ea08f: Downloading [==================================================>] 3.634GB/3.634GB 3fc97082f970: Download complete local error: tls: bad record MAC user@archival:~/src/termux-packages$ man curl user@archival:~/src/termux-packages$ vim get-blob.sh user@archival:~/src/termux-packages$ docker pull termux/package-builder:latest latest: Pulling from termux/package-builder 940122ec7d0c: Pull complete 72eac69c115e: Pull complete 0ce93801a2ac: Pull complete f4d7ee9010f1: Pull complete 465b346ea08f: Downloading [==================================================>] 2.08GB/2.08GB 3fc97082f970: Download complete local error: tls: bad record MAC i ran a curl that showed the openssl error too, but seem to have misplaced this. i'm not sure how to engage it. i guess it makes sense to try other network avenues. it could be nice to see the HTTP header mutating with manual requests
* Connected to production.cloudflare.docker.com (104.18.122.25) port 443 (#1) [37/275] * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [512 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [104 bytes data] * TLSv1.2 (IN), TLS handshake, Certificate (11): { [2371 bytes data] * TLSv1.2 (IN), TLS handshake, Server key exchange (12): { [116 bytes data] * TLSv1.2 (IN), TLS handshake, Server finished (14): { [4 bytes data] * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): } [37 bytes data] * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.2 (OUT), TLS handshake, Finished (20): } [16 bytes data] * TLSv1.2 (IN), TLS handshake, Finished (20): { [16 bytes data] * SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305 * ALPN, server accepted to use h2 * Server certificate: * subject: C=US; ST=California; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflaressl.com * start date: Jul 12 00:00:00 2021 GMT * expire date: Jul 11 23:59:59 2022 GMT * subjectAltName: host "production.cloudflare.docker.com" matched cert's "production.cloudflare.docker.com" * issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 } [5 bytes data] * Using Stream ID: 1 (easy handle 0x55a37b928210) } [5 bytes data]
GET /registry-v2/docker/registry/v2/blobs/sha256/46/465b346ea08f5ee600f43e9e3aee2a93a27086b9ff00139d6fbf4d8870a41a56/data?verify=1652888345-%2Fg%2B22grbGqV92cuG4vBaILM2c%2Fo%3D HTTP/2 Host: production.cloudflare.docker.com user-agent: curl/7.68.0 accept: */*
{ [5 bytes data] * Connection state changed (MAX_CONCURRENT_STREAMS == 256)! } [5 bytes data] < HTTP/2 200 < date: Wed, 18 May 2022 14:49:05 GMT < content-type: application/octet-stream < content-length: 3969175610 < cf-ray: 70d565c08f611861-EWR < accept-ranges: bytes < age: 2884 < cache-control: public, max-age=14400 < etag: "50597ad2b4876c3d19173cec7cf1f2bf-119" < expires: Wed, 18 May 2022 18:49:05 GMT < last-modified: Sun, 15 May 2022 02:51:31 GMT < vary: Accept-Encoding < cf-cache-status: HIT < expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" < x-amz-id-2: 4ikeTX2/JZOe/DYSwx1hOIapU9XP3BrkzNbm7kmgLqYNw5USAfuGByQD527WMPoofBLOyKmiYhA= < x-amz-request-id: RJMVYFH1D0H7M4B2 < x-amz-version-id: _kNw65_P0_lxxxmo75UV9vNyk_3ivFEd < server: cloudflare < { [915 bytes data] 2 3785M 2 86.8M 0 0 16.0M 0 0:03:55 0:00:05 0:03:50 17.3M* TLSv1.2 (OUT), TLS alert, bad record mac (532): } [2 bytes data] * OpenSSL SSL_read: error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac, errno 0 * Failed receiving HTTP2 data * OpenSSL SSL_write: SSL_ERROR_SYSCALL, errno 0 * Failed sending HTTP2 data 2 3785M 2 109M 0 0 16.4M 0 0:03:49 0:00:06 0:03:43 18.7M * Connection #1 to host production.cloudflare.docker.com left intact curl: (56) OpenSSL SSL_read: error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac, errno 0
well i dunno what to do about this. i managed to manually download a layer that matched the complete sha256 checksum. its size is 3969175610 bytes. i'm not sure how to inject it into docker. this isn't the task i'm trying to pursue right now anyway, it was just a small thing.
the preceding was on a remote server this building has now lost internet. the router isn't quite booting up. so I am doing other things for a bit.
participants (2)
-
Karl Semich -
Undiscussed Horrific Abuse, One Victim of Many