开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Error running FRStack using wiki procedure


 

I am new to Nodered and FRStack. I followed the procedure on the Wiki to install and ran into an issue with the FRStack WebAPI.

I am using the procedure here:?/g/nodered-hamradio/wiki/22502


I did the steps to download and unzip FRStack. I verified each step worked.

Install FRStack WebAPI on RPi

sudo mkdir -p /usr/local/frstack

cd /usr/local/frstack

sudo wget http://www.mkcmsoftware.com/download/FRStackWebApiRpi.zip

sudo unzip FRStackWebApiRpi

?

Run FRStack WebAPI from commandline

dotnet FRStackWebApi.dll --urls "http://*:5025"

When I enter the?botnet?command, I receive the following error:

pi@nodered:/usr/local/frstack$ dotnet FRStackWebApi.dll --urls "http://*:5025"

-bash: /usr/bin/dotnet: cannot execute binary file: Exec format error




Has anyone run into that?

Thanks,

Tom NY4I



 

Hi Tom,

I had the same error. What fixed everything for me was installing the service and then rebooting the pi.

Install FRStackWebApi as service

sudo cp FRStackWebApi.service /lib/systemd/system

sudo systemctl daemon-reload

sudo systemctl enable FRStackWebApi



Gary
K6HN


 

开云体育

Hmm. I wrote the WiKi copying Mark’s instructions.?

I would think you would want 127.0.0.1 instead of *

Strange. Let me know if it works using the 127.0.0.1 address and I will update the WiKi

73
Dave wo2x

Sent from my waxed string and tin cans.?

On Aug 19, 2020, at 2:15 PM, Tom Schaefer NY4I <thomasmschaefer@...> wrote:

?I am new to Nodered and FRStack. I followed the procedure on the Wiki to install and ran into an issue with the FRStack WebAPI.

I am using the procedure here:?/g/nodered-hamradio/wiki/22502


I did the steps to download and unzip FRStack. I verified each step worked.

Install FRStack WebAPI on RPi

sudo mkdir -p /usr/local/frstack

cd /usr/local/frstack

sudo wget http://www.mkcmsoftware.com/download/FRStackWebApiRpi.zip

sudo unzip FRStackWebApiRpi

?

Run FRStack WebAPI from commandline

dotnet FRStackWebApi.dll --urls "http://*:5025"

When I enter the?botnet?command, I receive the following error:

pi@nodered:/usr/local/frstack$ dotnet FRStackWebApi.dll --urls "http://*:5025"

-bash: /usr/bin/dotnet: cannot execute binary file: Exec format error




Has anyone run into that?

Thanks,

Tom NY4I



 

开云体育

I just realized I am on Stretch. Upgrading the RPi to Buster and trying again.?

Hazards of having 15 RPis in the house.?

Tom NY4I


Principal Solutions Architect
Better Software Solutions, Inc.?
727-437-2771

On Aug 19, 2020, at 2:15 PM, Tom Schaefer NY4I via groups.io <thomasmschaefer@...> wrote:

?I am new to Nodered and FRStack. I followed the procedure on the Wiki to install and ran into an issue with the FRStack WebAPI.

I am using the procedure here:?/g/nodered-hamradio/wiki/22502


I did the steps to download and unzip FRStack. I verified each step worked.

Install FRStack WebAPI on RPi

sudo mkdir -p /usr/local/frstack

cd /usr/local/frstack

sudo wget http://www.mkcmsoftware.com/download/FRStackWebApiRpi.zip

sudo unzip FRStackWebApiRpi

?

Run FRStack WebAPI from commandline

dotnet FRStackWebApi.dll --urls "http://*:5025"

When I enter the?botnet?command, I receive the following error:

pi@nodered:/usr/local/frstack$ dotnet FRStackWebApi.dll --urls "http://*:5025"

-bash: /usr/bin/dotnet: cannot execute binary file: Exec format error




Has anyone run into that?

Thanks,

Tom NY4I



 

开云体育

That’s a lot of Pi. Too bad they aren’t the kind you can eat. I prefer Boston Creame Pie.?

Sorry. Needed some humor today.?

Dave wo2x

Sent from my waxed string and tin cans.?

On Aug 19, 2020, at 2:19 PM, Tom Schaefer NY4I <thomasmschaefer@...> wrote:

?I just realized I am on Stretch. Upgrading the RPi to Buster and trying again.?

Hazards of having 15 RPis in the house.?

Tom NY4I


Principal Solutions Architect
Better Software Solutions, Inc.?
727-437-2771

On Aug 19, 2020, at 2:15 PM, Tom Schaefer NY4I via groups.io <thomasmschaefer@...> wrote:

?I am new to Nodered and FRStack. I followed the procedure on the Wiki to install and ran into an issue with the FRStack WebAPI.

