OminousOrange

joined 2 years ago
[–] OminousOrange@lemmy.ca 2 points 12 hours ago (2 children)

Well, Canada's only meaningful land border and a vast amount of transportation infrastructure is to the US, so any reasonable leader would probably try to maximize trade with that neighbour as long as they are an ally. Carney has definitely focused on more European trade, but yes, perhaps there should have been more diversification even before Donny.

[–] OminousOrange@lemmy.ca 1 points 2 days ago (1 children)

Extending history by a lot isn't recommended. A database add-on is recommended for long term storage.

[–] OminousOrange@lemmy.ca 2 points 2 days ago

While I agree that one should support developers of games they enjoy if they are able, I recently tried another playthrough of this game and it reminded me how unpolished it is.

Things like

  • Quest NPCs taking very robot-like paths while walking (walk straight for 10 steps, turn right 90 degrees instantly, walk straight 5 steps...) instead of something more natural
  • Needing to wait 5 minutes for an NPC to get to a specific spot and/or complete actions before being able to continue conversation. Typically on the fight missions, you'd win the fight, they'd take 30 s to get up, then saunter over (using an unnatural path) to the designated spot, which then took another 10 seconds to activate the speech option finally.
  • Pedestrians diving into the road in front of your car instead of away.

Perhaps games like GTA spoiled us, but I just found these too annoying to continue.

[–] OminousOrange@lemmy.ca 8 points 4 days ago (1 children)

Indefensible as in it is a decision Trump cannot defend, or as in no one can do anything about it? Seems to be both.

Executive branch power has been bolstered for decades. Unfortunately, this is the first time a narcissist with a complete lack of empathy is in a position to use it. Even if you support Trump, what happens when one of the other side takes that seat?

[–] OminousOrange@lemmy.ca 1 points 4 days ago* (last edited 4 days ago)

I was just discussing Saskatchewan's unique climate today and a colleague made a great point; because of our extreme climate (80 degree C temperature differences annually with several severe weather events), we have less sensitivity to noticing worsening climate events or trends.

Drought seems kind of normal. Severe thunderstorms and hail are kind of normal. Blizzards are kind of normal. Heat waves and cold snaps are kind of normal. Unfortunately, this is a bad frame of mind to have for a province with a large agriculture industry.

[–] OminousOrange@lemmy.ca 5 points 5 days ago (1 children)

Yeah those get put on the no internet access network.

[–] OminousOrange@lemmy.ca 3 points 6 days ago

That is a good point. It's one of the largest centres making law that could be used elsewhere.

[–] OminousOrange@lemmy.ca 1 points 1 week ago

I've got a similar setup. BlueIris is my NVR but I have the reolink integration on HA to trigger alert notifications that include a screenshot and activate lights at night upon detection. Only downside is that BlueIris is Windows only.

OP, I also think it's probably doable with automations if you're fine without full time recording (suppose you could throw an SD card in the cams for that), but some data management automations that delete clips older than x days are probably good too.

[–] OminousOrange@lemmy.ca 5 points 1 week ago (5 children)

This is quite Toronto specific. Not sure it really fits in /c/Canada.

[–] OminousOrange@lemmy.ca 37 points 1 week ago (4 children)

Traffic data kind of requires driver tracking data to be sent to the cloud, which usually goes against the philosophy of projects like this. Unless they're obtaining it from a third party, I doubt it'll be a feature they implement.

[–] OminousOrange@lemmy.ca 9 points 1 week ago

It's always been a bit of a mind bender. Provinces with a massive industry extremely sensitive to actually being able to grow things in the ground who lobby for a separate industry of which the products actively threaten the former's existence. Especially troubling when the former is renewable, and the latter is not.

I suppose it makes sense when the politicians are in the deep pockets of the giant oil corps rather than the smaller pockets of farmers, though farming is becoming more of a giant corp game too.

 

Three Drunkenslug invites to the first three unique comments on this thread. I might not get to sending them until tomorrow.

Happy holidays!

 

Hello fine usenet folks. Looking to get a DS invite, and I'd be happy to share any that I get upon registration.

 

