Date
1 - 20 of 44
DRAWS™ Manager Demo #drawsmanager
|
Charlie Hein
I'll say! Needed to flash a new card with just the raw image on it. I'm guessing that it's been maybe a half hour from the time I put the card into the Pi, and I'm seeing packets off the air and DRAWS-Manager is functional. Got almost no errors coming through the setup, either.
Charlie
|
|
|
|
4.19.118 good
toggle quoted messageShow quoted text
5.4.51 BAD Charlie Hein <chein@bellsouth.net> writes:
If you skip that update the kernel is at "4.19.118-v7+"
|
|
|
|
Charlie Hein
If you skip that update the kernel is at "4.19.118-v7+"
Charlie
|
|
|
|
Charlie Hein
Basil - that includes the "Welcome to Raspberry Pi" automated configuration where it asks to update Software as well, correct?
Charlie
|
|
|
|
Charlie Hein
Okay, start over from scratch it is! A little repetition never hurt the learning curve!
Thanks, Charlie
|
|
|
|
Yes that is what I get as well.
toggle quoted messageShow quoted text
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:
|
|
|
|
Charlie Hein
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)
|
|
|
|
I believe the problem is with one of the drivers using i2c in the latest
toggle quoted messageShow quoted text
kernel which causes the sensors command to not run. Could you please post the console output of these 2 commands: uname -a journalctl -u draws-manager.service Thanks, /Basil n7nix Charlie Hein <chein@bellsouth.net> writes:
OH! Thanks for the grace applied to my ignorance, Gayland!
|
|
|
|
Gayland Gump
No, problem. Been there, done that and am still there more often than I care to admit. Gayland KG7GCF
On Wed, Jul 29, 2020 at 11:13 AM Charlie Hein <chein@...> wrote: OH! Thanks for the grace applied to my ignorance, Gayland!
|
|
|
|
Charlie Hein
OH! Thanks for the grace applied to my ignorance, Gayland!
John: Here is the output: pi@nvdpi:/etc $ cd
pi@nvdpi:~ $ which node
/usr/bin/node
pi@nvdpi:~ $ which npm
/usr/local/bin/npm
pi@nvdpi:~ $
Charlie (N4NVD)
|
|
|
|
Gayland Gump
Charlie, I believe, John is asking you to run "which node" and "which npm" commands, which is a program that tells you if these programs are installed. Gayland KG7GCF
On Wed, Jul 29, 2020 at 11:03 AM Charlie Hein <chein@...> wrote: I'm not sure I follow, John.
|
|
|
|
Charlie Hein
I'm not sure I follow, John.
"What is the response to which node
which npm"
Are there specific commands I should know?Charlie
|
|
|
|
What is the response to which node which npm
On Wed, Jul 29, 2020 at 10:08 AM Charlie Hein <chein@...> wrote:
--
John D. Hays Kingston, WA K7VE
|
|
|
|
Charlie Hein
Here's the output from the command:
pi@nvdpi:~ $ sudo systemctl status draws-manager ● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™
Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor pr
Active: failed (Result: exit-code) since Wed 2020-07-29 11:31:46 CDT; 30min a
Docs: https://github.com/nwdigitalradio/draws-manager
Process: 1709 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
Main PID: 1709 (code=exited, status=1/FAILURE)
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 scrip
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! This is probably not a problem with np
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! A complete log of this run can be foun
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! /root/.npm/_logs/2020-07-29T16_31_
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Main process exited, co
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Failed with result 'exi
lines 1-17/17 (END)...skipping...
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-07-29 11:31:46 CDT; 30min ago
Docs: https://github.com/nwdigitalradio/draws-manager
Process: 1709 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
Main PID: 1709 (code=exited, status=1/FAILURE)
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'.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
pi@nvdpi:~ $
|
|
|
|
Look at the output of systemctl status draws-manager
On Wed, Jul 29, 2020 at 9:57 AM Charlie Hein <chein@...> wrote:
--
John D. Hays Kingston, WA K7VE
|
|
|
|
Charlie Hein
Watched the Demo Video, got excited, but when I try to run draws-manager from either a desktop or localhost, I get this:
I've tried stopping and restarting draws-manager to no avail. Charlie
|
|
|
|
Fred Hirsch <Hirschfh@...>
Test worked great now that I know what to look for, 100% fixed. Sorry I made it hard on you, but I learned a lot and thanks for that.
toggle quoted messageShow quoted text
I never have programed in C, C+, or linux. I was an old FORTRAN guy. Somebody wanted to know what I wanted DRAWS to do with my
Kenwood TH-H710G. I told him I just wanted it to monitor the radio on which I run APRS and have it put out WX data from my weather station. Is there a app
for that?
Now for HF I am keen to have it help me with RTTY and other digital modes. Guess I will have to build a cable or have the guy who makes them
help me out. I like the GPS/antenna which works well on the back porch.
Thank you very much for the help.
-----Original Message-----
From: John D Hays - K7VE <john@...> To: udrc <udrc@nw-digital-radio.groups.io> Sent: Fri, Apr 5, 2019 2:25 pm Subject: Re: [udrc] DRAWS™ Manager Demo #drawsmanager It only saves the values, not the selected radio.
E.g. if you select ft-817 AF, note the values. Then save. When you restart the selected values should be what you saved, but the radio pre-select will go back to default.
On Fri, Apr 5, 2019, 13:08 Fred Hirsch via Groups.Io <Hirschfh=aol.com@groups.io> wrote:
I may have found my problem. I am running a device that protects my server it is call RECON SENTENEL so I checked it and found
|
|
|
|
It only saves the values, not the selected radio. E.g. if you select ft-817 AF, note the values. Then save. When you restart the selected values should be what you saved, but the radio pre-select will go back to default.
On Fri, Apr 5, 2019, 13:08 Fred Hirsch via Groups.Io <Hirschfh=aol.com@groups.io> wrote: I may have found my problem. I am running a device that protects my server it is call RECON SENTENEL so I checked it and found
|
|
|
|
Fred Hirsch <Hirschfh@...>
I may have found my problem. I am running a device that protects my server it is call RECON SENTENEL so I checked it and found
toggle quoted messageShow quoted text
that it had blocked the raspberry pi. I unblocked it and did an update. No error message so I assume it worked. Selected a sample radio type and
tried to save the audio picked. Rebooted, but the saved did not return. So 50% fixed.
-----Original Message-----
From: John D Hays - K7VE <john@...> To: udrc <udrc@nw-digital-radio.groups.io> Sent: Fri, Apr 5, 2019 11:10 am Subject: Re: [udrc] DRAWS™ Manager Demo #drawsmanager You need to figure out why you are not resolving the address. This is a local network administration issue, not a draws-manager specific issue.
Try the ping tests I listed earlier. You can also try, from a terminal on the Raspberry Pi.
cd /usr/local/var/draws-manager
sudo git pull
sudo systemctl restart draws-manager
Wait about 30 seconds and try connecting from your browser again. On Fri, Apr 5, 2019 at 9:44 AM Fred Hirsch via Groups.Io <Hirschfh=aol.com@groups.io> wrote:
I used https://draws.local:8080 and received the same error message several second after commanding John D. Hays
Edmonds, WA K7VE
  
