Date   

Re: New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Microbes
 

Thanks Basil.

HF to begin, I am new to digital modes and have worked with Windows and my IC-7300. In reality using on an FT818, but should be the same settings as 817 to start. I figured I can adjust settings for AZ25 once I get going.

I already ran through the "fix" for the new image version, which states the draws-manager web app is disabled:

https://nw-digital-radio.groups.io/g/udrc/message/5111

I see from your post, there are other options to set the ALSA, I used the ft817 script and the values changed; I assume to some that another person used for their rig.

Tuning the FM for VHF/UHF can be done if I get that far. As of now, chrony isn't using the GPS for time (shows #? instead of #*). I thought that would be set up in the image already.

I am on separate PC responding, so I abbreviated some of the outputs to reduce typing.

Following the check GPS link you provided:

To clarify what I meant by it "running"

systemctl status chronyd returns: active(running), but no indication of a GPS as a selected source.

gpsmon show data scrolling at bottom, but no latitude/longitude/speed/altitude values (all zero)

Antenna has a clear view of sky.

cgps show no values in the boxed area, lots of "n/a"

underneath, this refreshes every second:

{"class":"TPV","device"":"/dev/ttySC0","mode":1,"time":"changes-everysecond", "ept":0.005}

running chronyc sourcestats give:

GPS 0 0 0 +0.0000 2000.000 +0ns 4000ms
PPT is same
then several web sources listed.

Maybe the chrony not set up to take PPT?

chronyc tracking shows a web server for the Reference ID


I am going to run through the complete installation again, using the ft817 script.

For "Third Boot" on the walk-through it may be helpful to edit the statement "You must set your ALSA configuration for your particular radio at this time" with instruction on how to do that, which seems to be either with draws-manager, or with alsamixer, or by running a script.

Thanks again for your help. I think if folks have experience setting up Pis to run digital modes without the DRAWS hat, a lot of the tools are already understood.

-S


Re: New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Basil Gunn
 

on the "Third Boot" stage , it states:
"You must set your ALSA configuration for your particular radio at this time" - with no instruction on what that means or how to do it.

I followed a video online and got "alsa-show.sh" to show different values, I assume for the FT817.
You are not providing any information about which HF or VHF/UHF
radio on the FT817 you are using.

Assuming you want packet on your VHF/UHF radio working, like any TNC
or sound card you need to set the FM deviation properly.

There is a section on how to set your deviation here:
https://github.com/nwdigitalradio/n7nix/tree/master/deviation

You can run run draws-manager to help set that up.
Or you can set ALSA settings with the alsamixer program
Or you can run the setalsa-ft817.sh script

https://github.com/nwdigitalradio/n7nix/blob/master/docs/DRAWS_ALSA.md

Need help with: Do need the radio connect with control cable and
powered up during any of the DRAWS set-up?
No but the DRAWS hat needs to be installed. The left mDin6 connector is
direwolf port 0.

I can't figure out if I am supposed to try to get draws_manager to run
or not.
This was brought up in the forums last week:

https://nw-digital-radio.groups.io/g/udrc/topic/can_t_access_draws_manager/76528127?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,76528127

# To install the latest version of draws-manager
cd
cd n7nix
git pull
cd manager
sudo su
./install.sh

I had it running in the past, but can't get it to run now and I read
it is not compatible with current sensor files.
That was fixed about 6 months ago

So, do I need it?
It is a nice tool to use.

Are there ways to change the same values without the web interface
(always fails to connect and went through other troubleshooting posted
here, gave up).
alsamixer
or
just run the script.
setalsa-ft817.sh

Do I need GPS working up-front?
I can run gpsd, and it is listed as active an running, but no
longitude or latitude shows up.
Not sure what you mean. gpsd is already running on the NWDR image.
If you want to verify the gps follow the examples under Check GPS

https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md#check-gps

I suspect DRAWS doesn't see the antenna.
It helps to put your antenna close to a window.

Do I focus on getting draws_manager to run or get the gps to report data?

Maybe someone can point me to a step-by-step walk through, but I
haven't found one.
The "Getting Started Guide" found in the wiki is the step-by-step guide
you want to use. There are a number of links in that guide for other
documentation for example under '3. Third boot' there is a link for
verifying your installation.

https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md

Be aware that you will probably need different alsa settings for the HF
radio FT817 and the vhf/uhf radio. Search the forum for your radio for
more hints.
https://nw-digital-radio.groups.io/g/udrc/search?q=ft817

If I remember correctly I had to remove pin 6 on the mDin6 connector to
get audio working on the FT-817. This was discussed on the forum here:

https://nw-digital-radio.groups.io/g/udrc/topic/33061161#4083


New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Microbes
 

I bought the DRAWS hat in the summer with the intent of using an FT817 for digital on a pi4 B.

I gave up then after getting gps to work, but never getting radio control.

I recently revisited for the holidays - installed fresh image ( current_image ) and tried again. Following the wiki:

on the "Third Boot" stage , it states:

"You must set your ALSA configuration for your particular radio at this time" - with no instruction on what that means or how to do it.  

I followed a video online and got "alsa-show.sh" to show different values, I assume for the FT817. 

Need help with: 

Do  need the radio connect with control cable and powered up during any of the DRAWS set-up?

I can't figure out if I am supposed to try to get draws_manager to run or not. I had it running in the past, but can't get it to run now and I read it is not compatible with current sensor files.
 So, do I need it? Are there ways to change the same values without the web interface (always fails to connect and went through other troubleshooting posted here, gave up).

Do I need GPS working up-front?  I can run gpsd, and it is listed as active an running, but no longitude or latitude shows up. I suspect DRAWS doesn't see the antenna.

Do I focus on getting draws_manager to run or get the gps to report data?

Maybe someone can point me to a step-by-step walk through, but I haven't found one. 

I appreciate any help. 










Re: Can't access Draws Manager

 

You should turn DRAWS™ Manager off when not in use.   It is basically a configuration application. 

You can use systemctl to turn it on and off. To make it automatically start and stop you can use enable and disable. 

Try

man systemctl



On Fri, Dec 18, 2020, 09:21 Tim Huffaker <thuffaker@...> wrote:
Basil,
I re-imaged with a fresh copy of V18.  Ran this script:
cd
cd n7nix
git pull
cd manager <---- you didn't do this
sudo su
./install.sh
Now I have Draws manager running.  
Do I need to restart Draws manager anytime or does it run all the time?
thank you for your help. 
Tim 
KM4ESU


Re: Can't access Draws Manager

Tim Huffaker
 

Basil,
I re-imaged with a fresh copy of V18.  Ran this script:
cd
cd n7nix
git pull
cd manager <---- you didn't do this
sudo su
./install.sh
Now I have Draws manager running.  
Do I need to restart Draws manager anytime or does it run all the time?
thank you for your help. 
Tim 
KM4ESU


Re: Can't access Draws Manager (slightly off topic)

Daniel VE3NI
 

Basil,

Thanks for the explanation.

Daniel

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Friday, December 18, 2020 2:01 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager (slightly off
topic)


sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh
This is exactly right. This will get almost all of the contents of the
latest image. I try to keep everything updated via scripts. If you are using
some of the HF programs you should also do:

cd
cd n7nix/hfprogs
./hf_verchk.sh

# To do the actual update add a -u
./hf_verchk.sh -u

# For the NWDR18 image at this time everything is current.

cd hfprogs/
./hf_verchk.sh

js8call: current version: 2.2.0, installed: 2.2.0
wsjtx: current version: 2.2.2, installed: 2.2.2
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.17, installed: 4.1.17
flrig: current version: 1.3.53, installed: 1.3.53
flmsg: current version: 4.0.17, installed: 4.0.17
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: 1.2.6

Everything that makes sense to get from the Debian/Raspberry Pi OS
repositories I do. For most of the HAM programs I try to use their own
repositories since they are generally not maintained in the Debian repo any
way.

My image started out as NWDR16

I have been using the commands below after each release announcement.

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

After running these commands I am running the equivalent of the NWDR
released software?

Just want to be sure that I am doing it right.

Thanks,
Daniel VE3NI


-----Original Message-----
From: udrc@nw-digital-radio.groups.io
<udrc@nw-digital-radio.groups.io> On Behalf Of Basil Gunn
Sent: Thursday, December 17, 2020 7:18 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager


I won't discourage someone from installing the latest version of some
tool but a lot of time has gone into making sure that what is on the
image actually works. I don't have time to support anything other than
what is on the image. Perhaps someone else on the forum can help.

To be clear many/most of the HAM apps on the image are the latest
version and there are scripts on the image to keep them that way.
I used to use the latest version of nodejs, been down that road and
currently don't want or need to do that.

You should confirm that your image started out as NWDR18:

head -n1 /var/log/udr_install.log

2020 12 04 13:45:55 PST: SD image version: nwdr18

Also:

aplay -l
showudrc.sh

Did you follow the getting started guide?
https://nw-digital-radio.groups.io/g/udrc/wiki/8921


Re: Can't access Draws Manager (slightly off topic)

Basil Gunn
 

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh
This is exactly right. This will get almost all of the contents of the
latest image. I try to keep everything updated via scripts. If you are
using some of the HF programs you should also do:

cd
cd n7nix/hfprogs
./hf_verchk.sh

# To do the actual update add a -u
./hf_verchk.sh -u

# For the NWDR18 image at this time everything is current.

cd hfprogs/
./hf_verchk.sh

js8call: current version: 2.2.0, installed: 2.2.0
wsjtx: current version: 2.2.2, installed: 2.2.2
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.17, installed: 4.1.17
flrig: current version: 1.3.53, installed: 1.3.53
flmsg: current version: 4.0.17, installed: 4.0.17
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: 1.2.6

Everything that makes sense to get from the Debian/Raspberry Pi OS
repositories I do. For most of the HAM programs I try to use their own
repositories since they are generally not maintained in the Debian repo
any way.

My image started out as NWDR16

I have been using the commands below after each release announcement.

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

After running these commands I am running the equivalent of the NWDR
released software?

Just want to be sure that I am doing it right.

Thanks,
Daniel VE3NI


-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Thursday, December 17, 2020 7:18 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager


I won't discourage someone from installing the latest version of some tool
but a lot of time has gone into making sure that what is on the image
actually works. I don't have time to support anything other than what is on
the image. Perhaps someone else on the forum can help.

To be clear many/most of the HAM apps on the image are the latest version
and there are scripts on the image to keep them that way.
I used to use the latest version of nodejs, been down that road and
currently don't want or need to do that.

You should confirm that your image started out as NWDR18:

head -n1 /var/log/udr_install.log

2020 12 04 13:45:55 PST: SD image version: nwdr18

Also:

aplay -l
showudrc.sh

Did you follow the getting started guide?
https://nw-digital-radio.groups.io/g/udrc/wiki/8921


Re: Can't access Draws Manager (slightly off topic)

Daniel VE3NI
 

Basil,

Just so that I understand.

My image started out as NWDR16

I have been using the commands below after each release announcement.

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

After running these commands I am running the equivalent of the NWDR
released software?

Just want to be sure that I am doing it right.

Thanks,
Daniel VE3NI

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Thursday, December 17, 2020 7:18 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager


I won't discourage someone from installing the latest version of some tool
but a lot of time has gone into making sure that what is on the image
actually works. I don't have time to support anything other than what is on
the image. Perhaps someone else on the forum can help.

To be clear many/most of the HAM apps on the image are the latest version
and there are scripts on the image to keep them that way.
I used to use the latest version of nodejs, been down that road and
currently don't want or need to do that.

You should confirm that your image started out as NWDR18:

head -n1 /var/log/udr_install.log

2020 12 04 13:45:55 PST: SD image version: nwdr18

Also:

aplay -l
showudrc.sh

Did you follow the getting started guide?
https://nw-digital-radio.groups.io/g/udrc/wiki/8921


Re: Can't access Draws Manager

Basil Gunn
 

I won't discourage someone from installing the latest version of some
tool but a lot of time has gone into making sure that what is on the
image actually works. I don't have time to support anything other than
what is on the image. Perhaps someone else on the forum can help.

To be clear many/most of the HAM apps on the image are the latest
version and there are scripts on the image to keep them that way.
I used to use the latest version of nodejs, been down that road and
currently don't want or need to do that.

You should confirm that your image started out as NWDR18:

head -n1 /var/log/udr_install.log

2020 12 04 13:45:55 PST: SD image version: nwdr18

Also:

aplay -l
showudrc.sh

Did you follow the getting started guide?
https://nw-digital-radio.groups.io/g/udrc/wiki/8921


Tim Huffaker <thuffaker@mindspring.com> writes:

Basil,
I thought this was V18 Draws image. I did not program the SD card a buddy did sine my computer crashed and the new one wont get here until Jan 4.

pi@KM4ESU:~ $ nodejs --version
v15.4.0
pi@KM4ESU:~ $ npm --version
6.14.9
pi@KM4ESU:~ $

Tim
KM4ESU


Re: Can't access Draws Manager

Tim Huffaker
 

Basil,
I thought this was V18 Draws image.  I did not program the SD card a buddy did sine my computer crashed and the new one wont get here until Jan 4. 

pi@KM4ESU:~ $ nodejs --version
v15.4.0
pi@KM4ESU:~ $ npm --version
6.14.9
pi@KM4ESU:~ $ 

Tim
KM4ESU 


Re: Can't access Draws Manager

Basil Gunn
 

It looks like you are not using an NWDR image?

nodejs comes installed on an NWDR image and is a version that works with
most things, ie. it's in the Debian repository. It looks like you
installed nodejs from source, is that true?

nodejs is already the newest version (15.4.0-1nodesource1)
Show me the version of nodejs & npm on your unit.

nodejs --version
npm --version

For example from the NWDR18 image

$ nodejs --version
v10.21.0
$ npm --version
6.14.9


Tim Huffaker <thuffaker@mindspring.com> writes:

Hi Basil,it looks like some dependency is missing see below.

=== Installing required PACKAGES
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.20.1-2+deb10u3).
nodejs is already the newest version (15.4.0-1nodesource1).

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
nodejs : Conflicts: npm
npm : Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Package install failed. Please try this command manually:
apt-get -y nodejs npm git
root@KM4ESU:/home/pi/n7nix/manager#