I am using the procedure here:?/g/nodered-hamradio/wiki/22502


I did the steps to download and unzip FRStack. I verified each step worked.

Install FRStack WebAPI on RPi

sudo mkdir -p /usr/local/frstack

cd /usr/local/frstack

sudo wget http://www.mkcmsoftware.com/download/FRStackWebApiRpi.zip

sudo unzip FRStackWebApiRpi

?

Run FRStack WebAPI from commandline

dotnet FRStackWebApi.dll --urls "http://*:5025"

When I enter the?botnet?command, I receive the following error:

pi@nodered:/usr/local/frstack$ dotnet FRStackWebApi.dll --urls "http://*:5025"

-bash: /usr/bin/dotnet: cannot execute binary file: Exec format error




Has anyone run into that?

Thanks,

Tom NY4I



 

Tom

I had the same problem with that step.? In the end, the step was not necessary?and I skipped it.? Here are my notes on the FRS install.? Suggest you re-boot?your Raspberry Pi and run all of the steps from the beginning, as shown in my notes.

Alan
WA9WUD

Install .NET Notes.png

Screen Shot 2020-08-19 at 2.30.27 PM.png


 

开云体育

Thanks Alan. I will update the WiKi later.?

Dave wo2x

Sent from my waxed string and tin cans.?

On Aug 19, 2020, at 2:35 PM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:

?
Tom

I had the same problem with that step.? In the end, the step was not necessary?and I skipped it.? Here are my notes on the FRS install.? Suggest you re-boot?your Raspberry Pi and run all of the steps from the beginning, as shown in my notes.

Alan
WA9WUD

<Install .NET Notes.png>


<Screen Shot 2020-08-19 at 2.30.27 PM.png>


 

I went through your updated instructions.

Is this usually this hard? FRStackWebAPI ending with error code of "error code" is curious to say the least.


pi@nodered:~$ sudo systemctl start FRStackWebApi

Job for FRStackWebApi.service failed because the control process exited with error code.

See "systemctl status FRStackWebApi.service" and "journalctl -xe" for details.

pi@nodered:~$ journalctl -xe

Aug 19 17:41:13 nodered systemd[1]: Stopped FRStack Web APIs.

-- Subject: A stop job for unit FRStackWebApi.service has finished

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--?

-- A stop job for unit FRStackWebApi.service has finished.

--?

-- The job identifier is 1777 and the job result is done.

Aug 19 17:41:13 nodered systemd[1]: FRStackWebApi.service: Start request repeated too quickly.

Aug 19 17:41:13 nodered systemd[1]: FRStackWebApi.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--?

-- The unit FRStackWebApi.service has entered the 'failed' state with result 'exit-code'.

Aug 19 17:41:13 nodered systemd[1]: Failed to start FRStack Web APIs.

-- Subject: A start job for unit FRStackWebApi.service has failed

-- Defined-By: systemd

-- Support: https://www.debian.org/support

--?

-- A start job for unit FRStackWebApi.service has finished with a failure.

--?

-- The job identifier is 1777 and the job result is failed.

Not much in the sense of diagnostics here. This is on a Pi3B now with Buster. Rebooted several times since upgrade.

I'm willing to start from scratch on anything else if that it easier.

Heck - I'll take an IMG if we just want to test the hardware.

Thanks,

Tom NY4I

?


 

Tom

Mine went very smooth, using my notes. ? I did start with a "fresh" build on the Raspberry Pi using the Debian OS.

Alan

On Wed, Aug 19, 2020 at 5:54 PM Tom Schaefer NY4I <thomasmschaefer@...> wrote:
I went through your updated instructions.

Is this usually this hard? FRStackWebAPI ending with error code of "error code" is curious to say the least.


pi@nodered:~$ sudo systemctl start FRStackWebApi

Job for FRStackWebApi.service failed because the control process exited with error code.

See "systemctl status FRStackWebApi.service" and "journalctl -xe" for details.

pi@nodered:~$ journalctl -xe

Aug 19 17:41:13 nodered systemd[1]: Stopped FRStack Web APIs.

-- Subject: A stop job for unit FRStackWebApi.service has finished

-- Defined-By: systemd

-- Support:

--?

-- A stop job for unit FRStackWebApi.service has finished.

--?

-- The job identifier is 1777 and the job result is done.

Aug 19 17:41:13 nodered systemd[1]: FRStackWebApi.service: Start request repeated too quickly.

Aug 19 17:41:13 nodered systemd[1]: FRStackWebApi.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support:

--?

-- The unit FRStackWebApi.service has entered the 'failed' state with result 'exit-code'.

Aug 19 17:41:13 nodered systemd[1]: Failed to start FRStack Web APIs.

