Failed to Update Database and Host

[maxcarpone]

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

[Tom Elliott]

@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.

[maxcarpone]

@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!

[maxcarpone]

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?

[Tom Elliott]

@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 instance am I connecting to” definitely causing headaches.

[Fog_Newb]

@maxcarpone I had the same problem with 2390 and reverted to an older back up. That version was broke AF

[maxcarpone]

@Fog_Newb : Good to know I’m not the only one having this problem. I’ll wait for a patch.

[Fog_Newb]

@maxcarpone 1.5.10.2402 is out. It works. I was able to capture from both my PC and laptop successfully. But it has a weird issue with null tasks.

https://forums.fogproject.org/topic/18230/1-5-10-2402-additional-null-tasks-created-but-this-time-manages-to-start-a-transfer

[maxcarpone]

@Fog_Newb : Well it doesn’t work for me. I still have problems with this version.

[maxcarpone]

I tried new things : I created a new user to see if I have the same problems as user “Fog”.

Well, when I perform a registration with immediate deployment : it works!

But it failed to update the database at the end of the deployment.

It looks like it has something to do with active tasking.

So, it’s still broken somewhere…

[Tom Elliott]

@maxcarpone

I’m suspecting you’re not entering the correct password?

This is your FOG Web login user/password.

[maxcarpone]

@Tom-Elliott : Unfortunately, it is the right password. I was wondering myself when the problem appeared but the prompt says something when it’s not the good one and you have 3 tries before giving up.

And by the way, it works using “deploy image” from PXE menu.

I’m available if you want me to do some special moves to find out where is the culprit ^^

[Tom Elliott]

I’ve found and fixed several ways these empty tasks get created — a group deploy of two or more hosts was failing outright, and deleting an image was leaving its queued tasks pointing at nothing — but before I ship a cleanup for the rows you already have, I need to know whether the bad tasks hold a 0 or the id of something that got deleted, because that changes what the cleanup has to match on. Could you run this against your FOG database and paste the output?

SELECT  t.taskID,
        t.taskStateID,
        t.taskTypeID,   IF(tt.ttID   IS NULL, 'MISSING', tt.ttName)   AS type_row,
        t.taskHostID,   IF(h.hostID  IS NULL, 'MISSING', h.hostName)  AS host_row,
        t.taskImageID,  IF(i.imageID IS NULL, 'MISSING', i.imageName) AS image_row,
        t.taskName,
        t.taskCreateBy,
        t.taskCreateTime
FROM       tasks      t
LEFT JOIN  hosts      h  ON h.hostID   = t.taskHostID
LEFT JOIN  images     i  ON i.imageID  = t.taskImageID
LEFT JOIN  taskTypes  tt ON tt.ttID    = t.taskTypeID
WHERE      t.taskStateID IN (0,1,2,3)
ORDER BY   t.taskID;

SELECT  t.taskStateID,
        COUNT(*)                AS rows_total,
        SUM(h.hostID  IS NULL)  AS host_missing,
        SUM(i.imageID IS NULL)  AS image_missing,
        SUM(tt.ttID   IS NULL)  AS type_missing,
        SUM(t.taskHostID  = 0)  AS host_zero,
        SUM(t.taskImageID = 0)  AS image_zero,
        SUM(t.taskTypeID  = 0)  AS type_zero,
        MIN(t.taskCreateTime)   AS oldest,
        MAX(t.taskCreateTime)   AS newest
FROM       tasks      t
LEFT JOIN  hosts      h  ON h.hostID   = t.taskHostID
LEFT JOIN  images     i  ON i.imageID  = t.taskImageID
LEFT JOIN  taskTypes  tt ON tt.ttID    = t.taskTypeID
GROUP BY   t.taskStateID;

SELECT * FROM schemaVersion;

[maxcarpone]

@Tom-Elliott : I can do that if you tell me how to do it!

Update : I figured it out.

[Tom Elliott]

@maxcarpone I don’t know if this is directed specifically at you @maxcarpone but if you want the gist:

sudo mariadb -u root fog

Then enter the select statements provided earlier.

[maxcarpone]

@Tom-Elliott : I found a way to do it :

mysql --user=fogstorage --password=MYPASSWORDHERE -D fog

Here are the results :