Fine folks of c/selfhosted, I've got a Docker LXC (Debian) running in Proxmox that loses its local network connection 24 hours after boot. It's remedied with a LXC restart. I am still able to access the console through Proxmox when this happens, but all running services (docker ps still says they're running) are inaccessible on the network. Any recommendations for an inexperienced selfhoster like myself to keep this thing up for more than 24 hours?

Tried:

  • Pruning everything from Docker in case it was a remnant of an old container or something.
  • Confirming network config on the router wasn't breaking anything.
  • Checked there were no cron tasks doing funky things.

I did have a Watchtower container running on it recently, but have since removed it. It being a 24 hr thing got me thinking that was the only thing that would really cause an event at the 24 hr post start mark, and it started about that same time I removed Watchtower (intending to do manual updates because immich).

...and of course, any fix needs 24 hours to confirm it actually worked.

A forum post I found asked for the output of ip a and ip r, ~~see below.~~ Notable difference on ip r missing the link to the gateway after disconnecting.

Update: started going through journalctl and found the below abnormal entries when it loses connection, now investigating to see if I can find out why...

Apr 16 14:09:16 docker 922abd47b5c5[376]: [msg] Nameserver 1.1.1.1:53 has failed: request timed out.
Apr 16 14:09:16 docker 922abd47b5c5[376]: [msg] Nameserver 192.168.1.5:53 has failed: request timed out.
Apr 16 14:09:16 docker 922abd47b5c5[376]: [msg] All nameservers have failed

Update 2: I found using systemctl status networking.service that networking.service was in a failed state (Active: failed (Result: exit-code)). I also compared to a separate stable Docker LXC which showed networking.service was active, so, did some searching to remedy that.

x networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-04-16 17:17:41 CST; 8min ago
       Docs: man:interfaces(5)
    Process: 20892 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
    Process: 21124 ExecStopPost=/usr/bin/touch /run/network/restart-hotplug (code=exited, status=0/SUCCESS)
   Main PID: 20892 (code=exited, status=1/FAILURE)
        CPU: 297ms

Apr 16 17:17:34 docker dhclient[20901]: DHCPACK of 192.168.1.104 from 192.168.1.1
Apr 16 17:17:34 docker ifup[20901]: DHCPACK of 192.168.1.104 from 192.168.1.1
Apr 16 17:17:34 docker ifup[20910]: RTNETLINK answers: File exists
Apr 16 17:17:34 docker dhclient[20901]: bound to 192.168.1.104 -- renewal in 37359 seconds.
Apr 16 17:17:34 docker ifup[20901]: bound to 192.168.1.104 -- renewal in 37359 seconds.
Apr 16 17:17:41 docker ifup[20966]: Could not get a link-local address
Apr 16 17:17:41 docker ifup[20892]: ifup: failed to bring up eth0
Apr 16 17:17:41 docker systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Apr 16 17:17:41 docker systemd[1]: networking.service: Failed with result 'exit-code'.
Apr 16 17:17:41 docker systemd[1]: Failed to start networking.service - Raise network interfaces.

A reinstall of net-tools and ifupdown seems to have brought networking.service back up. apt-get install --reinstall net-tools ifupdown

Looking at the systemctl status return, I bet everything was fine until dhclient/ifup requested renewal about 24 hours after initial connection (boot), found that networking.service was down, and couldn't renew, killing the network connection.

We'll see if it's actually fixed in 24 hours or so, but hopefully this little endeavour can help someone else plagued with this issue in the future. I'm still not sure exactly what caused it. I'll confirm tomorrow...

Update 3 - Looks like that was the culprit. Container is still connected 24+ hrs since reboot, network.service is still active, and dhclient was able to renew.

Update 4 - All was well and good until I started playing with setting up Traefik. Not sure if this brought it to the surface or if it just happened coincidentally, but networking.service failed again. Tried restarting the service, but it failed. Took a look in /etc/networking/interfaces and found there was an entry for iface eth0 inet6 dhcp and I don't use ipv6. Removed that line and networking.service restarted successfully. Perhaps that was the issue the whole time.

 

This has been one of the key features I've been waiting for to finally be able to move away from Google Photos and OneDrive for mobile photos backup.

 

This has been one of the key features I've been waiting for to finally be able to move away from Google Photos and OneDrive.

 

This has been one of the key features I've been waiting for to finally be able to move away from OneDrive.

 

Just made this sectional following the plans from Ana White.

Roughly $900 CAD in materials, $750 of that being the cushions. I used Duvholmen cushions with Jarpon covers from Ikea, accent pillows I found at Home Sense. All 2x4 lumber and I used pocket holes where screws would be visible. Finished with Ready Seal natural cedar.

Quite happy with it overall. It's really comfortable and will last far longer than (and was cheaper than) those plastic weave ones from big box stores.

view more: next ›