Re: DRAWS™ Manager Demo #drawsmanager


Basil Gunn
 

Yes that is what I get as well.
The sensors command (along with a bunch of other things) is not working
in kernel 5.4.51, that is what is causing draws-manager to fail.

The only solution I have at the moment is to start over with NWDR16 and NOT do
a kernel update (ie. do not do apt-get dist-upgrade or rpi-update)

There are a lot of forums complaining about the new kernel. I will post
any news as I hear it.

/Basil


Charlie Hein <chein@bellsouth.net> writes:

Here you go, Basil:

pi@nvdpi:~ $ uname -a
Linux nvdpi 5.4.51-v7+ #1327 SMP Thu Jul 23 10:58:46 BST 2020 armv7l GNU/Linux
pi@nvdpi:~ $ journalctl -u draws-manager.service
-- Logs begin at Thu 2019-02-14 04:11:59 CST, end at Wed 2020-07-29 15:11:07 CDT
Jul 29 11:21:34 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm npm does not support Node.js v10.21
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You should probably upgrade to a ne
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm can't make any promises that npm wi
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm Supported releases of Node.js are t
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You can find the latest version at
Jul 29 11:21:43 nvdpi npm[542]: > webapp@0.0.1 start /usr/local/var/draws-manage
Jul 29 11:21:43 nvdpi npm[542]: > node ./bin/www
Jul 29 11:21:51 nvdpi npm[542]: ::
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: child_process.js:669
Jul 29 11:21:52 nvdpi npm[542]: throw err;
Jul 29 11:21:52 nvdpi npm[542]: ^
Jul 29 11:21:52 nvdpi npm[542]: Error: Command failed: /usr/bin/sensors *-i2c-1-
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: at checkExecSyncError (child_process.js:629:
Jul 29 11:21:52 nvdpi npm[542]: at execSync (child_process.js:666:13)
Jul 29 11:21:52 nvdpi npm[542]: at getSensors (/usr/local/var/draws-manager/
Jul 29 11:21:52 nvdpi npm[542]: at Timeout._onTimeout (/usr/local/var/draws-
Jul 29 11:21:52 nvdpi npm[542]: at ontimeout (timers.js:436:11)
Jul 29 11:21:52 nvdpi npm[542]: at tryOnTimeout (timers.js:300:5)
Jul 29 11:21:52 nvdpi npm[542]: at listOnTimeout (timers.js:263:5)
lines 1-23...skipping...
-- Logs begin at Thu 2019-02-14 04:11:59 CST, end at Wed 2020-07-29 15:11:07 CDT. --
Jul 29 11:21:34 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration..
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm npm does not support Node.js v10.21.0
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You should probably upgrade to a newer version of node as we
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm can't make any promises that npm will work with this version.
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You can find the latest version at https://nodejs.org/
Jul 29 11:21:43 nvdpi npm[542]: > webapp@0.0.1 start /usr/local/var/draws-manager/webapp
Jul 29 11:21:43 nvdpi npm[542]: > node ./bin/www
Jul 29 11:21:51 nvdpi npm[542]: ::
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: child_process.js:669
Jul 29 11:21:52 nvdpi npm[542]: throw err;
Jul 29 11:21:52 nvdpi npm[542]: ^
Jul 29 11:21:52 nvdpi npm[542]: Error: Command failed: /usr/bin/sensors *-i2c-1-48
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: at checkExecSyncError (child_process.js:629:11)
Jul 29 11:21:52 nvdpi npm[542]: at execSync (child_process.js:666:13)
Jul 29 11:21:52 nvdpi npm[542]: at getSensors (/usr/local/var/draws-manager/webapp/io.js:45:15)
Jul 29 11:21:52 nvdpi npm[542]: at Timeout._onTimeout (/usr/local/var/draws-manager/webapp/io.js:118:27)
Jul 29 11:21:52 nvdpi npm[542]: at ontimeout (timers.js:436:11)
Jul 29 11:21:52 nvdpi npm[542]: at tryOnTimeout (timers.js:300:5)
Jul 29 11:21:52 nvdpi npm[542]: at listOnTimeout (timers.js:263:5)
Jul 29 11:21:52 nvdpi npm[542]: at Timer.processTimers (timers.js:223:10)
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! code ELIFECYCLE
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! errno 1
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! Exit status 1
Jul 29 11:21:52 nvdpi npm[542]: npm ERR!
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! Failed at the webapp@0.0.1 start script.
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! A complete log of this run can be found in:
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! /root/.npm/_logs/2020-07-29T16_21_52_279Z-debug.log
Jul 29 11:21:52 nvdpi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 11:21:52 nvdpi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
Jul 29 11:31:35 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration..
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm npm does not support Node.js v10.21.0
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm You should probably upgrade to a newer version of node as we
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm can't make any promises that npm will work with this version.
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm You can find the latest version at https://nodejs.org/
Jul 29 11:31:39 nvdpi npm[1709]: > webapp@0.0.1 start /usr/local/var/draws-manager/webapp
Jul 29 11:31:39 nvdpi npm[1709]: > node ./bin/www
Jul 29 11:31:45 nvdpi npm[1709]: ::
Jul 29 11:31:46 nvdpi npm[1709]: Specified sensor(s) not found!
Jul 29 11:31:46 nvdpi npm[1709]: child_process.js:669
Jul 29 11:31:46 nvdpi npm[1709]: throw err;
Jul 29 11:31:46 nvdpi npm[1709]: ^
Jul 29 11:31:46 nvdpi npm[1709]: Error: Command failed: /usr/bin/sensors *-i2c-1-48
Jul 29 11:31:46 nvdpi npm[1709]: Specified sensor(s) not found!
Jul 29 11:31:46 nvdpi npm[1709]: at checkExecSyncError (child_process.js:629:11)
Jul 29 11:31:46 nvdpi npm[1709]: at execSync (child_process.js:666:13)
Jul 29 11:31:46 nvdpi npm[1709]: at getSensors (/usr/local/var/draws-manager/webapp/io.js:45:15)
Jul 29 11:31:46 nvdpi npm[1709]: at Timeout._onTimeout (/usr/local/var/draws-manager/webapp/io.js:118:27)
Jul 29 11:31:46 nvdpi npm[1709]: at ontimeout (timers.js:436:11)
Jul 29 11:31:46 nvdpi npm[1709]: at tryOnTimeout (timers.js:300:5)
Jul 29 11:31:46 nvdpi npm[1709]: at listOnTimeout (timers.js:263:5)
Jul 29 11:31:46 nvdpi npm[1709]: at Timer.processTimers (timers.js:223:10)
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! code ELIFECYCLE
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! errno 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Exit status 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Failed at the webapp@0.0.1 start script.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! A complete log of this run can be found in:
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! /root/.npm/_logs/2020-07-29T16_31_46_715Z-debug.log
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
lines 30-69/69 (END)

Join udrc@nw-digital-radio.groups.io to automatically receive all group messages.