[OS] nvOC easy-to-use Linux Nvidia Mining

[Stubo]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

[1714176568]

1714176568

[1714176568]

1714176568

[1714176568]

1714176568

[Temporel]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

I have one of those motherboard on nvOC but with 10 GTX-1070 + 2 GTX-1080 Ti and I never had your problem. Im still on v19 though.
The only downtime I ever had was 2 weeks ago when the Nvidia drivers tried to autoupdate.

Please make sure to report back if you ever find the problem.

TYIA

[kk003]

Just installed this nvoc on one of my rigs, looks good. So questions though (no, I did not read all the pages..):

- Is there a way to limit telegram messages to be sent only when there is something wrong, i.e. reboot of server or miner is needed ?
- My rig has some stability issues, I am mining Ethereum with ethminer. In order to track the GPUs causing problems they would have to be run as separate instances/sessions, (xmos does this by default). Any plans for implementing such feature? If not maybe I try with claymore or plug in xmos USB stick, adjust overclock settings and copy them to nvOC.

--
Tigel

I suggest you to read the notes and comments on /home/m1/kk003_telegram and see if its ok for your needs.
Or you can go here:
https://pastebin.com/vPnb6TKn

and see.

I guess if you leave empty var USER_CUSTOM_TIMES_TO_SEND_TELEGRAM you'll get only warnings (including warnings from IAmNotAJeep_and_Maxximus007_WATCHDOG).

Form:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=("12:00" "18:00" "21:32")

To:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=()

I did not do this check, hope it works for you (I think so).
Let me know if it does not and I'll fix it.

You may too set USER_CUSTOM_TIMES_TO_SEND_TELEGRAM like this:

Code:

USER_CUSTOM_TIMES_TO_SEND_TELEGRAM=("18:00")

to get a telegram once a day at 18:00 (or any other time/s of day you want)

Here is the warnings list (most of them):

Code:

# Some warning you can choose to get via telegram or not 
SEND_WARNING_SYSTEM_RESTARTED="YES" # YES or NO
SEND_WARNING_XORG_RESTARTED="YES"   # YES or NO
SEND_WARNING_LOAD_AVERAGE="YES"     # YES or NO
SEND_WARNING_CHECK_DISPLAY="YES"    # YES or NO
SEND_WARNING_WHEN_NO_L_ON_SCREEN="YES"  # YES or NO     YES send a telegram when screen is not starting miner with -L (create log file)

And some info you may choose to get or not in your telegram msg:

Code:

# some information you can choose to receive or not on your telegram msg
SEND_REBOOT_REQUIRED="YES"      # YES or NO
SEND_WORKERNAME="YES"           # YES or NO
SEND_MINING_COIN="YES"          # YES or NO
SEND_MINING_ADDRESS="YES"       # YES or NO
MASK_MINING_ADDRESS="YES"       # YES or NO
SEND_MINER_EXEC_NAME="YES"      # YES or NO
SEND_MINER_EXEC_PATH="YES"      # YES or NO
SEND_MINER_UP_TIME="YES"        # YES or NO
SEND_PRIVATE_IP="YES"           # YES or NO
SEND_PUBLIC_IP="YES"            # YES or NO
MASK_PUBLIC_IP="NO"             # YES or NO
SEND_SSHD_PORT="YES"            # YES or NO
SEND_UP_SINCE="YES"         # YES or NO
SEND_UP_TIME="YES"          # YES or NO
SEND_RAM="YES"              # YES or NO
SEND_CPU_MODEL="YES"            # YES or NO
SEND_LOGGED_USERS="YES"         # YES or NO
 
CUSTOMIZE_SYSTEM_NAME=""        # "PRIVATE_IP" or "PUBLIC_IP" or "AnY CusTom nAme you want here", if empty it uses the system's hostname
                    # This is the main header you'll get in your telegram message
                    # PRIVATE_IP will use your private ip/s (remenber you may have more than one)
                    # PUBLIC_IP will use your public ip

Warnings auto-clear when system gets back to normal.

I try to read your huge script and i think you're a very experienced scripter. Thank for it.

But i see multiple auto_gram openden when WTM restart 3main at each switching coin. and i get en ps error but i don't know how.
I will post tomorrow in this thread about that

Thx  . I don't have a nvoc 19+ installed. The script was tested on nvoc 19 stable so I don't know yet how to get it working with WMT switch.
If some one have WMT switch working on Nvoc 19 stable and want to share a how to I'll be happy to modify the script.
Post what you have anyway.

