.pem file lost and various other problems
Published: May 5, 2015 - 10:03
Good morning,
I installed WAPT on my 700 machines and everything worked until my .pem file was lost (hard drive crash and I forgot to make a backup)
).
So, my first idea was to reinstall a workstation with the console, generate a new key pair and therefore a new agent that I would deploy to replace the old one.
But, as a result, in my console, I still see all the old clients that I absolutely cannot control or delete.
When I formatted a workstation and tried to manually reinstall the client via waptdeploy, this is what I got:

And when manually installing the agent, it does not appear in the console (still the old client of the same name with the latest April update).
A wapt-get register command returns:
And so on the console I always get the message: HTTP/1.1 404 NOT FOUND when I try to make an intervention on a client.
I admit that I'm completely lost now and I have no idea how to get out of this... Is it salvageable?
Thanks in advance.
My versions:
WAPT Server version: 1.2.3
WAPT Agent version: 1.1.1
WAPT Setup version: 1.1.1
WAPT Deploy version: 1.2.3.0
I installed WAPT on my 700 machines and everything worked until my .pem file was lost (hard drive crash and I forgot to make a backup)
So, my first idea was to reinstall a workstation with the console, generate a new key pair and therefore a new agent that I would deploy to replace the old one.
But, as a result, in my console, I still see all the old clients that I absolutely cannot control or delete.
When I formatted a workstation and tried to manually reinstall the client via waptdeploy, this is what I got:

And when manually installing the agent, it does not appear in the console (still the old client of the same name with the latest April update).
A wapt-get register command returns:
Code: Select all
2015-05-05 10:14:50,631 CRITICAL Unable to delete param uuid
FATAL ERROR : OperationalError: attempt to write a readonly databaseI admit that I'm completely lost now and I have no idea how to get out of this... Is it salvageable?
Thanks in advance.
My versions:
WAPT Server version: 1.2.3
WAPT Agent version: 1.1.1
WAPT Setup version: 1.1.1
WAPT Deploy version: 1.2.3.0