@Tom-Elliott I think we can mark this as a one off problem. Maybe I missed a step when I migrated the old images. Thanks for looking into it.

@dolf Simple doesn’t get the job done when you’re trying to measure bufferbloat, or other multi-variable problems 😉

Check out Flent: https://flent.org/

I’ve solved this for now as the other thread is also reporting as solved since switching to ksort from asort.

@Tom-Elliott Sorry for the delay… patch week and all that fun.

I ran with disabling dynamic memory for other VMs until today. I updated my dev server to build 8597 and kept the 4.6.2 that the installer downloaded today (2016/07/14) and the issue appears resolved.

Confirmed fixed, the client is now showing in the logs the scheduled power task.

I’m pretty sure it does fall on the installer already.

I’ll double check just to be sure:

1 configureSnapins() { 2 dots "Setting up FOG Snapins" 3 mkdir -p $snapindir >>$workingdir/error_logs/fog_error_${version}.log 2>&1 4 if [[ -d $snapindir ]]; then 5 chmod -R 775 $snapindir 6 chown -R fog:$apacheuser $snapindir 7 fi 8 errorStat $? 9 }

That’s the script portion in the installer’s functions.sh file.

I see what’s wrong now. Thanks for leading me to it. Yes, Servers were getting the information set, but plain nodes were not. Should be fixed in latest. Thanks for reporting. Also fixed a few minor issues while I was there.

This is solved as the version is now operational again, though Sourceforge is still DITW (Dead in the water) at this point.

@Tom-Elliott yes it’s working again, ty.

alt text

Regards X23

@Tom-Elliott said in ipxe login after upgrading to latest trunk + no such file or directory:

Again? Anything to report for this?

I eventually went with a clean install of 14.04 and a new database and the problem went away. In that way it’s resolved on my end though I don’t know what was in my old database that could have caused this.

@neodawg I have solved this thread for now. Please keep us posted if you’re still running into this issue. I’m fairly confident fog can do this with little problem, but I can not know all the possible scenarios that might present this problem.

Please confirm if this is good to go with 0.11.3 please? Yes it’s basically impossible to expect this to work with 0.10.6 (and probably prior issues). I’ve renamed the heading to “FOG Client - not fully uninstalling” as making it rely on the specific version that will never be able to be fixed seems strange.

Again, anything on this?

Again, anything to report?

I’m fairly sure this is working, though I’m not sure I am a good tester for this. I only have two machines.

@Wayne-Workman woot. I think the other thread that was similar to this should be updated as well. Sorry it took so long to figure out at any rate.

@Tom-Elliott Trunk 8485 appears to be functional for imaging with the location plugin - confirmed at two sites so far. I assume the rest are good.

@ddavis I am sure you’ve gone through the tutorial on FTP issues, have you? https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

As stated in the other thread very similar to this, I’m now fairly certain this is fixed in latest. Solving for now, please keep us apprised. To verify you will have to perform one of the taskings requiring capture or deploy types.

Should be fixed in latest, sorry about causing the issue.

@Tom-Elliott I don’t know what happened, but due to another issue, I updated to 8440 and the new host joined with no issue. So adding all of the existing hosts to a group and applying AD changes to them took care of those, and the patch to 8440 seems to have changed something that was keeping my defaults from populating on new hosts. Thanks!