UI reflects wrong commit

Dropdown menu in upper right corner still lists my server as being on commit d743d22. git log indicates this commit is nearly a year old (Tue Dec 3 18:43:17 2019 +0000)

Meanwhile:
git status
On branch master
Your branch is up-to-date with ‘origin/master’.
nothing to commit, working tree clean
git fetch && git pull:
Already up-to-date.

1 Like

Did you restart your mineos service after updating?

Tried service mineos restart and it claimed it could not find mineos.service.
Tried running ./service.js restart and it gives a message claiming to have worked, but when I then ./service.js status it claims it’s not running, and further when I ps | grep for the PID it gives me I get no results.

All the while, nothing about the webui appears to change.

Possibly relevant detail: this is the Turnkey version of MineOS (Linux mineos-tkldev 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux)

Further update: tried running ./webui.js -restart and it gives me input ending with

info: Starting up server, using commit: 2cd410a Fix ERR_OUT_OF_RANGE during Buffer.write() (#373)

which appears to be the most recent commit according to git log. However, after refreshing the page, it still lists the current commit as d743d22.

Have you followed the instructions found on the Wiki?

1 Like

Ran the Update instructions at that page. Got this error from npm-install:

added 569 packages from 430 contributors and audited 573 packages in 8.121s
found 12 vulnerabilities (8 low, 2 moderate, 2 high)
run `npm audit fix` to fix them, or `npm audit` for details

npm audit yields the following list:

               === npm audit security report ===

# Run  npm install socket.io@3.0.3  to resolve 5 vulnerabilities
SEMVER WARNING: Recommended action is a potentially breaking change

Low             Regular Expression Denial of Service

Package         debug

Dependency of   socket.io

Path            socket.io > socket.io-adapter > debug

More info       https://npmjs.com/advisories/534




Low             Regular Expression Denial of Service

Package         debug

Dependency of   socket.io

Path            socket.io > socket.io-adapter > socket.io-parser > debug

More info       https://npmjs.com/advisories/534




Low             Regular Expression Denial of Service

Package         debug

Dependency of   socket.io

Path            socket.io > socket.io-client > socket.io-parser > debug

More info       https://npmjs.com/advisories/534




Low             Regular Expression Denial of Service

Package         debug

Dependency of   socket.io

Path            socket.io > socket.io-client > debug

More info       https://npmjs.com/advisories/534




Low             Regular Expression Denial of Service

Package         debug

Dependency of   socket.io

Path            socket.io > socket.io-client > engine.io-client > debug

More info       https://npmjs.com/advisories/534



# Run  npm install angular@1.8.2  to resolve 1 vulnerability

Moderate        Prototype Pollution

Package         angular

Dependency of   angular

Path            angular

More info       https://npmjs.com/advisories/1343




                         Manual Review
     Some vulnerabilities require your attention to resolve

  Visit https://go.npm.me/audit-guide for additional guidance


High            Regular Expression Denial of Service

Package         parsejson

Patched in      No patch available

Dependency of   socket.io

Path            socket.io > socket.io-client > engine.io-client > parsejson

More info       https://npmjs.com/advisories/528


Low             Regular Expression Denial of Service

Package         debug

Patched in      >= 2.6.9 < 3.0.0 || >= 3.1.0

Dependency of   socket.io

Path            socket.io > debug

More info       https://npmjs.com/advisories/534


Low             Regular Expression Denial of Service

Package         debug

Patched in      >= 2.6.9 < 3.0.0 || >= 3.1.0

Dependency of   socket.io

Path            socket.io > engine.io > debug

More info       https://npmjs.com/advisories/534


Low             Regular Expression Denial of Service

Package         debug

Patched in      >= 2.6.9 < 3.0.0 || >= 3.1.0

Dependency of   socket.io

Path            socket.io > socket.io-parser > debug

More info       https://npmjs.com/advisories/534


Moderate        Prototype Pollution

Package         hoek

Patched in      > 4.2.0 < 5.0.0 || >= 5.0.3

Dependency of   mcquery

Path            mcquery > code > hoek

More info       https://npmjs.com/advisories/566


High            Arbitrary File Overwrite

Package         fstream

Patched in      >=1.0.12

Dependency of   unzip

Path            unzip > fstream

More info       https://npmjs.com/advisories/886

running npm audit fix yields this:

+ angular@1.8.2
updated 1 package in 2.035s
fixed 1 of 12 vulnerabilities in 573 scanned packages
6 vulnerabilities required manual review and could not be updated
1 package update for 5 vulnerabilities involved breaking changes
(use `npm audit fix --force` to install breaking changes; or refer to `npm audit` for steps to fix these manually)

That’s normal to see that (as far as I know/ I forced npm audit fix broke the ui). Just continue with the instructions and it will “just work”.

TL;DR Don’t run npm audit fix. Just continue with update.

Just continue with update

Instructions on page end after npm install. What’s next? Reloading the page at that point shows no update from commit d743d22.

Try running these commands again:

As root: cd /usr/games/minecraft /bin/bash update_webui.sh

Then I run: /bin/bash reset_webui.sh

service mineos restart wouldn’t be the daemon manager for MineOS Turnkey. If you’re using Turnkey, it’ll be supervisord (which matches the daemon for Debian installs): supervisorctl stop mineos and supervisorctl start mineos

When it started, it ran a process of your original commit: d743d22.

When you ran additional process, you had one process running d743d22 and one running 2cd410a (but this second one couldn’t bind to the interface).

Solution: stop all processes and let supervisor start up the new one.

Possible ways to achieve this:

supervisorctl stop mineos
supervisorctl start mineos

Or alternatively, simply reboot the machine, which would kill the old process and make sure the new one starts up by default, as well.

1 Like

Progress! Refreshing the page after supervisorctl restart mineos dumps me back to the login screen, and after logging in, commit is at 2cd410a.

Problem is, now it can’t see the running server. I’ve clicked ‘Refresh Server List’ a couple of times, and the ‘Currently Selected Server’ dropdown remains blank. Server is still running, as a ps -eaf | grep 'java' shows, but I can’t interact with it from MineOS.

2 Likes

Never mind, was logged in as root rather than as mc. Can see running server now.

Thanks for all your help!

2 Likes