ohshit604

joined 1 year ago
sorted by: new top controversial old
Searching for Discord Alternative with Multi-Screenshare Feature in c/games@sh.itjust.works
[–] ohshit604@sh.itjust.works 2 points 1 day ago* (last edited 1 day ago)

Chances are they’re running into the issue with Element not displaying the arrows to switch between streams.

It is possible for everyone to screen sharing simultaneously however, the bug I mentioned above can make people believe it’s not possible.

Edit: Appears nobody made a bug report for it on GitHub, weird because this issue has occurred for months. #32559 for folks who are invested in this issue.

[Ubuntu] [Docker] Need help with Nvidia hardware acceleration in Jellyfin in c/selfhosted@lemmy.world
[–] ohshit604@sh.itjust.works 3 points 2 days ago* (last edited 2 days ago)

Jellyfin isn’t the most secure piece of software out there, I would avoid giving it permissions it doesn’t need.

Step 1) Check /dev/dri for the GPU

user@debian:~/compose$ ls /dev/dri
total 0
drwxr-xr-x  3 root root        120 Jan 25 11:50 .
drwxr-xr-x 18 root root       3360 Feb 11 03:03 ..
drwxr-xr-x  2 root root        100 Jan 25 11:50 by-path
crw-rw----  1 root video  226,   0 Jan 25 11:50 card0
crw-rw----  1 root video  226,   1 Jan 25 16:39 card1
crw-rw----  1 root render 226, 128 Jan 25 11:50 renderD128

Documentation indicates renderDXXX typically refers to Intel GPU’s

Make sure at least one renderD* device exists in /dev/dri. Otherwise upgrade your kernel or enable the iGPU in the BIOS.

  1. Edit your docker-compose.yaml and add this In your Jellyfin block
devices:
 - /dev/dri/renderD128:/dev/dri/renderD128
  1. Start your container and enter it to verify the device is recognized.

sudo docker compose up -d; sudo docker exec -it jellyfin bash

Once inside ls /dev/dri to confirm the GPU is recognized inside the container, once you confirm it then you can exit the container.

user@debian:~/compose$ sudo docker exec -it jellyfin bash
I have no name!@jellyfin:/$ ls /dev/dri
renderD128
I have no name!@jellyfin:/$ exit
exit
user@debian:~/compose$
  1. On the Jellyfin dashboard go to the hardware acceleration page and follow the notes left by Jellyfin devs.

Based on this graph, and this graph alone, guess at what time I completely blocked OpenAI crawlers in c/selfhosted@lemmy.world
[–] ohshit604@sh.itjust.works 3 points 4 days ago* (last edited 3 days ago)

For a while my GoAccess instance wasn’t working properly so I couldn’t visualize my access logs from Traefik, got lazy trying to fix it and left it as is, well in the meantime I wasn’t lazy enough to setup Synapse and begin federating on my home network.

Finally fixed my GoAccess today to be surprised to see Synapse hits labelled as crawlers, well over a million hits.

If you are not in a tech field, what got you into self-hosting? in c/selfhosted@lemmy.world
[–] ohshit604@sh.itjust.works 1 points 5 days ago* (last edited 5 days ago) (1 children)

I'm considering doing Jellyfin, but I'm not a huge movie/shows consumer,

Well, if you’re paying for [Insert Streaming Service Here] than I’d say it’s worth it. Save yourself the extra 10, 15, 20 dollars a month and use it on a company (or open sourced project!) that actually cares about its consumers, this can be said for Music streaming and “cloud” storage as well.

Discord roll out global age verification system, including an "age inference" model that runs in the background in c/technology@lemmy.world
[–] ohshit604@sh.itjust.works 27 points 1 week ago* (last edited 1 week ago) (2 children)

What do i say to my friends to get them to leave? Ive already tried and they won't.

I just abruptly switched to Matrix and encouraged anyone who wanted to get a hold of me to do the same, held my ground and did not look back, now a good handful of my friends have a Matrix account.

