Fiservedpi

Yep all "test" notifications work properly just not when it really counts! Lol, ok I'll try out the mirror syslog option to see what's going on thank you

Yes the battery is just for the Unraid server I've got other UPS for the "network", the network remains up

I've had a couple power issue recently and I've not received any UPS Alerts, I've got email and Pushbullet set up and tested to be working. Is there anything I might be missing? In order to receive an alert when the server goes on Battery.

Did you ever figure out what the "mixed HW and IP" Warning was about? I'm getting the same thing

Has this been resolved? Didn't have much luck with the Google machine. ```Tower kernel: igb 5 eth0: mixed HW and IP checksum settings```

i totally biffed it, old router ip range 192.168.86.0/24 new roter ip range 192.168.1.0/24, So gues what i did? went through every device manually and resetup rather than just editing the new ip range so everything got new ip's, needless to say its been about 2weeks and im almost at 100% again. Lesson Learned

I'll be getting a new router tomorrow and I want to make it as painless as possible, in order for my Unraid server to get the same IP address as the old router do I have have to configure a static IP in the new router? and fwd the same ports? Or is there anything else I should be aware of?

So I borked my whole docker setup today and I'm just getting this bot back up and running but I'm having trouble with the Sopranos is not "airing" but I'm personally still downloading my purchased content how can I get notified of new episodes added to my server? I tried the notifications include show but the Sopranos doesn't show up anywhere in the bot what should I do to make the bot discover it, P.S the show is visible in both sonarr and tautulli

You can stop this by adding blacklist amd64_edac_mod To the /lib/modprobe.d and /etc/modprobe.d/ create a new .conf, I named it amd64_edac_mod.conf then within that file place this blacklist amd64_edac_mod Source

Thank you @Squid

If you go to the beta can you go back to stable simply? I'm getting some crazy errors when trying to go back to stable. And my Cachē drive unmounted/unassigned itself ```Linux 5.7.2-Unraid. root@Tower:~# tail -f /var/log/syslog Jun 27 15:15:19 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:19 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:19 Tower kernel: veth3f1bd44: renamed from eth0 Jun 27 15:15:19 Tower kernel: br-341c40ac3595: port 1(vethde87652) entered disabled state : SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:23 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:23 Tower kernel: docker0: port 1(veth48c12f9) entered disabled state Jun 27 15:15:23 Tower kernel: device veth48c12f9 left promiscuous mode Jun 27 15:15:23 Tower kernel: docker0: port 1(veth48c12f9) entered disabled state Jun 27 15:15:24 Tower kernel: br-341c40ac3595: port 1(vethde87652) entered disabled state Jun 27 15:15:24 Tower kernel: device vethde87652 left promiscuous mode Jun 27 15:15:24 Tower kernel: br-341c40ac3595: port 1(vethde87652) entered disabled state Jun 27 15:15:24 Tower kernel: docker0: port 2(vethd184548) entered disabled state Jun 27 15:15:24 Tower kernel: device vethd184548 left promiscuous mode Jun 27 15:15:24 Tower kernel: docker0: port 2(vethd184548) entered disabled state Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:24 Tower kernel: vethd492f19: renamed from eth0 Jun 27 15:15:24 Tower kernel: device br0 left promiscuous mode Jun 27 15:15:24 Tower kernel: veth94e50e2: renamed from eth0 Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:24 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:27 Tower kernel: vethb5852b4: renamed from eth0 Jun 27 15:15:27 Tower kernel: docker0: port 6(vethcbd2e42) entered disabled state Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:27 Tower kernel: veth2262833: renamed from eth0 Jun 27 15:15:27 Tower kernel: docker0: port 3(vethb2d76f2) entered disabled state Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:27 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:29 Tower kernel: veth20b9485: renamed from eth0 Jun 27 15:15:29 Tower kernel: docker0: port 5(vethaabdc05) entered disabled state Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:15:29 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:15:37 Tower kernel: docker0: port 6(vethcbd2e42) entered disabled state Jun 27 15:15:37 Tower kernel: device vethcbd2e42 left promiscuous mode Jun 27 15:15:37 Tower kernel: docker0: port 6(vethcbd2e42) entered disabled state Jun 27 15:15:37 Tower kernel: docker0: port 3(vethb2d76f2) entered disabled state Jun 27 15:15:37 Tower kernel: device vethb2d76f2 left promiscuous mode Jun 27 15:15:37 Tower kernel: docker0: port 3(vethb2d76f2) port ........................................................................................................................................................................................................................................................................ :14 Tower root: error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory Jun 27 15:18:14 Tower root: cat: /var/run/libvirt/libvirtd.pid: No such file or directory Jun 27 15:18:14 Tower root: kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [1602b7c] Jun 27 15:18:16 Tower kernel: SQUASHFS error: Unable to read page, block 1602b7c, size 3a4c Jun 27 15:18:17 Tower root: /etc/rc.d/rc.libvirt: line 151: 7185 Bus error /sbin/modprobe -ra $MODULE $MODULES 2> /dev/null Jun 27 15:18:17 Tower root: virtlogd is not running... cache entry [1602b7c] Jun 27 15:18:17 Tow Jun 27 15:18:18 Tower avahi-dnsconfd[16049]: read(): EOF```

How do I remove/unsubscribe from the @watching role? Like I don't want to be notified when someone starts playback EDIT* nvm I got it !unlink {@user}

Oh ok I thought I double enrolled myself or something

How would I stop the doubles?

Yep I've implemented it thanks for the swift responses!✊