EFI Pace Won't Start After Vault Configuration Change
-
We have EFI Pace running on Debian Linux. It backs up to an external vault location on a Windows 2012 R2 server. EFI recommends a local user rather than a domain one, so we have a local user created for this purpose.
Pace was running fine, but when the vault settings were changed, it was unable to fire up. In the logs, if the vault is misconfigured (wrong user, for example) it throws an obvious error and Java crashes out (great programming there.)
When we have the vault configured correctly, the error is not thrown and the process does not crash. However, it simply says that it is "starting Pace" indefinitely and never actually starts and does not continue to log anything. It appears to just stall during the startup process.
Could it be attempting to populate the vault in some way and silently stalling because of that? Has it crashed? Is there some action we can take short of waiting for EFI's extremely slow support to look into it (they've been engaged but take days, not hours, to respond - they don't have any production level support offerings from what we can tell.)
-
Turns out that EFI Pace stores critical files on its backup location and actually creates a dependency and if the backup disappears the system can't boot. So not really a backup as much as a dependency! What a disaster of a system.
-
@scottalanmiller said in EFI Pace Won't Start After Vault Configuration Change:
Turns out that EFI Pace stores critical files on its backup location and actually creates a dependency and if the backup disappears the system can't boot. So not really a backup as much as a dependency! What a disaster of a system.
WTF - the system can't boot if the backup is gone - what were those jokers thinking?
-
@Dashrender said in EFI Pace Won't Start After Vault Configuration Change:
@scottalanmiller said in EFI Pace Won't Start After Vault Configuration Change:
Turns out that EFI Pace stores critical files on its backup location and actually creates a dependency and if the backup disappears the system can't boot. So not really a backup as much as a dependency! What a disaster of a system.
WTF - the system can't boot if the backup is gone - what were those jokers thinking?
They don't appear to allow patching, either.
-
We have EFI Fiery print "servers" here and I hate them with a passion.
Windows 7 desktops, that are "managed" (means never maintained or touched) and we aren't allowed to because of the aforementioned "maintenance".
-
Had to deal with Fiery too.
-
@scottalanmiller said in EFI Pace Won't Start After Vault Configuration Change:
Had to deal with Fiery too.
I think they misspelled that name slightly. Fire that company (I know, you wish they would.)