Discord to Require ID or Face Scan Next Month for Full Access in c/technology@lemmy.world
[–] ohshit604@sh.itjust.works 3 points 1 week ago* (last edited 1 week ago) (2 children)

Misconfiguration with SMTP is likely or their SMTP server is under maintenance and you just tried at a poor time.

Granted for a production environment there should be some notice to users.

Question: Is there a Self Hosted Discord like app? in c/selfhosted@lemmy.world
Question: Is there a Self Hosted Discord like app? in c/selfhosted@lemmy.world
[–] ohshit604@sh.itjust.works 5 points 1 week ago* (last edited 1 week ago)

Setting up Element Call on my instance was difficult on its own, I understand why Synapse doesn’t come with it out of the box, essentially you spin up Matrix’s JWT service for authenticating clients and it if approved forwards the connection to the Livekit ports which must be opened on your firewall (ie port forwarded), otherwise people will not be able to connect to calls.

Big PITA and in my experience, on my home network, can conflict with games with VOIP chats so don’t follow the default 50000:55000 port range Livekit recommends or you’ll run into issues like I did, each person consumes 2 ports so adjust the range to your need.

Edit: I don’t suggest running Element Call standalone, it has issues of its own, once you get Livekit and JWT running and follow This guide you should have your element call support in Synapse now, pro-tip for those running synapse behind docker and get confused on the whole ./well-known part of the documentation you can edit your ./well-known in your homeserver.yaml file like such:

serve_server_wellknown: true

extra_well_known_client_content:
  optional: client
  "org.matrix.msc4143.rtc_foci": [
      {
          "type": "livekit",
          "livekit_service_url": "https://livekit-jwt.your.domain/"
      }
  ]
Question: Is there a Self Hosted Discord like app? in c/selfhosted@lemmy.world
Building OpenWatch: an open-source alternative to YouTube in c/selfhosted@lemmy.world
[–] ohshit604@sh.itjust.works 3 points 1 week ago

I stand corrected, apologies.

Building OpenWatch: an open-source alternative to YouTube in c/selfhosted@lemmy.world
Geo-distributed Jellyfin in c/selfhosted@lemmy.world
[–] ohshit604@sh.itjust.works 2 points 1 week ago* (last edited 1 week ago)

You don’t necessarily have to host another Jellyfin instance, I would find a server somewhere in-between the middle of your current Europe server and your Asian homies and setup a reverse proxy there and point it to your current Jellyfin instance.

The only hassle with this is you’re going to need a way to expose your Eu Jellyfin to the new server, a VPN would prevent port forwarding 443, perhaps split tunneling?

Not the most elegant solution but at least this way you can make an attempt at optimizing the connection.

Edit - (if you wanted to go the second Jellyfin instance route): Could also copy your current database to the second server, host a second Jellyfin instance and have something like sshfs or sftp sharing the directory to your media library, reverse proxy it as something like asia-jellyfin.your.domain and keep it separated from your Eu server.

1
Is it wise to reverse proxy or port forward Pihole's port :53? (sh.itjust.works)
 

I want to make use of PiHoles blocklist while I’m outside my network, my WireGuard server which is hosted via my ASUS WRT Merlin router does not appear to respect the DNS = flag on configuration files and just sends all queries through the routers default DNS provider (aka my ISP).

I’ve been trying to troubleshoot this on-and-off for the last year now and have now considered reverse proxying port :53 (hell port forwarding is also on my mind), curious to see if people has done this before and what their experience has been?

Example WireGuard config:

18
Can I remove Pipewire-ALSA without removing Pipewire itself? (sh.itjust.works)
submitted 4 months ago* (last edited 4 months ago) by ohshit604@sh.itjust.works to c/linux@lemmy.ml
3 comments fedilink
 

This kinda stems from this issue I asked about a while back, Pipewire an PulseAudio have caused me quite a bit of confusion lately as I recently started experiencing crackling/static sounds from my Bluetooth speaker when playing audio.

