@migsterzs Can you please post your fog-client log here so we see the actually calls and might be able to help.

Thank you!

I clicked the update button but didnt wait long enough it seems.

Sorry for bothering you with this trivial stuff, thanks for the help.

Sébastien

Soooo … 🙂

After Resetting the Encryption it works.

So in this case uninstalling the FOG Client, then Reinstalling it, manually started the FOG Service in Window and reset the Encryption Data solved the problems for this client.

I have a second machine that seems to have the same problem at first glance, but have to check that to make sure it really is the same.

And the Thread you found from me at the beginning of my FOG journey … i still add the certificate manually during sysprep via the setupcomplete. On this client I havent imaged in quite some time and its only me using it. Really strange. 😕

I’ll check the other client and report back.

Thanks !

@Taspharel Only when initially created yes. I don’t think it resets the permissions after.

Aaaaand… stupid me.

Duplicate Mac Adress due to an external USB Networking Adapter.

Sorry for bothering you.

Can you upload the pcap of your pxe boot where PXE error T01 is thrown? I’d be interested in seeing why for my knowledge, especially if this is the only model giving this error?

Thank you so much, with the new / old inits the capture process ran successfully. Am trying to deploy now and see if everythin works out.

Thanks for your help
Sébastien

This is fixed in the working branch (pre 1.5.3). This issue is known and will be addressed in 1.5.3 when its released (very soon).

Solved by Tom Elliot as per this thread: https://forums.fogproject.org/topic/11717/fog-1-5-2-host-module-settings-don-t-save/7

@Taspharel Client version 0.11.16 (included in the FOG 1.5.1 release) features the new Snapin messages (currently only for English, other translations will follow in future releases).

Thanks for suggesting this change!

@Taspharel Sorry we haven’t got back to you on this. Must have gone under the screen. Did you actually want to delete the initial question? I think it’s a valid request depending on the resources one has. Shall I restore it?

It does. Thanks!

While George’s solution might have worked for the “bug” the cleaner solution is probably doing it right with the partition order…is it “frech” to mark my own post as solution?

@taspharel said in CPU Usage high:

In the long term the question remains: Why did that happen at all and is it related to our error regarding the web-gui “freeze” when looking at scheduled tasks?

Well it might be related as in the “freeze” might have been caused by the same “zombie” jobs. But I don’t really know.

Looking at the three tasks in the database again I see that all of them had stImageID zero. Don’t think that is valid. Not sure if that was causing it.

@Taspharel This hopefully helps:

chmod 777 /var/www/fog/service/ipxe chmod 666 /var/www/fog/service/ipxe/bzImage*

Then try kernel update again.

Thanks for staying on top of this, they never asked back, I guess they just accepted that thats something we needed. 🙂

Already enabled and works like a charm. 🙂

Can be closed, thx for helping out.

@taspharel it was good that you started that discussion and it sounds like that we maybe can expect that feature in the future. Thank you.

Ah well … turns out i’m just simply blind 😛

I changed the path in the commands to my local folder structure but missed one spot … since it booted pretty far I thought everything must be written correctly, turns out: No.

Thanks for the help.

I know this is quite an old topic, but we ran across this on the latest version of fog and I wanted to share my solution.

What ended up working for me was to get into the database console with mysql -u root

I then selected the fog database use fog;

Then I listed out the tasks SELECT * FROM scheduledTasks;

In my case the most recent record had an stID of 13, so I dropped that row, which fixed the issue DELETE FROM scheduledTasks where stID = 13;. After that the scheduled tasks menu loads fine.

@Sebastian-Roth Thank you very much. It worked. Now everything is ok.