I needed to restore a node this evening and had to use the online settings restore (which worked); later I needed to start over and it says I have no backups…WTF…?
Also, other bizarre behavior; trying to do an apt update/upgrade give all sorts of error messages about lockfiles; cockpit reports services not starting, etc. Was there a cosmic ray event I didn’t hear about…or is it…uh-oh…me?
You dont give enough information for people to give any guidance. What is your setup?
In this case it’s a HSR Duplex unit but all these problems are independent of the hardware. It wasn’t even plugged in at the time. Anyway I re-imaged after a break and finally got it going.
Just the same, I’d love to know where my backups went.
A couple of Q’s.
- were/are you using ASL3?
- did you use the
asl-menuto create the backup? - when prompted, did you ask that the backup be saved to
backup.allstarlink.org?
If you answered “yes” to all of these questions then the backup archive should (still) be stored on the ASL backup server and should be available to recover your configuration. And, should you need to recover a saved configuration I would recommend using asl-menu.
Also, please note that we only backup/recover the asterisk/allstarlink configuration files. You’re on your own for any other packages / configurations you have added.
Yes to all 3.
Node 27277
Remember, I restored from said backup an hour earlier (there were 2 of them at the time) but they disappeared.
I’m hip to what the bu saves; I can remember most of it but usually not the audio settings.
That’s what I did last night; just reconfigured it and roughed in the audio for the time being.
Back to one of the other glitches, can anyone tell me why I get this when I try to do updates?
Further, the cockpit update pgm (the 1st time I ran it) said “Updates Failed”
Now it says everything’s up to date. I never got any updates accomplished.
EDIT: Just noticed this:
EDIT#2: Tried to do a new backup tonight; gave me the error:
There was an error in the file transfer (error code 4)
Now I’m thinking some kind of permissions thing…
Does dmesg report any disk corruption?
FYI : the backup server still has two archives stored for your node (2025-01-10-231646 and 2025-02-10-034029).
As long as your system, with the exception of the ASL configuration, is behaving then you should be able to restore these saved configurations.
Nothing jumps out with dmesg (though I’m no expert, duh); I spent several hours last night sleuthing around and the best I can determine is I’m having some sort of DNS problem, Though it seems to be the only device on my network that’s having the problem (and likely why it doesn’t see the backups or complete updates). I’ve gone over my port forwards and my static leases with meticulous detail. I DID change the DHCP-allocated IP to a static one (using the networking facility in cockpit); did I miss something?
With DHCP you typically get both your IP address and your DNS configuration.
If you switched away from DHCP to a static IP then you would also need to specify the DNS configuration.
Personally, I configure my router to set a fixed IP address for my nodes based on their MAC address. That way the nodes keep using DHCP but they always get the same address from the router.
If there’s something I neglected to do (in ASL3) after changing to that static IP, I’m all ears. The new IP is mapped to the MAC in the router already. Otherwise I can try reinstalling and trust it’ll pickup the right address this time (yes, the router mapping was entered AFTER the last ASL3 reinstall but BEFORE changing the IP in ASL3).
If you do host register-west.allstarlink.org from the Linux shell, what happens?
I also set the register => line in iax.conf but of course that would be useless without DNS I suppose…
Yeah your DNS is messed up. Is this an ASL3 appliance with NetworkManager or a stock Debian system?
You know, I’ve never been a 100% clear on what you guys are referring to when you use the word appliance (I think toaster ovens when I hear the word!); It’s the raspberry pi image. And yes, I used network manager to change the IP.
So go into cockpit on port 9090 and edit the wired or wireless configuration that you changed and in the IPV 4 setting add a DNS server which is likely your Routers IP address. You could also use 9 .9 .9 .9
You rock; that was it. In retrospect, of course when I delete an interface, everything associated with it goes out the window too; When I added the new IP, I didn’t bother to even look down… Thanks again.
ps. Although everything’s working, my software update says everything’s up-to-date, even though I never accomplished any updates…weird…
Thie Pi Appliance image does a firstboot update.
I think I’m starting to understand the ‘appliance’ part…
Bob
KK6RQ
Occasional Appliance Ham 
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.