[ mining os ] nvoc

[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.

[ComputerGenie]

...Forgive me for my English, I mean...

That wasn't you; I read it wrong. 

[dartec]

Is anyone having a problem mining with skunk algo with ccminer.
I have set it up, but can't get it to work.
I tested the syntax from the command line, and this is the result I get (I have replaced my real username with "username" in this example):

m1@m1-desktop:~$ /home/m1/TPccminer/ccminer -a skunk -o stratum+tcp://zpools.de:3300 -u username.miner1 -p x -i 22
*** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 8.0 64-bits

  Originally based on Christian Buchner and Christian H. project
  Include some algos from alexis78, djm34, sp, tsiv and klausT.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2017-11-06 14:15:14] Starting on stratum+tcp://zPools.de:3300
[2017-11-06 14:15:14] NVML GPU monitoring enabled.
[2017-11-06 14:15:14] 2 miner threads started, using 'skunk' algorithm.
Illegal instruction
m1@m1-desktop:~$

Any help would be appreciated.

Is there anyone successfully mining the skunk algo?

[CryptAtomeTrader44]

That "ps ... " error is probably when miner restart and script cant catch miner up time, you can ignore it.
I changed WTM  auto switch so it dont restart 3main and only start miner, you can test new version in z_papampi_versions

First copy PAPAMPI_WTM,  WTM_AUTO_SWITCH from /home/m1 to a new folder to keep my old version, then copy and replace my versions from  z_papampi_versions to /home/m1/

My new version just restart miner and wdog (to prevent wdog from catching gpu under utilizations) and get faster switch (under 30 seconds with 7 cards)
If you add any new coins or edit miners in 3main you should do the same in wtm-miner,
The new version doesnt work with damNmad OC, so you should disable it.

Done. Thx papami.

1/ Did i could ignore all the tabs auto_gram in guake ?
2/ I replaced all the "

Code:

screen -dmsL

" by

Code:

"screen -dmS"

because i run nvOC with datatravel kingston usb key for now more than  two month. I will réplace it with classic 2.5" HDD soon and réactivate screenlog.o after this replacement.
3/ Is it possible not to kill cpuOPT when you restart your wtm-miner script
I saw this in code :

Code:

#kill miner
pkill -e miner

For now, i disable CPUOPT because it restart to much and its not a good idea to restart xmr_miner.

About xmr_miners. What do you think about adding xmrig and xmr_stack_cpu wxhat i use on some workstation with xeon processor ?

4/ What is the problem with OC_Spécific Settings and how do you do for OC your mémory and GPU cards ? This feature is really great, it is a bad loss can't using it.

NB : I try to write in english directly without translator, so it is possible that we have difficulties to understand us corectly.

[CryptAtomeTrader44]

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.

look at this error message i can see on my miner's screen in a guake tab named auto_gram:

Code:

m1@MINER:~$ bash /home/m1/kk003_telegram
error: list of process IDs must follow -p

Usage:
 ps [options]

 Try 'ps --help <simple|list|output|threads|misc|all>'
  or 'ps --help <s|l|o|t|m|a>'
 for additional help text.

For more details see ps(1).

Note : my version is nvOC19-1.4 and i'm using WTM_Switch included in z-papami_WTM folder

[kk003]

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.

look at this error message i can see on my miner's screen in a guake tab named auto_gram:

Code:

m1@MINER:~$ bash /home/m1/kk003_telegram
error: list of process IDs must follow -p

Usage:
 ps [options]

 Try 'ps --help <simple|list|output|threads|misc|all>'
  or 'ps --help <s|l|o|t|m|a>'
 for additional help text.

For more details see ps(1).

Note : my version is nvOC19-1.4 and i'm using WTM_Switch included in z-papami_WTM folder

Please login using ssh or terminal as m1 user and exec kk003_telegram:

Code:

bash kk003_telegram

Let me know if you see same error.
EDIT: If possible stop mining with WTM, mine with any miner and test if error persists

UPDATE:
From console run:

Code:

ps -o etime= -p $(pgrep -f miner)

and

Code:

ps -o etimes= -p $(pgrep -f Xorg)

see if retuns any values

I guess the first one fails because miner process is missing

I just upload a new version of kk003_telegram with Papampi's WTM switch statics support (thx Papampi ) that don't fix the problem miner process is missing (if I am right) but search for miner and Xorg process before exec ps.
Hope works well on Nvoc 19+ as I dont have it installed and in 19 stable don't get that error.
I would appreciate feedback.
Here the link: https://pastebin.com/vPnb6TKn

To update the script:
1. Backup the old one

Code:

cp /home/m1/telegram /home/m1/telegram.old

2. Edit /home/m1/telegram. Find :

Code:

#mod by kk003
if [ $TELEGRAM_TYPE == "kk003" ]
then
#!/bin/bash

3. Remove all from (including this line)

Code:

#!/bin/bash

 

to penultimate line

Code:

) >> $KK003_LOG_FILE ##### DON'T REMOVE THIS CLOSED PARENTHESIS OR WE'LL MISS THE LOG FILE

(Remove that last line too)

So you have to see the last lines of /home/m1/telegram like this:

Code:

#mod by kk003
if [ $TELEGRAM_TYPE == "kk003" ]
then
fi

4. Make a blank line between "then" and "fi" and get your cursor there
5. Copy and paste the new code from the link provided above
6. Save the file
7. From terminal run

Code:

bash telegram

and see if you get any errors

Let me know how it goes.

[MentalNomad]

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.

Where did you download from? And did you only try to download once?

It could be one of the hosted files is corrupted, so it depends on your source.

It also could be that your download got corrupted, so trying again may help.

[papampi]

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.

look at this error message i can see on my miner's screen in a guake tab named auto_gram:

Code:

m1@MINER:~$ bash /home/m1/kk003_telegram
error: list of process IDs must follow -p

Usage:
 ps [options]

 Try 'ps --help <simple|list|output|threads|misc|all>'
  or 'ps --help <s|l|o|t|m|a>'
 for additional help text.

For more details see ps(1).

Note : my version is nvOC19-1.4 and i'm using WTM_Switch included in z-papami_WTM folder

I replied to your earlier  post here
That's when it checks for miner Uptime and miner haven't started yet , just ignore it for now
Will add an if statement for next version.


Update :

Edit telegram and change all

From:

Code:

MINER_UP_TIME=$(ps -p `pgrep miner` -o etime | grep -v ELAPSED)

To:

Code:

MINER_PID=$(ps ax | grep SCREEN | grep miner | awk '"miner" {print $1}')
if [ -n  "$MINER_PID" ]
then
MINER_UP_TIME=$(ps -p $MINER_PID -o etime | grep -v ELAPSED)
else
MINER_UP_TIME=(" ")
fi

[papampi]

Update dstm zm miner easy way :


It seems like for some reason we cant download the file from google drive by wget


Download zm_0.5.4.tar.gz from HERE
Put it in Downloads folder , then run the script

V19-1.3 update zm 5_1 to 5_4 :

Download v19_1_3_update_zm_5_1_to_5_4
then run :

Code:

bash v19_1_3_update_zm_5_1_to_5_4

V19-1.4 update zm 5_3 to 5_4 :

Download v19_1_4_update_zm_5_3_to_5_4
then run :

Code:

bash v19_1_4_update_zm_5_3_to_5_4

[papampi]

My latest telegram
Fixed miner uptime
With some WTM auto switch and profit check info

LINK