After days of digging and thinking that I’ve fixed the issue by editing /usr/share/piperwire.conf and /usr/share/pipewire-pulse.conf and following guides like this one (I know the link is for EndeavorOS) I have seem to come to the conclusion that Pipewire-ALSA is the issue to the crackling/static sounds I’m hearing.

I stumbled upon qpwgraph which appears to visualize the flow and when I disconnect Pipewire-ALSA from the flow the cracking sounds stop, now from my understanding Pipewire and PulseAudio cannot coexist which is causing my confusion because Pipewire-ALSA also appears to connect to a bunch of PulseAudio Volume Controllers.

Edit; I failed to mention my distro or hardware:

-------------
OS: Debian GNU/Linux 13 (trixie) x86_64
Kernel: Linux 6.12.48+deb13-amd64
Uptime: 2 hours, 19 mins
Packages: 4836 (dpkg), 50 (flatpak), 5 (snap)
Shell: bash 5.2.37
Display (VG249Q3A): 1920x1080 @ 165 Hz in 24" [External] *
Display (ASUS VG24V): 1920x1080 @ 120 Hz in 23" [External]
DE: KDE Plasma 6.3.6
WM: KWin (X11)
WM Theme: Nothing
Theme: Breeze (Nothing) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: WhiteSur (24px)
Terminal: konsole 25.4.2
CPU: Intel(R) Core(TM) i7-8700 (12) @ 4.60 GHz
GPU: NVIDIA GeForce RTX 3060 Ti [Discrete]
Memory: 9.36 GiB / 15.54 GiB (60%)
Swap: 1.26 GiB / 6.91 GiB (18%)
Disk (/): 172.66 GiB / 232.24 GiB (74%) - ext4
Disk (/media/user/Barracuda): 1.58 TiB / 1.78 TiB (89%) - ext4
Local IP (enp4s0): 192.168.1.17/24
Locale: en_US.UTF-8
24
Is there a Macro application that doesn't need a whole lot of scripting knowledge? (sh.itjust.works)
submitted 5 months ago* (last edited 5 months ago) by ohshit604@sh.itjust.works to c/linux@lemmy.ml
12 comments fedilink
 

Morning y’all

Since I switched from windows a couple years back I have yet to find a useful macro application that can handle both mouse and keyboard inputs that also doesn’t need a lot of scripting knowledge.

Back on Windows the Logitech GHub was the perfect application for making macros. Record the macro, edit the key press down & up, delay and change whether or not the macro was a toggle or of the key needed to be held was really easy to do but ever since I switched to Linux/Debian I’ve tried numerous different applications that all seem to need a bunch of scripting knowledge that I honestly don’t have the time nor energy to learn.

I’ve tried:

19
Anyone else lose the Bluez5 AAC audio codec after upgrading to Debian 13? (sh.itjust.works)
submitted 6 months ago* (last edited 6 months ago) by ohshit604@sh.itjust.works to c/linux@lemmy.ml
7 comments fedilink
 

cross-posted from: https://sh.itjust.works/post/44380955

Previously on Debian 12 I followed a guide to install the AAC audio codec for my Air Pods yet after upgrading to Debian 13 I seem to have lost the codec as I can no longer select them in KDE sound settings leaving only A2DP/SBC and A2DP/SBC-XQ, now I’m a bit at a lost as I remember all I had to do was put a aac.so file into /usr/lib/x86\_64-linux-gnu/spa-0.2/bluez5/

Bluez5 directory list:

  • libspa-codec-bluez5-sbc.so
  • libspa-codec-bluez5-opus-g.so
  • libspa-codec-bluez5-opus.so
  • libspa-codec-bluez5-ldac.so
  • libspa-codec-bluez5-lc3.so
  • libspa-codec-bluez5-g722.so
  • libspa-codec-bluez5-faststream.so
  • libspa-codec-bluez5-aptx.so
  • libspa-codec-bluez5-aac.so
  • libspa-bluez5.so