-- Subject: A start job for unit FRStackWebApi.service has failed

-- Defined-By: systemd

-- Support:

--?

-- A start job for unit FRStackWebApi.service has finished with a failure.

--?

-- The job identifier is 1777 and the job result is failed.

Not much in the sense of diagnostics here. This is on a Pi3B now with Buster. Rebooted several times since upgrade.

I'm willing to start from scratch on anything else if that it easier.

Heck - I'll take an IMG if we just want to test the hardware.

Thanks,

Tom NY4I

?


 

开云体育

Thanks. I will break out a fresh download of Buster.

I usually use Buster-Lite. Any reason to use a desktop config with Nodered/FRStack?

I may be wrong but I am assuming that after the flows are built, one goes to a web page to access them—not the Flow editor. I hope that is right and I do not access the flows from only the local interface of the RPi with a desktop.

Thanks,

Tom NY4I

PS Sorry for the noob questions.

On Aug 19, 2020, at 6:05 PM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:

Tom

Mine went very smooth, using my notes. ? I did start with a "fresh" build on the Raspberry Pi using the Debian OS.

Alan

On Wed, Aug 19, 2020 at 5:54 PM Tom Schaefer NY4I <thomasmschaefer@...> wrote:
I went through your updated instructions.

Is this usually this hard? FRStackWebAPI ending with error code of "error code" is curious to say the least.


pi@nodered:~$ sudo systemctl start FRStackWebApi

Job for FRStackWebApi.service failed because the control process exited with error code.

See "systemctl status FRStackWebApi.service" and "journalctl -xe" for details.

pi@nodered:~$ journalctl -xe

Aug 19 17:41:13 nodered systemd[1]: Stopped FRStack Web APIs.

-- Subject: A stop job for unit FRStackWebApi.service has finished

-- Defined-By: systemd

-- Support:?

--?

-- A stop job for unit FRStackWebApi.service has finished.

--?

-- The job identifier is 1777 and the job result is done.

Aug 19 17:41:13 nodered systemd[1]:?FRStackWebApi.service: Start request repeated too quickly.

Aug 19 17:41:13 nodered systemd[1]:?FRStackWebApi.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support:?

--?

-- The unit FRStackWebApi.service has entered the 'failed' state with result 'exit-code'.

Aug 19 17:41:13 nodered systemd[1]:?Failed to start FRStack Web APIs.

-- Subject: A start job for unit FRStackWebApi.service has failed

-- Defined-By: systemd

-- Support:?

--?

-- A start job for unit FRStackWebApi.service has finished with a failure.

--?

-- The job identifier is 1777 and the job result is failed.

Not much in the sense of diagnostics here. This is on a Pi3B now with Buster. Rebooted several times since upgrade.

I'm willing to start from scratch on anything else if that it easier.

Heck - I'll take an IMG if we just want to test the hardware.

Thanks,

Tom NY4I

?




 

Tom

Yes, you go to any browser?and access Node-Red.? IP:1880 for the flows and IP:1880/ui for the dashboard.

You do not need a desktop....However, ? Mark puts his Flows on the Raspberry Pi, "/usr/local/frstack" directory and I found running a browser on the Raspberry Pi desktop an easy way to import the flows.? Then thereafter I used my desktop browser.

I can send you the MKCM flows directly for import into your desktop Node-Red browser, if you like.? Just?let me know.? Then you do not need a Raspberry Pi desktop for accessing the flows.

You do need to access, with a terminal program, to make changes to the "/usr/local/frstack/appsettings.json" configuration file.? Settings are shown in MKCM's?instructions:



Alan


On Wed, Aug 19, 2020 at 6:11 PM Tom Schaefer NY4I <thomasmschaefer@...> wrote:
Thanks. I will break out a fresh download of Buster.

I usually use Buster-Lite. Any reason to use a desktop config with Nodered/FRStack?

I may be wrong but I am assuming that after the flows are built, one goes to a web page to access them—not the Flow editor. I hope that is right and I do not access the flows from only the local interface of the RPi with a desktop.

Thanks,

Tom NY4I

PS Sorry for the noob questions.

On Aug 19, 2020, at 6:05 PM, Alan Blind, WA9WUD <a.alan.blind@...> wrote:

Tom

Mine went very smooth, using my notes. ? I did start with a "fresh" build on the Raspberry Pi using the Debian OS.

Alan

On Wed, Aug 19, 2020 at 5:54 PM Tom Schaefer NY4I <thomasmschaefer@...> wrote:
I went through your updated instructions.

Is this usually this hard? FRStackWebAPI ending with error code of "error code" is curious to say the least.


pi@nodered:~$ sudo systemctl start FRStackWebApi

Job for FRStackWebApi.service failed because the control process exited with error code.