Tim
KM4ESU


Re: Can't access Draws Manager

Tim Huffaker
 

Hi Basil,it looks like some dependency is missing  see below.  

pi@KM4ESU:~/n7nix/manager $ sudo su
root@KM4ESU:/home/pi/n7nix/manager# ./install.sh
2020 12 17 15:01:06 CST: install.sh: draws-manager install script START
Check required packages: nodejs npm git
install.sh: Will Install npm package
   Check for existence of local draws-manager repo
true
About to update draws-manager repo, removing package-lock
Successfully removed webapp/package-lock.json
remote: Enumerating objects: 29, done.
remote: Counting objects: 100% (29/29), done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 29 (delta 18), reused 3 (delta 3), pack-reused 0
Unpacking objects: 100% (29/29), done.
From https://github.com/nwdigitalradio/draws-manager
   8e7edb6..a3cbdd7  master     -> origin/master
 * [new branch]      sensor_fix -> origin/sensor_fix
Updating 8e7edb6..a3cbdd7
Fast-forward
 webapp/io.js             |   6 +-
 webapp/package-lock.json | 685 +++++++++++++++++++++++++----------------------
 webapp/package.json      |   2 +-
 3 files changed, 363 insertions(+), 330 deletions(-)
 
=== Installing required PACKAGES
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.20.1-2+deb10u3).
nodejs is already the newest version (15.4.0-1nodesource1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
 
The following packages have unmet dependencies:
 nodejs : Conflicts: npm
 npm : Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Package install failed. Please try this command manually:
apt-get -y nodejs npm git
root@KM4ESU:/home/pi/n7nix/manager# 

Tim 
KM4ESU


Re: Can't access Draws Manager

Basil Gunn
 

You missed the command that changes to the manager directory which is
where the manager install.sh script lives.

cd
cd n7nix
git pull
cd manager <---- you didn't do this
sudo su
./install.sh

Tim Huffaker <thuffaker@mindspring.com> writes:

Basil, I think I am getting closer, but I get this error

pi@KM4ESU:~ $ cd
pi@KM4ESU:~ $ cd n7nix
pi@KM4ESU:~/n7nix $ get pull
bash: get: command not found
pi@KM4ESU:~/n7nix $ git pull
pi@KM4ESU:~/n7nix $ sudo su
root@KM4ESU:/home/pi/n7nix# ./install.sh
bash: ./install.sh: No such file or directory
root@KM4ESU:/home/pi/n7nix# ./install.sh
bash: ./install.sh: No such file or directory
root@KM4ESU:/home/pi/n7nix# ls
aprx bin deviation gps mailserv splitchan vnc
ardop ChangeLog direwolf hfprogs manager systemd watchdog
ax25 change_user docs hostap plu tracker xastir
baudrate config dstar iptables README.md uronode yaac
bbs debug email kernbuild rmsgw usbsnd
root@KM4ESU:/home/pi/n7nix# ./install.sh
bash: ./install.sh: No such file or directory


Re: Can't access Draws Manager

Tim Huffaker
 

Basil,  I think I am getting closer, but I get this error

pi@KM4ESU:~ $ cd
pi@KM4ESU:~ $ cd n7nix
pi@KM4ESU:~/n7nix $ get pull
bash: get: command not found
pi@KM4ESU:~/n7nix $ git pull
remote: Enumerating objects: 29, done.
remote: Counting objects: 100% (29/29), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 20 (delta 12), reused 18 (delta 10), pack-reused 0
Unpacking objects: 100% (20/20), done.
From https://github.com/nwdigitalradio/n7nix
   4e95d77..17e0c79  master     -> origin/master
Updating 4e95d77..17e0c79
Fast-forward
 baudrate/README.md  | 10 ++++++++++
 bin/alsa-show.sh    |  1 +
 deviation/README.md | 12 +++++++-----
 manager/install.sh  | 40 +++++++++++++++++++++++++++-------------
 4 files changed, 45 insertions(+), 18 deletions(-)
pi@KM4ESU:~/n7nix $ sudo su
root@KM4ESU:/home/pi/n7nix# ./install.sh
bash: ./install.sh: No such file or directory
root@KM4ESU:/home/pi/n7nix# ./install.sh
bash: ./install.sh: No such file or directory
root@KM4ESU:/home/pi/n7nix# ls
aprx   bin        deviation  gps      mailserv splitchan  vnc
ardop   ChangeLog    direwolf   hfprogs    manager systemd    watchdog
ax25   change_user  docs   hostap     plu tracker    xastir
baudrate  config       dstar   iptables   README.md uronode    yaac
bbs   debug        email   kernbuild  rmsgw usbsnd
root@KM4ESU:/home/pi/n7nix# ./install.sh
bash: ./install.sh: No such file or directory
root@KM4ESU:/home/pi/n7nix# 
 


Re: Can't access Draws Manager

Basil Gunn
 

Thank you Daniel, I appreciate you letting me know.
/Basil n7nix

Daniel VE3NI <dgoodier@gmail.com> writes:

Basil,

Thanks.

That did the trick.

Daniel VE3NI

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Basil Gunn
Sent: Thursday, December 17, 2020 1:53 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager


Tim,
Thanks for the console output.

It looks like draws-manager did not get refreshed in the latest NWDR image. Could you please update the n7nix repo and then run the draws-manager install which will update it to the latest version.

cd
cd n7nix
git pull
cd manager
sudo su
./install.sh


Re: Can't access Draws Manager

Daniel VE3NI
 

Basil,

Thanks.

That did the trick.

Daniel VE3NI

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Basil Gunn
Sent: Thursday, December 17, 2020 1:53 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager


Tim,
Thanks for the console output.

It looks like draws-manager did not get refreshed in the latest NWDR image. Could you please update the n7nix repo and then run the draws-manager install which will update it to the latest version.

cd
cd n7nix
git pull
cd manager
sudo su
./install.sh

Hi Basil, I tried the commands and got errors.

pi@KM4ESU:~ $ sudo systemctl start draws-manager pi@KM4ESU:~ $ sudo
systemctl --no-pager status draws-manager ● draws-manager.service -
DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
Loaded: loaded (/etc/systemd/system/draws-manager.service; disabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-12-17 11:26:31 CST;
43s ago
Docs: https://github.com/nwdigitalradio/draws-manager
Process: 29517 ExecStart=/usr/bin/npm start (code=exited,
status=1/FAILURE) Main PID: 29517 (code=exited, status=1/FAILURE)


Re: Can't access Draws Manager

Basil Gunn
 

Tim,
Thanks for the console output.

It looks like draws-manager did not get refreshed in the latest
NWDR image. Could you please update the n7nix repo and then run the
draws-manager install which will update it to the latest version.

cd
cd n7nix
git pull
cd manager
sudo su
./install.sh

Hi Basil, I tried the commands and got errors.

pi@KM4ESU:~ $ sudo systemctl start draws-manager
pi@KM4ESU:~ $ sudo systemctl --no-pager status draws-manager
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
Loaded: loaded (/etc/systemd/system/draws-manager.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-12-17 11:26:31 CST; 43s ago
Docs: https://github.com/nwdigitalradio/draws-manager
Process: 29517 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
Main PID: 29517 (code=exited, status=1/FAILURE)


Re: Can't access Draws Manager

Daniel VE3NI
 

Hi Basil,

 

I am running into the same situation.

 

Here is the log.

 

0 info it worked if it ends with ok

1 warn npm npm does not support Node.js v10.21.0

2 warn npm You should probably upgrade to a newer version of node as we

3 warn npm can't make any promises that npm will work with this version.

4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.

5 warn npm You can find the latest version at https://nodejs.org/

6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]

7 info using npm@5.8.0

8 info using node@...

9 verbose run-script [ 'prestart', 'start', 'poststart' ]

10 info lifecycle webapp@0.0.1~prestart: webapp@0.0.1

11 info lifecycle webapp@0.0.1~start: webapp@0.0.1

12 verbose lifecycle webapp@0.0.1~start: unsafe-perm in lifecycle true

13 verbose lifecycle webapp@0.0.1~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/local/var/draws-manager/webapp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

14 verbose lifecycle webapp@0.0.1~start: CWD: /usr/local/var/draws-manager/webapp

15 silly lifecycle webapp@0.0.1~start: Args: [ '-c', 'node ./bin/www' ]

16 silly lifecycle webapp@0.0.1~start: Returned: code: 1  signal: null

17 info lifecycle webapp@0.0.1~start: Failed to exec start script

18 verbose stack Error: webapp@0.0.1 start: `node ./bin/www`

18 verbose stack Exit status 1

18 verbose stack     at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16)

18 verbose stack     at EventEmitter.emit (events.js:198:13)

18 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)

