#soylent | Logs for 2024-06-14
« return
[01:17:13] <chromas> I don't see any bugs
[02:18:01] -!- anontor has quit [Quit: anontor]
[02:41:40] -!- anontor [anontor!~anontor@103.251.oxm.xi] has joined #soylent
[02:50:14] -!- anontor2 [anontor2!~anontor@185.220.org.is] has joined #soylent
[02:52:13] -!- anontor has quit [Ping timeout: 252 seconds]
[02:52:38] -!- anontor2 has quit [Remote host closed the connection]
[02:58:03] -!- anontor [anontor!~anontor@185.243.zsn.xno] has joined #soylent
[04:00:31] -!- anontor has quit [Remote host closed the connection]
[04:01:17] -!- anontor [anontor!~anontor@23.154.vnk.on] has joined #soylent
[05:28:22] <janrinok> Bytram, the response to the =blame query has been there for at least 5 years. It was based on you ability to find bugs that could crash the system if I recall correctly.
[05:28:25] <janrinok> =islam
[05:28:40] <janrinok> ... does nothing
[05:28:51] <janrinok> =rehashctl
[05:28:51] <systemd> Options: login
[05:29:50] <janrinok> That might be a useful one if we can only work out what it does...
[05:47:38] <chromas> it just logs into sn when the cookie expires
[06:14:12] <janrinok> ah, nowhere near as useful as I hoped it might be then.
[06:17:10] <janrinok> =devsub https://phys.org
[06:17:14] <systemd> ✓ Sub-ccess! "03Molecules Derived From Sea Sponge Show Promising Effects in Cancer, Mitochondrial Function" (21p) -> https://soylentnews.org
[06:34:04] -!- _dx3bydt3 [_dx3bydt3!~|dx3bydt3@129.224.whx.sk] has joined #soylent
[06:36:37] -!- dx3bydt3 has quit [Ping timeout: 252 seconds]
[06:59:13] <chromas> not sure why that doesn't point to dev, oh well
[07:00:47] <chromas> dumb knob on 3d printer controller broke. apparently using it to home the printer is the only way to make use of the z probe, so if I use octoprint then homing just smashes the head into the bed. fpos
[07:04:46] <janrinok> I don't suppose you can make a new knob until you have made a new knob.....
[07:05:38] <janrinok> Ah, so that is where it put my submission... fpos indeed!
[07:06:33] <chromas> it's the encoder itself that died. just started seizing up once everything else was working. a little wd-40 and lube got it spinning, but it's also a button and that part is stuck down. new one coming this afternoon
[07:07:05] <janrinok> The occasional site down messages that we are seeing are also existing on the dev system. As dev is entirely different the problem must come for whatever infrastructure we have that is common to both - I think?
[07:07:42] <chromas> after the restructening, who knows what's in common anymore
[07:07:49] <janrinok> exactly...
[07:08:39] <chromas> but I guess if there's a change in mysql that enables log diarrhea, it's probably on dev as well
[11:05:40] <Bytram> =blame Barrel-Of-Monkeys
[11:05:40] * systemd points at Bytram
[11:06:08] <Bytram> =blame "Barrel-Of-Monkeys"
[11:06:08] * systemd points at Bytram
[11:06:47] <Bytram> =blame 'Barrel-Of-Monkeys'
[11:06:47] * systemd points at Bytram
[11:42:08] <Ingar> in its current form, that gets boring fast
[12:35:21] <Ingar> need a command to add a blame subject
[12:35:55] <Ingar> !addblame Socialism !addblame Capitalism !addblame Nihilism !addblame North Korea
[12:36:21] <Ingar> and Canada ofc
[13:08:59] <requerdanos> Not even a real country anyway.
[13:44:34] <janrinok> oooh, burn
[14:27:57] <fab23> it seems that the server needs a weekend to rest :)
[14:30:45] <janrinok> why - it has a pause for a minute or so but then restarts itself.
[14:48:05] <Ingar> you have to scold it
[14:50:04] <Ingar> g*d d*mn you fsckin piece of sh|t server!
[14:50:08] <Ingar> works with windows
[15:06:34] -!- Ox0000 [Ox0000!~Ox0000@ysig-694-71-0-819.washdc.fios.verizon.net] has joined #soylent
[15:07:13] <Ox0000> Another day, another notification of a 500/internal server error
[15:11:56] -!- soylentil43 [soylentil43!~soylentil@iqe-987-907-954-378.res.spectrum.com] has joined #soylent
[15:13:48] <soylentil43> Internal Server Error
[15:15:02] <Ox0000> is there anything you can share about _why_ those errors keep happening?
[15:16:11] <soylentil43> I'm just a user, not admin
[15:17:23] <Ox0000> I was asking the admins here though, not you :)
[15:17:26] -!- soylentil43 has quit [Quit: Client closed]
[15:21:05] <janrinok> It has been doing that for a few days. But it has, until now, restarted itself, so I am not quite sure what is happening.
[15:23:47] -!- Runaway1956 [Runaway1956!~OldGuy@the.abyss.stares.back] has joined #soylent
[15:24:12] <Runaway1956> Internal Server Error
[15:24:36] <Runaway1956> It was working fine about 20 minutes ago, now that's all I get.
[15:27:04] <janrinok> yep, me too. It has been flakey for a few days but has usually sorted itself out.
[15:27:47] <janrinok> I've emailed for assistance but whether that will help at this time on a Friday is anyone's guess.
[15:28:03] <Ox0000> Oh, it's a bank that's hosting the server? :P
[15:28:35] <Ox0000> Do you as operators have access to it's logs?
[15:28:45] <Runaway1956> A bank would likely be much worse - they still run Windows 2K
[15:30:24] <janrinok> I don't personally, no.
[15:34:55] -!- pTamok [pTamok!~pTamok@82.148.lts.sjg] has joined #soylent
[15:38:07] <pTamok> Another "500 Internal Server Error" here. Maybe, instead of saying "Please contact the server administrator, admin@soylentnews.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.", perhaps it would be a good idea to point people at this IRC server/channel? Shrug. I don't think mailing
[15:38:07] <pTamok> admin@soylentnews.org helps right now, although I would be happy to be shown to be wrong.
[15:42:21] <janrinok> It lets all staff know what is happening with a single email
[15:44:44] <janrinok> It is a disk that has run out of space - but finding what can be deleted is another matter...
[15:47:22] <chromas> =blame canadia
[15:47:22] * systemd points at chromas
[15:52:25] -!- pTamok has quit [Quit: Ping timeout (120 seconds)]
[15:55:43] <Ox0000> janrinok I hear that you c:\windows\system32 can be deleted if you want to make your computer faster
[15:57:28] <janrinok> lol
[15:58:25] <janrinok> There are backups on here going back to 2022 - I'm fairly sure that they are no longer needed but they are not my files. I have asked others if I can delete them.
[15:59:01] -!- InterestedParty [InterestedParty!~Intereste@199.195.iim.lrn] has joined #soylent
[15:59:10] <Runaway1956> My uninformed uneducated opinion, you probably don't need backups more than six months old.
[16:00:58] <janrinok> Agreed, but I don't know if they are part of kolies own docker installation
[16:01:53] <chromas> wouldn't that only be on the staging server?
[16:02:29] <chromas> Plus I thought the new system was Do What You Want and Tell No One
[16:02:32] <chromas> ™
[16:04:58] <janrinok> I'm not saying it is a backup of the staging system, but it 'might' be something that is called in by docker build or ansible
[16:05:14] <fab23> 🙈🙊🙉
[16:05:50] <janrinok> There is a 1Gb+ file from years ago which is identified as corrupted but it belongs to root and I cannot delete it!
[16:06:22] <Runaway1956> In that case, you should follow past examples. Dump everything and see what breaks. Not naming any names here, of course.
[16:07:06] <janrinok> I could do that :), but if it doesn't work I would not be able to fix it either.
[16:07:33] <janrinok> I can't even move them to another machine to make some space. kerberos will not let me.
[16:08:45] <janrinok> I will give people a chance to respond to the emails but I might just have to make a decision in an hour or so and see what happens....
[16:09:30] <janrinok> I think the smell of burning might be part of my dinner - I'd better go and sort that out too
[16:09:58] <Runaway1956> Food usually tastes better with the scent of burnt carbon hanging in the air.
[16:35:27] <janrinok> I hope so....
[16:36:19] <janrinok> I have emailed the only 2 people who can delete the huge unwanted files and restart the system. All we can do now is wait a while.
[16:59:30] -!- InterestedParty has quit [Quit: Client closed]
[17:19:51] <Runaway1956> https://www.youtube.com
[17:19:52] <systemd> ^ 03Boomer Triggers Gen-Z Snowflakes. Brad Upton
[17:26:34] -!- pTamok [pTamok!~pTamok@82.148.lts.sjg] has joined #soylent
[17:28:38] <pTamok> OK, looks like I need to get my pseudonymous email wound up ready to spring into action. Sorry to hear about the disk, but it is nice, at east, that the likely source of the problem has been identified.
[17:31:53] <pTamok> Looks like I need to vanish, hope things get sorted out with a minimum of fuss.
[17:31:58] -!- pTamok [pTamok!~pTamok@82.148.lts.sjg] has parted #soylent
[17:38:04] <Ingar> /var/log is a good place to start trimming
[17:41:54] <Ingar> and make sure that big file isn't a swap file :D
[17:43:40] <fab23> also deleting a file which some process still has open, will not free the disk space
[17:45:23] <Ingar> I have some spare disks though, can I send them in
[17:45:24] -!- soylentil35 [soylentil35!~soylentil@y-66-736-832-896.hsd8.il.comcast.net] has joined #soylent
[17:53:51] <fab23> Ingar: can you please first virtualize them so they can be added in the cloud? :)
[17:54:15] <Ingar> fab23: do you have some burner I can use ?
[17:55:27] <Ingar> warehouse near the airport went up in flames two days ago, the smoke plume was visible dozens of km away
[17:56:10] <fab23> Ingar: hm, maybe you need the https://aws.amazon.com or https://aws.amazon.com :)
[17:56:11] <systemd> ^ 03Rugged Data Device, Terrabyte Data Transfer - AWS Snowcone - AWS
[17:56:11] <systemd> ^ 03Offline Data Transfer Device, Petabyte - AWS Snowball - AWS
[17:57:13] <fab23> Ingar: hm you can only hope that they did not store toxic stuff there
[17:57:30] <fab23> or I mean stuff which gets toxic when burning
[17:58:21] <Ingar> fab23: wasn't toxic according to officials, just the standard keep doors and windows closed. smoke wasnt coming my way anyway
[18:04:48] <fab23> usually they don't know it at that time for sure, so they say something to keep the people calm. Here they also mention to turn any ventilation off as well.
[18:07:20] <janrinok> I have had replies from kolie and NCommander. kolie gave me permission to delete his files but the perms are limited to him deleting them, I can only read them. NCommander will have access to a computer later 'tonight' (NY time?).
[18:24:28] <janrinok> without root access there is nothing I can do. I can see loads of useless files, but I cannot delete them.
[18:28:08] <fab23> :-(
[18:40:01] <Ingar> by accident, the system isn't old enough to have a known perm escalation bug?
[18:41:43] <Ingar> although the ethics of this approach might depend on things that are beyond my knowledge
[18:44:58] -!- Ox0000 has quit [Quit: Client closed]
[18:47:17] <janrinok> Hey - I got it back online!
[18:48:01] <Ingar> Ironically, the first news item is the Boeing's Leaky Boat Has More Leaks, Return Delayed.
[18:48:22] <Ingar> janrinok: but it works! thanks
[18:49:34] <janrinok> not sure how long for though - I have only recovered 2% of the disk space
[19:17:37] <chromas> You could trim the systemd journal
[19:19:12] <janrinok> OK, I've recovered about 5% now...
[19:24:33] <Ingar> chromas: if it is journald, you can just set a max size
[19:25:09] <Ingar> I usually do that on single boards and the likes
[19:35:58] <chromas> Yeah and the default used to be yuuuge, like half free disk space or something
[19:36:13] <chromas> Though in that case it shouldn't be able to fill it alone
[19:36:32] <janrinok> chromas - see PM
[19:42:16] <janrinok> chromas, that got me another 1% - not to be sniffed at!
[19:51:03] <janrinok> well, it is way past my bedtime so that is the end of my day. Hopefully it will keep working until tomorrow at least!
[20:48:01] -!- fliptop has quit [Ping timeout: 252 seconds]
[20:48:23] -!- fliptop [fliptop!~fliptop@69.43.kn.gu] has joined #soylent
[22:14:14] -!- drussell_ [drussell_!~drussell@2604:3d08:a77f:gykn:rxgj:qzpr:zypy:hrgs] has joined #soylent
[22:14:22] -!- drussell has quit [Ping timeout: 252 seconds]
[22:35:08] -!- anontor has quit [Quit: anontor]
[22:41:54] -!- anontor [anontor!~anontor@23.154.gxk.nt] has joined #soylent