exwebjunkie

I posted my diagnostic file - and the persistent option was already turned on (as per my screenshot above); so unsure why it would not be appearing in the file on this basis?

Anyone have any ideas here?

I've taken a look and looks like this is setup correctly already (Mirror syslog to flash) - what are you expecting to see in the diagnostic file that isn't there? And does the screenshot below look correct?

Hmm let me take another look - I am pretty sure that I set this up; which is what the syslog-previous was (which has the previous day before the crash?); is this something different?

Hi there, I've been using Unraid for a while now - and more recently I've found that it goes unresponsive - and I have to do a hard-reboot - which I'm obviously concerned could cause issues with my drives etc. It's running with a AMD Ryzen 5 3600X 6-Core @ 3800 MHz. have no idea what is causing it- I did change my syslog a while ago so it stores the previous version but I can't see anything in the syslog-previous for the day of the error - it only really shows the startup logs (I've attached the latest file from yesterday) Anyone have any ideas how I can try and find out what is wrong? Worth noting I am using IPvlan not MacVLAN and don't have any VMs running (only docker containers). I've made sure that all my Dockers are up to date (some needed an update) after the last crash but seems like I'm just waiting for the inevitable right now; one thing I did think of is running a script to reboot every day (so at least it's being shut down the right way) but seems better to get to the root cause first.. tower-diagnostics-20240609-1649.zip

Worth noting I did move from IPVlan to macvlan - as one of the apps I was using needed a specific Mac address that I don't think IPVlan supports. I've seen some people say move to IPVlan but that would be the issue in doing this I guess...

Hi there, I seem to be getting some random shutdowns, mainly at night but not at any specific time from what I can tell - only started happening recently and hoping someone might be able to help identify. I have attached my diagnosis zp and last time I changed it so that the syslog is kept (syslog-previous.txt). It looks from reading this to have had a meltdown at 23:19 The server stays on but nothing works and I have to do a hard-reset to get it running again. Any help much appreciated! tower-diagnostics-20240330-0857.zip

Did you ever anywhere with fixing this? Having a similar issue.

So when you did this, did the IP's / "machines" for each docker show up in the machines section of tailscale - assume I would need this to be able to get their tailscape IPs? I followed all the advice but I only see my main NAS show up - nothing else - can connect to it via the tailscale IP but can't connect to anything else or see anything else..

Sorry for the newbie question. My network is running on the 192.168.0.X network. I have Unraid set to 192.168.0.74 (with the web UI to port 84) All my dockers (well, most) are set with the br0 network and with dedicated IPs like 192.168.0.145 (for Sonarr for example). I have installed this plugin - and I can connect to unraid vs the "new" IP. I ran this command tailscale set --advertise-routes=192.168.0.0/24 and I can see in tailscale web gui that this has been accepted. BUT - I can't see any of my dockers that are on the br0 network - I thought they would be found due to being on the subnet that I setup. Any ideas what I need to change to make them appear so I can grab their IPs etc and connect to them? Thank you!

Sorry for a bit of a newbie question, but how would I go about installing python support for apache using this Docker? I think I need to add a2enmod cgid - is it possible to do this from the setup so I can do across multiple sites rather than doing any manual configuration?