Anyone here by chance know a solution to this?

145
Office workers - Has anyone here convinced their boss to let them install a Linux distro on their work desktop? (sh.itjust.works)
submitted 6 months ago* (last edited 6 months ago) by ohshit604@sh.itjust.works to c/linux@lemmy.ml
105 comments fedilink
 

Going from Windows to Linux then back to windows sucks.

Edit; Going through the comments it seems it doesn’t matter so long as IT supports the operating system, which is fair, in my scenario I’m not involved with our systems-management/IT/developers unless it’s an update to the software we use.

My desktop at work is still Windows 10 and while it works, kinda, my keyboard shortcuts are almost entirely different, I’ve encountered numerous moments where switching tab either by alt-tabbing or by the taskbar not working at all forcing me to minimize everything till I find that tab, couple times it wouldn’t even boot.

I started unplugging the Ethernet cable when I leave for work so IT can’t do any behind the scenes when I’m away.

I dredd the day they force a win 11 desktop on me.

30
Any tool to visualize Traefik access logs? (sh.itjust.works)
submitted 6 months ago* (last edited 6 months ago) by ohshit604@sh.itjust.works to c/selfhosted@lemmy.world
7 comments fedilink
 

Afternoon y’all -

I just spent the last few days fiddling with Prometheus under the impression I could visualize Traefik’s access logs with Perses however, after finally getting these three to communicate with one another it seems that Prometheus lacks the capability to query access logs.

I don’t host my own html/php, I typically find docker images like Invidious or Redlib spin them up in a compose/yaml file and reverse proxy them, my knowledge towards html/php is very minimal so when I read about adding files to the root path of my domain it may seem straight forward for some people but makes no sense to me, apologies if that comes off as ignorant.

I digress, I stumbled upon GoAccess and gave it a shot but from what I’m reading it seems that it needs access to the html that these application use to display reporting in a web-browser which I genuinely got no idea on how to do, Traefik currently spits access logs in a .log file which I assume would be enough to visualize from?

I want to thank everyone for their responses, I’ve been so busy that I couldn’t respond right away but I got GoAccess running and reverse proxied!

I was trying to stay away from Grafana and their associating applications as I’m under the impression they’re moving more towards close-sourced software and seem to be partnering with Google which lead to concerns in regard to data collection.

20
How do you configure CSP headers on 20+ applications ? (sh.itjust.works)
submitted 6 months ago* (last edited 6 months ago) by ohshit604@sh.itjust.works to c/selfhosted@lemmy.world
17 comments fedilink
 

I’ve been working on adding security headers to my reverse proxy and so far I believe to have gotten most of them except for Content Security Policies, I honestly can’t find a simplified way to apply a CSP to 20+ docker applications and hope folks of Lemmy know the best way to go about this.

I want to note that I never worked with headers in the past, I tried interpreting the Traefik documentation and Mozilla documentation as well as a bunch of random YT videos but can’t seem to get it right.

    headers:
      headers:
        customRequestHeaders:
          X-Forwarded-Proto: https
        accessControlAllowMethods:
          - GET
          - OPTIONS
          - PUT
        accessControlMaxAge: 100
        hostsProxyHeaders:
          - "X-Forwarded-Host"
        stsSeconds: 31536000
        stsIncludeSubdomains: true
        stsPreload: true
        forceSTSHeader: true # This is a good thing but it can be tricky. Enable after everything works.
        customFrameOptionsValue: SAMEORIGIN # https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
        contentTypeNosniff: true
        browserXssFilter: true
        contentSecurityPolicy: ""
        referrerPolicy: "same-origin"
        permissionsPolicy: "camera=(), microphone=(), geolocation=(), usb=()"
        customResponseHeaders:
          X-Robots-Tag: "none,noarchive,nosnippet,notranslate,noimageindex," # disable search engines from indexing home server
          server: "traefik"