18 verbose stack     at ChildProcess.emit (events.js:198:13)

18 verbose stack     at maybeClose (internal/child_process.js:982:16)

18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)

19 verbose pkgid webapp@0.0.1

20 verbose cwd /usr/local/var/draws-manager/webapp

21 verbose Linux 5.4.79-v7+

22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"

23 verbose node v10.21.0

24 verbose npm  v5.8.0

25 error code ELIFECYCLE

26 error errno 1

27 error webapp@0.0.1 start: `node ./bin/www`

27 error Exit status 1

28 error Failed at the webapp@0.0.1 start script.

28 error This is probably not a problem with npm. There is likely additional logging output above.

29 verbose exit [ 1, true ]

 

Thanks,

Daniel VE3NI

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Tim Huffaker
Sent: Thursday, December 17, 2020 12:32 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager

 

Hi Basil,  I tried the commands and got errors.

pi@KM4ESU:~ $ sudo systemctl start draws-manager

pi@KM4ESU:~ $ sudo systemctl --no-pager status draws-manager

● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.

   Loaded: loaded (/etc/systemd/system/draws-manager.service; disabled; vendor preset: enabled)

   Active: failed (Result: exit-code) since Thu 2020-12-17 11:26:31 CST; 43s ago

  Process: 29517 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)

 Main PID: 29517 (code=exited, status=1/FAILURE)

 

