benty

Members
  • Posts

    4
  • Joined

  • Last visited

benty's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I'm having a problem with a UPS where it very briefly goes offline every minute or two. This is resulting in a notification and an email every time, so my inbox is flooded with these notifications. I'm not really sure where to go with troubleshooting the 'going offline' problem, so instead I hope to just get rid of the notifications. I believe I should be able to do this by editing the shell scripts called by apcupsd when UPS comms is lost or restored, located in /etc/apcupsd. I can edit these scripts, save them, then re-open to confirm the changes were saved, no problem, BUT after a reboot, the scripts have been overwritten and reverted to their original content. I recall I've seen this behaviour with other config files other than apcupsd before so the solution to this could help me in multiple ways. Perhaps this is just my linux n00b showing. Please do let me know if that's the case Thanks in advance!
  2. Hi Guys, I'm trying to save some electricity by scheduling my server to go to sleep overnight using the Dynamix S3 sleep plugin, but when I send it to sleep using the button on the dashboard, it just immediately wakes up again. Searching around for similar topics I found someone suggested disabling everything except power button in /proc/acpi/wakeup but this did not help unfortunately. You'll find the 'Enter sleep mode' event on line 1881 of the syslog. Hoping you guys have some advice for me. Thanks in advance! albus-diagnostics-20191218-1253.zip
  3. I've been fiddling around with network settings a bit today and after I was done I found that clicking the 'webUI' button on a docker container just opens 'about:blank'. This was working prior to my messing with network settings, but I can't see why that would have caused it. EDIT: Attached logs. albus-diagnostics-20180505-2238.zip EDIT2: I tried connecting the server's 2nd NIC to the lan and the problem went away. Dockers now bind to the IP of the second NIC... Looks like somewhere in my fiddling I somehow managed to set up eth0 on br0 and eth1 on br1 rather than both interfaces on br0 like it used to be... I'm not sure how to go about fixing that - suggestions welcome there.