Let me know what you need from WTM and I provide it for your telegram
These are the additional info WTM gives:

Code:

BTC Price:: 7111 USD
WTM Current Profitabilty: HUSH:113 % ETH:100 % ZEN:95 % ZEC:94 % 
WTM Current USD Revenue: HUSH:14.82 ETH:13.15 ZEN:12.49 ZEC:12.39 
WTM 24H Average Revenue: 14.8939 USD 

I got it thanks

[Moordact]

forgive me for not looking through whole thread, is BitcoinZ minable?

[Temporel]

forgive me for not looking through whole thread, is BitcoinZ minable?

yes

[papampi]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

Usually when the whole network hangs its a sign of network, mac address or ip conflict.

I had same issue once with my home NAS, when I connect its both lans to switch all my network was freezing.
I couldnt even connect to router, until I found the problem

[Temporel]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

Usually when the whole network hangs its a sign of network, mac address or ip conflict.

I had same issue once with my home NAS, when I connect its both lans to switch all my network was freezing.
I couldnt even connect to router, until I found the problem

and what was the problem ?

[papampi]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

Usually when the whole network hangs its a sign of network, mac address or ip conflict.

I had same issue once with my home NAS, when I connect its both lans to switch all my network was freezing.
I couldnt even connect to router, until I found the problem

and what was the problem ?

Synology updated firmware and after that I can not connect both lan ports to same network any more
5-10 minutes after I connect both my whole network freezes.

[papampi]

Any one tried btcz.suprnova ?
Every time EWBF starts I get the  "ERROR: Cannot connect to the pool"
Then wdog restarts miner and it connects with no problem

Any idea why ?

Edit: Solved ...

[TAKCuCT]

Last part of fresh syslog:

Code:

Nov  7 02:19:51 m1-desktop gnome-session-binary[1711]: Entering running state
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (process:1969): indicator-application-service-WARNING **: Unable to get watcher name 'org.kde.StatusNotifierWatcher'
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (process:1969): indicator-application-service-WARNING **: Name Lost
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nm-applet:1962): nm-applet-WARNING **: NetworkManager is not running
Nov  7 02:19:51 m1-desktop dbus[640]: [system] Activating service name='org.freedesktop.fwupd' (using servicehelper)
Nov  7 02:19:51 m1-desktop systemd[1]: Starting Stop ureadahead data collection...
Nov  7 02:19:51 m1-desktop systemd[1]: Stopped Read required files in advance.
Nov  7 02:19:51 m1-desktop systemd[1]: Started Stop ureadahead data collection.
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (guake:1965): libglade-WARNING **: unknown attribute `swapped' for <signal>.
Nov  7 02:19:51 m1-desktop gnome-session[1711]: message repeated 21 times: [ (guake:1965): libglade-WARNING **: unknown attribute `swapped' for <signal>.]
Nov  7 02:19:51 m1-desktop gnome-session[1711]: INFO:guake.guake_app:Logging configuration complete
Nov  7 02:19:51 m1-desktop gnome-session[1711]: /usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]:   self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)
Nov  7 02:19:52 m1-desktop org.freedesktop.fwupd[640]: (fwupd:2010): Fu-WARNING **: Failed to coldplug: UEFI firmware updating not supported
Nov  7 02:19:52 m1-desktop dbus[640]: [system] Successfully activated service 'org.freedesktop.fwupd'
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Nov  7 02:20:23 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Nov  7 02:20:23 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Nov  7 02:20:23 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Nov  7 02:20:23 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Nov  7 02:20:23 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Nov  7 02:20:23 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Nov  7 02:20:23 m1-desktop systemd[1]: Startup finished in 6.349s (kernel) + 1min 30.189s (userspace) = 1min 36.539s.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.
Nov  7 02:20:53 m1-desktop gnome-session[1711]: ** (update-notifier:2695): WARNING **: log file empty (logrotate?) /var/log/dpkg.log
Nov  7 02:20:53 m1-desktop gnome-session[1711]: ** (update-notifier:2695): WARNING **: log file empty (logrotate?) /var/log/apt/term.log
Nov  7 02:23:54 m1-desktop anacron[607]: Job `cron.daily' started
Nov  7 02:23:54 m1-desktop anacron[3608]: Updated timestamp for job `cron.daily' to 2017-11-07
Nov  7 02:23:54 m1-desktop cracklib: no dictionary update necessary.
Nov  7 02:23:54 m1-desktop systemd[1]: Reloading LSB: Apache2 web server.
Nov  7 02:23:54 m1-desktop apache2[3667]:  * Reloading Apache httpd web server apache2
Nov  7 02:23:54 m1-desktop apache2[3667]:  *
Nov  7 02:23:54 m1-desktop systemd[1]: Reloaded LSB: Apache2 web server. 

