20190104 Configuration Control Panel Bug

Here is where you can get help with using and setting up POCSAG and related topics
Post Reply
KE6INZ
Posts: 3
Joined: Sun Jan 06, 2019 5:05 am

20190104 Configuration Control Panel Bug

Post by KE6INZ » Mon Jan 07, 2019 8:47 pm

Hello:
I have been trying to find where to submit a bug report, but I
haven't had any success. I have upgraded my recently obtained
Zumspot, running:

Pi-Star: 3.4.16
Dashboard: 20190104
FW: ZUMspot v1.3.3

There is a typo in the file "/var/www/dashboard/mmdvmhost//function.php",
that is causing the display of the "POCSAG Setting" under the
"MMDVMHost Configuration" to not appear.

Here's the diff:

Code: Select all

308c308
<                 if (file_exists("/var/log/pi-star/DAPNETGateway-".gmdate("Y-m-d", time() - 86340).".log")) {
---
>                 if (file_exists("/var/log/pi-starDAPNETGateway-".gmdate("Y-m-d", time() - 86340).".log")) {
This corrects this minor bug.

User avatar
VK7HSE
Posts: 78
Joined: Sun Apr 15, 2018 6:35 pm
Contact:

Re: 20190104 Configuration Control Panel Bug

Post by VK7HSE » Mon Jan 07, 2019 9:42 pm

Firstly please update your zumspot firmware, that is the initial release version and it does not support POCSAG!

The current firmware version is v1.4.14

Sent from my Pixel 2 XL using Tapatalk


Image

KE6INZ
Posts: 3
Joined: Sun Jan 06, 2019 5:05 am

Re: 20190104 Configuration Control Panel Bug

Post by KE6INZ » Thu Jan 10, 2019 3:23 am

Sure, however, there is an error with the S3 bucket for the 1.4.14 firmware:

Code: Select all

[email protected](ro):~# pistar-zumspotflash rpi
ZUMspot-v1.3.3 20180224 ADF7021 FW by CA6JAU GitID #62323e7
Press any key to write the rpi firmware to this modem or Ctrl-C to quit...
Flashing your rpi modem to the latest version
--2019-01-09 19:13:27--  http://github.com/juribeparada/MMDVM_HS/releases/download/v1.4.14/install_fw_rpi.sh
Resolving github.com (github.com)... 192.30.255.112, 192.30.255.113
Connecting to github.com (github.com)|192.30.255.112|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/juribeparada/MMDVM_HS/releases/download/v1.4.14/install_fw_rpi.sh [following]
--2019-01-09 19:13:27--  https://github.com/juribeparada/MMDVM_HS/releases/download/v1.4.14/install_fw_rpi.sh
Connecting to github.com (github.com)|192.30.255.112|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/80589711/100ee800-014e-11e9-8f29-f006d630db4e?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190110%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190110T031327Z&X-Amz-Expires=300&X-Amz-Signature=c577f580ac38635318a6ee4f76bf27c2d6ba4bc9763d9f6c79fdb4e9bd775965&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dinstall_fw_rpi.sh&response-content-type=application%2Foctet-stream [following]
--2019-01-09 19:13:27--  https://github-production-release-asset-2e65be.s3.amazonaws.com/80589711/100ee800-014e-11e9-8f29-f006d630db4e?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190110%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190110T031327Z&X-Amz-Expires=300&X-Amz-Signature=c577f580ac38635318a6ee4f76bf27c2d6ba4bc9763d9f6c79fdb4e9bd775965&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dinstall_fw_rpi.sh&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... failed: Name or service not known.
wget: unable to resolve host address ‘github-production-release-asset-2e65be.s3.amazonaws.com’

Flashing your rpi modem complete, press any key to reboot your Pi-Star System...
The DNS entry for "‘github-production-release-asset-2e65be.s3.amazonaws.com"
does not currently exist (302 redirect access error).

Code: Select all

[email protected](ro):~# host github-production-release-asset-2e65be.s3.amazonaws.com
Host github-production-release-asset-2e65be.s3.amazonaws.com not found: 3(NXDOMAIN)
Thanks in advance for your assistance.

KE6INZ
Posts: 3
Joined: Sun Jan 06, 2019 5:05 am

Re: 20190104 Configuration Control Panel Bug

Post by KE6INZ » Fri Jan 18, 2019 6:16 pm

This thread can be closed. Access to the firmware AWS S3 bucket was resolved by correcting a proxy problem.

Rebuilding the SD card and doing a fresh install resolved strange interaction problems, due to errant leftover configuration settings between releases.

Post Reply