OminousOrange

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

Right, but I would say the same thing and for a gaming machine, I would much prefer something that did the Arch install for me and worked for most games out of the box.

[–] OminousOrange@lemmy.ca 2 points 19 hours ago (3 children)

I've found CachyOS to be fairly uncomplicated and it's gaming tweaks make most things work out of the box through Lutris. I'd probably avoid the standard Arch install for a newbie

[–] OminousOrange@lemmy.ca 4 points 19 hours ago (1 children)

I'm going to investigate more tomorrow, but it looks like you can add a forward zone to your unbound.conf to specify which upstream servers to use.

[–] OminousOrange@lemmy.ca 7 points 1 day ago

Not a bad question, but I'm not sure it's relevant to this story.

[–] OminousOrange@lemmy.ca 2 points 1 day ago* (last edited 1 day ago) (2 children)

A rather expensive but well performing one is Jack59. They make the only conditioner bar I've actually liked. The shampoo bar is great too but it's quite small for the price.

For cheaper options, I believe many store brands have more local packagers, but you'd have to look into each one.

I also use Unscented Company products but haven't tried their shampoo/conditioner.

Madeinca.ca lists a few others.

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

This is my setup too. I use WG-Tunnel to manage the VPN connection on my phone. It just monitors whenever you disconnect from your trusted WiFi network and automatically enables the VPN.

Only hiccup I've found is wireless Android Auto isn't a fan of a VPN.

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

It's kind of funny that we literally grow straws and just don't use them. Wheat straw is a biodegradable alternative that doesn't disintegrate and is often just left in the field after harvest. It might not work for thicker beverages like milkshakes or smoothies, but works great for everything else.

Loblaws (Canadian grocery overlords) sells some.

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

Thou shalt not speculate, but I'm going to do it anyway. Given the lack of a wing and icy conditions, I would guess a skid off the runway caused a roll once the wheels caught the snow, detaching a wing and leaving the plane on its roof. Thankfully the lower speed would mean simply rolling over rather than the more...destructive alternative.

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

Right, but having to stop to charge midway through a 2-300 km trip isn't that practical for most around here. That length of drive isn't uncommon and stopping would be a turnoff for people used to doing the whole trip with an ICE vehicle.

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

Cold weather performance has to improve a bit too. That 300km can easily become 200 or less in a Canadian prairie winter, which isn't enough to be competitive with ICE vehicles, and given the state of charging infrastructure.

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

That little blue triangle in the top left is quite the turnoff.

 

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.

14
submitted 10 months ago* (last edited 10 months ago) by OminousOrange@lemmy.ca to c/selfhosted@lemmy.world
 

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.

 

I'm fairly green at self-hosting, recently upgraded to running Proxmox on an old PC from OMV. A fairly simple setup for Plex, Nextcloud, PiHole, and some docker containers. I have an old Ryzen 5 2600 I'd like to replace the current CPU with (an even older FX-8350), but I'll need a new motherboard with an AM4 socket.

In sourcing a new mobo, are there any features or other considerations I should keep in mind, given its sole purpose of being a server now, rather than a general purpose PC? Or just try to find something relatively inexpensive that'll get the job done?

 

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 ›