Fog 0.33b Snappin deployment
-
no go… there is definitely an issue with tftp though…
When trying to download a different Kernel i get:
[CODE]Error: Unable to connect to tftp server.[/CODE] -
Apparently after installing and uninstalling fog, I have screwed up things like the tftp password for fog.
I have fixed the tftp password issue, is there anything else that i need to check/change I still cannot register a host. -
I found the following in /var/log/syslog
[CODE]Jan 28 12:39:01 10Fogserver CRON[25479]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null ; -delete)
Jan 28 12:40:26 10Fogserver in.tftpd[26591]: tftp: client does not accept options
Jan 28 12:41:23 10Fogserver in.tftpd[27420]: tftp: client does not accept options
Jan 28 12:52:50 10Fogserver in.tftpd[29509]: tftp: client does not accept options
Jan 28 12:53:50 10Fogserver in.tftpd[29634]: tftp: client does not accept options
[/CODE] -
I think I put the new fog scripts in place at revision 1145, maybe to to 1140?
-
Those errors are normal. But you’re still not getting the tftpserver running properly?
-
tftp is working now, I had to change the password to match…
I am getting these log messages with R1151 in a apache.
[CODE][Tue Jan 28 13:38:47 2014] [error] [client 192.168.10.130] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/service/inventory.php on line 16[/CODE] -
Replace that file with the one posted here.
[url=“/_imported_xf_attachments/0/521_inventory.php?:”]inventory.php[/url]
-
[quote=“Tom Elliott, post: 22048, member: 7271”]Replace that file with the one posted here.[/quote]
ok sorry for jumping the gun Tom, I reverted to R1140 before i saw you post above. With R1140 I can now image and inventory once again. would you like me to update to R1151 again and replace the inventory.php or keep stepping up one revision at a time till I find I cant image?
I’ll do whatever to help test…
Thanks. -
This post is deleted! -
Please step up in one increment at a time. I want to narrow down the exact nature of the bug. This is awesome.
-
ok will do…
-
Tom, i was able to update to R1141 and succesfully register a PC and image it.
I then updated to R1142 and it broke my image with the popup box saying “Windows Setup could not configure Windows to run on this computer’s hardware”
[IMG]http://imageshack.com/a/img713/4903/aq6m.jpg[/IMG] -
I think I know why. Can you disable HOSTNAME_EARLY on the fog server and try again?
I “fixed” HOSTNAME_EARLY, but it seems to me your systems are sysprepped already, so a hostname change isn’t the right way to go.
-
I disabled it and get the same result Tom.
-
I’m resubmitting another release, should work, (but no guarantee’s) on hostname_early.
-
r1155 should have fixed the hostname_early issue, but I don’t know if just turning it off has helped you out at all.
-
I updated to R1155 and still get the popup box…
-
Tom I was double checking that hostname_early was disabled( It is disabled) and noticed this…
[IMG]http://imagizer.imageshack.us/v2/800x600q90/14/dmnb.png[/IMG] -
I haven’t, quite, figured that out yet. I get those as well. It seems to be something from the Capone plugin causing the issue.
Actually, it appears to be the way the method is called.in the ServiceConfigurationPage.class.php file. I’m checking if this is correct.
-
It, by itself, is nothing to be worried about. You can remove those entries from the database, as they are a nuisance. I’ve updated the trunk and this should be fixed.