Are you getting an error? I still haven't figured out how to get it running and I've been using nvOC for a long time.. Waiting for one of the smarter guys to chime in on my issue.

Follow these instructions and you'll be good to go! You need to connect to the rig itself to update. Open Quake Terminal and use the first window, then copy and paste. Simple as that.

https://linuxize.com/post/how-to-install-teamviewer-on-ubuntu-18-04/

Hey guys!

Anyone catch this error before when trying to get the Salfter Nicehash Profit switching working?

This is in the "Auto_Switch" tab of the Quake Terminal
- The following arguments were not expected: -O -S -SP

This is showing up under the miner, then Foreman does it's thing all over again until the rig restarts.
- ERROR: Error parsing assignment '[gpu:0]/GPUGraphicsClockOffset[3]=' (No attribute value specified).

I have all my power levels set, over-clocking, etc.. So I'm a bit lost on what to try next. No issues running the Nicehash algo's by themselves either as well as my other coins. The WTM numbers that come back aren't close to what I see on the website either. Again, not sure what the dealio is.

You connect your relay in NO & COM to the PWR pins or the Reset pins?

OK...

So update time. It turns out that the issue all along was a faulty graphics card. In moving to SMOS, I had left the mining screen up on my computer and just happen to walk into an error on GPU 12. The rig crashed, and it took the other rig out as well. We replaced the riser and it crashed again. SO we removed the card completely.

It's been over 4 days running constantly for BOTH rigs and not a single crash or issue..

With this. We are moving back to a fresh copy of nvOC tomorrow as I really do dislike SMOS. But I wanted to update all. So, check your GPU's if you have a crashing issue you can't figure out! We are going to try and replace all other parts and re-insert the card and hope it's not an actual issue with the card. But I have a feeling it is. So it may be going back to TRY and get a replacement. I guess we will see.

Well after much frustration with my rigs crashing, I thought I had it figured out but the problem continued.

Originally I had setup SMOS but really didn't care for the simplicity of the interface or should I say lack there of and found nvOC.

As my rigs are remote in another state, it was even more difficult to diagnose.

For ease, I had my brother-in-law load up SMOS on both rigs and they have been running for over 4 days with under-volting (100W 1070 & 1070 Ti / 175W 1080 & 1080 Ti) and overclocking (-50 core 1070/1070 Ti, 200 core 1080 & 1080 Ti with 1100 Mem for the 1070/1070 Ti and 1000 for the 1080 & 1080 Ti). Mining ETH.

Whatever my issue was, it was an issue within nvOC. The question is why and what was causing the crashing issue.

Later this week, I plan on loading up a fresh copy of nvOC and see if the issue continues. Unfortunately I cleared the USB sticks we were using that had the nvOC OS on them. Had I though about it, it would have been good to have them to see if anyone could identify any issues. The only thing I really did was re-compile the miners.

It is difficult to pin-point when the issue really showed up as we were having to re-set the miners at least once a week and then eventually even would crash once daily. Both at the same time even on different algorithms. I tried multiple different mining programs, no over clocks, half overclock, full overclock. Nothing seemed to matter. 18-24 hours the crash was inevitable.

I wish I had more information on this, but wanted to get it into the forum in-case this ever happened to anyone else. I will update once I re-load up nvOC and see what happens.

I would like to give a special shout out to Stubo for so far helping me solve my crashing issue. Through multiple replies within the forum and additional through PM. Neither of my two 13 card Nvidia rigs has crashed in over 33 hours. Up from 12-18ish hours until crashing and freezing.

