forum.pistar.uk

When running an update, one of my Pi-Star boards reverts back to M1ABC as the call. I note there is an error when updating and it looks like something may be set to read only preventing changes. This is what is displayed when running the update:
-----
Starting update, please wait...
Stopping Services...
Done
Updating DV Binaries...
No updates for /usr/local/bin available
Done
Updating Pi-Star Binaries...
No updates for /usr/local/sbin available
Done
Updating Hostfiles...
Done
Updating Dashboard...
Updating /var/www/dashboard...
From https://github.com/AndyTaylorTweet/Pi-Star_DV_Dash
* branch master -> FETCH_HEAD
Already up to date.
Updates were not successfull, reverting to Pi-Star original files...
HEAD is now at a3b9b5c9 Update configure.php
Done
Updating PiStar-Firewall...
Done
Starting Services...
Done
Updates complete, syncing disk cache before making the disk Read-Only
Finished
-----
The "reverting to original files" would seem to be where M1ABC returns. Any idea as to an easy fix, otherwise I can rebuild and restore.

Thanks
Dave

Known problem. No need to restore.

Simply go back into Configure and reset your callsign, language preference, and time zone and hit "apply".

With most cases where this happens theres no need to even go that far. Just hit apply changes on any of the config panels and it will revert back to showing ur previously entered callsign/ data etc.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

The fetch-head problem might need a little more doing to fix...

From the CLI type

cd /usr/local/bin
sudo git stash
sudo git pull

Sent via smoke signals from my SM-G935F M1DNS (Admin)

M1DNS wrote: ↑Wed Apr 05, 2023 10:23 pm The fetch-head problem might need a little more doing to fix...

From the CLI type

cd /usr/local/bin
sudo git stash
sudo git pull

Sent via smoke signals from my SM-G935F M1DNS (Admin)

Tried that, unfortunately without success.
It still returns the following afterwards when I run "update":
Updating Dashboard...
Updating /var/www/dashboard...
From https://github.com/AndyTaylorTweet/Pi-Star_DV_Dash
* branch master -> FETCH_HEAD
Already up to date.
Updates were not successfull, reverting to Pi-Star original files...
HEAD is now at a3b9b5c9 Update configure.php
Done
Updating PiStar-Firewall...
Done
Starting Services...
Done
I will do a re-build and that should fix whatever the problem is, thanks for trying to fix it.

73 Dave

Update... A little midnight oil later, did a backup. Formatted the card and re-installed a fresh image, restored from backup.

Problem solved and the backup even restored my colour scheme. Quite painless and quick.

73 Dave

Same here, have this issue for sometime now.

The CLI above did not resolve the issue, still get the error. The easiest way for me is to just click apply changes in the Configuration tab and deal with it.

I have 8 pi-star hotspots to redo with fresh image, however I can 2nd that, if I do the fresh image and restored the backup it will fix the fetch-head issue.

73, Kit