dmidecode is not available by default in OSX it seems. I started the fog debug mode and got the following:

# dmidecode 2.12 # SMBIOS entry point at 0x8cd15000 SMBIOS 2.4 present. 51 structures occupying 2746 bytes. Table at 0x8CD14000``` The message " Invalid entry length (0). DMI table is broken! Stop." only appears at the end of the dmidecode command.

Thank you I wasn’t able to find similar posts.

@Wayne-Workman I did. I think I’m good for now, I just deployed an image and it worked quickly and perfectly on SVN vs when I tried with 1.2.0 earlier. Thank you guys for your help and building this wonderful tool.

@Sebastian-Roth @george1421 After setting up a fresh install of Ubuntu 14.04 Server and FOG Server 1.2.0 I have finally got it working on a isolated network - only thing now is that the switch I want to use has to have STP disabled (waiting to get a console cable). Thank you all for your help.

@Tom-Elliott Thanks Tom! All is working great. You and the rest of Fog team are the best! I truly appreciate all the great things you do.

I did a fresh install again and did sudo -i and installed if from that prompt the first time, and everything worked now. It is currently up and running, thanks for all the help.

Maybe checkmark boxes in the image definition to tell the inits to move the start sectors? Could be I guess 5 checkboxes, for 5 partitions. Some may have more partitions than that but I think 5 would cover most.

@Tom-Elliott

The group settings change in the update fixed the problem!

Thanks!

Updated to 8341, this seems to be fixed. had me freaked out, as my 4th of july weekend involves imaging 1200 machines…

This may be a good time to mention the custom web-based isc-dchp thing I made specifically for fog?
https://github.com/wayneworkman/fogDHCP

Ok just an update, I got the issue fixed. To do so I had to delete the entries manually from the MariaDB for Fog. (Mysql)

[root@localhost ~]# mysql -u root fog Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 29 Server version: 10.0.23-MariaDB MariaDB Server Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [fog]> delete from hosts where hostName NOT LIKE ' '; Query OK, 51 rows affected (0.00 sec).

So basically

mysql -u root fog delete from hosts where hostName NOT LIKE ’ ';

As a note the second line as I used it deletes all hosts, if you have a problem with only certain hosts then you would want to alter that.

Thanks Wayne. I checked out the log and also communicated some with Tom. I had to update my Active Directory info in Fog for Legacy Fogcrypt and the new password system. All is well now. Thanks!

I found that was wrong, it was one host that was blocked on start on fog without any task pending on it ??
IP 172.19.81.167.

We have to find what host ( there is 800 computers in school) without having his hostname.

I have to compare export of hosts in Fog with mac adress and the apache log file.

After i have to find in my GLPI inventory where was that netbios name in the school rooms.

The computer failed to start on PXE. I shutdown it too quickly to save the error message.

After shutdown it, i delete again with mysql command blank images and fog runs fine again.

Thanks for your help searching in apache log ! i understand how it works now.

@Tom-Elliott
OK

Thanks a lot for your help. I think I need to expend some time looking for the best solution here. I will update the thread with progress.

@gwhitfield said in FOG service on 0.10.6 not restarting after reboot:

demon ninja gremlins

We are certified demon ninja gremlin dispatchers.

@Stilty update, and all should work hopefully.

Updated to the latest trunk release on the SVN and had to run the SQL commands listed here:
https://forums.fogproject.org/topic/7734/snapin-id-was-not-set-or-unable-to-be-created-svn-revision-5661/27

After that, it started working great.

Thanks for the help, guys!

@Tom-Elliott Fixed as of 5772. Thanks Tom!