@Sebastian-Roth And I’m not seeing the same issue. I go to the page on my server and it works just fine. So I’m really not sure whats going on.
@jmeyer HOw many hosts do you have?
On one of the “clean” systems you have, can you add only one host and it’s image information? Then go to that URL in the browser? Does that return anything?
This seems to be like it’s processing too many hosts at once.
As this is handled from the inits, there is no log available for you to “get”.
If you can run the task in Debug, when this errors out can you get us a photo of the exact error in context? (I know the check in’s happen every 10 seconds until it fully fails out, at which point it should give more information.
If it doesn’t I’m not quite sure how to troubleshoot at this point. I’m not seeing the issue on my side.
Can you also, in the browser try going to:
http://<yourfogserver/fog/service/Pre_Stage1.php?mac=<macofhost>&type=down
It should fail. The problem has nothing to do with the line you’re seeing reporting in the log (that’s just where the issue occurs, but it’s before that point that it’s caused.)
Force task to start is more intended for deploy tasks.
I’m not quite sure why it would clear the storage node when you click force to start though.
Your iPXE files appear to have been custom made. I’m not seeing this being discussed in your original post so if you can give us details about either how you built your iPXE files or where you got them from it’d be helpful.
I say this because of the: params: command not found
The iPXE files we build for our stuff includes this already configured.
Reading a little further:
And yes, I did check my config.h file and I did add the #define PARAM_CMD.
Did you rebuild the iPXE files after adding the #define PARAM_CMD? Simply uncommenting this does nothing to the iPXE binaries.
@rogalskij what’s the lowest version kernel you’ve tried?
@rogalskij while I understand the slowdown is problematic some of it seems bound to network speeds. For your tests are you only imaging a single machine, or multiples at the same time? Are they on a separated network or a congested one? No matter how fast an ssd disk you have, these things need to be thought of as well. What are the speeds of the performing network?
Please don’t take this as the only word. I just want to best understand the whole.
@Sebastian-Roth I fixed the versioning issue. No update needed to see this.
There was a slight issue on the remote side code that checks the version information for us.
@Kiweegie We’re aware of that, and 1.5.x GUI was a step toward the right direction. If you want a much nicer GUI, you are more than welcome to test working-1.6.
@Kiweegie In the past the mobile group was setup for users who you didn’t want access to the main gui, but allowed access to the mobile gui.
This has kind of fallen down the wayside as we moved to making a responsive gui vs. two seperate gui’s.
Now there is really not much difference between them, though it’s kept more as a safety as you can code things around based on it if you so needed.
Now, though, if you need to limit controls, I’d suggest using the AccessControl plugin. This isn’t a catch-all by any means, but is probably light years better at managing user’s and controlling what they can and cannot do in the GUI than anything FOG had prior to 1.5.x.
@Kiweegie I should add that the Admin group and Mobile Groups should not need to be full DNs.
So, for example, you have “Admin Group” set as a DN in your example, but you can just do: fogserver_admins
Similarly, you can also add multiple groups to allow by using a comma such as:
domain admins,domain manager computer objects,desktop administrators
You can do the same for Mobile Group. You do not need both to be filled out.
@Kiweegie from the GUI you should be able to get the fogstorage password from FOG Configuration Page->FOG Settings->Storage Password. I forget the exact string to look for but should be pretty close
@Sebastian-Roth That, I think, is okay. 30 seconds could be too short a time (as the partition get’s re-expanded) potentially. It’s one minute vs 10 seconds or 30 seconds. I’m just taking a cautious approach. Only one minute to wait between a partition isn’t too much to ask I don’t think. I can certainly shorten the time. Or we could add a global setting for the admin to select an appropriate time.
@Sebastian-Roth I made the change in working-1.6. I took a more cautious approach to set to one minute instead of 30 seconds.
For 1.5.X LDAP ports were being applied within the database, but not used in all areas. I have since fixed this so it will use the ports list defined by the user instead of predetermined ports.
@Sebastian-Roth no I’ve never seen this before. While it doesn’t display, does it at least complete? I ask because of the nature of multicast.
If you have 10 machines to image and all 10 connect, imaging will proceed immediately. If one of those hosts were shut off after, then imaging would only proceed after a specified timeout, I think we default to 10 minutes.
Try running git clean -xfd; git pull then rerun installer. The installer should rebuild the ipxe files again.
@agray Re-enable what?
Just leave it on AHCI mode. You have to make the change to all machines anyway, so why would you do:
This adds another step that essentially is unneeded.
You will likely need to change the SATA Operation mode from Raid on to AHCI.
To do the switch safely follow the last post on this page: https://www.dell.com/community/Inspiron/Switched-SATA-settings-from-RAID-to-AHCI-broke-computer/m-p/6228180/highlight/true#M42298
Essential Steps:
Boot machine, open msconfig.exe and turn on safe boot.
Shutdown machine.
Power on and go into BIOS
Switch SATA operation mode from Raid On to AHCI
Reboot machine and let boot into windows.
Open msconfig and turn off safe mode.
Shutdown machine (or reboot)
Capture image.
On other machines, all you will need to do is change SATA operation mode.