#soylent | Logs for 2024-11-15
« return
[03:43:01] <chromas> I didn't even know player class could have spaces
[04:05:56] <kolie> Yeah I didn't know I could pick a specific type of my favorite ninja
[04:18:15] <chromas> What up, muh ninja
[06:26:27] <chromas> https://www.foundry.com
[06:26:28] <systemd> ^ 03Foundry winds down Modo development
[09:42:54] -!- soylentil81 [soylentil81!~soylentil@kq880559025754.49.openmobile.ne.jp] has joined #soylent
[09:43:48] -!- soylentil21 [soylentil21!~soylentil@l6781506-mjoqpd.ipoe.ocn.ne.jp] has joined #soylent
[09:44:16] <soylentil21> Having problems? Logs not available.
[09:45:25] -!- soylentil21 has quit [Client Quit]
[09:46:13] <janrinok> Logs are working fine - PEBKAC
[09:47:04] <inz> Error 1D107
[09:47:35] -!- soylentil81 has quit [Ping timeout: 272 seconds]
[09:47:48] <janrinok> https://logs.sylnt.us is working
[09:48:46] <janrinok> https://logs.sylnt.us is working - that perhaps need changing
[09:49:41] <fab23> Not participating in the channel and only reading the logs is stalking.
[09:50:13] <chromas> that's our-a-stalk-us
[09:50:39] <inz> I think the DNS server for sylnt.us has gone fishing
[09:52:07] <janrinok> kolie is on vacation until the middle of next week.
[09:52:30] <janrinok> But I am not seeing a problem here yet
[09:53:00] <chromas> doesn't work for me
[09:53:29] <inz> ;; Connection to 96.43.31.82#53(96.43.31.82) for sylnt.us failed: timed out.
[09:53:58] <chromas> at least some of the sylnt.us domains were working a couple days ago
[09:54:28] <inz> 192.163.30.227 works, but my resolvers seem hesitant to try to contact it
[09:55:35] <janrinok> Well, we can live without the logs being visible for a few days. They appear to still be recording OK.
[09:55:37] <inz> No idea why all my devices try to contact the ns2
[09:56:05] <chromas> the regular domain works
[09:56:14] <chromas> with a logs. prefix
[09:57:41] <inz> I'm guessing it depends on the order in which the TLD DNS returns the additional section
[09:58:28] <inz> Same name servers for both domains, but .org lookups contact the ns0, which works, but .us use the b0rked one
[09:59:08] <chromas> all I get is SERVFAIL from any resolver
[09:59:41] * chromas blames Loggie
[10:05:16] <janrinok> If the rest of the site is working we can manage. Would like to know _why_ it is failing though.
[10:49:01] -!- kolie_ has quit [Ping timeout: 272 seconds]
[10:50:01] -!- kolie_ [kolie_!~kolie@208.91.qqu.m] has joined #soylent
[11:44:45] -!- prg has quit [Ping timeout: 272 seconds]
[11:47:03] -!- prg [prg!~prg@ryfhuvb.de] has joined #soylent
[17:14:12] <kolie> So I've noticed issues with tungsten
[17:14:33] <kolie> And it seems to be that there are iptables changes that removed docker stuff.
[17:15:14] <kolie> What I'm guessing is that NS2 doesn't work properly and NS0 responds ok
[17:15:39] <janrinok> Hi - as soon as they mentioned ns2 I came to a similar conclusion. But it will wait. You are on vacation! The Meta is going out just about now, fyi.
[17:47:01] -!- systemd has quit [Ping timeout: 272 seconds]
[17:47:39] -!- chromas has quit [Ping timeout: 272 seconds]
[17:48:17] -!- SedBot has quit [Ping timeout: 272 seconds]
[17:50:17] <kolie> Sylnt.us what should that go to
[17:50:22] <kolie> There is no @ record
[17:52:03] <kolie> 96.43.31.82 I don't even know that ip
[17:57:04] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[17:57:04] -!- mode/#soylent [+v chromas] by Imogen
[18:00:50] -!- systemd [systemd!~systemd@pid1] has joined #soylent
[18:10:21] <janrinok> Logix, Houston TX - never heard of them
[18:11:46] <janrinok> logs.sylnt.us works fine, at least for me.
[18:12:16] <janrinok> sorry for the delay - I was eating my dinner!
[19:50:54] -!- Runaway has quit [Read error: -0x1: ERROR - Generic error]
[20:23:23] -!- Runaway1956 [Runaway1956!~OldGuy@the.abyss.stares.back] has joined #soylent
[22:24:41] -!- chromas2 [chromas2!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[22:24:41] -!- mode/#soylent [+v chromas2] by Imogen
[22:26:19] -!- systemd has quit [Ping timeout: 272 seconds]
[22:26:19] -!- chromas has quit [Ping timeout: 272 seconds]
[23:49:29] chromas2 is now known as chromas