[SOLVED] Have not been able to update since commit 08d2edc

Web-UI
#1

Everything has been running well, but recently I started getting cron messages letting me know that my recent updates have been failing.
My update / reset script (I am running NodeWebUI on Ubuntu 14.04 as a VM) and results:
http://hastebin.com/omaruvusuh.pl

the TL;DR version (without the directory structure and versions is:
resetMineOSWebUI.sh
=====================================================
#!/bin/bash
cd /usr/games/minecraft
git fetch
git reset --hard origin/master
rm -rf node_modules
npm install
chmod +x mineos_console.js
=====================================================

Output from script - same when running script with sudo or through cron as root
=====================================================
$ sudo ./resetMineOSWebUI.sh
HEAD is now at 2d22dc1 Merge pull request #185 from hexparrot/revert-182-assorted_fixes
npm WARN deprecated static-favicon@1.0.2: use serve-favicon module
npm WARN deprecated graceful-fs@3.0.8: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated native-or-bluebird@1.2.0: 'native-or-bluebird' is deprecated. Please use 'any-promise' instead.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated graceful-fs@2.0.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.

> bufferutil@1.2.1 install /usr/games/minecraft/node_modules/bufferutil
> node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/bufferutil/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  COPY Release/bufferutil.node
make: Leaving directory `/usr/games/minecraft/node_modules/bufferutil/build'

> utf-8-validate@1.2.1 install /usr/games/minecraft/node_modules/utf-8-validate
> node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/utf-8-validate/build'
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  COPY Release/validation.node
make: Leaving directory `/usr/games/minecraft/node_modules/utf-8-validate/build'

> posix@4.0.1 install /usr/games/minecraft/node_modules/posix
> node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/posix/build'
  CXX(target) Release/obj.target/posix/src/posix.o
  SOLINK_MODULE(target) Release/obj.target/posix.node
  COPY Release/posix.node
make: Leaving directory `/usr/games/minecraft/node_modules/posix/build'

> userid@0.2.0 install /usr/games/minecraft/node_modules/userid
> node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/userid/build'
  CXX(target) Release/obj.target/userid/src/userid.o
  SOLINK_MODULE(target) Release/obj.target/userid.node
  COPY Release/userid.node
make: Leaving directory `/usr/games/minecraft/node_modules/userid/build'
mineos-node@1.1.1 /usr/games/minecraft

Any help, would of course be appreciated. It should be noted that this script has been running fine up until commit o8d2edc. It is now on commit 2d22dc1 with no success…

#2

I don’t see anything in that output that indicates a problem.

Are you restarting the mineos background process before trying it again? In most cases (such as the Turnkey ISO), this is by restarting the process via supervisor: supervisorctl restart mineos

#3

I don’t have the supervisorctl command, but I do have initctl - which did not do anything but show the status. I ended up rebooting the server and MineOS is now showing the correct commit.
I don’t recall having to restart the WebUI in the past other than logging out of it and back in to see the new commit, I would simply run the reset script I have and it would update in the WebUI automagically. What should be the expected behavior of running that script? Do I need to reboot every time there is an update? Don’t mind doing it, would just like to know.

Thanks!

#4

No, just restart the process. Whatever commit is in memory stays in memory until restarted. So realistically, even after running your upgrade script, the commit should still show the old commit–up until the process restarts. You can see this more linearly by checking the mineos.log where it indicates what version of the UI it’s starting up.

#5

Excellent! Thanks again, hexparrot.