Posts made by Wolfbane8653

[quote=“Tribble, post: 29689, member: 17221”]Finally managed to get around to looking at those switches. Disabled Spanning Tree Protocol, and they now boot correctly.

Thanks Tom.[/quote]

Just poking fun.

[quote=“Wolfbane8653, post: 29152, member: 3362”]Tribble check out this: [url]http://fogproject.org/forum/threads/nothing-is-working.10598/page-2#post-28305[/url]

I’m sure that the Dell Powerconnects have Spanning Tree Protocol (STP) enabled by default. Please confirm that these have be disabled.

Also there seems to be a portfast function as well. With portfast being disabled it would interfere with iPXE and not PXE[/quote]

Thank you for giving Fog Configuration --> FOG Settings --> “FOG Service - Printer manager”

Can you also post this location under services: Service Configuration --> “Printer Manager”

Edit: Should look something like what I have attached.

[url=“/_imported_xf_attachments/0/951_Untitled.png?:”]Untitled.png[/url]

Just to be sure can you post a screen capture for Service Configuration --> “Printer Manager” & Fog Configuration --> FOG Settings --> “FOG Service - Printer manager”

uh look in the /tftpboot folder…

Just change your Option 67 to undionly.kkpxe (or ipxe.kpxe, ipxe.kkpxe, etc.)

I had this twice when using v0.32…One time was a bad piece of RAM and the other a bad motherboard/onboard vid card. Double check your hardware and if you can get into the for menu run the memtest option on the fog menu.

Using parts from broken machines you really don’t know what your getting until everything boots.

FIXED!

I truncated the entire tasks table, removed the bad member reference in groupMembers, and anything else related to this 'BAD HOST"…The Invalid OS ID is due to a small bug in r1799.

Issue resolved.

THANKS TOM!!!

[S]I have fixed the Task Management page by Clearing the Tasks table were nameTask is “AutoRegTask”.[/S]
[S]For you coders out there:[/S]
[S][CODE]delete from tasks where taskName=‘AutoRegtask’;[/CODE][/S]

[S]Going to try to image machine see if I still get the “Invalid OS ID Windows 7 (5)” error.[/S]

[B]Edit:[/B] This did not fix the issue. The Task Management page is blank again as soon as I registered the next HOST and I am still getting the Invalid OS ID.

Good morning!

It’s been a while for listing problems b/c I just “NAG” Tom directly but I thought this would be a good idea to at least post this… I updated this morning (6/9/2014 @ 8:10am)

I was in the process of registering machines and I miss pressed a key when adding a HOST to a Group. The group ID I wanted was 3 and I pressed 4 in my haste. At this time Group 4 does not exist. I then continued and told Fog to image the machine. On the next boot I received “An error has been detected ***** Invalid OS ID Windows 7 (5) ***** An error has been detected”

I tried deleting the host from the Host Management and it would not delete using fog’s delete function due to the id field came up ID=0. So, I ran:
[CODE]delete from hosts where hostName=‘<HOSTNAME>’;[/CODE]

This deleted the host out of the HOST Management but when I went to delete the task for imaging this Host the Task Management page is blank. Here is what I get in the apache2 error log.

[QUOTE][FONT=arial][COLOR=#222222]PHP Fatal error: Call to a member function __toString() on a non-object in /var/www/fog/lib/pages/TaskManagementPage.class.php on line 419, referer: [url]http://10.0.0.252/fog/management/index.php?node=home[/url][/COLOR][/FONT]
[/QUOTE]

I have rebooted the Fog server and restarted apache2 service. Any ideas?

fog v1.1.0-r1799

[url=“/_imported_xf_attachments/0/945_fog-2014-06-09-12-36-50.png?:”]fog-2014-06-09-12-36-50.png[/url]

Ubuntu 14.04 LTS is having serious issues with mysql. At this time it is[B] not recommended[/B] by anyone here to have your fog installation on Ubuntu 14.04.

Can you verify that undionly.kpxe is located in /tftpboot?
What do you get when you go to: [url]http://<ipofserver>/fog/service/ipxe/boot.php?[/url]
What is your Fog Settings --> [FONT=Ubuntu][COLOR=#555555]FOG_TFTP_PXE_KERNEL[/COLOR][/FONT] read?

Machine gets ip from dhcp–> machine can’t access undionly.kpxe --> Machine exits ipxe

No bzImage should be located in /var/www/fog/service/ipxe

/tftpboot --> network boot files (undionly.kpxe/ipxe.kkpxe)
/var/www/<html/fog>/service/ipxe --> Kernels & Fog Menu Items (bzImage/bzImage_32)

[quote=“bveiga, post: 29369, member: 24091”]hi i´m getting the error “could not start: download operation not supported” but this only happens in one domain, in the others we have the same server with no problems,the switches are equals on both domains(cisco), can anybody help me please?
best regards

Bruno[/quote]

This is not the iPXE “0x040ee119 error” please make a new thread.

Can you upload a picture of your exact error message?

[B]Fog v1.0.1 bootfile should be undionly.kpxe[/B]

Alternate Options:
Option 1:
[url]http://fogproject.org/forum/threads/keep-up-to-date-with-all-the-fog-0-33-updates.10300/[/url]

Option 2:
[url]https://mastacontrola.com/fogboot/kernel/[/url]

Option 3:
[S][url]https://www.dropbox.com/sh/ny25xg5ms4vzv1y/AACT_yqeILg49lMyns_e1oFUa[/url][/S]
[S]This link will be deleted in 1 hour[/S] [B]Time has expired.[/B]

True but as a warning you DNS records and DHCP records will have probable issues. Since its the same MAC and JOINED to the domain DNS will have to fix the A record pointers and DHCP will have to updated the A records from the DNS. UNC paths may take much longer than expected and so on…

This dual boot is nice for testing software but I would not recommend it.

Yeah you would have too. The renaming will be also an issue. Since there are no duplicate mac addresses to computer names. This brings up an interesting point.

Edit: Jaymes is correct AD registers the OS and hostname. If the OS changes then you need to re-join the domain, so when dual booting you may need to disable Hostname change and change other things with this machine.

Also a “no touch” updater would cause everyone to be on the “bleeding edge”. If there is a serious error with the latest build then everyone would have the issue and trigger a mass error report from the public. I don’t know if you know what that feels like but it would force the developers to scramble to fix it. Which would cause the developers not to really touch a working product. At least if you have to install each and every time you know your taking that risk in having possible issues.

The Fog Service isn’t “a needless systray icon” If you only use for it is to join the domain then the more power to you!

BUT…the Fog Service does plenty!

[LIST]
[]Auto Logout --> Logs user out after x mins of inactivity
[]Client Updater --> Personally haven’t played with this
[]Directory Cleaner --> can set to clean out tmp folders and other specific folders
[]Display Manager --> Force a resolution size
[]Green FOG --> Shutdown/reboot services
[]Host Registration --> Not currently working (at least i think)
[]Hostname Changer --> changes name of the host to the host name listed in fog for that mac
[]Printer Manager --> manages printer installs
[]Snapin Client --> Program installs and roll outs
[]Task Reboot --> reboots host
[]User Cleanup --> deletes all users except for specific users listed
[]User Tracker --> makes a log of what users login to any of your registered fog machines
[/LIST]
[FONT=Ubuntu][COLOR=#555555]so it DOESN’T mean its use less and yes thank you for sharing the XML it will be useful.[/COLOR][/FONT]