If you’ve been following FOG for a little bit of time, you all may remember a week or so ago where we had the “random” mac deletions occurring?

Well, last night, or two nights ago (i don’t remember which exactly) i found the culprit and corrected it.

What this means:

FOG is actually working as intended. You’re missing the MAC that once existed because the hostMAC field for that host either one or both are set at id of 0 (which is invalid).

I don’t have a nice means to fix this, so if you’ve got phpmyadmin or are knowledgeable about database entries you can correct it on the fly.

The simplest method I can think if, for now, would be to delete the host (or hosts as the case may be) that’s causing a problem and attempt re-registering them.

Duplicate thread. Follow the thread here: [url]http://fogproject.org/forum/threads/pxe-menu-absent-svn-build-3325.12843/[/url]

[QUOTE]This isn’t highly documented as it’s relatively new. In an attempt to allow legacy and new client’s to operate with a single version of FOG, I created a Field for the New Client (FOG_AD_DEFAULT_PASSWORD) and the legacy client (FOG_AD_DEFAULT_PASSWORD_LEGACY).[/QUOTE]

Perfect explanation - I ran into this issue today, wasn’t aware of the new legacy field. All is working fine now.

Wearing my idiot hat this morning just used to seeing it all on one screen like in the add snapin screen. Off to get more caffeine.

r3254 fixed it.

Thank you for being awesome, Tom.

Hello
i noticed that some isatap adapter (IPV6 protocol) appear with the same mac address in the result of ipconfig/all

i tried to unchek ipv6 and the error message change :

CommunicationHandler Response : Error multiple hosts returned for list of mac addresses

Thank’s !!!

The update solved it !

Regards,
Ch3i.

[quote=“Wayne Workman, post: 45339, member: 28155”]So the moral of the story is to use ext4 ?[/quote]
Well, there are a lot of other nice filesystems out there too! ext4 is working for us right now and I am sure it will for others having an issue with deleting hugh files on ext3. But I am not saying that ext4 is the only fs that can do this…

r3232 fixed this.

Thank you, Tom.

The issue is resolved. The above post fixed it.

Same here, although this isn’t critical because things are working.

Just reporting the bug is still here. FOG r3218

[quote=“Wayne Workman, post: 45160, member: 28155”]This may or may not be related, but, I’m sitting in a lab watching it image right now.

Things are going smooth, but the “Tasks” tab in the FOG web GUI is reporting some hosts speeds correctly, while others are sitting at zero… FOG version r3218[/quote]

[url]http://fogproject.org/forum/threads/svn-2806-task-management.12134/#post-40095[/url]

This isn’t really a feature request. It’s a bug. I’ve since corrected for this. The only thing you can’t do is set multiples for the same time, but you can set how ever many of any kind. It was only allowing one greenFog entry at all and this was incorrect.

This might fix the issue [url]http://stackoverflow.com/questions/118884/what-is-an-elegant-way-to-force-browsers-to-reload-cached-css-js-files[/url]

Thank you very much! I think that’s it - an ftp password issue. I set the user password and the password in the fog configuration to the same thing and my latest test upload put everything in /images/testimage.

The first two errors derive from FOG trying to check if you clients are up. You can turn this off in FOG Settings -> General Settings -> FOG_HOST_LOOKUP (uncheck and save).

Hi,

Updated to latest version and I haven’t the msi in the client folder.

Regards,
Ch3i.

Edit : Solved using that : [url]http://fogproject.org/forum/threads/latest-development-fog.10556/page-28#post-44440[/url]

I believe its alphabetical what I did was prefix my snapins with a number to force an install order it also helped to put my commonly used snapins at the top of the list.

Seeing as we’re on 3132, I’d recommend updating and seeing if this still occurs.