[Temporel]

I have 3 rigs on Asrock h110 BTC+ nvidia based (1070 + 1060) on different PSU's and connected to different routers. All of them has very unpleasant problem: once or twice or thrice per day the system hangs and hangs the entire network. This happens only on nvOC, on smos or on ubuntu 16.04 - ok about 2 days. Tried: disable (and remove) dhcp, another router, disable network manager, usb-lan but problem still here. Any thoughts?

You say "the system hangs and hangs the entire network" yet you also say you have 3 rigs. Do you have any idea which system is responsible for a particular "hang"? Also, how do you fix the hang? You also mention disabling usb-lan so how are the rigs connected to the network - wired, wireless, or?

You may want to look for errors/issues in in each rigs /var/log/syslog.

Rigs are in different places but with the same symptoms. Connected by wire. Hangs only can be fixed by reset button or power switch.

Ok. Thanks for the clarification. What do you see in /var/log/syslog at around the time of the hangs? There should be some clues in there.

Usually when the whole network hangs its a sign of network, mac address or ip conflict.

I had same issue once with my home NAS, when I connect its both lans to switch all my network was freezing.
I couldnt even connect to router, until I found the problem

and what was the problem ?

Synology updated firmware and after that I can not connect both lan ports to same network any more
5-10 minutes after I connect both my whole network freezes.

thanks for replying 

[Stubo]

Last part of fresh syslog:

Code:

Nov  7 02:19:51 m1-desktop gnome-session-binary[1711]: Entering running state
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (process:1969): indicator-application-service-WARNING **: Unable to get watcher name 'org.kde.StatusNotifierWatcher'
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (process:1969): indicator-application-service-WARNING **: Name Lost
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GObject-WARNING **: invalid (NULL) pointer instance
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nautilus:1964): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (nm-applet:1962): nm-applet-WARNING **: NetworkManager is not running
Nov  7 02:19:51 m1-desktop dbus[640]: [system] Activating service name='org.freedesktop.fwupd' (using servicehelper)
Nov  7 02:19:51 m1-desktop systemd[1]: Starting Stop ureadahead data collection...
Nov  7 02:19:51 m1-desktop systemd[1]: Stopped Read required files in advance.
Nov  7 02:19:51 m1-desktop systemd[1]: Started Stop ureadahead data collection.
Nov  7 02:19:51 m1-desktop gnome-session[1711]: (guake:1965): libglade-WARNING **: unknown attribute `swapped' for <signal>.
Nov  7 02:19:51 m1-desktop gnome-session[1711]: message repeated 21 times: [ (guake:1965): libglade-WARNING **: unknown attribute `swapped' for <signal>.]
Nov  7 02:19:51 m1-desktop gnome-session[1711]: INFO:guake.guake_app:Logging configuration complete
Nov  7 02:19:51 m1-desktop gnome-session[1711]: /usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
Nov  7 02:19:51 m1-desktop gnome-session[1711]:   self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)
Nov  7 02:19:52 m1-desktop org.freedesktop.fwupd[640]: (fwupd:2010): Fu-WARNING **: Failed to coldplug: UEFI firmware updating not supported
Nov  7 02:19:52 m1-desktop dbus[640]: [system] Successfully activated service 'org.freedesktop.fwupd'
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Nov  7 02:20:23 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Nov  7 02:20:23 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Nov  7 02:20:23 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Nov  7 02:20:23 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Nov  7 02:20:23 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Nov  7 02:20:23 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Nov  7 02:20:23 m1-desktop systemd[1]: Startup finished in 6.349s (kernel) + 1min 30.189s (userspace) = 1min 36.539s.
Nov  7 02:20:23 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.
Nov  7 02:20:53 m1-desktop gnome-session[1711]: ** (update-notifier:2695): WARNING **: log file empty (logrotate?) /var/log/dpkg.log
Nov  7 02:20:53 m1-desktop gnome-session[1711]: ** (update-notifier:2695): WARNING **: log file empty (logrotate?) /var/log/apt/term.log
Nov  7 02:23:54 m1-desktop anacron[607]: Job `cron.daily' started
Nov  7 02:23:54 m1-desktop anacron[3608]: Updated timestamp for job `cron.daily' to 2017-11-07
Nov  7 02:23:54 m1-desktop cracklib: no dictionary update necessary.
Nov  7 02:23:54 m1-desktop systemd[1]: Reloading LSB: Apache2 web server.
Nov  7 02:23:54 m1-desktop apache2[3667]:  * Reloading Apache httpd web server apache2
Nov  7 02:23:54 m1-desktop apache2[3667]:  *
Nov  7 02:23:54 m1-desktop systemd[1]: Reloaded LSB: Apache2 web server. 

