-- Leo's gemini proxy
-- Connecting to gemini.techrights.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini;lang=en-GB
00:17 schestowitz; pi@raspberrypi:~/old/pi $ ls -la /var/log/syslog*
00:17 schestowitz; -rw-r----- 1 root adm 10883849 Jan 25 00:16 /var/log/syslog
00:17 schestowitz; -rw-r----- 1 root adm 13765320 Jan 23 00:00 /var/log/syslog.1
00:17 schestowitz; if you know how to make the rotation happen every 24 hours, such that .1 is always a 24-hour chunk, the stats in our gemini capsule will be corrected. I've not good at logrotate
00:41 *u-amarsh04 has quit (Quit: Konversation terminated!)
00:41 *u-amarsh04 has quit (Quit: Konversation terminated!)
01:16 schestowitz-TR2; rianne has been checking raspi 400
01:16 schestowitz-TR2; it is almost 100 pounds now
01:16 schestowitz-TR2; the idea is,
01:16 schestowitz-TR2; ipsec on it
01:16 schestowitz-TR2; she can experiment on it
01:16 schestowitz-TR2; it's vpn fallbak
01:16 schestowitz-TR2; to what extent it can nbe used to back up for the main pi I do not know
01:16 schestowitz-TR2; but I assume they are compatible as it is the same board inside
01:18 Techrights-sec; same CPU IIRC in the recent models but ever so slightly different in the old
01:18 Techrights-sec; models/ The 400 is like a slightly heavy keyboard. It's mostly quite nice
01:18 Techrights-sec; as far as inexpensive keyboards go. The main downside I see is that the
01:18 Techrights-sec; attached keyboard itself uses one of the USB ports internally, leaving only
01:18 Techrights-sec; three on the outside.
01:18 schestowitz-TR2; regarding logrotate, maybe it is set to weekly rotation?
01:18 schestowitz-TR2; maybe I am one command away from 'fixing' it?
01:18 schestowitz-TR2; regarding logrotate, maybe it is set to weekly rotation?
01:18 schestowitz-TR2; maybe I am one command away from 'fixing' it?
01:19 Techrights-sec; Yes, taking a look at how to modify the the systemd.timer. Take a look in ~
01:19 Techrights-sec; for logrotate for /etc/logrotat.d/rsyslog and logrotate.timer for
01:19 Techrights-sec; /lib/systemd/system/logrotate.timer replacements. Not sure yet how to
01:19 Techrights-sec; reload the "timers"
01:21 Techrights-sec; I guess it is systemctl daemon-reload ; systemctl restart logrotate.timer
01:24 schestowitz; WantedBy=timers.target
01:24 schestowitz; pi@raspberrypi:/home/gemini $ diff logrotate.timer /lib/systemd/system/logrotate.timer
01:24 schestowitz; 7c7
01:24 schestowitz; < AccuracySecs=1us
01:24 schestowitz; ---
01:24 schestowitz; > AccuracySec=1h
01:24 schestowitz; pi@raspberrypi:/home/gemini $ sudo cp logrotate.timer /lib/systemd/system/logrotate.timer
01:26 schestowitz; pi@raspberrypi:/home/gemini $ diff logrotate.timer /lib/systemd/system/logrotate.timer
01:26 schestowitz; pi@raspberrypi:/home/gemini $
01:31 schestowitz; there is no rsyslog where you specified it, I find some find| grep, no luck
01:31 Techrights-sec; YEs, it's already set for daily. Hopefully systemd means that to be at 00:00
01:31 Techrights-sec; exactly, but who knows.
01:31 Techrights-sec; """
01:31 Techrights-sec; Warning: The unit file, source configuration file or drop-ins of logrotate.timer
01:31 Techrights-sec; changed on disk. Run 'systemctl daemon-reload' to reload units.
01:31 Techrights-sec; """
01:31 Techrights-sec; ~gemini/rsyslog
01:32 schestowitz-TR2; I mean for target file
01:37 Techrights-sec; /etc/logrotate.d/rsyslog
01:37 Techrights-sec; changed the order within ~gemini/rsyslog
01:38 Techrights-sec; remember to later do 'systemctl daemon-reload' and 'systemctl restart logrotat.ti
01:38 Techrights-sec; mer'
01:41 schestowitz-TR2; done
01:41 Techrights-sec; also double check to ensure that there is no logrotate entry in root's cron
01:41 Techrights-sec; thanks
01:42 schestowitz-TR2; i suppose easiest thing now is, wait till midnight
01:42 schestowitz-TR2; as this had no immediate effect on existing files, of which there are two only
01:43 Techrights-sec; ack
01:44 schestowitz-TR2; as you shall see based on irc logs, which I redact as best I can for site-elated
01:44 schestowitz-TR2; comms, my goal is to make 3 videos a day
01:44 schestowitz-TR2; ltely we have had lots of technical barriers so a lot of time was lost
01:44 schestowitz-TR2; i will try to make up this week
01:44 schestowitz-TR2; I alraeady havbe 6 or 8 days off work next month
01:44 Techrights-sec; ack
01:44 Techrights-sec; the modifications to the above files need to go in the backuos some how, too
01:45 schestowitz-TR2; can you pls add these to git?
01:46 Techrights-sec; ok no problem
01:46 schestowitz; comments of interest:
01:46 schestowitz; 10x in http://patentblog.kluweriplaw.com/2022/01/19/upc-provisional-application-period-enters-into-force/#comments
01:47 -TechrightsBN/#boycottnovell-patentblog.kluweriplaw.com | UPC - Provisional Application Period enters into force - Kluwer Patent Blog
01:47 schestowitz; still open for commenting: http://patentblog.kluweriplaw.com/2022/01/21/interviews-for-future-judges-unified-patent-court-will-take-place-this-spring/#comments
01:47 -TechrightsBN/#boycottnovell-patentblog.kluweriplaw.com | Interviews for future judges Unified Patent Court will take place this spring - Kluwer Patent Blog
01:48 schestowitz; email caught up with today (after one week of hectic schedule), pasted in irc some searx-related chat. we do huge damage to ddg^h^hrosoft
01:49 schestowitz; vulpes proxy still down???? replaced for now with contingency, which required JS and nodejs (at back end) https://proxy.vulpes.one/
01:49 -TechrightsBN/#boycottnovell- ( status 502 @ https://proxy.vulpes.one/ )
01:50 schestowitz; https://lists.orbitalfox.eu/archives/gemini/2021/ still dead, I wonder if it'll ever come back at all (been ~2 months)
01:50 -TechrightsBN/#boycottnovell- ( status 404 @ https://lists.orbitalfox.eu/archives/gemini/2021/ )
01:51 Techrights-sec; added to git now
01:51 Techrights-sec; they need to clean up their act; there is a need for a privacy-oriented
01:51 Techrights-sec; search service but they 1) might not be capable 2) might not be allowed
01:51 Techrights-sec; See also recent changes in the EU with the DSA
01:51 Techrights-sec; too bad
01:52 schestowitz; tested gemini again, I think it should be 100% same as before the crash starting next day/midnight, traffic in past 2 days was around 45k requests (just enough to slow down our upstream connection a little bit)
01:53 Techrights-sec; excellent
01:53 Techrights-sec; BTW perhaps the unit file directory in Git should be renamed to something
01:53 Techrights-sec; more generic?
01:54 schestowitz-TR2; based on drafts I saw, andy will assign gemini projects to students
01:54 Techrights-sec; Awesome! It used to be that writing a HTTP server was the "Hello, World!"
01:54 Techrights-sec; of networking, but Gemini is even better. It's a simpler protocol and
01:54 Techrights-sec; gets them exposed to TLS right away.
01:55 schestowitz-TR2; i am reluctant to change too much at skeletal level of git as some scripts have
01:55 schestowitz-TR2; hard-coded in them the names of directories to display, so there will be some
01:56 schestowitz-TR2; extra work and testing needed for small changes
01:56 Techrights-sec;
01:56 Techrights-sec; :( hardcoding is not safe
01:56 schestowitz-TR2; yes, you can see the code in question in git by grep -R some-git-dir and then improve that a bit, deploy
02:01 Techrights-sec; ok
02:01 Techrights-sec; $ grep -l -R 'Unit-files' ./*
02:01 Techrights-sec; ./Gemini/gemini-git-update.sh.orig
02:01 Techrights-sec; just the one legacy script. It is not used I think?
02:02 schestowitz-TR2; I have just surfed the whole git section to check it's all "sane".
02:02 schestowitz-TR2; it is working correctly
02:02 schestowitz-TR2; there is a script that looks for "autorised" (for public viewing) dirs
02:02 schestowitz-TR2; and then presents them with a friendlier name
02:02 schestowitz-TR2; and their full contents
02:02 schestowitz-TR2; from 'cat' iirc
02:03 schestowitz-TR2; the part which rewrites the names if the dirs
02:03 schestowitz-TR2; that might be a little barrier to full automation for all dirs
02:03 schestowitz-TR2; iirc, last week we added another new dir
02:03 schestowitz-TR2; I cannot recall what it was calledp
02:03 schestowitz-TR2; you added one
02:04 schestowitz-TR2; my sister's bday today, 2 years my senior
02:05 schestowitz-TR2; back to GE in onbe month
02:05 schestowitz-TR2; it's GE that I mentioned yesterday in relation to still using Vista and very anci
02:05 schestowitz-TR2; ent Debian
02:19 Techrights-sec; It's bizarre that they started with Vista in the first place, there were
02:19 Techrights-sec; no advantages to it and the migration costs were similar to upgrading to
02:19 Techrights-sec; GNU/Linux
02:19 Techrights-sec; LTS distros are a better fit, if they delay so long. But there needs to be
02:19 Techrights-sec; a budget for upgrades in addition to marking it on the calendar some years
02:19 Techrights-sec; in advance. Otherwise they must choose a rollingrelease distro and deal with
02:19 Techrights-sec; the small amounts of inconvenience very frequently. I'd say that
02:19 Techrights-sec; the LTS route is the way to go but one of the risks is that there will be
02:19 Techrights-sec; turn over in managment long before then and that the budget (both time and
02:19 Techrights-sec; money and staffing) for migration will get looted between now and then.
02:19 Techrights-sec; The migration from Vista to Vista11 will be more than to KDE probably.
02:19 Techrights-sec; There used to be lots of cost-benefit studies showing that even if the gains
02:19 Techrights-sec; were temporary in regards to desktop security, there were still very big savings
02:19 Techrights-sec; to be had by upgradingto GNU/Linux. Since the KDE 3.x days, Windows has had
02:19 Techrights-sec; worse usability than GNU/Linux.
02:20 Techrights-sec; They have to look further ahead than a single financial quarter though.
02:21 *DaemonFC has quit (Quit: Leaving)
02:24 schestowitz-TR2; oh, wait, this is GE
02:24 schestowitz-TR2; did I mention these idiots drove away all the *NIX people?
02:24 schestowitz-TR2; And they now use MS Tgeams for a bunch of Windows wintendo operators?
02:24 schestowitz-TR2; to be spoonfed commands over the phone etc?
02:38 Techrights-sec; If they are idealogially wed to M$ on the desktop, they will get hit with
02:38 Techrights-sec; ransomware. it is a matter of when not if. The impact of that can be mitigated
02:38 Techrights-sec; by having remote desktops mounted from GNU/Linux or FreeBSD with Samba on top
02:38 Techrights-sec; of OpenZFS. The OpenZFS allows very inexpensive snapshotting which means
02:38 Techrights-sec; it is trival to roll back to last known good files.
02:38 Techrights-sec; So they have /no/ IT staff any more? That's a business heading for failure.
02:38 Techrights-sec; They need to hire at least two IT staff and send the poseurs packing.
02:38 Techrights-sec; M$ Teams (r) is not even third place among the collaboration tools of its kind.
02:38 Techrights-sec; militant ignorance
02:39 schestowitz-TR2; they offered my sister a lot of money to come back
02:42 schestowitz-TR2; think of it as Intel/... trying hard to bring back actual geeks
02:42 schestowitz-TR2; but afaiok mIntel failed to get rid of the saboteurs
02:42 schestowitz-TR2; who tore down gitlab and drupal in favour of microsoft garbage
02:42 Techrights-sec; money is one thing but if it is the same old mess without a mandate to clean\hous
02:42 Techrights-sec; e then the money might not be enough
02:46 Techrights-sec; yes, the presents of /any/ M$ product is always a staffing problem.
02:46 Techrights-sec; there's not way they can be safely kept on the payroll and trusted not to
02:46 Techrights-sec; do more damage.
02:46 schestowitz-TR2; another toipic:
02:46 schestowitz-TR2; wishlist: a dd command that would, as root, over ssh, ISOify the raspi
02:46 schestowitz-TR2; such that I end up with one file to which I can 'restore' to SD card
02:46 schestowitz-TR2; the OS has enough space in it to dump its wholem self into a file in /hoome
02:47 Techrights-sec; I'm rather sure dd is the wrong tool for that. Yes, but will the later
02:47 Techrights-sec; target device be small enough ? I'd say to use one of the stock Raspberry Pi OS
02:47 Techrights-sec; images and modifiy that with Rsync.
02:47 Techrights-sec; They can be mounted and then written easily.
02:48 schestowitz-TR2; ok, but restore and rsync would not cover system-level stuff, unless you literally rsync the whole of root, which would not go down too well
02:49 Techrights-sec; With dd the problem is not
02:49 Techrights-sec; the copying from the source it is the copying to the destination.
02:50 schestowitz-TR2; either way, it would be nice to havw a routine by which the whole DSD card gets c
02:50 schestowitz-TR2; lone to another
02:50 schestowitz-TR2; an OUT-OF-DATE cloe can be brought up to date with rsync
02:51 Techrights-sec;
02:51 Techrights-sec; There is probably an established method documented out there.
02:51 schestowitz-TR2; that I would love to know about
02:52 schestowitz-TR2; tonight it won't be perfect or gold standard but close to where we were before, with an LTS with lots of life left in it
02:54 schestowitz-TR2; if rianne gets another pi, we can ever HA/load-balance something like gemini, tho
02:54 schestowitz-TR2; ugh with one single IP address (IPv4, no NAT) I doubt it'll be simple
02:54 schestowitz-TR2; also, main point of failure is just ISP
02:54 schestowitz-TR2; *one ISP
02:55 Techrights-sec; yes
02:55 Techrights-sec; clustering is a common activity
02:56 schestowitz-TR2; the spare USB stick I have (32GB) can allow for quick recovery with the bullseye image, then rsync missing bits, maybe recovery time of 1 hour assuming boot from USB
02:57 Techrights-sec; there might be scripts to shrink the partition prior to using dd to copy it.
03:08 Techrights-sec; That would probablhy work. The dd image would be a copy which would be mounted a
03:08 Techrights-sec; nd then the new installation would be the rsync target from the mounted image
03:08 Techrights-sec; The Raspberry Pi uses a primary partition rather than an LVM
03:19 schestowitz-TR2; tidying up desk
03:19 schestowitz-TR2; first time in months
03:19 schestowitz-TR2; need to learn to use the pen while recording
03:19 schestowitz-TR2; to keep mental flow
03:19 schestowitz-TR2; but would not work if camera on face
03:27 Techrights-sec; ack
03:27 Techrights-sec; just tested adding an extra partition to the end of the stock RPi image
03:27 Techrights-sec; to reserve the space. The expansion script can't handle the presence
03:27 Techrights-sec; of an additional partition. Some other approach is needed.
03:28 schestowitz-TR2; my knowledge of dd and .img file is weak
03:30 Techrights-sec; creating an image from dd is no problem. the solution might be to
03:30 Techrights-sec; do that and then when needed, mount it loopback on your destop annd rsync to
03:30 Techrights-sec; the new image on a new device.
04:39 *u-amarsh04 (~amarsh04@asrpphbur8fa4.irc) has joined #boycottnovell
04:39 *u-amarsh04 (~amarsh04@joseon-rmogvn.g0d7.dtdf.mc4289.IP) has joined #boycottnovell
05:10 *u-amarsh04 has quit (Quit: Konversation terminated!)
05:10 *u-amarsh04 has quit (Quit: Konversation terminated!)
05:11 *u-amarsh04 (~amarsh04@asrpphbur8fa4.irc) has joined #boycottnovell
05:11 *u-amarsh04 (~amarsh04@joseon-rmogvn.g0d7.dtdf.mc4289.IP) has joined #boycottnovell
05:24 *u-amarsh04 has quit (Quit: Konversation terminated!)
05:24 *u-amarsh04 has quit (Quit: Konversation terminated!)
08:33 Techrights-sec; http not responding
08:33 Techrights-sec; restarting httpd
08:41 schestowitz-TR2; thanks!
08:41 schestowitz-TR2; the downtime must have been short as I did not even receive an alert
08:41 schestowitz-TR2; email from montanstic afaik
08:45 Techrights-sec; np
08:46 Techrights-sec; My script and montastic are certainly out of sync and check at different times,
08:46 Techrights-sec; which is good, since it increases the coverage. All the bugs are not out of
08:46 Techrights-sec; my script though, due to my unfamiliarity with python's modules and
08:46 Techrights-sec; the slight inconsistency in the documentation. Once it is more tested
08:46 Techrights-sec; I can add it to the Git repository.
08:46 Techrights-sec; Anyway, http was completely unresponsive for a bit but ssh was fortunately ok.
08:49 schestowitz-TR2; some time soon there will be a storage component migration, causing a downtime ra
08:49 schestowitz-TR2; ther long
08:55 Techrights-sec; At HV's level?
08:55 schestowitz-TR2; physical
09:10 Techrights-sec; ack
09:16 *u-amarsh04 (~amarsh04@joseon-rmogvn.g0d7.dtdf.mc4289.IP) has joined #boycottnovell
09:16 *u-amarsh04 (~amarsh04@asrpphbur8fa4.irc) has joined #boycottnovell
09:25 schestowitz-TR2; I was going to make some unimportant remark about monitoring
09:25 schestowitz-TR2; but I forgot what it was
09:25 schestowitz-TR2; spent over 20 mins trying to recall it lol
09:25 schestowitz-TR2; in vain
09:25 schestowitz-TR2; tbh, better not to demand such a recall
09:25 schestowitz-TR2; I ever reread what triggered the though
09:25 schestowitz-TR2; but that did not come back
09:25 schestowitz-TR2; a few times before I reran videos where something I covered made
09:25 schestowitz-TR2; me feel like after recording I need to do something
09:25 schestowitz-TR2; but was unable to take notes
09:25 schestowitz-TR2; the conclusion of it all is,
09:25 schestowitz-TR2; better not to even try to remember
09:25 schestowitz-TR2; I am going to record in a few mins
09:25 schestowitz-TR2; OTA
10:23 *u-amarsh04 has quit (connection closed)
10:23 *u-amarsh04 has quit (Connection closed)
10:51 schestowitz-TR2; did something happen with the site?
10:51 schestowitz-TR2; Was it or apache handled?
10:53 Techrights-sec; ack
10:53 Techrights-sec; yes, I saw that the logs stopped flowing up the screen and then checked and
10:53 Techrights-sec; saw that httpd had stopped responding so I restarted httpd. It stopped about
10:53 Techrights-sec; 25/Jan/2022:10:40:05
10:53 Techrights-sec; I restarted it after 10:45
10:54 schestowitz-TR2; so maybe same issue as last friday
10:56 Techrights-sec; I have no idea where to look at the moment. The error logs continued for
10:56 Techrights-sec; a few minutes longer, but also stopped at Jan 25 10:49:49.009597
11:21 schestowitz-TR2; draft
11:21 schestowitz-TR2; transcoding at the mment
11:21 schestowitz-TR2; today I keep forgetting things
11:21 schestowitz-TR2; first in yalk
11:21 schestowitz-TR2; then while recording
11:21 schestowitz-TR2; maybe a lack of sleeep and concentration deficit
11:21 Techrights-sec; :/
11:21 Techrights-sec; sign of the times?
11:30 Techrights-sec; looking at more of the logs
11:30 schestowitz-TR2; excellent, that's very important
11:31 Techrights-sec; [25-Jan-2022 10:40:00] WARNING: [pool www] server reached pm.max_children setting
11:31 Techrights-sec; (50), consider raising it
11:32 Techrights-sec; [25-Jan-2022 10:40:04] WARNING: [pool www] child 25045, script '/home/boycottn/pu
11:32 Techrights-sec; blic_html/index.php' (request: "
11:32 Techrights-sec; GET /index.php") executing too slow (5.410458 sec), logging
11:32 Techrights-sec; preceedes with other errors and preceeded with more 'too slow' errors
11:32 Techrights-sec; in /var/log/php-fpm/error.log
11:32 schestowitz-TR2; i wonder to what degree the bots are causing this by pushing towards bottlenecks
11:42 Techrights-sec; ack
11:42 Techrights-sec;
11:42 Techrights-sec; What is /var/log/sa/sa25 ? It looks like a binary of some kind.
11:42 schestowitz-TR2; i am not familiar with it
11:53 schestowitz-TR2; i have to be honest
11:53 schestowitz-TR2; i do not know acess patterns
11:53 schestowitz-TR2; we never used gulag 'anal'iticcs or the likes of that
11:53 schestowitz-TR2; the way I undrstand it
11:54 schestowitz-TR2; there are egulars
11:54 schestowitz-TR2; there are also first times, the ones who retrieve the pertinent files from css
11:54 schestowitz-TR2; and they stick around, due to the nature of the site, and follow link to binge so
11:54 schestowitz-TR2; me info
11:54 schestowitz-TR2; and read the site like an expandable booklet
11:54 schestowitz-TR2; the real hog issue comes from bopts
11:54 schestowitz-TR2; they got worse in recent weeks
11:54 schestowitz-TR2; like swallowing up thousands of the same thing, per 5 minutes
11:54 schestowitz-TR2; I see this in apachelog
11:54 schestowitz-TR2; maybe they hit some hard limits
11:54 schestowitz-TR2; so apache vomits
11:55 Techrights-sec; me neither
11:55 Techrights-sec; # sar -s 10:00:00 -e 11:00:00
11:55 Techrights-sec; system performance logs, probably something RHEL or CentOS
11:55 Techrights-sec; could be
11:55 Techrights-sec; none of Gemini's cron jobs fire at the times when the load was recorded as
11:55 Techrights-sec; heavym so that's not it.
12:13 Techrights-sec; https://www.juve-patent.com/news-and-stories/cases/ericsson-and-apple-escalate-pa
12:13 Techrights-sec; ent-war-in-europe/
12:13 -TechrightsBN/#boycottnovell-www.juve-patent.com | Ericsson and Apple escalate patent war in Europe - JUVE Patent
12:13 schestowitz-TR2; fosspatents wrote like 8 aerticles about this and is at the cuttign edghe
12:13 schestowitz-TR2; juve is shite shite shite
12:15 Techrights-sec; that's what I was wondering, should it be added to the spam site list for
12:15 Techrights-sec; automated culling?
12:16 schestowitz-TR2; no, I am still watching that site for being able to rebut
12:16 schestowitz-TR2; short story is
12:16 schestowitz-TR2; they used to do ok journalism
12:16 schestowitz-TR2; they covered epo scnadals
12:16 schestowitz-TR2; in german and english
12:16 schestowitz-TR2; some time along the way they became spamfarm for litigation companies
12:17 schestowitz-TR2; half of their 'articles' are ads
12:17 schestowitz-TR2; and most of the site is just a directory for litigaition firms (sponsors)
12:17 Techrights-sec; timeout again on httpd
12:17 Techrights-sec; ok it's a spam site
12:18 schestowitz-TR2; i am not sure if the site had a real issue or just a surge in traffic due to the new post, but I guess the former, i might need a nap soon
12:18 *u-amarsh04 (~amarsh04@joseon-rmogvn.g0d7.dtdf.mc4289.IP) has joined #boycottnovell
12:18 *u-amarsh04 (~amarsh04@asrpphbur8fa4.irc) has joined #boycottnovell
12:19 Techrights-sec; ack
12:19 Techrights-sec; still timed out, again,
12:19 Techrights-sec; third time over as many minutes
12:20 schestowitz-TR2; looking at more of the logs
12:22 Techrights-sec; timeout again -- restarting httpd
12:23 schestowitz-TR2; yes, I saw the same at my end
12:24 schestowitz-TR2; i do see unusual patterns in apachetop
12:24 schestowitz-TR2; notably a lot more requests than usual for old media files
13:03 *psydroid4 (~psydroid@cqggrmwgu7gji.irc) has joined #boycottnovell
14:11 *u-amarsh04 has quit (Quit: Konversation terminated!)
14:11 *u-amarsh04 has quit (Quit: Konversation terminated!)
15:55 *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #boycottnovell
17:18 Techrights-sec; timeout again -- restarting httpd
17:18 Techrights-sec; timeout again
17:18 Techrights-sec; httpd had to be restarted, it seems available again
17:18 schestowitz-TR2; thsaks, I saw your message while recording
17:18 schestowitz-TR2; that helped explain why I could not reach ti nwhile rtecoprding
17:18 Techrights-sec; it was probably unavailable for < 10 minutes
17:19 schestowitz-TR2; last friday the issue lasted less than 24 hours all in all
17:20 Techrights-sec; The script
17:22 schestowitz-TR2; ty so much
17:24 Techrights-sec; ack
17:24 Techrights-sec; np
17:24 Techrights-sec; the script checks every 10 minutes and then sets off lights on the first failure
17:24 Techrights-sec; and checks again after 1 minute. Every second failed check produces a morse
17:24 Techrights-sec; signal on a piezoelectric buzzer. It needs fine tuning but was quick to write
17:24 Techrights-sec; As such it always needs manual reset, but that is good in this context.
18:30 *DaemonFC (~daemonfc@geufhbnmd9gbq.irc) has joined #boycottnovell
18:54 schestowitz-TR2; httpd restart
18:54 schestowitz-TR2; lol, now the other gateway gemini->html (JS actually) is also down
18:54 schestowitz-TR2; both down at the same time
19:55 *DaemonFC has quit (Quit: Leaving)
22:28 *u-amarsh04 (~amarsh04@joseon-rmogvn.g0d7.dtdf.mc4289.IP) has joined #boycottnovell
22:28 *u-amarsh04 (~amarsh04@asrpphbur8fa4.irc) has joined #boycottnovell
22:32 *psydroid4 has quit (Ping timeout: 2m30s)
22:36 *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #boycottnovell
-- Response ended
-- Page fetched on Sun May 19 12:50:07 2024