See "systemctl status FRStackWebApi.service" and "journalctl -xe" for details.

pi@nodered:~$ journalctl -xe

Aug 19 17:41:13 nodered systemd[1]: Stopped FRStack Web APIs.

-- Subject: A stop job for unit FRStackWebApi.service has finished

-- Defined-By: systemd

-- Support:?

--?

-- A stop job for unit FRStackWebApi.service has finished.

--?

-- The job identifier is 1777 and the job result is done.

Aug 19 17:41:13 nodered systemd[1]:?FRStackWebApi.service: Start request repeated too quickly.

Aug 19 17:41:13 nodered systemd[1]:?FRStackWebApi.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support:?

--?

-- The unit FRStackWebApi.service has entered the 'failed' state with result 'exit-code'.

Aug 19 17:41:13 nodered systemd[1]:?Failed to start FRStack Web APIs.

-- Subject: A start job for unit FRStackWebApi.service has failed

-- Defined-By: systemd

-- Support:?

--?

-- A start job for unit FRStackWebApi.service has finished with a failure.

--?

-- The job identifier is 1777 and the job result is failed.

Not much in the sense of diagnostics here. This is on a Pi3B now with Buster. Rebooted several times since upgrade.

I'm willing to start from scratch on anything else if that it easier.

Heck - I'll take an IMG if we just want to test the hardware.

Thanks,

Tom NY4I

?




 

Thanks for the help on this issue. The problem was that I installed the 64 bit version of aspnetcore-runtime by mistake. My Pi (3B) did not like that version.

This was my mistake but I followed the bolded instructions versus reading closer and getting the 32 bit version (in the comment below it).

I might suggest something in that Wiki article like this to help the next person to avoid that mistake.
If you have a 32 bit Raspberry PI, sudo wget this file:?

If you have a 64 bit version, sudo wget this file:?sudo wget https://download.visualstudio.microsoft.com/download/pr/76829580-79b2-4ec5-97ff-1a733936af14/6ba68613c7491951b896396f7d7490d9/aspnetcore-runtime-3.1.6-linux-arm64.tar.gz // Note check??for latest version under Linux...

------ Original below -----

?sudo wget https://download.visualstudio.microsoft.com/download/pr/76829580-79b2-4ec5-97ff-1a733936af14/6ba68613c7491951b896396f7d7490d9/aspnetcore-runtime-3.1.6-linux-arm64.tar.gz

?

# The following website has this info. https://dotnet.microsoft.com/download/dotnet-core/3.1

?

# Here is the current one for ARM32 devices

# https://download.visualstudio.microsoft.com/download/pr/92e90ed5-dba3-427b-a876-8b46fe5e16b6/69cae4fe4a0ec6bc7585de6fa889fd66/aspnetcore-runtime-3.1.6-linux-arm.tar.gz

?

# From the Downloads folder, execute the following commands:

Thanks ,

Tom NY4I


 

开云体育

Thanks Tom. I will update the WiKi to make it clear which version to install and update the links to the latest version of ASPNet.?

73
Dave wo2x

Sent from my waxed string and tin cans.?

On Aug 20, 2020, at 3:08 AM, Tom Schaefer NY4I <thomasmschaefer@...> wrote:

?Thanks for the help on this issue. The problem was that I installed the 64 bit version of aspnetcore-runtime by mistake. My Pi (3B) did not like that version.

This was my mistake but I followed the bolded instructions versus reading closer and getting the 32 bit version (in the comment below it).

I might suggest something in that Wiki article like this to help the next person to avoid that mistake.
If you have a 32 bit Raspberry PI, sudo wget this file:?

If you have a 64 bit version, sudo wget this file:?sudo wget https://download.visualstudio.microsoft.com/download/pr/76829580-79b2-4ec5-97ff-1a733936af14/6ba68613c7491951b896396f7d7490d9/aspnetcore-runtime-3.1.6-linux-arm64.tar.gz // Note check??for latest version under Linux...

------ Original below -----

?sudo wget https://download.visualstudio.microsoft.com/download/pr/76829580-79b2-4ec5-97ff-1a733936af14/6ba68613c7491951b896396f7d7490d9/aspnetcore-runtime-3.1.6-linux-arm64.tar.gz

?

# The following website has this info. https://dotnet.microsoft.com/download/dotnet-core/3.1

?

# Here is the current one for ARM32 devices

# https://download.visualstudio.microsoft.com/download/pr/92e90ed5-dba3-427b-a876-8b46fe5e16b6/69cae4fe4a0ec6bc7585de6fa889fd66/aspnetcore-runtime-3.1.6-linux-arm.tar.gz

?

# From the Downloads folder, execute the following commands:

Thanks ,

Tom NY4I