@Wayne-Workman Already confirmed and should now be fixed.

@Wayne-Workman You better marry that girl, or I’m going to offer her a job up north (in snowy Michigan) in my group. 😆

I think there is something with the tasks pages. When I just sit on the tasks page the little popup 0 active tasks found is consuming about 8% cpu according to top. On my first test of this that 8% cpu task persisted even when I moved to another page. Then I was getting a session time out popup. Closing the browser and going back in still netted the session timeout. I had to actually log out for that session cookie to reset.

[Edit] After additional testing that 8% httpd process seems to be related to that popup message (i.e. tasks/session/loading/load failed) [/Edit]

It seems to be the same end result, not sure if it is the same cause.

Feel free to close this though and I’ll watch the other one – sorry I didn’t find that one in my search 😞

One potential think to note is that it seems like you got to that state from quick/full host registration, whereas I got to this state by entering data directly into the web interface.

From my experience, the installer doesn’t update users/passwords for the web interface for a re-installation. It just does it for the first installation.

The FTP Path issue is more concerning to me. @Developers

I also updated that part of the WiKi with this info:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#You_must_first_upload_an_image_to_create_a_download_task

This turned out to be our anti-virus program blocking the FOG executables. I really should have checked that first.

This can be marked as solved.

Please update.

I saw the issue and have corrected it now.

Thank you,

Finally, somebody who admits it was necessarily anything I did.

LOL.

All in all, I can try to figure out the information gathered in the logs, as those shouldn’t be visible at that point.

@Tom-Elliott Now it works as expected. Thanks!

This is now fixed.

@Wayne-Workman This should now be fixed.

You can edit past the hyphen because I will now remove them altogether when you focus on the window.

When it initially loads it will present the proper key with dashes, but when you click in the field it will remove the hyphens. When you’re typing it will simply capitalize the letters and will strip any non-alphanumeric keys even if you type them in. When you leave the field it auto formats it. The PHP will also add the dashes as needed similarly so if you update by pressing enter in the field, it will add the slashes properly too.

Fixed please update.

@jmeyer

The client automatically updates itself whenever you upgrade the server.

Another thread being solved because this isn’t “directly” a FOG issue, but rather SELinux issue.

As this isn’t really a BUG in FOG or something, I’m solving this thread so people don’t think this is an issue directly relatable to FOG as a whole.

Semms to be solved in rev 5664
Thanks

@Tom-Elliott Thanks for fixing the two other bugs also. I’m on git5662 now and it is working again.

And something other worth mentioning:
It is a great change that the state in the snapin log is now displayed as “complete” instead of “4” - this makes things more clear.

The only reason I visit the home page is for two things - the storage pie chart and bandwidth. That’s just me though.

I’m glad to see this improvement made - it’ll make FOG work a lot better on older lower powered systems.

@Tom-Elliott Yep, sorry the images weren’t enabled.

Many thanks,

Ollie

@Tom-Elliott Confirmed fixed. I can now delete MAC addresses - and they stay gone. 🙂