Ok, nothing there other than @fullzero's USB reference (comment out last 2 lines of /etc/fstab to fix those mount timeout errors). Anyway, let's try another tact. Can you find anything related to the time when it last happened using:

Code:

journalctl -u NetworkManager

that should give you detailed networking information.

[TAKCuCT]

Ok, nothing there other than @fullzero's USB reference (comment out last 2 lines of /etc/fstab to fix those mount timeout errors). Anyway, let's try another tact. Can you find anything related to the time when it last happened using:

Code:

journalctl -u NetworkManager

that should give you detailed networking information.

Networkmanager - disabled.
Syslog from another rig

Code:

WARNING **: log file empty (logrotate?) /var/log/apt/term.log
Nov  6 06:40:18 m1-desktop AptDaemon: INFO: Quitting due to inactivity
Nov  6 06:40:18 m1-desktop org.debian.apt[554]: 06:40:18 AptDaemon [INFO]: Quitting due to inactivity
Nov  6 06:40:18 m1-desktop org.debian.apt[554]: 06:40:18 AptDaemon [INFO]: Quitting was requested
Nov  6 06:40:18 m1-desktop AptDaemon: INFO: Quitting was requested
Nov  6 07:17:01 m1-desktop CRON[10281]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Nov  6 07:30:01 m1-desktop CRON[12570]: (root) CMD (test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null)
Nov  6 07:30:01 m1-desktop anacron[12592]: Anacron 2.3 started on 2017-11-06
Nov  6 07:30:01 m1-desktop anacron[12592]: Will run job `cron.daily' in 5 min.
Nov  6 07:30:01 m1-desktop anacron[12592]: Jobs will be executed sequentially
Nov  6 07:30:01 m1-desktop systemd[1]: Started Run anacron jobs.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Nov  6 07:31:31 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Nov  6 07:31:31 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Nov  6 07:31:31 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Nov  6 07:31:31 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Nov  6 07:31:31 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Nov  6 07:31:31 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Nov  6 07:35:01 m1-desktop anacron[12592]: Job `cron.daily' started
Nov  6 07:35:01 m1-desktop anacron[13336]: Updated timestamp for job `cron.daily' to 2017-11-06
Nov  6 07:35:01 m1-desktop cracklib: no dictionary update necessary.
Nov  6 07:35:01 m1-desktop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="553" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

It looks like problems start after

Code:

Nov  6 07:35:01 m1-desktop anacron[12592]: Job `cron.daily' started
Nov  6 07:35:01 m1-desktop anacron[13336]: Updated timestamp for job `cron.daily'

[Ibizian]

I need an Ubuntu expert please!!

I am having a reboot freeze issue. For whatever reason my rig will do this only on ETH so far. Other coins have not done this so I think it is an OC or heat issue. However thats not the main concern.

Once the system reboots it gives the usual black screen, BIOS , then flashes to a blueish screen. Sits there for a second or 2 then flashes again to the same blueish screen and stays forever.

When the system reboots properly that second flash is followed by the loading of nvOC and mining commences. So it is right before the command to load.

This happens randomly and not every time it reboots.

I know this thing has to keep logs that we can look at to see what step it is failing to load on. Right?? It has cost me HOURS of downtime when it fails at 3am. This time it mined ETH all evening and night and failed at 0530ish.. I found it at 0700.

Last week I mined a different coin and it did not have one single failure!!

So who can help me troubleshoot this mystery?

Thank you in advance and remember, I know very little about Linux ( I took a couple classes 15 years ago!) so if you do make a suggestion pretend you are writing it in Greek cause thats what it is. I will need it barneystyle!

[Stubo]

Ok, nothing there other than @fullzero's USB reference (comment out last 2 lines of /etc/fstab to fix those mount timeout errors). Anyway, let's try another tact. Can you find anything related to the time when it last happened using:

Code:

journalctl -u NetworkManager

that should give you detailed networking information.

Networkmanager - disabled.
Syslog from another rig

Code:

WARNING **: log file empty (logrotate?) /var/log/apt/term.log
Nov  6 06:40:18 m1-desktop AptDaemon: INFO: Quitting due to inactivity
Nov  6 06:40:18 m1-desktop org.debian.apt[554]: 06:40:18 AptDaemon [INFO]: Quitting due to inactivity
Nov  6 06:40:18 m1-desktop org.debian.apt[554]: 06:40:18 AptDaemon [INFO]: Quitting was requested
Nov  6 06:40:18 m1-desktop AptDaemon: INFO: Quitting was requested
Nov  6 07:17:01 m1-desktop CRON[10281]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Nov  6 07:30:01 m1-desktop CRON[12570]: (root) CMD (test -x /etc/init.d/anacron && /usr/sbin/invoke-rc.d anacron start >/dev/null)
Nov  6 07:30:01 m1-desktop anacron[12592]: Anacron 2.3 started on 2017-11-06
Nov  6 07:30:01 m1-desktop anacron[12592]: Will run job `cron.daily' in 5 min.
Nov  6 07:30:01 m1-desktop anacron[12592]: Jobs will be executed sequentially
Nov  6 07:30:01 m1-desktop systemd[1]: Started Run anacron jobs.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Nov  6 07:31:31 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Nov  6 07:31:31 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Nov  6 07:31:31 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Nov  6 07:31:31 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Nov  6 07:31:31 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Nov  6 07:31:31 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Nov  6 07:31:31 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Nov  6 07:35:01 m1-desktop anacron[12592]: Job `cron.daily' started
Nov  6 07:35:01 m1-desktop anacron[13336]: Updated timestamp for job `cron.daily' to 2017-11-06
Nov  6 07:35:01 m1-desktop cracklib: no dictionary update necessary.
Nov  6 07:35:01 m1-desktop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="553" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

