Unable to read source configuration files

[wp4ofo]

Decided to update my hotspots and all got bricked. VER 4.1.2 Dashboard update 20200706. Something makes the build unable to ready configuration files.
After updates run, reboot the hotspot and then you are unable to define modem, make changes to whatever displayed config due to receiving error when saving. Unable to read source configuration file(s)...

Performed base install 4.1.2 and all works. All goes down the hill when doing latest update.

Anyone seen this behavior?

Cheers,

Joe
WP4OFO/1

[wp4ofo]

Thank you for your help Jason.

Installed base 4.1.2. ssh in and perform - sudo apt-get update - sudo apt-get upgrade - sudo apt-get install. (dont remember exact order - fyi) After those updates, sudo pistar-update <-- this step downloads some new files - changes build date to 20200706. Its the only thing i can identify.

Rebooted, maybe 30 times in a row and still read-only.

When going to Expert and clicking MMDVMHost, nothing happens - page stays blank. All other options in Expert open their respective options page.

Where do I find this file to try and correct permissions?

Will get back to you with specifics on micro sd. Have several and same result, 16gb and 32gb.

Regards,

Joe
WP4OFO/1

[G8SEZ]

What flavour of hardware are you using?

Also, have you tried sudo apt-get dist-upgrade instead of just upgrade?

Might be worth a shot.

[wp4ofo]

Thank you for the testing. Dont know what to tell you.

I can say that for some unknown reason it definitely changes to read only. Bought a new microsd today and same thing. Kingston CANVAS v10 32gb

Latest steps.
1. Install 4.1.2 and configured everything.
2. Performed BER tuning. No problem as usuall.
3. Did testing, Parrot was perfect. Both slots recoginzed. Brandmeister api configured. Again everything is working.
4. SSH in and execute sudo pistar-update. It runs complete. No issue. Reboot is expected. On next reboot I get the unable to read source... whenever changing any configuration.

Since the read only config is a working config I have to say the hotspot works, nextion displays correct information. I am simply unable to change any settings afterwards.

Observed Symptoms. When executing pistar-update you get warning - sudo: unable to resolver host pi-star: name or service not know. This is not the name of this appliance. I always rename the hostname from pi-star to something else. The second odd symptom is that in expert, mmdvmhost page does not load at all. No error. Simply not shown. Every other page loads well.

As for hardware: Pi3b+ with mmdvm_hs_dual_hat - fw 1.4.17. Nextion 2.4 display. The other hotspots also Pi3b+ with zumspot hats also fw 1.4.17. One has nextion 2.4 and the other oled. Built myself those hotspots quite some time ago. Till three nights ago perfect.

Jason - Which log file I can check further while Im loading the expert configuration pages, specifically mmdvmhost to see if I can get any further with thist issue.

Next test - Revert to build 3.4.17 and perform the same steps and see what happens. This behavior had never occurred before, at the end of the road if this keeps happening will replace hardware. Electronics can fail.. although suspicious all at the same time.

Appreciate your help with testing to see if this can be corrected.

Stay safe.

Jose
WP4OFO/1

[G8SEZ]

What are the kernel versions you have, before and after the problem.

I wonder if this is somehow related to the masked services in the 5.4 kernels that are now in Buster?

[wp4ofo]

Hello Brian.

Will provide details later on tonight. Will do a downgrade to 3.1.17 and see what happens and move from there. Will provide kernel levels. Also, will try sudo apt-get dist-upgrade and see what happens.

Thank you.

Jose
WP4OFO/1

[ke4iyp]

There was a bug that would cause this very problem that I fixed and Andy pushed into pistar Jun 23rd. It has to do with how the password for the Brandmeister API is handled or rather not handled well. You should be able to install a fresh 4.1.2 and then just do sudo pistar-update. I don't think the apt update stuff is necessary as pistar-update seems to trigger this anyways. Then the updated code should be present and work... Seems like one time you configured everything (probably breaking it as a result of the bug) then updated. Do it the other way around. Install fresh, update, then configure it.

Another thing you can try is to set your Brandmeister API password to simple alphanumerics, no symbols in there. Then even the buggy version should be able to handle it ok. The buggy version would stumble on the symbols and then not be able to read the configuration file.

Also I should note that there's an outstanding bug that is similar but it's when you use symbols in the SSH/Linux password. It creates a similar self-destruction. I made a fix for it but it hasn't been added yet. https://github.com/AndyTaylorTweet/Pi-S ... h/pull/112

[wp4ofo]

Thanks again for the support. Is it a bug? Could be. Although I cannot replicate in all my hotspots, which baffles me. Friday night did everything just as you said, Michael(ke4iyp).


1. Installed base 4.1.2
2. SSHd into
3. Performed update with only pistar-update
4. Configured everything. (still default password and hostname)
5. Have to report that it is working read-write and no weird behavior has been detected.

Dont know if my install happened after fixes were posted to any repository or not, but this order seems to apply everything as it should. So far solid, no glitches or slowness.



Based on this https://www.androidcentral.com/best-sd- ... rry-pi-3-b. Ended up ordering SanDisk Extreme Pro micro sd cards for all hotspots. As soon as they arrive will reinstall.

[ke4iyp]

Glad I could help... Hopefully my other patch will get added in shortly. I think the bugs have existed for something like 2 years, but it's dependent on whether or not you use certain characters in your password. Many people would never trigger it, but when you do trigger it, it's pretty catastrophic.