Critical Armada Error

[tweiss3]

I went to open Armada this morning and work on a template I'm building, and I get this error:

I see two new files in the Armada database folder, one is a .db-wal and the other is .db.ArmadaLock. Removing those two files does nothing, they get recreated when I try to open Armada again and get the same error.

 

[Project25_MASTR]

What version of Armada are you running?

 

[tweiss3]

1.42.12.216

 

[tweiss3]

I figured it out. The armada.db file was corrupt. There were 3 others armada-xxxxxxx.db files, grabbed the one with today's date and renamed it to armada.db, worked no problem, everything still in there.

I left it open over night by mistake, so now I have checked "Automaticall close Armada on suspend or when inactive for 60 minutes" in an effort to prevent corrupting the database again.

 

[wd8chl]

Umm...you're supposed to shut down your PC when you're done for the day. Leaving windows open all the time can and eventually will cause problems. It needs to be rebooted on a regular basis.
Why would someone leave their computer on over night? That makes no sense.

 

[Project25_MASTR]

Umm...you're supposed to shut down your PC when you're done for the day. Leaving windows open all the time can and eventually will cause problems. It needs to be rebooted on a regular basis.
Why would someone leave their computer on over night? That makes no sense.

I leave mine running until Windows updates reboots them. Especially when you are dealing with hardware keys…not having to dig them out of your bag everytime you edit codeplugs when you can just load them when you start the application and then leave it open especially when the computer sits in a secured office (there are days I don't even get my backpack out of my pickup which is where the hardware keys are stored so I have them available for field programming).

My Armada Server (and RM Server) don't get rebooted but once every four or five months (if I could move the databases to a linux based solution easily I would and then never reboot). No issues with their databases.

 

[wd8chl]

That's a bad idea. Shutting down your PC every day is always the best plan. Besides wasting energy, more importantly, windows does not like being open that long, plus there are routine maintenance that takes place on restarts, even without updates. Caches get flushed, hard drive/SSD maintenance takes place, temp files get dumped, RAM gets reset, etc, etc, etc. Windows is notorious for memory leaks and things like that too, so RAM or the swap file need to be cleaned up often too.
As to the keys, you don't have to unplug them when you shut it off if you don't want to, and when you're in a secure environment as you say. It will find them just fine when you re-boot.
Server is a different form of windows, and can run longer. But normal windows doesn't like it, and gets messy quickly.

 

[tweiss3]

This computer stays on all the time, I end up remoting into it multiple times a day.

I had meant to get back to the computer and work on the template more, but after a Zoom meeting and grabbing dinner, I lost track of time......

I guess mistake learned. I never saw the auto close option before, it should help when I get scatterbrained.

 

[Project25_MASTR]

That's a bad idea. Shutting down your PC every day is always the best plan. Besides wasting energy, more importantly, windows does not like being open that long, plus there are routine maintenance that takes place on restarts, even without updates. Caches get flushed, hard drive/SSD maintenance takes place, temp files get dumped, RAM gets reset, etc, etc, etc. Windows is notorious for memory leaks and things like that too, so RAM or the swap file need to be cleaned up often too.
As to the keys, you don't have to unplug them when you shut it off if you don't want to, and when you're in a secure environment as you say. It will find them just fine when you re-boot.
Server is a different form of windows, and can run longer. But normal windows doesn't like it, and gets messy quickly.

I guess you missed the part where the keys get unplugged and left in the truck so they are always available for field programming (just like one of the programming laptops).

Windows may like to be shutdown regularly but unless you are patching the kernel or running on less than 16 GB of memory clearing the catche's isn't really necessary. Chrome(Edge/Brave/etc) is by far the biggest memory hog and closing that out free's up most of your memory. I could go on a whole rant about Motorola requiring reboots for updates on machines in use on consoles that are intended for 24x7 operation…I've been embarassing them on meetings when they say they are limited by Microsoft as most modern Linux kernels allow for live patching of the kernel and therefore Microsoft is not an appropriate solution for the application.

 

[AM909]

I've seen problems in KPG-D* on a newer HP/Win11 laptop (that should not have been bought) resuming in a dog-slow mode after sleep/hibernate. Other than that, our desktops stay on and laptops are turned off or hibernated. YMMV.