January 15, 20215 yr Hello, For the past couple of weeks my server has been randomly crashing / freezing. When the server freezes I have no access at all, not through SSH not directly via the server and no remote access. The system stays operating between 18 and 48 hours, when it is running I see no issues at all. I pulled a diagnostic after rebooting it today that I am attaching. I am hoping that someone can advise me on where to start looking in order to fix this issue. Thanks in advance. Chas tower-diagnostics-20210115-1646.zip
January 16, 20215 yr Author I'm sorry it seems that nothing wants to work for me, here is my settings, I believe that I followed the instructions correctly. I go to the syslog1 folder and it is empty - shouldn't I see a file syslog-192.168.1.2.log ? What am I missing? I tried using a different share and no Joy.
January 16, 20215 yr Author I'm sorry it seems that nothing wants to work for me, here is my settings, I believe that I followed the instructions correctly. I go to the syslog1 folder and it is empty - shouldn't I see a file syslog-192.168.1.2.log ? What am I missing? I tried using a different share and no Joy. I added the syslog showing the errors, not sure if it will help or not. Also I am trying to get the syslog fixed using, this fix failed. it recreated the files in boot/config without any improvement. Should I delete them in Boot/config and delete the rsyslog.conf in /etc as well? waiting for restart. But I thought I'd add that the server also has a shutdown issue. I stopped the array about 10 minutes ago and it is still "Syncing Filesystems" not sure if that is important or not. tower-syslog-20210116-1416.zip Edited January 16, 20215 yr by kysdaddy
January 16, 20215 yr Community Expert You need to update to latest v6.9-rc, also see this: https://forums.unraid.net/bug-reports/prereleases/solved-690-beta25-through-690-rc1-syslog-server-broken-error-in-logs-r1003/?do=findComment&comment=12179
January 16, 20215 yr Author Ok, I did the update, still not seeing the syslog file being created. What should I try next, delete the files again and reboot? These are the last entries on my syslog. I tried setting the syslog server to mirror to the Flash, but that doesn't seem to work either Edited January 16, 20215 yr by kysdaddy
January 16, 20215 yr Author OK. I was able to get a kiwi syslog server setup on one of my window machines that will hopefully capture the error next time I freeze up.
January 16, 20215 yr Author Here are the logs after/during a freeze. I hope that this makes more sense to someone out there. Chas
January 16, 20215 yr Author Sorry. 14:38:50 to 15:29:07 15:50:56 was when I did a hard powerswitch reboot. SyslogCatchAll-2021-01-16.txt
January 17, 20215 yr Community Expert NIC driver crashed, if you can try with a different NIC, Intel recommended.
January 17, 20215 yr Author Thank you JorgeB. I switched out the nic card and put in an intel card. Hopefully that will stop the freezing. I'm guessing that the nic card isn't the problem with my system shutting down. When I click on any of the shutdown icons in the gui or tell the system to reboot in a terminal the system doesn't shutdown. I have let it run up to a half an hour and nothing happens. If I stop the array the process seems to stick on sync filesystems. Attached is a diagnostic that I pulled after trying to switch off, waiting a few minutes, not all that long but the system did not show that it had switched to shutting down. I stopped the array and then pulled the diagnostic. Any suggestions are appreciated tower-diagnostics-20210117-0951.zip
January 18, 20215 yr Community Expert 19 hours ago, kysdaddy said: I'm guessing that the nic card isn't the problem with my system shutting down. Not likely, several possible reasons for that, start with booting in safe mode and see if shutdown works normally.
January 18, 20215 yr Author Unfortunately the server was frozen again when I woke up this morning. I copied and pasted the syslog entries from the first error to the reboot. I added a diag since the syslogs mention read errors on disk 1 freeze2.txt tower-diagnostics-20210118-0815.zip
January 18, 20215 yr Community Expert Macvlan call traces are usually the result of having dockers with a custom IP address, see below: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-to-dockers/
January 30, 20215 yr Author On 1/18/2021 at 6:04 PM, kysdaddy said: I have shutdown Pihole, will see if that stops the issues. thx Problem solved, Pihole/macvlan was the issue. Thanks all
Archived
This topic is now archived and is closed to further replies.