I’ve just found out that the management password of my storage node has been truncated by 1 character. After typing it again, everything is back to normal.
That version has definitely changed my password

Well I’m not sure my problem is related to the one described above, sorry for that.

Morning,

Have you tried to update kernels of your FOG Server guys? To do so, you click on “Fog Configuration” then “DefaultMember FOG Version” to display both running kernels (mines are 5.15.19 for example).

Then you click on Kernel Update in left panel. You pick those 5.xx.xx kernels Intel 64 Bits and Intel 32 Bits and download them to start the installation process.

You probably need a 5.xx kernel and don’t have it installed.

Let us know if it works

Hey guys!

It looks like it works so far. I tested with 2 fresh installations of W10 1803, one in MBR and the other one in UEFI and each capture has its own d1.fixed_size_partitions populated.

Content of these files :

• MBR => :1
  which is the partition labeled : Réservé au système

• UEFI => :2:3:1
  Which are Recover, System, MSR

I will do more experiments soon but I like what I saw ^^

Thanks for the good work

It’s all good !

As you can see, informations are now written in the database (last image).

Many thanks for your help. And long live Fog and all of you who are involved in the project !

Bingo!

(I tried the older password just to be sure before typing the good one)

This one was related to our password which started with ‘&’
I modified it and now, I can image I soon as I register a new host. I must say that password has always worked right from the beginning till the previous version 1734 (prior to update to 2390).

So now, everything should be sorted out after updating our server to the last commit?

(Still those instances of MariaDB but I’m no good to debug it without help)

-> I’ve made some progress

@Tom-Elliott : Good explanation and I understood the most of it. Many thanks.

I will try to help resolving these remaining bugs.

About the MariaDB Instances. I don’t understand why there are 2 instances but I’m not the only person using this server. Are they both related to Fog? I used your codelines :

I don’t know where to find the count in the web UI?

I remember I had problems with phpmysql for several years and I had to modify a file to be able to update our FOG servers. I noticed I hadn’t have to modify that file (functions.sh) anymore. Could it be related to those MariaDB instances?

Now, speaking about invalid login led me to think the password could be the culprit because it’s started with ‘&’. I’ve just modified it and will try again and finally let you know what happened.

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

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

Here are the results :

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

Update : I figured it out.

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

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…

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

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

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?