|
|
|
|
Fred Hirsch <Hirschfh@...>
Set nameservers to 1.1.1.1 and 8.8.8.8 and verified they took, but ping gitHub.com came back with a name recognition problem.
toggle quoted messageShow quoted text
ping google.com worked fine. I better have my son on site get the fix. Don't understand why the pi can not connect to gitHub.com when it connects to other sites. Let's not spend time on this you have better thing to do. Yes, after a reboot name servers go back to the original values. Maybe I should just delete the 295.1/1.2.25, and try that?
-----Original Message-----
From: John D Hays - K7VE <john@...> To: udrc <udrc@nw-digital-radio.groups.io> Sent: Fri, Apr 5, 2019 11:58 am Subject: Re: [udrc] DRAWS™ Manager Demo #drawsmanager See notes below
On Fri, Apr 5, 2019 at 10:31 AM Fred Hirsch via Groups.Io <Hirschfh=aol.com@groups.io> wrote:
domain Home What I would try is editing /etc/resolv.conf
cd /etc
cp resolv.conf resolv.conf.backup
sudo nano resolv.conf
In the editor delete or comment out (comments are lines starting with a # or ;) the two nameserver lines and add
nameserver 1.1.1.1
nameserver 8.8.8.8
Save and exit, then try pinging again to github.com
If that works, you should then be able to run the scripts or the update button.
These edited lines may disappear upon reboot, but when your son is over have him troubleshoot your network setup.
For the readers -- 1.1.1.1 is a very fast, distributed nameserver by Cloudflare, 8.8.8.8 is a public nameserver by Google.
John D. Hays
Edmonds, WA K7VE
|
|
|