I had both machines at a 0/0 core/memory overlock running at 120W of power (1070 / 1070 Ti's) and 175W (1080 / 1080Ti).

I did not re-name the rigs, so both were named m1@m1-Desktop. This may have been causing an issue with the DNS registration (correct me if I am wrong Stubo).

The second thing I did was set my core to -100 and memory to +700 for mining ETH. The negative core suggested by Stubo. But keep the same power input. Nothing else was modified or changed.

I not only had an increase in my Mh/s (from 27 to 29.5) but the rigs seem stable thus far.

I will keep everyone posted if I come across anything else as I plan on setting back the original lack of overclock to see if there was any effect there or if the non-renaming was the issue. 

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.

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.

May  2 08:54:13 m1-desktop rtkit-daemon[2515]: Successfully made thread 2514 of process 2514 (n/a) owned by '1000' high priority at nice level -11.
May  2 08:54:13 m1-desktop rtkit-daemon[2515]: Supervising 1 threads of 1 processes of 1 users.
May  2 08:54:13 m1-desktop dbus[821]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
May  2 08:54:13 m1-desktop systemd[1]: Starting Daemon for power management...
May  2 08:54:13 m1-desktop gnome-session[2410]: gnome-session-binary[2410]: WARNING: Could not parse desktop file print-applet.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session-binary[2410]: WARNING: Could not parse desktop file print-applet.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session[2410]: gnome-session-binary[2410]: WARNING: Could not parse desktop file indicator-printers.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session-binary[2410]: WARNING: Could not parse desktop file indicator-printers.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop dbus[821]: [system] Successfully activated service 'org.freedesktop.UPower'
May  2 08:54:13 m1-desktop systemd[1]: Started Daemon for power management.
May  2 08:54:13 m1-desktop gnome-session[2410]: gnome-session-binary[2410]: WARNING: Could not parse desktop file gnome-user-share-webdav.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session-binary[2410]: WARNING: Could not parse desktop file gnome-user-share-webdav.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session[2410]: gnome-session-binary[2410]: WARNING: Could not parse desktop file deja-dup-monitor.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session-binary[2410]: WARNING: Could not parse desktop file deja-dup-monitor.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session[2410]: gnome-session-binary[2410]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session-binary[2410]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session[2410]: gnome-session-binary[2410]: WARNING: Could not parse desktop file zeitgeist-datahub.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session-binary[2410]: WARNING: Could not parse desktop file zeitgeist-datahub.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session[2410]: gnome-session-binary[2410]: WARNING: Could not parse desktop file onboard-autostart.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session-binary[2410]: WARNING: Could not parse desktop file onboard-autostart.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session[2410]: gnome-session-binary[2410]: WARNING: Could not parse desktop file gnome-user-share-obexpush.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session-binary[2410]: WARNING: Could not parse desktop file gnome-user-share-obexpush.desktop or it references a not found TryExec binary
May  2 08:54:13 m1-desktop gnome-session[2410]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May  2 08:54:13 m1-desktop gnome-session[2410]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May  2 08:54:13 m1-desktop gnome-session[2410]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May  2 08:54:14 m1-desktop dbus[821]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
May  2 08:54:14 m1-desktop systemd[1]: Starting Manage, Install and Generate Color Profiles...
May  2 08:54:14 m1-desktop dbus[821]: [system] Successfully activated service 'org.freedesktop.ColorManager'
May  2 08:54:14 m1-desktop systemd[1]: Started Manage, Install and Generate Color Profiles.
May  2 08:54:15 m1-desktop rtkit-daemon[2515]: Supervising 1 threads of 1 processes of 1 users.
May  2 08:54:15 m1-desktop rtkit-daemon[2515]: Successfully made thread 2664 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:15 m1-desktop rtkit-daemon[2515]: Supervising 2 threads of 1 processes of 1 users.
May  2 08:54:16 m1-desktop dbus[821]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May  2 08:54:16 m1-desktop systemd[1]: Starting Disk Manager...
May  2 08:54:16 m1-desktop udisksd[2670]: udisks daemon version 2.1.7 starting
May  2 08:54:16 m1-desktop dbus[821]: [system] Successfully activated service 'org.freedesktop.UDisks2'
May  2 08:54:16 m1-desktop systemd[1]: Started Disk Manager.
May  2 08:54:16 m1-desktop udisksd[2670]: Acquired the name org.freedesktop.UDisks2 on the system message bus
May  2 08:54:16 m1-desktop udisksd[2670]: Cleaning up mount point /media/m1/12D3-A869 (device 8:1 is not mounted)
May  2 08:54:16 m1-desktop org.gtk.vfs.AfcVolumeMonitor[2270]: Volume monitor alive
May  2 08:54:17 m1-desktop rtkit-daemon[2515]: Supervising 2 threads of 1 processes of 1 users.
May  2 08:54:17 m1-desktop rtkit-daemon[2515]: Successfully made thread 2714 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:17 m1-desktop rtkit-daemon[2515]: Supervising 3 threads of 1 processes of 1 users.
May  2 08:54:17 m1-desktop org.gnome.ScreenSaver[2270]: ** Message: Lost the name, shutting down.
May  2 08:54:19 m1-desktop rtkit-daemon[2515]: Supervising 3 threads of 1 processes of 1 users.
May  2 08:54:19 m1-desktop rtkit-daemon[2515]: Successfully made thread 2773 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:19 m1-desktop rtkit-daemon[2515]: Supervising 4 threads of 1 processes of 1 users.
May  2 08:54:22 m1-desktop rtkit-daemon[2515]: Supervising 4 threads of 1 processes of 1 users.
May  2 08:54:22 m1-desktop rtkit-daemon[2515]: Successfully made thread 2776 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:22 m1-desktop rtkit-daemon[2515]: Supervising 5 threads of 1 processes of 1 users.
May  2 08:54:26 m1-desktop rtkit-daemon[2515]: Supervising 5 threads of 1 processes of 1 users.
May  2 08:54:26 m1-desktop rtkit-daemon[2515]: Successfully made thread 2777 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:26 m1-desktop rtkit-daemon[2515]: Supervising 6 threads of 1 processes of 1 users.
May  2 08:54:32 m1-desktop rtkit-daemon[2515]: Supervising 6 threads of 1 processes of 1 users.
May  2 08:54:32 m1-desktop rtkit-daemon[2515]: Successfully made thread 2778 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:32 m1-desktop rtkit-daemon[2515]: Supervising 7 threads of 1 processes of 1 users.
May  2 08:54:34 m1-desktop rtkit-daemon[2515]: Supervising 7 threads of 1 processes of 1 users.
May  2 08:54:34 m1-desktop rtkit-daemon[2515]: Successfully made thread 2779 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:34 m1-desktop rtkit-daemon[2515]: Supervising 8 threads of 1 processes of 1 users.
May  2 08:54:37 m1-desktop rtkit-daemon[2515]: Supervising 8 threads of 1 processes of 1 users.
May  2 08:54:37 m1-desktop rtkit-daemon[2515]: Successfully made thread 2780 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:37 m1-desktop rtkit-daemon[2515]: Supervising 9 threads of 1 processes of 1 users.
May  2 08:54:39 m1-desktop rtkit-daemon[2515]: Supervising 9 threads of 1 processes of 1 users.
May  2 08:54:39 m1-desktop rtkit-daemon[2515]: Successfully made thread 2781 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:39 m1-desktop rtkit-daemon[2515]: Supervising 10 threads of 1 processes of 1 users.
May  2 08:54:41 m1-desktop rtkit-daemon[2515]: Supervising 10 threads of 1 processes of 1 users.
May  2 08:54:41 m1-desktop rtkit-daemon[2515]: Successfully made thread 2782 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:41 m1-desktop rtkit-daemon[2515]: Supervising 11 threads of 1 processes of 1 users.
May  2 08:54:43 m1-desktop rtkit-daemon[2515]: Supervising 11 threads of 1 processes of 1 users.
May  2 08:54:43 m1-desktop rtkit-daemon[2515]: Successfully made thread 2786 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:43 m1-desktop rtkit-daemon[2515]: Supervising 12 threads of 1 processes of 1 users.
May  2 08:54:45 m1-desktop rtkit-daemon[2515]: Supervising 12 threads of 1 processes of 1 users.
May  2 08:54:45 m1-desktop rtkit-daemon[2515]: Successfully made thread 2787 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:45 m1-desktop rtkit-daemon[2515]: Supervising 13 threads of 1 processes of 1 users.
May  2 08:54:47 m1-desktop rtkit-daemon[2515]: Supervising 13 threads of 1 processes of 1 users.
May  2 08:54:47 m1-desktop rtkit-daemon[2515]: Successfully made thread 2788 of process 2514 (n/a) owned by '1000' RT at priority 5.
May  2 08:54:47 m1-desktop rtkit-daemon[2515]: Supervising 14 threads of 1 processes of 1 users.
May  2 08:54:48 m1-desktop pulseaudio[2514]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
May  2 08:54:48 m1-desktop rtkit-daemon[2515]: Successfully made thread 2790 of process 2790 (n/a) owned by '1000' high priority at nice level -11.
May  2 08:54:48 m1-desktop rtkit-daemon[2515]: Supervising 15 threads of 2 processes of 1 users.
May  2 08:54:48 m1-desktop pulseaudio[2790]: [pulseaudio] pid.c: Daemon already running.
May  2 08:54:48 m1-desktop rtkit-daemon[2515]: Successfully made thread 2796 of process 2796 (n/a) owned by '1000' high priority at nice level -11.
May  2 08:54:48 m1-desktop rtkit-daemon[2515]: Supervising 15 threads of 2 processes of 1 users.
May  2 08:54:48 m1-desktop pulseaudio[2796]: [pulseaudio] pid.c: Daemon already running.
May  2 08:54:48 m1-desktop dbus[821]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
May  2 08:54:48 m1-desktop systemd[1]: Starting Locale Service...
May  2 08:54:48 m1-desktop gnome-session[2410]: (nautilus:2808): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
May  2 08:54:48 m1-desktop gnome-session[2410]: (nautilus:2808): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
May  2 08:54:48 m1-desktop dbus[821]: [system] Successfully activated service 'org.freedesktop.locale1'
May  2 08:54:48 m1-desktop systemd[1]: Started Locale Service.
May  2 08:54:48 m1-desktop gnome-session[2410]: (nautilus:2808): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
May  2 08:54:48 m1-desktop gnome-session[2410]: (nautilus:2808): GLib-GObject-WARNING **: invalid (NULL) pointer instance
May  2 08:54:48 m1-desktop gnome-session[2410]: (nautilus:2808): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
May  2 08:54:48 m1-desktop gnome-session[2410]: (process:2814): indicator-application-service-WARNING **: Unable to get watcher name 'org.kde.StatusNotifierWatcher'
May  2 08:54:48 m1-desktop gnome-session[2410]: (process:2814): indicator-application-service-WARNING **: Name Lost
May  2 08:54:48 m1-desktop gnome-session-binary[2410]: Entering running state
May  2 08:54:48 m1-desktop kernel: [  217.746122] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
May  2 08:54:48 m1-desktop udisksd[2670]: Mounted /dev/sda1 at /media/m1/12D3-A869 on behalf of uid 1000
May  2 08:54:48 m1-desktop dbus[821]: [system] Activating service name='org.freedesktop.fwupd' (using servicehelper)
May  2 08:54:49 m1-desktop org.freedesktop.fwupd[821]: (fwupd:2860): Fu-WARNING **: Failed to coldplug: UEFI firmware updating not supported
May  2 08:54:49 m1-desktop dbus[821]: [system] Successfully activated service 'org.freedesktop.fwupd'
May  2 08:54:49 m1-desktop gnome-session[2410]: (guake:2809): libglade-WARNING **: unknown attribute `swapped' for <signal>.
May  2 08:54:49 m1-desktop gnome-session[2410]: message repeated 21 times: [ (guake:2809): libglade-WARNING **: unknown attribute `swapped' for <signal>.]
May  2 08:54:49 m1-desktop gnome-session[2410]: INFO:guake.guake_app:Logging configuration complete
May  2 08:54:49 m1-desktop gnome-session[2410]: /usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
May  2 08:54:49 m1-desktop gnome-session[2410]:   self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)
May  2 08:54:53 m1-desktop dbus[821]: [system] Activating service name='org.debian.apt' (using servicehelper)
May  2 08:54:53 m1-desktop AptDaemon: INFO: Initializing daemon
May  2 08:54:53 m1-desktop org.debian.apt[821]: 08:54:53 AptDaemon [INFO]: Initializing daemon
May  2 08:54:53 m1-desktop dbus[821]: [system] Successfully activated service 'org.debian.apt'
May  2 08:54:53 m1-desktop AptDaemon.PackageKit: INFO: Initializing PackageKit compat layer
May  2 08:54:53 m1-desktop org.debian.apt[821]: /usr/lib/python3/dist-packages/aptdaemon/worker/pkworker.py:35: PyGIWarning: PackageKitGlib was imported without specifying a version first. Use gi.require_version('PackageKitGlib', '1.0') before import to ensure that the right version gets loaded.
May  2 08:54:53 m1-desktop org.debian.apt[821]:   from gi.repository import PackageKitGlib as pk
May  2 08:54:53 m1-desktop org.debian.apt[821]: 08:54:53 AptDaemon.PackageKit [INFO]: Initializing PackageKit compat layer
May  2 08:54:53 m1-desktop AptDaemon: INFO: UpdateCache() was called
May  2 08:54:53 m1-desktop org.debian.apt[821]: 08:54:53 AptDaemon [INFO]: UpdateCache() was called
May  2 08:54:53 m1-desktop gnome-session[2410]: (gnome-software:2822): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
May  2 08:54:53 m1-desktop AptDaemon.Trans: INFO: Queuing transaction /org/debian/apt/transaction/3c2c7e9039dd4e919f975e6a7dba4e3f
May  2 08:54:53 m1-desktop org.debian.apt[821]: 08:54:53 AptDaemon.Trans [INFO]: Queuing transaction /org/debian/apt/transaction/3c2c7e9039dd4e919f975e6a7dba4e3f
May  2 08:54:53 m1-desktop AptDaemon.Worker: INFO: Simulating trans: /org/debian/apt/transaction/3c2c7e9039dd4e919f975e6a7dba4e3f
May  2 08:54:53 m1-desktop org.debian.apt[821]: 08:54:53 AptDaemon.Worker [INFO]: Simulating trans: /org/debian/apt/transaction/3c2c7e9039dd4e919f975e6a7dba4e3f
May  2 08:54:53 m1-desktop AptDaemon.Worker: INFO: Processing transaction /org/debian/apt/transaction/3c2c7e9039dd4e919f975e6a7dba4e3f
May  2 08:54:53 m1-desktop org.debian.apt[821]: 08:54:53 AptDaemon.Worker [INFO]: Processing transaction /org/debian/apt/transaction/3c2c7e9039dd4e919f975e6a7dba4e3f
May  2 08:54:54 m1-desktop AptDaemon.Worker: INFO: Updating cache
May  2 08:54:54 m1-desktop org.debian.apt[821]: 08:54:54 AptDaemon.Worker [INFO]: Updating cache
May  2 08:55:07 m1-desktop AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/3c2c7e9039dd4e919f975e6a7dba4e3f
May  2 08:55:07 m1-desktop org.debian.apt[821]: 08:55:07 AptDaemon.Worker [INFO]: Finished transaction /org/debian/apt/transaction/3c2c7e9039dd4e919f975e6a7dba4e3f
May  2 08:55:51 m1-desktop gnome-session[2410]: ** (update-notifier:3760): WARNING **: log file empty (logrotate?) /var/log/dpkg.log
May  2 08:55:51 m1-desktop gnome-session[2410]: ** (update-notifier:3760): WARNING **: log file empty (logrotate?) /var/log/apt/term.log
May  2 08:56:22 m1-desktop anacron[771]: Job `cron.daily' started
May  2 08:56:22 m1-desktop anacron[3949]: Updated timestamp for job `cron.daily' to 2018-05-02
May  2 08:56:22 m1-desktop cracklib: no dictionary update necessary.
May  2 08:56:22 m1-desktop systemd[1]: Reloading LSB: Apache2 web server.
May  2 08:56:22 m1-desktop apache2[4008]:  * Reloading Apache httpd web server apache2
May  2 08:56:22 m1-desktop apache2[4008]:  *
May  2 08:56:22 m1-desktop systemd[1]: Reloaded LSB: Apache2 web server.
May  2 08:56:23 m1-desktop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="781" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