It looks like problems start after

Code:

Nov  6 07:35:01 m1-desktop anacron[12592]: Job `cron.daily' started
Nov  6 07:35:01 m1-desktop anacron[13336]: Updated timestamp for job `cron.daily'

Wait, that is a syslog from a different miner? It looks like you have 2 hosts both with the default name of "m1-desktop". Are they on the same network? If so, that could certainly be a problem.

[TAKCuCT]

As i said above: all rigs in different places and different networks.

[medi91]

Tried my best to search for an answer, but no luck so far...

has anyone successfully gotten rid of the login loop issue?

Ive console logged in, did a re-image, tried different versions, and every ubuntu based fix i could find online (clear and .Xauthority fixes)

Board is a HP z400 board

Try this:
press CTRL- ALT- F1 together, terminal window will open. Login as m1, pass miner1

type:

Code:

sudo apt update && sudo apt upgrade && sudo reboot

Please reply with results

After login in ssh, try the others commands given in page 246 (dpkg ...)

and try to réinstall latest nvidia drivers with

Code:

sudo apt install nividia-387

or try to install nvOC V0019-1.4

Unfortunately did not get rid of the login loop

Does it go into a loop with -1.4?

yes it does

also not working on a z210 unfortunately

I have e3-1220 as the cpu that doesnt have onboard video could that be affecting anything?
will be trying a different cpu this week

[Stubo]

As i said above: all rigs in different places and different networks.

The problem you describe sounds a lot like this:

https://superuser.com/questions/183982/ubuntu-server-9-04-computer-freezes-the-entire-network-periodically

As the link says, I think this would be an interesting test:

"Next time this happens, it would be interesting to see if the problem goes away simply by disconnecting the Ubuntu server's Ethernet link to the network, and if it does, does the problem come back when you plug the Ethernet cable back in?"

[divxl]

Hello.
I download v19-1.4 and does not coincide with SHA256, at all so? Or the broken image is laid out?

[divxl]

Hello.
I download v19-1.4 and does not coincide with SHA256, at all so? Or the broken image is laid out?

Anymore, SHA256 is not for mining with GPU, unless you know of a coin that I don't...

Forgive me for my English, I mean this:

Code:

Note: you still need to implement bios setting changes.  The SHA256 hash (for the zip) is:
Code:
20a32841e07521b536083e7d4d4d64e2f8fdf2e259d277bb48e79f1520f57af4

The checksums do not match.