Quote from: urnzwy on May 04, 2018, 07:58:29 PM

Quote from: Stubo on May 04, 2018, 07:51:26 PM

Quote from: urnzwy on May 04, 2018, 07:03:59 PM

Found them! There is a lot in there... But I am not sure what I am looking for. There is some warnings I see in there, all the files look identical almost. Are you in the discord? I could send it to you on there? This is the last portion of it.

I am not in the discord. There is going to be a LOT of stuff in the syslog and most of it you can ignore. What you want to do is to zero in on the entries just before it froze. This is all done by timestamps. You can also look for entries that are hard errors but those may prove to be red herrings.

If you notice there are syslogs going back about a week. syslog is from today, syslog.1 is going to be yesterday, syslog.2.gz is the archived syslog from the day before that, etc. For the gz ones, just use "gunzip " as root to unzip them so that you can read them.

So start by recalling the day and time of the last freeze(s), and then figure out which log it would be in based upon the timestamp of the syslogs. Next, open whichever one(s) those are and find that day/time. You should then see additional clues (probably errors) that were logged. Once you find them, we can go from there.

Updated the previous post to include the last portion of the files.

It froze every day and all the files looks the same, so whatever this issue is it just happens over and over again.

Let me see if I can make it more clear. Unlike some nvOC specific logs, Ubuntu [any unix system] syslogs are written to constantly, so grabbing the last (most recent) part of one is unlikely to be helpful in diagnosing your problem. Instead, what you want to do is view the logs with an editor like vi and scroll through it until you find the day and time of when the freeze occurred.

For example, I had an issue with one of my miners on Wednesday morning. My pool indicated that it was not mining so tried to login via ssh but could not. I physically checked on the machine and it was running but I could not access it remotely (I don't have a display connected to it). So, I powered it down for a few minutes and then powered it back up. It came up just fine and started mining again. Of course, I wanted to find out what had happened so I started looking at my syslog for that day and at that time - sometime after 9:30am on May 2. When I found that part of the log, I saw this:

Code:

May 2 07:35:02 Miner1 anacron[30615]: Job `cron.daily' terminated
May 2 07:35:02 Miner1 anacron[30615]: Normal exit (1 job run)
May 2 08:17:01 Miner1 CRON[16925]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 2 08:24:20 Miner1 systemd[1]: Starting Cleanup of Temporary Directories...
May 2 08:24:20 Miner1 systemd-tmpfiles[19789]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
May 2 08:24:20 Miner1 systemd[1]: Started Cleanup of Temporary Directories.
May 2 09:17:01 Miner1 CRON[8112]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
[b]May 2 09:46:17 Miner1 avahi-daemon[821]: Withdrawing address record for 192.168.1.165 on enp0s31f6.
May 2 09:46:17 Miner1 avahi-daemon[821]: Leaving mDNS multicast group on interface enp0s31f6.IPv4 with address 192.168.1.165.
May 2 09:46:17 Miner1 avahi-daemon[821]: Interface enp0s31f6.IPv4 no longer relevant for mDNS.
[/b]May 2 10:17:01 Miner1 CRON[23962]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 2 10:23:30 Miner1 systemd[1]: Starting Daily apt download activities...
May 2 10:23:30 Miner1 systemd[1]: Started Daily apt download activities.
May 2 11:17:01 Miner1 CRON[32329]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 2 12:17:01 Miner1 CRON[8511]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 2 12:43:29 Miner1 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="846" x-info="http://www.rsyslog.com"] start

So for some still to be determined reason, my machine decided to withdraw its DNS registration from my DNS which resulted in loss of name resolution and connectivity.

While not at all relevant to your situation, I just wanted to use this example of an issue that I had, how I found it, and what caused it.

I hope this helps.