Capturing image update database failed

[Baessens]

@Sebastian-Roth I can also create a directory and upload a random file into that new dir.

[Sebastian Roth]

@Baessens said in Capturing image update database failed:

The password in the /.fogsettings file is different then the one in the GUI under TFTP server.

Are the usernames different as well?? When only the password is different we should see a login error in the picture instead of a “Could not create” message I reckon.

Please go through this: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

[Baessens]

@Sebastian-Roth

It seems to only be the password that is different.
i’ll try that resyncing thing too.

[Baessens]

@Sebastian-Roth I am still getting the same error.
I might just install a whole new server. Can you think of anything else that might be causing the error?

Thanks for all your help allready.

[Sebastian Roth]

@Baessens Too bad. I usually try to dig into things till I find the root cause of it. Though I understand if this just seems unsolvable.

Re-reading most of the topic I saw that you seem to have a subdirectory /images/dev/dev. Though I don’t think this can cause the issue I am wondering where this came from. Please run ls -alR /images/dev/dev and post output here.

Meanwhile I am digging through the code to see what else we can try.

[Baessens]

@Sebastian-Roth
Could it have something to do with the SQL creds?

I think it must have happened after an update, either from FOG or Ubuntu.

[Sebastian Roth]

@Baessens said in Capturing image update database failed:

Could it have something to do with the SQL creds?

With SQL creds wrong you’d see completely other issues and wouldn’t even be able to schedule a task in the web UI.

I think it must have happened after an update, either from FOG or Ubuntu.

Don’t think I have ever seen this happen from an update. Possibly something you did when moving images to a differnt disk/partition.

[Sebastian Roth]

@Baessens Ohhhhhhhh no!!! Why haven’t I noticed this before??? Can’t believe it. The second picture of your initial post actually has the solution to this riddle in it already. Image is named UEFI01/09/20v2004 and as a forward slash is the directory separator on Linux systems it will fail to rename the uploaded image…

Simply use dashes (-) instead of the slash in both the image name and path and I am sure it will upload just fine.

We don’t get that very often and I actually thought we had some kind of regex check in the web UI to prevent from this but seems like I was wrong.

[Baessens]

@Sebastian-Roth Wow… Good spot! I always use a dash, but for some reason it uses / in the path.
It doesn’t show it in the images list tho, need to click on the image name to actually see it.
I think there is a regex check but only for the image name, not the path. (which is usually the same)

I’ll try it right away.

[Baessens]

Works fine now. Thanks @Sebastian-Roth !