Latest Development FOG
-
[quote=“VincentJ, post: 28240, member: 8935”]When installing it prompts the user to leave the MySQL password blank.
however when you get near the end of the install it asks for your MySQL password and wont accept a blank password.could we update the warning or is this something different?[/quote]
I’ve added a check. It will ask if you left the password blank. If you did (which it defaults to) it continues on as normal, otherwise it will prompt for the password at install time. Hopefully this helps.
-
Possibly also consider getting the first warning to let users know they can enter it later rather than telling them they need to edit a file later
Just installed my test suite on the btsync version. luckily means every fog server becomes a btsync peer.
could we have a quick script that can be run without interaction that does updates?
-
when not participating in beta testing, updates only need to be installed infrequently. for this reason, i do not feel that a “no touch” updater is needed. there was another forum poster that created one, however, if you care to seek it out. though, as i recall, this script broke slightly with one of the updates to the install/update script.
-
Just trying out the location plugin,
when setting the location of a host, it doesn’t seem to stay past the refresh of the page.
-
I had a . instead of a : in my mac… seems to work, but odd that such a thing would make it fall over…
-
SVN 1751 released.
With this comes a fix, previously, to the Capone Serial number problem. Also, I’ve (with the help of Junkhacker) added a longer delay time in receiving dhcp requests with the undionly.kpxe, undionly.kkpxe, ipxe.pxe, ipxe.kpxe, and ipxe.kkkpxe files. Please give these a shot if you can.
[code]wget /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe
wget /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kkpxe
wget /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.pxe
wget /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.kpxe
wget /tftpboot/undionly.kpxe https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.kkpxe[/code] -
SVN 1753 released. Made the searching elements in Capone not case sensitive. Add’s an active task checker to the task scheduler service to push WOL to all systems have are still awaiting checkin. This is because the initial push of WOL happens too quickly. Some networks may block the multitude of UDP packets sent so this should help with getting systems up and running for you.
-
SVN 1756 released.
Adds better checking during the install phase for redhat based installation.
-
SVN 1759, maybe now I can be done with Capone?
-
SVN 1764 and 1765 released.
Fixes the SANBOOT/EXIT not selecting the one in DB. Fixes, hopefully, the MulticastManager and ImageReplicator bugs. (Thanks Scott and sirEgghead).
Hopefully all is good.
-
SVN 1768 Released.
With this release, I’ve added grub4dos binary and the FOG_BOOT_EXIT_STYLE.
Hopefully this will allow booting to the hard disk that much easier for those that have issues.
-
I really need to get testing… The exit issue is a problem on almost all the new Dell boxes… Hopefully soon!
Way to go Tom, it’s great to see things moving. -
Hopefully I’m not reposting a known issue, but I ran into this yesterday on FOG 1.0.1 (Ubuntu 13.04)
[SIZE=3][FONT=verdana][COLOR=#222222]The name format we use to register hosts (via Full Registration) is beyond the character number limit in some cases. FOG attempts to truncate the name when beyond the permitted length. When this happens, it gives a message something to the effect of ‘unable to append co.txt’ - I can get the exact message next time I’m at work if it helps. I assume the truncating is what’s failing, as the registration then halts completely and doesn’t register keypresses, etc. To do anything, you have to shut the machine down, boot to FOG again, but then registration succeeds the second time around - using the original too-long name. I know the ‘smart’ solution is probably to change to a shorter naming scheme, but I was hoping there would be something else that could be done[/COLOR][/FONT][/SIZE]
-
SVN 1778 released to fix a few issues.
First things first, init.xz and init_32.xz are updated to contain the GRUB2 fix from fractal13.
Next, add’s a “fix” for the xz compression to actually happen when buildroot is built.
Next, fixes an issue (hopefully) in wol information where when it accesses the directory, it was trying to redirect the page to /var/www/{html/fog,fog}/wol/management. If this doesn’t work, it will not hurt anything either so no loss or gain, just trying to neaten up errors logged. And, last but certainly not least, uses the path name of the image to delete the files rather than the image name. Sometimes the path is not the same as the image name due to varying reasons.
-
SVN 1780 released.
Fixes an issue with grub mbr generation if the first element found equates to 0. It would try to set the count to -1, but dd can’t create an mbr for a sector that does not exist in the first place.
Fixes the snapin search to group by the snapin names rather than just returning all the found results.
Fixes snapin task creation so if a host has no snapins associated, it’s not going to try to create a snapin tasking. And it won’t try to create one if the deploy job is specifically told to do a Download without snapins task.
-
SVN 1783 released.
Fixes a few more bugs found. Fixes the GRUB data that seems to “just work” now as well.
-
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.
-
svn 1788 released.
Includes an installer log file for helping troubleshoot issues. This is located at:
/var/log/foginstall.logIf you have issues during install, please post this file or the contents of the file with your posts.
Thank you!
-
I don’t think forcing everyone to be on the latest and get every bug is a good idea…
Tom is great at pushing out updates, but he’ll probably feel a great deal worse with
“grgrhdaslhasdfhlahf MY NETWORK IS DEAD auihwefiaewkjafds… FIX IT NOW, EVEN IF I HAVE NOT PAID FOR IT I DESERVE IT aiwlhflahflkhawfklhlawhflawdfl;ahflhaewfhflkaewhl”going on all day if there is a code mistake.
The installer uses past responses which is ‘good enough’ for those wanting to be bleeding edge providing they have BTSYNC
-
[quote=“VincentJ, post: 28257, member: 8935”]Possibly also consider getting the first warning to let users know they can enter it later rather than telling them they need to edit a file later
Just installed my test suite on the btsync version. luckily means every fog server becomes a btsync peer.
could we have a quick script that can be run without interaction that does updates?[/quote]
If it’s of any help:
[url]http://fogproject.org/forum/threads/automating-fog-0-33b-svn-updates-in-ubuntu-14-04-with-cron-easily-adapted-to-other-linux-distros.10409/#post-26920[/url]Though the part of the script that “auto confirms” the schema system may not work.
