Bugs in FOG 0.33
-
Hi Tom, sorry I have never used active-snapins, all I use is capture and deploy, but the error I am experiencing seem similar to the snapin issue in the latest fog thread.
-
r1120 released should help address the errors. The class is now created before storing the variable, which I think was throwing all those errors. Also fixed the GreenFog.class.php and HostAutoLogout.class.php variable issues as noted in Troye Johnson’s log file.
-
Hi Tom, have updated to the v 1124, still having same issues with multicsting as with my earlier post from yesterdat at 5:25, just letting you know, not sure if felt that multucasting should work or if your still working on it.
Thanks -
Try updating to 1125, somebody reported about an issue in variable set. (Multicas[B]e[/B]t instead of Multicast was used.)
-
Hello,
I get an error about firmware for nic driver, something with bnx2 firmware couldn’t be load. I tried now to build a new kernel and get this error:
[CODE] MK_FW firmware/bnx2/bnx2-mips-09-6.2.1b.fw.gen.S
make[1]: *** No rule to make targetlinux-firmware/bnx2/bnx2-mips-09-6.2.1b.fw', needed byfirmware/bnx2/bnx2-mips-09-6.2.1b.fw.gen.o’. Stop.
make: *** [firmware] Error 2
[/CODE]Any ideas?
-
Download my latest kernel from The local normal place and it already has that exact firmware loaded into the kernel.
-
I’ll try and post more formal HowTo to build the kernel using the TomElliott.config as there is an extra step involved now that I’m building firmware’s into the kernel.
-
[url]http://fogproject.org/wiki/index.php/Build_TomElliott_Kernel[/url]
Should help you guys all out.
-
Oh… Just noticed this thread. Not sure if i’ve found a bug or not, but I just updated to 1210 and now under Disk Information on the Dashboard, I have this error/link that says, “Failed to connect to DefaultMember”. When I click the link, it takes me to the Hardware Information screen and has a message saying, “[FONT=Ubuntu][COLOR=#555555]Unable to pull server information!” [/COLOR][/FONT]
-
That’s not really a bug, but a configuration issue on your FOG Server as far as I can tell.
-
Hmmm… I’m not sure how it was a config problem. I pretty much used the default settings, other than IP, subnet, etc…
-
Right,
How are you hosting your /images? Is it linked to another source or just the base /images?
Are there any messages in /var/log/{httpd,apache2}/{error_log,error.log}?
Maybe also check the access_log,access.log files.
-
Ok, I see what I did. I tried to modify default in /etc/apache2/sites-available/ to default to [url]http://(ip[/url] or host)/fog, so all I would need to do, is type [url]http://(ip[/url] or host) to get to the Fog login page. It was working, but I was getting the above error…
-
So it was a sort of configuration issue?
-
I guess so. I saw where the Fog install adds the index.php with a redirect to “./management/index.php”, but apache2 didn’t recognize it. It just kept showing the default apache “It Works!” page. But, once you remove the default “index.html” page, everything seems to work just fine. Perhaps a Fog installer oversight?
-
No it’s more an apache2 installation thing on Debian systems.
-
BigMan99211, You need to adjust apache to look for php before html, or remove the html file as you described above. This is not a bug.
That “This works!” page is a default created by apache as a courtesy to check on localhost to make sure your folder is accessible. I theory we could add a “remove index.html if exists” line, but for those of us that use our FOG servers as web servers (internal or external) this could cause a HUGE headache if your index.html went missing.
-
I can understand that. But, couldn’t you just put in a simple question during install, asking if you have any other websites or software that utilizes Apache? If yes, it skips. If no, it deletes the .html file. Seems pretty simple.
-
I’m sure it could, would be easier to attack the apache config file and add .php extension to the file so it looks for the php file first
Besides it tells you after you finish installation to navigate to the “[url]http://ipaddressofserver/fog/management[/url]”.
Hell, if I remember correctly the link is even clickable in the terminal window so you don’t actually HAVE to type or copy anything, just make a shortcut.
-
I’ve always been a proponent of making installations easier, or even more customizable through the installer. Ask a bunch of questions at first, and make the setup and configuration a lot more seamless.