m1@m1-desktop:~$ cat /etc/logrotate.d/rsyslog
/var/log/syslog
{
   rotate 7
   daily
   missingok
   notifempty
   delaycompress
   compress
   postrotate
      invoke-rc.d rsyslog rotate > /dev/null
   endscript
}

/var/log/mail.info
/var/log/mail.warn
/var/log/mail.err
/var/log/mail.log
/var/log/daemon.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/lpr.log
/var/log/cron.log
/var/log/debug
/var/log/messages
{
   rotate 4
   weekly
   missingok
   notifempty
   compress
   delaycompress
   sharedscrip

m1@m1-desktop:~$ ps -ef |grep rsys
syslog     774     1  0 08:06 ?        00:00:00 /usr/sbin/rsyslogd -n
m1        8535  2790  0 11:04 pts/17   00:00:00 grep --color=auto rsys
m1@m1-desktop:~$ /etc/logrotate.d/rsyslog?
bash: /etc/logrotate.d/rsyslog?: No such file or directory
m1@m1-desktop:~$ ll /var/log
total 6372
drwxrwxr-x 13 root              syslog    4096 May  4 08:09 ./
drwxr-xr-x 16 root              root      4096 Feb  9 13:08 ../
-rw-r--r--  1 root              root         0 Jan 19 01:22 alternatives.log
-rw-r--r--  1 root              root      5119 Dec 17 07:39 alternatives.log.1
drwxr-x---  2 root              adm       4096 May  4 07:43 apache2/
-rw-r-----  1 root              adm          0 Apr 17  2017 apport.log
drwxr-xr-x  2 root              root      4096 Mar  1 07:35 apt/
-rw-r-----  1 syslog            adm     123439 May  4 11:03 auth.log
-rw-r-----  1 syslog            adm      70998 Apr 29 07:30 auth.log.1
-rw-r-----  1 syslog            adm      19864 Apr 23 07:30 auth.log.2.gz
-rw-r-----  1 syslog            adm       8966 Apr 15 07:30 auth.log.3.gz
-rw-r-----  1 syslog            adm       3062 Apr  9 07:30 auth.log.4.gz
-rw-r--r--  1 root              root      3649 May  4 08:06 boot.log
-rw-r--r--  1 root              root     57457 Jul 19  2016 bootstrap.log
-rw-------  1 root              utmp         0 May  1 07:35 btmp
-rw-------  1 root              utmp         0 Apr  1 07:35 btmp.1
drwxr-xr-x  2 root              root      4096 Dec 17 08:03 cups/
drwxr-xr-x  2 root              root      4096 Apr 26  2016 dist-upgrade/
-rw-r-----  1 root              adm         31 Jul 19  2016 dmesg
-rw-r--r--  1 root              root         0 Apr  8 09:56 dpkg.log
-rw-r--r--  1 root              root      4135 Dec 20 06:44 dpkg.log.1
-rw-r--r--  1 root              root     32032 Oct 25  2017 faillog
-rw-r--r--  1 root              root      4042 Aug 18  2017 fontconfig.log
drwxr-xr-x  2 root              root      4096 Jul 19  2016 fsck/
-rw-r--r--  1 root              root      4919 May  4 08:06 gpu-manager.log
drwxrwxr-x  2 root              root      4096 Dec 17 08:03 installer/
-rw-r-----  1 syslog            adm    1696023 May  4 10:43 kern.log
-rw-r-----  1 syslog            adm    2234016 Apr 30 18:58 kern.log.1
-rw-r-----  1 syslog            adm     454234 Apr 22 07:20 kern.log.2.gz
-rw-r-----  1 syslog            adm     194858 Apr 16 07:17 kern.log.3.gz
-rw-r-----  1 syslog            adm       4990 Apr  8 07:34 kern.log.4.gz
-rw-rw-r--  1 root              utmp    292292 Jan 31 14:39 lastlog
drwxr-xr-x  2 root              root      4096 May  4 07:43 lightdm/
-rw-r--r--  1 root              root        55 May  4 08:09 prime-offload.log
-rw-r--r--  1 root              root        30 May  4 08:09 prime-supported.log
drwx------  2 speech-dispatcher root      4096 Feb 18  2016 speech-dispatcher/
-rw-r-----  1 syslog            adm     221063 May  4 11:03 syslog
-rw-r-----  1 syslog            adm     480516 May  4 07:43 syslog.1
-rw-r-----  1 syslog            adm      71338 May  3 10:28 syslog.2.gz
-rw-r-----  1 syslog            adm     101993 May  2 08:56 syslog.3.gz
-rw-r-----  1 syslog            adm      70681 May  1 07:35 syslog.4.gz
-rw-r-----  1 syslog            adm      37431 Apr 30 19:00 syslog.5.gz
-rw-r-----  1 syslog            adm       8234 Apr 29 07:35 syslog.6.gz
-rw-r-----  1 syslog            adm       8185 Apr 28 07:35 syslog.7.gz
drwxr-xr-x  2 root              root      4096 May  2 09:24 teamviewer12/
-rw-r--r--  1 root              root         0 May  4 07:55 test.txt
drwxr-x---  2 root              adm       4096 Dec 17 08:03 unattended-upgrades/
drwxr-xr-x  2 root              root      4096 May 19  2016 upstart/
-rw-rw-r--  1 root              utmp     29952 May  4 08:10 wtmp
-rw-rw-r--  1 root              utmp    137472 Apr 30 22:40 wtmp.1
-rw-r--r--  1 root              root    121024 May  4 11:03 Xorg.0.log
-rw-r--r--  1 root              root    114287 May  4 08:05 Xorg.0.log.old
-rw-r--r--  1 root              root      8774 Apr 26  2017 Xorg.1.log
-rw-r--r--  1 root              root     47236 Aug 13  2017 Xorg.failsafe.log
m1@m1-desktop:~$

Haha, you and me both.. Straight up driving me crazy.

I had enabled the system restart timer for 720 min / 12 hours yesterday to see if it would restart and not freeze (as it does about every 18 hours). It tried to restart and froze the systems instead.

Created the new directory -

m1@m1-desktop:~$ sudo su -
root@m1-desktop:~# cd /var/log
root@m1-desktop:/var/log# touch test.txt
root@m1-desktop:/var/log# ls test*
test.txt

These were in my Watchdog window upon loading today

Rig 1 -

tail -f  /home/m1/nvoc_logs/watchdog-screenlog.0
m1@m1-desktop:~$ tail -f  /home/m1/nvoc_logs/watchdog-screenlog.0
Watchdog for nvOC v0019-2.0 - Community Release
Version: v0019-2.0.011

LOG FILE: (Showing the last 10 recorded entries)
 cu  10:30:51|cuda-9    Set Device to current
 cu  10:30:51|cuda-9    Resetting device
 cu  10:30:51|cuda-5    Using device: GeForce GTX 1070  (Compute 6.1)
 cu  10:30:51|cuda-5    Set Device to current
 cu  10:30:51|cuda-5    Resetting device
 cu  10:30:51|cuda-10   Using device: GeForce GTX 1070  (Compute 6.1)
 cu  10:30:51|cuda-10   Set Device to current
 cu  10:30:51|cuda-10   Resetting device
  m  10:30:53|ethminer  Speed   0.00 Mh/s    gpu/0  0.00  gpu/1  0.00  gpu/2  0.00  gpu/3  0.00  gpu/4  0.00  gpu/5  0.00  gpu/6  0.00  gpu/7  0.00  gpu/8  0.00  gpu/9  0.00  gpu/10  0.00  gpu/11  0.00  gpu/12  0.00  [A0+0:R0+0:F0] Time: 00:00


Rig 2 -

tail -f  /home/m1/nvoc_logs/watchdog-screenlog.0
m1@m1-desktop:~$ tail -f  /home/m1/nvoc_logs/watchdog-screenlog.0
Watchdog for nvOC v0019-2.0 - Community Release
Version: v0019-2.0.011

LOG FILE: (Showing the last 10 recorded entries)
  ℹ  10:32:31|cuda-4    Solution found; Submitted to us-east.ethash-hub.miningpoolhub.com
  ℹ  10:32:31|cuda-4    Nonce: 0xf1a1cb19d6cee3e0
  ℹ  10:32:31|stratum    Accepted.
  m  10:32:31|ethminer  Speed 359.41 Mh/s    gpu/0 26.52  gpu/1 27.76  gpu/2 27.85  gpu/3 33.39  gpu/4 27.85  gpu/5 27.76  gpu/6 27.76  gpu/7 27.76  gpu/8 21.84  gpu/9 27.66  gpu/10 27.85  gpu/11 27.76  gpu/12 27.66  [A29+0:R0+0:F0] Time: 00:06
  ℹ  10:32:32|cuda-6    Solution found; Submitted to us-east.ethash-hub.miningpoolhub.com
  ℹ  10:32:32|cuda-6    Nonce: 0x5fc7829a336d53eb
  ℹ  10:32:32|stratum    Accepted.
  m  10:32:33|ethminer  Speed 359.51 Mh/s    gpu/0 26.61  gpu/1 27.85  gpu/2 27.76  gpu/3 33.39  gpu/4 27.85  gpu/5 27.76  gpu/6 27.85  gpu/7 27.76  gpu/8 21.84  gpu/9 27.66  gpu/10 27.76  gpu/11 27.76  gpu/12 27.66  [A30+0:R0+0:F0] Time: 00:06
  m  10:32:35|ethminer  Speed 359.41 Mh/s    gpu/0 26.61  gpu/1 27.85  gpu/2 27.76  gpu/3 33.29  gpu/4 27.85  gpu/5 27.76  gpu/6 27.85  gpu/7 27.76  gpu/8 21.84  gpu/9 27.66  gpu/10 27.76  gpu/11 27.76  gpu/12 27.66  [A30+0:R0+0:F0] Time: 00:06
CRITICAL: Thu May  3 10:32:50 MST 2018 - GPU Utilization is too low: restarting 3main...

Both my rigs have no logs. Neither are set to clear logs on reboot, so they should be there if they are. Only logs I have seen are the ones I posted that show up in miner_watchdog



m1@m1-desktop:~$ /var/log$ ll sys*
bash: /var/log$: No such file or directory

m1@m1-desktop:~$ sudo less /var/log/dmesg
(Nothing has been logged yet.)

Is all I get. I am using 19.2

The 850W PSU only runs the motherboard and one card and it's riser. I have three PSU's per rig. Two 1600W (6 cards and their risers each) and the 850W as described. I am no were near the amount of power the power supplies are capable of, so should be good there.

This is one of the rigs - https://imgur.com/a/WRfTksJ

I have two 1600W server PSU's for the cards (6 on each) one 850W EVGA ATX with one card / riser.

All using 6-8pin, risers are split once (1 cable per 2 risers)

Any chance it's a memory issue? I am running 4GB, my memory says 3.2GB / 4GB in use (85%).

Since disabling watchdog, it shouldn't be a server issue. The miner would just keep trying to reconnect.

Well... Disabling watchdog didn't work. Still crashed Blah

So it looks like the server is temp disconnecting and crashing the miners. This is going to happen. So I am going to disable watchdog and just let it re-connect on it's own.

I was on MPH and switched to miningspeed. Same issue. Maybe my rigs just don't like to be restarted and like to work all the time. lol




Latest Errors -

LOG FILE: (Showing the last 10 recorded entries)
CUDA: Device: 8 Thread exited with code: 46
CUDA: Device: 7 Thread exited with code: 46
CUDA: Device: 11 Thread exited with code: 46
CUDA: Device: 12 User selected solver: 0
CUDA: Device: 3 User selected solver: 0
CUDA: Device: 4 User selected solver: 0
CUDA: Device: 12 Thread exited with code: 46
CUDA: Device: 3 Thread exited with code: 46
CUDA: Device: 4 Thread exited with code: 46
CRITICAL: Tue May  1 15:17:20 MST 2018 - GPU Utilization is too low: restarting 3main...



LOG FILE: (Showing the last 10 recorded entries)
+-------------------------------------------------+
INFO: Server: mining.miningspeed.com:3062
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 1
CRITICAL: Tue May  1 04:00:44 MST 2018 - GPU Utilization is too low: restarting 3main...
WARNING: Tue May  1 16:03:20 MST 2018 - Internet is down, checking...

Hmmmm interesting about the electrical issue. I have two 8" hyperfans used as exhaust fans that run 100% 24/7. But could be a possibility.

Last night I recompiled the miners again, set the max fan limit to 90 from another one of your posts and set the power restore to 80 and changed EWBF to 3_3 from 3_4.

I will try this for a day and see if anything happens. It's just so strange that on Hush, it worked completely fine.

I had this kinda happen before and it was the mining server "disconnecting". Switched pools and all was good.

Any way to make watchdog wait an extended period of time for error's to clear themselves before trying to restart 3main?

Also, do the miners themselves if watch dog is disabled keep a max temp limit? I notice when starting EWBF it says max temp 90*. While I don't want temps that high, if it keeps the miner going and safe then I will consider it.

Error on rig 2 - Two different rigs, crashing within a minute of each other. Tell me that isn't weird.

tail -f  /home/m1/nvoc_logs/watchdog-screenlog.0
m1@m1-desktop:~$ tail -f  /home/m1/nvoc_logs/watchdog-screenlog.0
Watchdog for nvOC v0019-2.0 - Community Release
Version: v0019-2.0.011

LOG FILE: (Showing the last 10 recorded entries)
| 12  |    120W     |  3.42 Sol/W  |
+-----+-------------+--------------+
INFO 09:34:50: GPU3 Accepted share 186ms [A:454, R:1]
INFO 09:34:51: GPU7 Accepted share 187ms [A:477, R:1]
CRITICAL: Sun Apr 29 09:35:17 MST 2018 - GPU Utilization is too low: restarting 3main...
Mon Apr 30 22:35:29 MST 2018 - Lost GPU so restarting system. Found GPU's:
Unable to determine the device handle for GPU 0000:0F:00.0: GPU is lost.  Reboot the system to recover this GPU


Mon Apr 30 22:35:30 MST 2018 - reboot in 10 seconds