To prevent automatic updates in the future:
use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:
To:
and /etc/apt/apt.conf.d/20auto-upgrades
to
D
ps: Seriously, why was this ON?
use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:
Code:
APT::Periodic::Update-Package-Lists "1";
To:
Code:
APT::Periodic::Update-Package-Lists "0";
and /etc/apt/apt.conf.d/20auto-upgrades
Code:
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Periodic::Unattended-Upgrade "1";
to
Code:
APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";
APT::Periodic::Unattended-Upgrade "0";
D
ps: Seriously, why was this ON?
Very nice suggestion Doodkeen,
This is a community driven project and fullzero is doing the best job ever without asking for a dime (unlike other Linux mining distros)
Some times in the middle of the road we miss some small points that are so obvious to others,
So I'm kindly ask every Linux Guru here to do their best to look for improvements and fixes for nvOC
Feel free to PM me or post in forum any suggestion you have.
Thank you all.
Yep, please feel free and provide the valuable feedback, so that we can make nvOC even better.
Coming to the error, no one expected this sort of failure on this scale!! Hope we identify these sort of issues bit earlier.
I think the problem is while Nvidia driver was updating wdog restarted the rig because of low utilization and that cause a miss configured Nvidia driver,
I think solution is to prevent wdog from restarting the rig if dpkg is running.
Papampi, you are absolutely right I think solution is to prevent wdog from restarting the rig if dpkg is running.
I had this happen to 2 of my rigs. I will change all the update settings for -1.4 except security updates. My bad.
- disable automatic downloads of updates (drivers, system, nvOC)
- disable automatic installation of updates (drivers, system, nvOC)
I have a rig behind a firewall and absolutely no important data on a nvOC rig, so all I care is about stability.
And stability is more fragile because of USB key usage.
The logging is disabled by default, so there would be no writing to the USB key if I would disable updates.
The nvOC is pretty stable even now, but I think that disabling all updates would help with the stability of the system.
Of course I would also periodically update USB key with the whole image of nvOC, but only every month or so, when you publish the new version of stable nvOC.
I have disabled all updates on -1.4; it does have logs. I will work on a global long variable implementation ( LOGS="ON" or OFF ) for the next version