Failed to Update Database and Host
-
Hi there!
Recently, we updated one of our server from dev-branch 1734 to 2390. It updated smoothly without any error. We updated the database (schema) as well.
Afterwards, I wanted to delete an image from the webpage but I couldn’t do it with the files : it said “Wrong credentials” if I remember well.
I had to delete only the record then going to the server (ssh) and delete the folder.
It’s annoying but I can live with this.We encountered another problem which made me coming here. We imaged existing hosts. Imaging process went well but failed right at the end with these messages : “Failed to update database - Failed to update host”.
The host is well imaged but it is not updated in Fog, informations about last image aren’t written in the database.Also, when we want to deploy an image right after a full perform, it fails saying again “Wrong credentials”…
So there is a problem but I don’t know what it is. Any help?
Thanks.
Cheers!
PS : same problems with 2393
-
@maxcarpone From the sounds of things, the problem you’re running into is the FOG FTP username/password have potentially drifted?
https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password
Is still valid I think though how this happened I don’t know, but without much more information this is likely still the best starting point.
-
@Tom-Elliott : I tried what you suggested but it doesn’t work. When I try to register a new host, it works but it says “Invalid Login” when I try to deploy an image at the same time.
To succeed deploying an image, I must boot to pxe once more and deploy an image from the menu using the same credentials.Obviously, it’s not related to tftp password.
It’s really weird!
-
I may have found something related to my problem. When I rebooted the Fog Server, it tried to stop 2 instances of MariaDB. Could it be possible that a part of Fog is trying to join the wrong database?
-
@maxcarpone I don’t know for sure if 2 instances running would cause a problem specifically that you’re seeing, but I could see there being a mass confusion in “what
instanceam I connecting to” definitely causing headaches.