@Tom-Elliott said in FOG Issued Reboot Not Happening:

Task reboot not working properly should now be fixed properly. There’s a slight issue in the new client where the call it get’s to “recheck” for tasking it it calls a different url. That url wasn’t returning any data. A Hotpatch has been made that should correct this for you.

Thanks Tom!

@Scott-B , v0.10.3 addresses this issue, please update.

You are welcome! 🙂 As well I learned to pay even more attention to what I see in the PCAP file. Would have saved us at least an hour or two… When testing with the command line client Scott didn’t know about the important -i option for Windows tftp command line client as described here. When looking at the PCAP file Scott sent me I didn’t notice that it tried to request the file in ‘netascii’ mode instead of ‘binary’.

So everything is working now and it was just the upper case filename option in the DHCP config…

I’ve imaged Ubuntu 15, CentOS 7, and Fedora 21-23 many times.

Ubuntu defaults to extfs while in Fedora 21-23 you can select Ext4 as the filesystem to use.

This is important because FOG only supports ext type file system resizing in Linux. (and only ntfs resizing in windows).

I’m not sure what puppy uses… but it should work as non-resizable at the very least.

Sebastian is on the right path, though. Follow his instructions.

Amazing what I know sometimes, even if I can’t seem to do anything right today 🙂

Also,

From the image page, you can go to the image you want, and go to membership. Select all the hosts you want in that image assignment and add those hosts. A host can only be assigned to one image at a time, so all will automatically be “mass changed” as you described it.

@Wayne-Workman

I think so, if any new info or issues related comes up I’ll post.

@Sebastian-Roth said:

Marking this solved for now as we didn’t hear back from anyone. If you have printer issues please follow the link Wayne posted below. If you still think there is an issue within FOG please let us know!

I apologize for the delay, been swamped. It does seem the issue has been resolved. I have not seen it after the past several SVNs. Thank you very much for your help.

@Tom-Elliott said:

We are up and rolling after the latest SVN. Thank you Tom!

@Scott-B What I’m saying, somebody edited something in the code.

I’m not enforcing any PHP 7 anywhere.

Edit the /opt/fog/.fogsettings file and remove the packages line. Then try re-installing. Maybe it’ll work better?

@Tom-Elliott said:

What VM is FOG in? I may need to remote in once I get back from my appointment to see your issue. Right now, Wayne’s issue is not related to fog in any way. It is because he’s running a hyper-v VM and the systemd-udev is using all the cpu trying to set a file it can’t access.

Our two FOG servers are both physical boxes.

@Jbob said:

@Scott-B we have something similar planned for FOG 2.0. However, for 1.X we don’t want to add any more features (this one would take some significant time). Our focus now is to solely get 1.X as stable as possible for a 1.3 release.

Sweet. I look forward to seeing it down the road.

Excellent thanks!

This was fixed last night, sorry I didn’t update sooner and as always thanks for the report.

@Tom-Elliott said:

@Scott-B right but you don’t have anything in the advanced items. There is the login and it is working fine. But the advanced menu is its own configuration setting that you put your needs in.

Ah… okay. I thought that was just called from fog.advancedlogin.

The installer sets most of those things for you, they work for probably 95% of environments. The exceptions to the rule are the really, really large environments where FOG services over 6,000 hosts.

@Wayne-Workman said:

@Scott-B Just get rid of those…

Backup your DB first. FOG Configuration -> Configuration Save -> Export

For an individual:

update inventory set iOtherTag='' where iID=1972;

For everything:

update inventory set iOtherTag='' where iOtherTag like '%\\\\\\\\\\\\\\%';

Thank you, that cleaned up the list very well.

@Wayne-Workman said:

I’m pretty sure this is going to be fixed as soon as Tom implements the latest version of the new FOG Client into the trunk (version 0.9.6).

If you look at the announcement about it, it specifically talks about the backslashes and formatting stuff being fixed. https://news.fogproject.org/client-v0-9-6/

Fingers crossed!

Thanks for the help everyone, it seems up and working now, but I can’t say I know why. I didn’t get to change the MaxRequestWorkers before it came up.

I did notice in /var I have a fog and a wwwfog directory which I never remember seeing.

@Tom-Elliott said:

This is fixed in current. Thanks for reporting.

Excellent thanks Tom!