(ℹ) Join us now at the IRC channel | ䷉ Find the plain text version at this address.
Techrights-sec | Very few rC3 talks online yet. And those have had technical failures. | Dec 31 04:47 |
---|---|---|
Techrights-sec | One on climate suggests a tipping point has been crossed already | Dec 31 04:47 |
Techrights-sec | in regards to ice loss and sea level rise. | Dec 31 04:47 |
Techrights-sec | At least they have the moderators presenting the questions rather | Dec 31 04:47 |
Techrights-sec | than directly from participants. | Dec 31 04:47 |
*viera (~viera@2602:fd37:1::84) has joined #boycottnovell-social | Dec 31 05:42 | |
*viera has quit (Remote host closed the connection) | Dec 31 06:51 | |
*viera (~viera@2602:fd37:1::84) has joined #boycottnovell-social | Dec 31 06:52 | |
*viera has quit (Remote host closed the connection) | Dec 31 06:55 | |
schestowitz | Hi, on xmas/NYE 2018 I requested DNS changes to tuxmachines.org | Dec 31 08:35 |
schestowitz | That domain has been on my account for a while and again, when things are calm, we need to switch to another IP and DC. The new IP address for tuxmachines.org is 23.161.112.115 | Dec 31 08:35 |
schestowitz | The current: | Dec 31 08:35 |
schestowitz | NS5.CATALYST2.NET | Dec 31 08:35 |
schestowitz | 84.18.207.222 | Dec 31 08:35 |
schestowitz | NS6.CATALYST2.NET | Dec 31 08:35 |
schestowitz | 185.28.164.100 | Dec 31 08:35 |
schestowitz | 84.18.207.222 will be shut down soon, so please change to 23.161.112.115 | Dec 31 08:35 |
schestowitz | Can you update ASAP? We want to keep the old and new in sync while switching over | Dec 31 08:35 |
schestowitz | Last time you asked me for verification details | Dec 31 08:35 |
schestowitz | My postcode is xxxxx (might still be an older one on file, with xxxx). | Dec 31 08:35 |
schestowitz | I can phone you if that speeds things up. | Dec 31 08:35 |
schestowitz | at some stage various scripts will need to be updated to keep up with IP changes, later there will be more containers with alpine | Dec 31 09:12 |
schestowitz | at the moment I am checking logs for httpd on the new tuxmachines server to see if some have had their DNS servers updated already | Dec 31 09:13 |
schestowitz | I need help. I cannot figure out why the du size for the most important dir, /var/www , is not the same on old and new servers | Dec 31 09:13 |
schestowitz | and also the length of find, though I assume based on some tests that the changes in underlying filesystems cause the difference | Dec 31 09:14 |
Techrights-sec | diff <(ssh old "ls -R /var/www/ | sort") <(ssh new "ls -R /var/www/ | sort") | Dec 31 09:22 |
schestowitz | OK, let's start with this | Dec 31 09:22 |
schestowitz | 1. can you ssh both servers OK? The new ones? | Dec 31 09:22 |
schestowitz | 2. I want to do a sanity check (that "dirty" and "offensive" term) to make sure we leave no files 'behind'. The rest we can repair in place, I just don't want to lose files from the past 17 years | Dec 31 09:23 |
schestowitz | 3. after the sanity check we need to stress-test the thing, to make sure all sorts of things work. Later on (4-x) will be steps like alpine, adding ssl... we'll have TBs of disk space | Dec 31 09:25 |
Techrights-sec | What is the current IPv4 number of the new TR and TM? | Dec 31 09:25 |
schestowitz | 23.161.112.115 and 23.161.112.116 | Dec 31 09:25 |
schestowitz | 32 cores, no ME :-) | Dec 31 09:26 |
Techrights-sec | Different ssh_host_rsa_key? | Dec 31 09:29 |
schestowitz | use password, then change your key if needed? | Dec 31 09:30 |
Techrights-sec | Not my key, /etc/ssh/ssh_host_rsa_key ? | Dec 31 09:31 |
Techrights-sec | On the new server. | Dec 31 09:31 |
Techrights-sec | Can you run ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub and post the fingerprint? | Dec 31 09:31 |
schestowitz | good news. ls -R /var/www/ | sort | wc worked like a charm | Dec 31 09:38 |
schestowitz | and it shows identical number of files across old and new | Dec 31 09:38 |
schestowitz | I just assume the files too are the same, or I'll just check character count | Dec 31 09:39 |
schestowitz | in techrights there are some cache files building up, so crude file count might yield different results | Dec 31 09:39 |
schestowitz | As I expected, the wordpress post for today's IRC was added shorted after we rsynced the DB, so will manually copy that across to the new DC | Dec 31 09:41 |
schestowitz | I will do this now, carefully | Dec 31 09:41 |
Techrights-sec | Ok. 115 matches and can log in. Takes a bit to translate the checksum format | Dec 31 09:42 |
Techrights-sec | for 116? | Dec 31 09:42 |
schestowitz | : --- )))) /dev/vda3 1052255236 99572080 952683156 10% / | Dec 31 09:45 |
schestowitz | doing some sanity checks on the filesystem of TR now, could not find issues on TM | Dec 31 09:46 |
Techrights-sec | ok | Dec 31 09:47 |
Techrights-sec | Ok can log into the new TM too | Dec 31 09:47 |
schestowitz | 116 is new TR | Dec 31 09:47 |
schestowitz | On my ISP TM is now the new server... the DNS entry is updated here | Dec 31 09:48 |
schestowitz | That's you ->> TR: xxxx pts/6 2020-12-31 09:46 | Dec 31 09:49 |
schestowitz | irc-archives]$ ls -la | wc | Dec 31 09:49 |
schestowitz | 2990 26903 242527 | Dec 31 09:49 |
schestowitz | 8 new files per day, plus additional one annually for the tuxmachines channel | Dec 31 09:50 |
Techrights-sec | I seem to still have the old DNS entries | Dec 31 09:50 |
schestowitz | I checked the IRC bot, it gives 404 if I feed it the new test post on the "other side" (new machine) | Dec 31 09:50 |
schestowitz | I instructed rianne not to post until late in the day, otherwise people in places like chile will just get frustrated with error pages (wrong server reached) | Dec 31 09:51 |
schestowitz | Migrating TuxMachines to a Bigger Server | Dec 31 09:52 |
schestowitz | <font size="5"><b><a name="top">W</a></b></font>e are in the process of moving the TuxMachines Web site to a better server with more capacity and better hardware. There may be temporarily odd behaviour on the site (if data is accessed which is out of date). <a href="#top">█</a> | Dec 31 09:52 |
Techrights-sec | It's too late now but was the TTL reduced before the changeover | Dec 31 09:52 |
Techrights-sec | and then turned back to normal TTL? | Dec 31 09:52 |
schestowitz | I have not checked, why? | Dec 31 09:53 |
schestowitz | What I do know is that with more CPU cores TR >ought< to load up faster, for all parts of the side | Dec 31 09:53 |
schestowitz | What I do know is that with more CPU cores TR >ought< to load up faster, for all parts of the site | Dec 31 09:53 |
schestowitz | it seems like adding the 'new' IRC blog post to the new server would be easier to do after the DNS switchover, as WordPress has rather strict domain-based restrictions and I don't want to mess things up | Dec 31 09:56 |
schestowitz | With my ISP now pointing at the right place I am stress testing and stuff at TM | Dec 31 09:58 |
schestowitz | You can force feed the new IP address in places of techrights.org for various URLs and CMSs part to see if you can spot issue. Then we can update DNS and in case there are issues we can roll back. | Dec 31 09:59 |
schestowitz | LOL, my ISP's DNS is not consistent or in 'flux'... will map the requests to different IPs at different times ;) | Dec 31 10:01 |
Techrights-sec | Probably some round-robin DNS and one of them got queried while the old | Dec 31 10:01 |
Techrights-sec | IPv4 number was in effect. | Dec 31 10:01 |
schestowitz | Yes, that's what I assumed. That makes proper testing a tad premature at this level. | Dec 31 10:02 |
schestowitz | I did: | Dec 31 10:02 |
schestowitz | 1) check that static files are OK | Dec 31 10:02 |
schestowitz | 2) mine types | Dec 31 10:02 |
schestowitz | 3) mailing lists archives | Dec 31 10:02 |
schestowitz | 4) | Dec 31 10:02 |
schestowitz | wiki | Dec 31 10:02 |
schestowitz | 5) drupal: SOON | Dec 31 10:02 |
schestowitz | 6) wordpress is slightly out of date, I will copy across the IRC post later on, it's just a 1-minute copy-paste job | Dec 31 10:03 |
schestowitz | I am going to crude file-count now | Dec 31 10:04 |
schestowitz | kaniini did rsync twice over just in case, but I want to examine for confidence | Dec 31 10:04 |
Techrights-sec | Usually one should stop the VM completely for final sync | Dec 31 10:06 |
schestowitz | I think the only files changes 'in vivo' are wordpress cache files | Dec 31 10:06 |
schestowitz | ok, thanks for the help | Dec 31 10:09 |
Techrights-sec | xxxxx | Dec 31 10:09 |
schestowitz | report to self/record: | Dec 31 10:11 |
schestowitz | 1) files across /root identical (without doing checksums, just names) | Dec 31 10:12 |
schestowitz | 2) almost 170,000 files in /home and due to caching one is expected to be a tad higher than the other | Dec 31 10:13 |
schestowitz | nevertheless, at the moment number of files are the same, and char length/count the same also | Dec 31 10:14 |
schestowitz | ls -R /home | sort | wc | Dec 31 10:14 |
schestowitz | 168247 162554 5868471 | Dec 31 10:14 |
schestowitz | 3) no issues encountered with database/settings, checking video for mime type issues (we had such issues 7 years ago when we had to change configs manually in centos) | Dec 31 10:14 |
schestowitz | 4) permissions copied across correctly, just checked SLAPPed URLs are blocked (not mine, patent trolltracker's, he asked me to hide his archives posts due to the lawsuit Ray Niro filed) | Dec 31 10:18 |
Techrights-sec | yes, the backups also don;t get trolltracker | Dec 31 10:22 |
Techrights-sec | afaik | Dec 31 10:22 |
schestowitz | only about 4 pages, IIRC, the ones that cause him trouble if accessed | Dec 31 10:22 |
schestowitz | in tmux you can see the reqs/second for tuxmachines (old server) decreasing. avg over xmas and all 8.8/sec, now about half that, as traffic gets into the new machine. | Dec 31 10:23 |
Techrights-sec | yes, the rates are slowing | Dec 31 10:26 |
Techrights-sec | however, it was only that the VMs were copied as-is and no OS upgrade or change? | Dec 31 10:26 |
schestowitz | yes, one container migration will follow at a time... to reduce complexity | Dec 31 10:26 |
schestowitz | remember that one of 5 DBs (TuxMachines Drupal) is still not migrated successfully to the DB container | Dec 31 10:27 |
schestowitz | the plan is, each CMS will then have its own FS/container, so that's 5 containers at least | Dec 31 10:28 |
schestowitz | FS as in filespace, not filesystem | Dec 31 10:28 |
schestowitz | The old days: -) http://www.tuxmachines.org/gallery/v/pclos092/pclos09_2_ff2.jpg.html Slashdot 10+ years ago | Dec 31 10:30 |
-TechrightsSocial/#boycottnovell-social-www.tuxmachines.org | pclos09.2_ff2 | Dec 31 10:30 | |
Techrights-sec | container or vm? | Dec 31 10:38 |
Techrights-sec | \ | Dec 31 10:38 |
schestowitz | I am actually not sure if the machines we now access as the new server are themselves containers rather than VM, I can check on the hypervisor | Dec 31 10:38 |
schestowitz | hypervisor on 114, you have credentials for it | Dec 31 10:39 |
schestowitz | lxc-start -n techrights-old | Dec 31 10:41 |
schestowitz | as root, assuming you're in sudoers | Dec 31 10:41 |
schestowitz | BUT | Dec 31 10:41 |
schestowitz | don't run it | Dec 31 10:41 |
schestowitz | it is already running | Dec 31 10:42 |
schestowitz | sudo lxc-attach -n viera for IRC bot | Dec 31 10:42 |
Techrights-sec | ok wont't test for a bit yet | Dec 31 10:42 |
schestowitz | so no more virtual machines basically and I suppose performance can improve as a result, too | Dec 31 10:43 |
schestowitz | testing performance on the zero-traffic machine for various notorious slow pages | Dec 31 10:50 |
schestowitz | TODO: | Dec 31 10:52 |
schestowitz | add missing irc post, test | Dec 31 10:52 |
schestowitz | update backup scripts | Dec 31 10:52 |
schestowitz | update irc and raspi scripts | Dec 31 10:52 |
schestowitz | observation: site noticeably faster now and with that many cpu cores I doubt additional traffic would strain things | Dec 31 10:53 |
schestowitz | maybe the backup-related downtimes will almost go away as well | Dec 31 10:54 |
schestowitz | TM feels lightening fast now, like less than a second to load a page | Dec 31 10:56 |
Techrights-sec | Ok. I can log into hv and have access via sudo. I won't test anything beyond | Dec 31 11:16 |
Techrights-sec | that for now. | Dec 31 11:16 |
Techrights-sec | I can check the DNS here in about 45 minutes, the TTL is that long. | Dec 31 11:16 |
Techrights-sec | I guess we forgot to ramp own the TTL for the changeover. | Dec 31 11:16 |
schestowitz | is that something we can improve when switching TECHRIGHTS.ORG /COM / BN.com over? | Dec 31 11:17 |
schestowitz | (I have not directed Catalyst2 to do this yet, am still testing here and there... and I think you should add you to list of authorised persons for that, just in case I get hospitalised or worse) | Dec 31 11:18 |
Techrights-sec | Yes. I'm not sure how commonly known it is but in the hours leading up | Dec 31 11:21 |
Techrights-sec | to the switch over of DNS reduce the TTL. It increass the load of the | Dec 31 11:21 |
Techrights-sec | DNS slightly (more traffic) but then the change over lasts only as long | Dec 31 11:21 |
Techrights-sec | as the final TTL. So if the TTL is now an hour it can be set to a 5 minutes | Dec 31 11:21 |
Techrights-sec | or ramped down gradually. But then once it reaches 1 minute, switch over | Dec 31 11:21 |
Techrights-sec | then the site can only be unavailable for up to 1 minute for any given visitor | Dec 31 11:21 |
Techrights-sec | should they hit the DNS at just the wrong minute. | Dec 31 11:21 |
schestowitz | I do not know how to change those settings | Dec 31 11:21 |
Techrights-sec | It has been a Very Long Time (tm) since I did it so things will be new | Dec 31 11:22 |
Techrights-sec | all over again. | Dec 31 11:22 |
Techrights-sec | I presume it will be somewhere on the catalyst2 web interface? | Dec 31 11:22 |
schestowitz | the thing is, I asked them to do this for me, to reduce the chance of my making a mistake. They said it would apply within no more than 10 mins. Are you OK with me switching over the three techrights domain names now and maybe mention to them TTL? | Dec 31 11:23 |
schestowitz | is the net benefit just quicker passover from one address to the next and nothing else? because I don't mind taking a day off from posting today and tomorrow | Dec 31 11:26 |
Techrights-sec | The TTL needs to be done first. Then once the DNS records reflect the new TTL | Dec 31 11:26 |
Techrights-sec | it will be time to change over. Then after the change over the TTL | Dec 31 11:26 |
Techrights-sec | can be put back to the old, longish value. | Dec 31 11:26 |
Techrights-sec | Doing it in a different order has no benefit. | Dec 31 11:26 |
Techrights-sec | The benefit is fewer visitors going to the old site once the new one becomes | Dec 31 11:29 |
Techrights-sec | active. | Dec 31 11:29 |
Techrights-sec | Less disruptive for them. | Dec 31 11:29 |
Techrights-sec | The first time I helped with that we did it with a very busy site and | Dec 31 11:29 |
Techrights-sec | there was noone who noticed, among those that were watching for problems. | Dec 31 11:29 |
Techrights-sec | So it went that smoothly. | Dec 31 11:29 |
schestowitz | I will ask catalyst2 | Dec 31 11:29 |
Techrights-sec | BTW TM is calling itself tuxmachines-old and it is itself using Quad9 for DNS | Dec 31 11:35 |
Techrights-sec | lookups. | Dec 31 11:35 |
Techrights-sec | That is based in California. | Dec 31 11:35 |
schestowitz | maybe it is inherited from the HV? | Dec 31 11:35 |
schestowitz | BTW, it is called "old" because the "new" would be alpine with containers, the proper way | Dec 31 11:35 |
schestowitz | Hithank you for the quick response, that has worked really wellWe now have the bigger site to switch over, it's accessed over techrights.org techrights.com and boycottnovell.com ... and I'm told that changing TTL prior to changeover the time taken to move over to the news DNS can be reduced but I don't know how/if this can be done. The new IP address for this site (all domains are the same) is 23.161.112.116 | Dec 31 11:38 |
schestowitz | Ok so techrights.org techrights.com and boycottnovell.com should be switched over to 23.161.112.116 also?yes, this is a different address from the one for TuxMachinesOk Ill add that to the ticket and get it processedthank you so much! | Dec 31 11:44 |
schestowitz | No prob, will let you know when complete | Dec 31 11:45 |
schestowitz | yes, this is a different address from the one for TuxMachines | Dec 31 11:46 |
schestowitz | just blocked news-roundup category in TR due to ddos-ish, load avg 70+. We'll need to move monitoring over to the new server soon and redo the session of tmux as suits us both (we don't always use same screen size and some stuff we no longer need to do/monitor | Dec 31 11:50 |
schestowitz | I am guessing to stress-test TM now using social control media links | Dec 31 11:53 |
schestowitz | new traffic starting to arrive at new TR server, TM seems to now take most traffic (maybe 80%) from the new server | Dec 31 12:01 |
Techrights-sec | Excellent | Dec 31 12:02 |
schestowitz | It's a lot easier to test AFTER the changeover, rianne had a go at TM and could not find any issues, but sometimes the wrong server is reached (still, round robin scheduled for DNS allocation I assume) | Dec 31 12:03 |
schestowitz | It's a lot easier to test AFTER the changeover, rianne had a go at TM and could not find any issues, but sometimes the wrong server is reached (still, round robin scheduler for DNS allocation I assume) | Dec 31 12:03 |
Techrights-sec | Yes, chech the TTL to see how long she must wait to get the new IP from DNS | Dec 31 12:04 |
schestowitz | 15 23.161.112.115 (23.161.112.115) 172.377 ms 172.352 ms 174.390 ms | Dec 31 12:05 |
schestowitz | from traceroute here | Dec 31 12:05 |
Techrights-sec | Traceroute does the packet ttl for TCP or UDP not the DNS record | Dec 31 12:06 |
Techrights-sec | see dig or similar | Dec 31 12:06 |
Techrights-sec | ] | Dec 31 12:06 |
schestowitz | ;; Query time: 59 msec | Dec 31 12:07 |
schestowitz | Query time: 931 msec for techrights.org | Dec 31 12:08 |
schestowitz | I have just restored access to news-roundup and will reset apachetop on tm and tr (old server) to better assess how much traffic they receive in recent mins/hours | Dec 31 12:12 |
Techrights-sec | techrights.org. 3600 IN A 23.161.112.116 | Dec 31 12:12 |
Techrights-sec | ;; Query time: 287 msec | Dec 31 12:12 |
Techrights-sec | ;; SERVER: 9.9.9.9#53(9.9.9.9) | Dec 31 12:12 |
Techrights-sec | ;; WHEN: Thu Dec 31 12:06:47 2020 | Dec 31 12:12 |
Techrights-sec | ;; MSG SIZE rcvd: 48 | Dec 31 12:12 |
Techrights-sec | 3600 | Dec 31 12:12 |
Techrights-sec | seconds | Dec 31 12:12 |
Techrights-sec | wit hthe new address | Dec 31 12:12 |
schestowitz | OK, changed and shuffled a bit in old tmux, I'll be relaxed when each site is at less than 1 req/sec on the old one. I'll configure tmux on "new" | Dec 31 12:15 |
schestowitz | I don't think we need the pane for htop now that we have nmon with graphs, correct? waste of space... | Dec 31 12:20 |
Techrights-sec | ok no htop | Dec 31 12:28 |
schestowitz | ok, go to new tr (.116) and run monitor-techrights, change as suits you as well | Dec 31 12:29 |
schestowitz | I now have two tmux sessions, one for new another for old | Dec 31 12:29 |
schestowitz | dig techrights.org | Dec 31 12:31 |
schestowitz | 199.19.78.19 | Dec 31 12:31 |
schestowitz | ;; Query time: 252 msec | Dec 31 12:31 |
schestowitz | dig techrights.com | Dec 31 12:32 |
schestowitz | 23.161.112.116 | Dec 31 12:32 |
schestowitz | ;; Query time: 65 msec | Dec 31 12:32 |
schestowitz | dig boycottnovell.com | Dec 31 12:32 |
schestowitz | 199.19.78.19 | Dec 31 12:32 |
schestowitz | ;; Query time: 895 msec | Dec 31 12:32 |
Techrights-sec | ok my dns now directs to the new machine | Dec 31 12:35 |
schestowitz | Mine still flaps a bit as I run dig periodically, but it's getting there and for tuxmachines it's sending most traffic to new | Dec 31 12:37 |
schestowitz | "The A record has been updated. Please allow up to 24hrs for propagation to occur" | Dec 31 13:02 |
schestowitz | "techrights.org techrights.com and boycottnovell.com are now on 23.161.112.116" | Dec 31 13:02 |
schestowitz | Let's take time to think of a multi-party strategy with the Intel story, maybe series title will be InteLeaks | Dec 31 13:22 |
schestowitz | installing sshpass on the pi here, will set things for pi/root to be able to upload daily stuff without human intervention | Dec 31 13:38 |
schestowitz | I want to pass time doing much needed work while not posting anything as the sites flap | Dec 31 13:38 |
schestowitz | I am cronning ipfs updates at the moment and preventing anyone else from having keyless access to the server | Dec 31 14:14 |
schestowitz | with IP changes I think now is a good time to revise the crontabs on the servers as well | Dec 31 14:16 |
schestowitz | pi cron job set to update the ipfs txt and html index every hour between 1am and 5am each day | Dec 31 14:19 |
schestowitz | next, automating the irc log generation, with i/o going to file so I can check the process for sanity when I wake up | Dec 31 14:29 |
schestowitz | OK, /home/links will be updated each day 3am U/GMT | Dec 31 14:38 |
schestowitz | cp output.txt /home/links/ipfs/ will be run as well, that's the output of the run, in case there are errors to be found or something bad in the output file for WordPress, so there's a copy | Dec 31 14:42 |
Techrights-sec | ack | Dec 31 14:42 |
Techrights-sec | Wouldn't an hour or two earlier be better? | Dec 31 14:42 |
schestowitz | it would, but... longstanding issue is, WordPress server clock/CMS clocks not the same. the server is US east coast time, so IPFS stuff runs until 5am our time (UK) for a given day | Dec 31 14:43 |
schestowitz | usually if I write additional things between bulletin and 5am I can just regenerate the bulletin afterwards | Dec 31 14:44 |
schestowitz | tail -5 /home/links/ipfs/output.txt && uptime | Dec 31 14:46 |
schestowitz | Bandwidth | Dec 31 14:46 |
schestowitz | TotalIn: 5.9 GB | Dec 31 14:46 |
schestowitz | TotalOut: 2.3 GB | Dec 31 14:46 |
schestowitz | RateIn: 16 kB/s | Dec 31 14:46 |
schestowitz | RateOut: 5.1 kB/s | Dec 31 14:46 |
schestowitz | 14:46:23 up 2 days, 22:12, 3 users, load average: 0.90, 0.99, 1.02 | Dec 31 14:46 |
schestowitz | tail -18 /home/links/ipfs/output.txt | head -n 1 | Dec 31 14:47 |
schestowitz | <FONT size=1 color=white>This page was last modified on Thu 31 Dec 14:36:55 GMT 2020 | Dec 31 14:47 |
schestowitz | "pi" user will reupload this pair of files until 5am, then the next day again | Dec 31 14:48 |
schestowitz | 40 02 * * * /home/roy/yesterday-irc.log.sh > /home/roy/output.txt | Dec 31 15:02 |
schestowitz | 05 03 * * * kate /home/roy/output.txt | Dec 31 15:02 |
schestowitz | the second one, I think, will forcibly remind me to check the sanity of it and then maybe see the ipfs index to ensure all went well at the pi as well, without having to actually access it | Dec 31 15:04 |
Techrights-sec | The second one will need to set the environment variable. | Dec 31 15:21 |
Techrights-sec | for the display, for the logged in user: | Dec 31 15:21 |
Techrights-sec | 05 03 * * * DISPLAY=:0.0 /home/roy/output.txt | Dec 31 15:21 |
Techrights-sec | Set it to a few minutes from now and test. | Dec 31 15:21 |
Techrights-sec | 05 03 * * * DISPLAY=:0.0 kate /home/roy/output.txt | Dec 31 15:21 |
Techrights-sec | I forgot the editor in the first one | Dec 31 15:21 |
schestowitz | will fix | Dec 31 15:21 |
schestowitz | it looks like you already readded the irc blog post to the new server? It's confusing me that it's always showing up | Dec 31 15:22 |
schestowitz | 23.161.112.115 tuxmachines.org | Dec 31 15:22 |
schestowitz | 23.161.112.115 www.tuxmachines.org | Dec 31 15:22 |
schestowitz | 23.161.112.116 techrights.org | Dec 31 15:22 |
schestowitz | 05 03 * * * DISPLAY=:0.0 falkon http://techrights.org/ipfs | Dec 31 15:36 |
-TechrightsSocial/#boycottnovell-social-techrights.org | Techrights Full IPFS Index | Dec 31 15:36 | |
Techrights-sec | I haven't changed any cron tabs yet. | Dec 31 15:38 |
Techrights-sec | I'll wait till th edust settles a little before poking artound. | Dec 31 15:38 |
schestowitz | makes sense; I did after some hours realise that I was looking at the new site in fact and that IRC blog post had already been reposted in it, which is good (I just didn't expect that) | Dec 31 15:39 |
schestowitz | I have just checked old TM, over the past few hours it served as much as the new, 23k hits each. I'm checking to ensure nobody submits story/comment to old as that would be lost when we wipe clean the old server | Dec 31 15:45 |
schestowitz | remember we can keep the existing centos container for utilities that are not quite web-facing | Dec 31 15:50 |
Techrights-sec | The existing old one could be updated then. | Dec 31 15:59 |
schestowitz | yes, after critical services like httpd and all are moved entirely out of that ageing container | Dec 31 15:59 |
schestowitz | I updates the "hosts" file on rianne's laptop and mine so now we resume posting in tuxmachines (assuming people's DNS servers are mostly updated) and will resume techrights later, at least Daily Links | Dec 31 16:00 |
schestowitz | *updated | Dec 31 16:00 |
Techrights-sec | Probably not. BTW is Scotland in a position to reject Brexit? | Dec 31 16:19 |
schestowitz | It already rejects it, even publicly, based on a statement I saw mentioned in counterpunch (Binoy) 2 days ago. IndyRef might follow. | Dec 31 16:20 |
schestowitz | Heck, if they do this, and as they speak English, they could braindrain Wales and England | Dec 31 16:21 |
schestowitz | http://schestowitz.com/royrianne/gallery/index.php/Edinburgh | Dec 31 16:22 |
-TechrightsSocial/#boycottnovell-social-schestowitz.com | Edinburgh | Dec 31 16:22 | |
Techrights-sec | It would pull in a lot of escapees if they are able to rejoin the EU quickly or | Dec 31 16:22 |
Techrights-sec | even flat out reject Brexit. | Dec 31 16:22 |
Techrights-sec | I guess visits to various Royal gardens are out for the foreseeable future. | Dec 31 16:25 |
Techrights-sec | Same for garden shows. | Dec 31 16:25 |
schestowitz | I am doing some checks, found out we use https://downloads.mariadb.org/mariadb/5.5.56/ | Dec 31 16:39 |
-TechrightsSocial/#boycottnovell-social-downloads.mariadb.org | MariaDB 5.5.56 Stable - MariaDB | Dec 31 16:39 | |
Techrights-sec | 5.x is really far behind. It might not be a fully automated upgrade to get | Dec 31 16:44 |
Techrights-sec | to 10.x or 11.x | Dec 31 16:44 |
schestowitz | should brian kerbs be in automated links? | Dec 31 16:45 |
schestowitz | I want to support folks who do their own thing, esp. if they know what they cover | Dec 31 16:45 |
Techrights-sec | Krebs? Ok. I can see if there is a feed to add. | Dec 31 16:46 |
Techrights-sec | https://krebsonsecurity.com/feed/ | Dec 31 16:46 |
schestowitz | in 2021 I think we ought to speed up our retreat from the "burning platforms" of PR as "media" | Dec 31 16:47 |
schestowitz | I am trying not to link to either TM or TR today, knowing many will get 404s because of outdated DNS upsteam. People can forgive for not posting on last/first day of a year... | Dec 31 16:48 |
schestowitz | https://www.bbc.co.uk/news/election-us-2020-55494005 | Dec 31 16:49 |
-TechrightsSocial/#boycottnovell-social-www.bbc.co.uk | Republican senator to dispute certification of Biden victory - BBC News | Dec 31 16:49 | |
Techrights-sec | git needs tweaking, but otherwise the updated files are in place on TR | Dec 31 16:51 |
Techrights-sec | Krebs' feed will be checked starting tomorrow. He goes for quality not | Dec 31 16:51 |
Techrights-sec | quantity so there may be some delay before any posts of his show up, | Dec 31 16:51 |
Techrights-sec | aside from the site anniversary announcement. | Dec 31 16:51 |
Techrights-sec | Yeah, there will be little of substance for the next 96 hours or so. | Dec 31 16:51 |
Techrights-sec | I will check a few sites anyway. | Dec 31 16:51 |
schestowitz | with the sites on the other side of the DC space, at least my biggest xmas worry is mostly behind now, I can relax a bit. No signs of anything broken or missing data yet. | Dec 31 16:52 |
schestowitz | new tmux session has wasted space as nmon does not scale fully horizontally. Anything else we need on screen? | Dec 31 17:01 |
schestowitz | how's this? shows cpu strain only when above 70% | Dec 31 17:02 |
Techrights-sec | Not that I can think of. You are more familiar with site monitoring at | Dec 31 17:03 |
Techrights-sec | that level. | Dec 31 17:03 |
Techrights-sec | FWIW I have maximized the window on my side, so any space there can be used, | Dec 31 17:03 |
Techrights-sec | but not any additional expansion. | Dec 31 17:03 |
Techrights-sec | Ok. Low system loads are probably not so important. | Dec 31 17:03 |
Techrights-sec | Too bad there is not a more recent version of tmux there, | Dec 31 17:03 |
Techrights-sec | otherwise we could label the panes. | Dec 31 17:03 |
schestowitz | the monitoring can be put on any machine, inc. this pi of even this ytalk session | Dec 31 17:03 |
*TechrightsSocial has quit (Remote host closed the connection) | Dec 31 18:33 | |
*TechrightsSocial (~b0t@23.161.112.116) has joined #boycottnovell-social | Dec 31 18:34 | |
TechrightsSocial | Hello World! I'm TechrightsSocial running phIRCe v0.77 | Dec 31 18:34 |
*liberty_box has quit (Ping timeout: 256 seconds) | Dec 31 19:01 | |
*rianne_ has quit (Ping timeout: 256 seconds) | Dec 31 19:01 | |
*rianne_ (~rianne@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social | Dec 31 19:46 | |
*liberty_box (~liberty@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social | Dec 31 19:47 | |
*rianne_ has quit (Ping timeout: 240 seconds) | Dec 31 19:52 | |
*liberty_box has quit (Ping timeout: 246 seconds) | Dec 31 19:53 | |
*rianne_ (~rianne@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social | Dec 31 19:55 | |
*liberty_box (~liberty@81.154.173.106) has joined #boycottnovell-social | Dec 31 19:55 | |
*liberty_box has quit (Ping timeout: 260 seconds) | Dec 31 20:12 | |
*rianne_ has quit (Ping timeout: 256 seconds) | Dec 31 20:12 | |
*liberty_box (~liberty@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social | Dec 31 20:27 | |
*rianne_ (~rianne@host81-154-173-106.range81-154.btcentralplus.com) has joined #boycottnovell-social | Dec 31 20:27 | |
*rianne_ has quit (Ping timeout: 240 seconds) | Dec 31 23:28 | |
*liberty_box has quit (Ping timeout: 240 seconds) | Dec 31 23:28 |
Generated by irclog2html.py
2.6 | ䷉ find the plain text version at this address.