12
[Proxmox/Debian 12] Drives randomly disconnect an unmount (sh.itjust.works)
submitted 6 months ago* (last edited 6 months ago) by ohshit604@sh.itjust.works to c/linux@lemmy.ml
11 comments fedilink
 

Hey y'all

I've been running into this issue on my home's server, the host OS is Proxmox while i have a Debian 12 VM running within it as a VM i have two external HDD's (1tb, 5tb) running in a drive bay which are randomly disconnecting from the server and i can't seem to make heads or tails of the error in my journalctl, i don't think there is corruption on the drives but i'm hesitant to run any checks as i cannot back these up given how full they are.

The drives typically get recogniced under a different device name/ID right away. for example, /dev/sdb1 will now be /dev/sdd1, and that cycle just repeats every time they disconnect

This is kinda frustrating having to re-mount and re-add these to the VM, is there any way i could simply automate the re-mount of these drives and have the VM pick it up right away?

Jul 30 21:00:53 proxmox kernel:  sdb: sdb1
Jul 30 21:00:53 proxmox kernel:  sdc: sdc1
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] 9767541168 512-byte logical blocks: (5.00 TB/4.55 TiB)
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Attached scsi generic sg2 type 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Direct-Access     WDC WD10 EZEX-21WN4A0     0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:0: Direct-Access     ST5000DM 000-1FK178       0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi host3: uas
Jul 30 21:00:53 proxmox kernel: usb 4-1: SerialNumber: RANDOM__1CC4CDBF833E
Jul 30 21:00:53 proxmox kernel: usb 4-1: Manufacturer: JMicron
Jul 30 21:00:53 proxmox kernel: usb 4-1: Product: JMS56x Series
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0565, bcdDevice= 0.09
Jul 30 21:00:53 proxmox kernel: usb 4-1: new SuperSpeed USB device number 8 using xhci_hcd
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-1tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd...
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-5tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd...
Jul 30 21:00:53 proxmox pvestatd[1165]: status update time (17.646 seconds)
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): unmounting filesystem 181f4235-7fbf-4e0a-8ad1-fd4813367644.
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sde1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost sync page write
Jul 30 21:00:53 proxmox kernel: JBD2: previous I/O error detected for journal superblock update for sde1-8.
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sde1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): unmounting filesystem f966a59f-db1a-433c-9977-040037e7d69e.
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sdd1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sdd1, logical block 610304000, lost sync page write
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sdd1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: device offline error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: usb 4-1: USB disconnect, device number 7
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159739392 op 0x0:(READ) flags 0x200000 phys_seg 8 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6653857768 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438292752 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 822151464 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 973345232 op 0x1:(WRITE) flags 0x808800 phys_seg 3 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=47s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9155874912 op 0x0:(READ) flags 0x200000 phys_seg 64 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: xhci_hcd 0000:00:0d.0: bad transfer trb length 112 in event trb
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:1: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Mode Sense: 67 00 10 08
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] Write Protect is off
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: [sdb] 9767541168 512-byte logical blocks: (5.00 TB/4.55 TiB)
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Attached scsi generic sg2 type 0
Jul 30 21:00:53 proxmox kernel: sd 3:0:0:0: Attached scsi generic sg1 type 0
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:1: Direct-Access     WDC WD10 EZEX-21WN4A0     0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi 3:0:0:0: Direct-Access     ST5000DM 000-1FK178       0009 PQ: 0 ANSI: 6
Jul 30 21:00:53 proxmox kernel: scsi host3: uas
Jul 30 21:00:53 proxmox kernel: usb 4-1: SerialNumber: RANDOM__1CC4CDBF833E
Jul 30 21:00:53 proxmox kernel: usb 4-1: Manufacturer: JMicron
Jul 30 21:00:53 proxmox kernel: usb 4-1: Product: JMS56x Series
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jul 30 21:00:53 proxmox kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0565, bcdDevice= 0.09
Jul 30 21:00:53 proxmox kernel: usb 4-1: new SuperSpeed USB device number 8 using xhci_hcd
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-1tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-1tb\x2dhdd.mount - /root/mnt/1tb-hdd...
Jul 30 21:00:53 proxmox systemd[1]: Unmounted root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd.
Jul 30 21:00:53 proxmox systemd[1]: root-mnt-5tb\x2dhdd.mount: Deactivated successfully.
Jul 30 21:00:53 proxmox systemd[1]: Unmounting root-mnt-5tb\x2dhdd.mount - /root/mnt/5tb-hdd...
Jul 30 21:00:53 proxmox pvestatd[1165]: status update time (17.646 seconds)
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): unmounting filesystem 181f4235-7fbf-4e0a-8ad1-fd4813367644.
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sde1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost sync page write
Jul 30 21:00:53 proxmox kernel: JBD2: previous I/O error detected for journal superblock update for sde1-8.
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sde1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sde1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sde1, logical block 121667584, lost async page write
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): unmounting filesystem f966a59f-db1a-433c-9977-040037e7d69e.
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: JBD2: I/O error when updating journal superblock for sdd1-8.
Jul 30 21:00:53 proxmox kernel: Buffer I/O error on dev sdd1, logical block 610304000, lost sync page write
Jul 30 21:00:53 proxmox kernel: Aborting journal on device sdd1-8.
Jul 30 21:00:53 proxmox kernel: EXT4-fs (sdd1): shut down requested (2)
Jul 30 21:00:53 proxmox kernel: device offline error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: usb 4-1: USB disconnect, device number 7
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 2002831328 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159739392 op 0x0:(READ) flags 0x200000 phys_seg 8 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: rejecting I/O to offline device
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6653857768 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438292752 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 822151464 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#8 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=52s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sde, sector 973345232 op 0x1:(WRITE) flags 0x808800 phys_seg 3 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: [sde] tag#11 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=47s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9155874912 op 0x0:(READ) flags 0x200000 phys_seg 64 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 CDB: Read(16) 88 00 00 00 00 02 21 bb 90 60 00 00 02 00 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 9159851824 op 0x0:(READ) flags 0x200000 phys_seg 5 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 CDB: Read(16) 88 00 00 00 00 02 21 f8 3f 30 00 00 00 28 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Jul 30 21:00:53 proxmox kernel: I/O error, dev sdd, sector 6438525440 op 0x0:(READ) flags 0xa00000 phys_seg 1 prio class 0
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 CDB: Read(16) 88 00 00 00 00 01 7f c4 1a 00 00 00 00 08 00 00
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=30s
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:1: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: sd 4:0:0:0: Device offlined - not ready after error recovery
Jul 30 21:00:53 proxmox kernel: scsi host4: uas_eh_device_reset_handler FAILED to get lock err -19
Jul 30 21:00:53 proxmox kernel: scsi host4: uas_eh_device_reset_handler FAILED err -19
Jul 30 21:00:52 proxmox kernel: usb 4-1: device firmware changed
Jul 30 21:00:52 proxmox kernel: usb 4-1: reset SuperSpeed USB device number 7 using xhci_hcd
Jul 30 21:00:52 proxmox kernel: scsi host4: uas_eh_device_reset_handler start
Jul 30 21:00:52 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 CDB: Read(16) 88 00 00 00 00 01 7f c4 1a 00 00 00 00 08 00 00
Jul 30 21:00:52 proxmox kernel: sd 4:0:0:0: [sdd] tag#15 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN 
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 CDB: Read(16) 88 00 00 00 00 02 21 f8 3f 30 00 00 00 28 00 00
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#14 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN 
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 CDB: Read(16) 88 00 00 00 00 02 21 bb 90 60 00 00 02 00 00 00
Jul 30 21:00:41 proxmox kernel: sd 4:0:0:0: [sdd] tag#13 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN 
Jul 30 21:00:35 proxmox kernel: sd 4:0:0:1: [sde] tag#11 CDB: Write(10) 2a 00 3a 04 11 d0 00 00 18 00
Jul 30 21:00:35 proxmox kernel: sd 4:0:0:1: [sde] tag#11 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:1: [sde] tag#8 CDB: Read(10) 28 00 31 01 09 28 00 00 08 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:1: [sde] tag#8 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 CDB: Read(16) 88 00 00 00 00 01 7f c0 8d 10 00 00 00 08 00 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#10 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN 
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cf e8 00 00 00 08 00 00
Jul 30 21:00:30 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
Jul 30 20:59:59 proxmox kernel: critical medium error, dev sdd, sector 6653857080 op 0x0:(READ) flags 0x4000 phys_seg 128 prio class 0
Jul 30 20:59:59 proxmox kernel: blk_print_req_error: 47 callbacks suppressed
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 CDB: Read(16) 88 00 00 00 00 01 8c 99 cd 38 00 00 04 00 00 00
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 Add. Sense: Unrecovered read error
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 Sense Key : Medium Error [current] 
Jul 30 20:59:59 proxmox kernel: sd 4:0:0:0: [sdd] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jul 30 20:56:01 proxmox postfix/smtp[3945942]: 2F670200A1A: to=<proxmox.snowcap946@passmail.net>, relay=mx2.simplelogin.co[176.119.200.136]:25, delay=330448, delays=330369/0.01/79/0, dsn=4.4.2, status=deferred (l>
Jul 30 20:55:42 proxmox postfix/smtp[3945942]: 2F670200A1A: lost connection with mx2.simplelogin.co[185.205.70.136] while receiving the initial server greeting

25
Docker Swarm networking vs Docker Compose (sh.itjust.works)
submitted 7 months ago* (last edited 7 months ago) by ohshit604@sh.itjust.works to c/selfhosted@lemmy.world
5 comments fedilink
 

Evening y’all

I’ll try to keep it brief, I need to move my reverse proxy (traefik) to another machine and I’m opting to utilize Docker Swarm for the first time this way I’m not exposing a bunch of ports on my main server over my network, so ideally I’d like to have almost everything listening on local host while traefik does it’s thing in the background

Now I gotta ask, is Docker Swarm the best way to go about this? I know very little about Kubernetes and from what I’ve read/watched it seems like Swarm was designed for this very purpose however, I could be entirely wrong here.

What are some key changes that differ typical Compose files from Swarm?

Snippet of my current compose file:

services:
  homepage:
    image: ghcr.io/gethomepage/homepage
    hostname: homepage
    container_name: homepage
    networks:
      main:
        ipv4_address: 172.18.0.2
    environment:
      PUID: 0 # optional, your user id
      PGID: 0 # optional, your group id
      HOMEPAGE_ALLOWED_HOSTS: MY.DOMAIN,*
    ports:
      - '127.0.0.1:80:3000'
    volumes:
      - ./config/homepage:/app/config # Make sure your local config directory exists
      - /var/run/docker.sock:/var/run/docker.sock #:ro # optional, for docker integrations
      - /home/user/Pictures:/app/public/icons
    restart: unless-stopped
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.homepage.rule=Host(`MY.DOMAIN`)"
      - "traefik.http.routers.homepage.entrypoints=https"
      - "traefik.http.routers.homepage.tls=true"
      - "traefik.http.services.homepage.loadbalancer.server.port=3000"
      - "traefik.http.routers.homepage.middlewares=fail2ban@file"
  traefik:
    image: traefik:v3.2
    container_name: traefik
    hostname: traefik
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    networks:
      main:
        ipv4_address: 172.18.0.26
    ports:
      # Listen on port 80, default for HTTP, necessary to redirect to HTTPS
      - target: 80
        published: 55262
        mode: host
      # Listen on port 443, default for HTTPS
      - target: 443
        published: 57442
        mode: host
    environment:
      CF_DNS_API_TOKEN_FILE: /run/secrets/cf_api_token # note using _FILE for docker secrets
      # CF_DNS_API_TOKEN: ${CF_DNS_API_TOKEN} # if using .env
      TRAEFIK_DASHBOARD_CREDENTIALS: ${TRAEFIK_DASHBOARD_CREDENTIALS}
    secrets:
      - cf_api_token
    env_file: .env # use .env
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./config/traefik/traefik.yml:/traefik.yml:ro
      - ./config/traefik/acme.json:/acme.json
      # - ./opt:/opt
      #- ./config/traefik/config.yml:/config.yml:ro
      - ./config/traefik/custom-yml:/custom
      # - ./config/traefik/homebridge.yml:/homebridge.yml:ro
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.traefik.entrypoints=http"
      - "traefik.http.routers.traefik.rule=Host(`traefik.MY.DOMAIN`)"
      #- "traefik.http.middlewares.traefik-ipallowlist.ipallowlist.sourcerange=127.0.0.1/32, 192.168.1.0/24, 208.118.140.130, 172.18.0.0/16"
      #- "traefik.http.middlewares.traefik-auth.basicauth.users=${TRAEFIK_DASHBOARD_CREDENTIALS}"
      - "traefik.http.middlewares.traefik-https-redirect.redirectscheme.scheme=https"
      - "traefik.http.middlewares.sslheader.headers.customrequestheaders.X-Forwarded-Proto=https"
      - "traefik.http.routers.traefik.middlewares=traefik-https-redirect"
      - "traefik.http.routers.traefik-secure.entrypoints=https"
      - "traefik.http.routers.traefik-secure.rule=Host(`traefik.MY.DOMAIN`)"
      #- "traefik.http.routers.traefik-secure.middlewares=traefik-auth"
      - "traefik.http.routers.traefik-secure.tls=true"
      - "traefik.http.routers.traefik-secure.tls.certresolver=cloudflare"
      - "traefik.http.routers.traefik-secure.tls.domains[0].main=MY.DOMAIN"
      - "traefik.http.routers.traefik-secure.tls.domains[0].sans=*.MY.DOMAIN"
      - "traefik.http.routers.traefik-secure.service=api@internal"
      - "traefik.http.routers.traefik.middlewares=fail2ban@file"

networks:
  main:
    external: true
    ipam:
     config:
       - subnet: 172.18.0.0/16
         gateway: 172.18.0.1

I censored out my actual domain with MY.DOMAIN so if that confuses people i apologize.

Update:

So, I’ve came across an application called Traefik-Kop which essentially allows for swarm like communication between traefik and two docker engines.

This isn’t full-proof as I do have to expose ports over the main server however, this was the simplest way of achieving what I was going for.

I want to say thank you to everyone who has commented I haven’t had much time to respond to comments here but I have read them all, y’all’s insight is much appreciated!

Update 2:

People here suggest Pangolin however, I just spent the last 3 hours trying to integrate pangolin with the Traefik instance that I already have setup, it was not fun, i couldn’t figure out how Pangolin is able to communicate with Traefik if it doesn’t expose any ports or define docker labels, once I figured out Pangolins web-ui runs on 3002:3002 I was able to reverse proxy it however, when attempting to login I kept running into 404 errors.

I’ll give it another go when I’m no longer frustrated with it as it does seem like the best route for me to take.

14
Packages similar to Earlyoom? (sh.itjust.works)
submitted 1 year ago* (last edited 1 year ago) by ohshit604@sh.itjust.works to c/linux@lemmy.ml
8 comments fedilink
 

So recently I just come across Earlyoom and it has completely resolved my desktop crashing and better handles my memory, I was wondering if there is any other software that I’m missing that could potentially improve my systems resource handling?

Distro = Debian 12, KDE Plasma 5

view more: next ›