Dec 17 11:26:31 KM4ESU npm[29517]:   ]

Dec 17 11:26:31 KM4ESU npm[29517]: }

Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! code 1

Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! path /usr/local/var/draws-manag…bapp

Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! command failed

Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! command sh -c node ./bin/www

Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! A complete log of this run can … in:

Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR!     /root/.npm/_logs/2020-12-17….log

Dec 17 11:26:31 KM4ESU systemd[1]: draws-manager.service: Main process exit…LURE

Dec 17 11:26:31 KM4ESU systemd[1]: draws-manager.service: Failed with resul…de'.

Hint: Some lines were ellipsized, use -l to show in full.

pi@KM4ESU:~ $ 


Tim 
KM4ESU


Re: Can't access Draws Manager

Tim Huffaker
 

Hi Basil,  I tried the commands and got errors.

pi@KM4ESU:~ $ sudo systemctl start draws-manager
pi@KM4ESU:~ $ sudo systemctl --no-pager status draws-manager
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
   Loaded: loaded (/etc/systemd/system/draws-manager.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-12-17 11:26:31 CST; 43s ago
     Docs: https://github.com/nwdigitalradio/draws-manager
  Process: 29517 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
 Main PID: 29517 (code=exited, status=1/FAILURE)
 
Dec 17 11:26:31 KM4ESU npm[29517]:   ]
Dec 17 11:26:31 KM4ESU npm[29517]: }
Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! code 1
Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! path /usr/local/var/draws-manag…bapp
Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! command failed
Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! command sh -c node ./bin/www
Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR! A complete log of this run can … in:
Dec 17 11:26:31 KM4ESU npm[29517]: npm ERR!     /root/.npm/_logs/2020-12-17….log
Dec 17 11:26:31 KM4ESU systemd[1]: draws-manager.service: Main process exit…LURE
Dec 17 11:26:31 KM4ESU systemd[1]: draws-manager.service: Failed with resul…de'.
Hint: Some lines were ellipsized, use -l to show in full.
pi@KM4ESU:~ $ 

Tim 
KM4ESU


Re: Can't access Draws Manager

Basil Gunn
 

I decided to use draws manager to see how the configure the
draws for other modes. When I tried localhost:8080 the browser said
the site cannot be reached.
How do I get the draws manager working?
sudo systemctl start draws-manager
sudo systemctl --no-pager status draws-manager

581 - 600 of 5868