Latest FOG 0.33b
-
[quote=“Timelord83, post: 26127, member: 10119”]I have looked till my eyes are crossed and i am sure someone is going to point it out right off and i’ll want to facepalm… where does .33b store the kernels so i can add a couple we use on legacy machines? Sorry in advance if more than 1 braincell is required for my answer.
and if it is tftpboot folder which one is the base kernel? and did the format for the kernel change? will i still be able to use the kernels from .32 on .33b?[/quote]
The base kernel for 0.33 is now a 64 bit kernel. The files are:
/var/www/<FOGDIR>/service/ipxe/bzImage (64 bit)
/var/www/<FOGDIR>/service/ipxe/bzImage32 (32 bit <- FOG 0.32 and below as well) -
r1504 released.
There were a few bugs squished today and this is the last one I’m aware. Please keep reporting.
Thank you,
-
r1512 released.
Fixes a few items. Well that and between 1504 and 1512 of course.
1.) Fixes location searching if location plugin is enabled.
2.) Fixes the ubuntu “line 276” issue.
3.) Doesn’t remove the /var/www/fog or /var/www/html/fog if it exists. Simply copies the new files to the original. So if you made customizations to the core files, they’re back to what FOG Developers have coded, but it won’t erase your custom hooks/plugins anymore during an update. (BIG PLUS IN MY EYES)
4.) Various other bugs (I can’t remember all now) fixed.
5.) seccomp_sandbox=no added to vsftp config file now.
6.) Hooks that were activated, then deactivated, then for whatever reason, removed from the hooks dir no longer breaks the GUI. The work around would be to clear the browser cache, but that method varies based on the browser in use. -
r1516 released.
Some more minor bug changes from 1512 up to now. Also kernels are updated to 3.14.2.
-
I get this error: “call to a member function get() on a non-object in /var/www/html/fog/lib/fog/MulticastManager.class.php on line 83”
-
[quote=“nikonaum, post: 26151, member: 2897”]I get this error: “call to a member function get() on a non-object in /var/www/html/fog/lib/fog/MulticastManager.class.php on line 83”[/quote]
Can you provide more information? Such as what you were doing that caused this error?
-
I’m doing nothing, this message popups on the console of my server just after boot and login. I’m using CentOS 6.5 and the latest trunk of fog 0.33b.
[OFF-topic] I saw that a lot of files and locations have changed in this version and I would be thankful to you to point me to a tutorial for 0.33b for adding some software to the boot menu of fog. I basicly want HIREN’s boot cd, clonezila, Ubuntu LiveCD and menu to image the computer by the menu, not using the web interface for scheduling the job. -
One more error in the apache log file which says:
[error] [client 192.168.1.13] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘FOGFTP: Failed to put file. Remote Path: /var/www/html/fog/service/ipxe/bzImage001, Local Path: /tmp/bzImage001, Error: ftp_put(): Could not create file.’ in /var/www/html/fog/lib/fog/FOGFTP.class.php:88\nStack trace:\n#0 /var/www/html/fog/management/ajax/kernel-fetcher.php(59): FOGFTP->put(‘/var/www/html/f…’, ‘/tmp/bzImage001’, 2)\n#1 {main}\n thrown in /var/www/html/fog/lib/fog/FOGFTP.class.php on line 88, referer: [url]http://192.168.1.10/fog/management/index.php?node=about&sub=kernel-update[/url]
This happens when I try to download new kernel.
Also the unofficial kernels are not showing either! -
r1518 released.
Should fix the error message reported by nikonaum. The FOGFTP error I’m not fully aware of. Unofficial kernels were not showing because my website web down.
-
I can confirm that the first error message reported by me has gone now, but still have problems with downloading different kernels from the menu. Maybe It’s smoe kind of permission problem or vsftpd problem. My machine has firewall off and selinux disabled.
-
nikonaum,
Can you, possibly, provide more information?
For example, how did you install FOG 0.33b? Was it a fresh install or an upgrade?
What OS are you running?
Are your FTP username and password set correct? If they are, are permissions set properly?
The kernels and init are now located in the FOG Web directory in service/ipxe/
So in most Debian installs the default location is: /var/www/fog/service/ipxe/
So in most Redhat installs the default location is: /var/www/html/fog/service/ipxe/
The permissions should be on Debian installs:
[code]chown -R fog:www-data /var/www/fog/service/ipxe[/code]
The permissions should be on Redhat installs:
[code]chown -R fog:apache /var/www/html/fog/service/ipxe[/code]
The FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD need to be set to that of the fog user (not the GUI, but the FOG user from the terminal on the FOG Server with:
[code]sudo passwd fog[/code]
The default password I’ve set to it is currently password
You set this password in FOG Configuration->FOG Settings->TFTP Server
FOG_TFTP_FTP_USERNAME should be set to fog
FOG_TFTP_FTP_PASSWORD should be set to whatever you set the fog user password to.
For storage node on the same FOG Server, you also set the Storage Management Username and Password to the same:
Storage Management Page-><SELECT YOUR STORAGE NODE>->
Management Username should be set to fog
Management Password should be set to whatever you set the fog user password to.Hopefully this helps you out.
-
r1519 released.
Fixes the setting of the TFTP_PXE_KERNEL_DIR variable in the db and config files so they work properly.
If you’re getting an error on downloading the kernels, check this in FOG Settings->TFTP Server-TFTP_PXE_KERNEL_DIR and make sure it points at the proper web location (/var/www/fog/service/ipxe/ for ubuntu/debian, /var/www/html/fog/service/ipxe/ for redhat/centos/fedora).
r1520 released.
Changes the “Location” to not be small in the Host list for readability.
-
After I installed a Linux Mint on a computer, I tried to deploy Windows 8.1. I got this
[IMG]http://i.imgbox.com/X9S7lCy3.jpg[/IMG] -
How about powering on the system and performing a proper shutdown as the information is telling you?
Here’s a google search on how to do it.
[url]http://lmgtfy.com/?q=remove+hibernation+file[/url] -
-
I don’t know how I missed that…so sorry for wasting your time on such a stupid problem.
-
[quote=“Mr.Myagy, post: 26171, member: 23824”]I don’t know how I missed that…so sorry for wasting your time on such a stupid problem.[/quote]
It’s not a waste of time. Sometimes we all miss the little indicators. Just read what the screen is telling you next time a little more closely.
-
Hello all, I’m having some problems with fog 0.33B (r1519). The set up of Fog went without too many issues and I’ve updated my DNS/DHCP server appropriately and I can now access the web interface, add machines and upload images via iPXE. The problem comes when I attempt to deploy the image, part clone starts but I end up with the following message;
Starting to restore image (-) to device (dev/sda1)
It then remains like that ad nauseam.
It does appear to wipe the system but fails to deploy the stored image, having no experience of part clone I can only speculate that it’s because it’s failing to find the image on server or is failing to pick up what image it should be using from Fog (speculation from seeing image (-) where I would assume that it should say image (<image name>)), I’ve checked the /images folder and the image is in the correct folder and the permissions are set for fog to be able to access the folder (hence it can upload without any issues).
Unfortunately there are no errors in the multicast log and having gone through the config section of the site and the config.php file with a fine tooth comb I can’t see where it would be failing, here’s a summary of the system that I’m running;
OS: Debian Wheezy running as a virtual machine on ESXi
PHP/5.4.4-14+deb7u9
Apache/2.2.22
MySQL client version: 5.5.31In terms of images I’ve created two images, the first was built using VMPlayer (win7 32 bit), prepared using the fog prep tool and sysprep with an unattend.xml file, the second is the same but using a physical machine on the off chance VMPlayer was doing something to the image (clutching at straws!).
I’m at a loss
-
Check that the FOGMulticastManager service is running on your fog server:
[code]service FOGMulticastManager restart[/code]You can check the multicast log from /opt/fog/log/multicast.log
-
Why not try a unicast first?
