10-08-2018, 05:49 PM
lol, stray neutrino.
Symptoms suggest part of the update bombed, prolly due to a repo being too busy to accept connections.
Unless you ran the original update vie SSH using the cmd below it would difficult to determine what exactly happened.
sudo /var/www/command/updater.sh r42
-Tim
Symptoms suggest part of the update bombed, prolly due to a repo being too busy to accept connections.
Unless you ran the original update vie SSH using the cmd below it would difficult to determine what exactly happened.
sudo /var/www/command/updater.sh r42
-Tim