Confirm this plz…
mysql -u fog -p fog
Then type in the password. Do you get…
ERROR 1045 (28000): Access denied for user 'fog'@'localhost' (using password: YES)
Just had a small hickup in svn 5680. Had to do the following…
mysql> create user 'fog'@'localhost' identified by 'your password here';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT ALL PRIVILEGES ON * . * TO 'fog'@'localhost';
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Did you create an A Record pointer on your DNS Server to point FOG-SERVER to IP xxx.xxx.xxx.xxx.?
@Jbob nicely done making it 100% isolated.
@Wayne-Workman I stuck with the old client this past year as Joe was still pushing the development of the new client. I’m interested in using the new client. Try not to strike things down so quickly.
When working in a school and pulling out 30+ laptops in a classroom you want to cut down as much as you can on the wifi traffic. As our current setup can easily accommodate the 6MB download per laptop, it just seems like it’s wasted. Is there any possible way only have a select clients not update?
@Roger-Saffle Are you using an image that was already attached to the domain when you uploaded it?
To make it official , I spoke with Tom today and I learned that the client auto updates at boot. (yeah been out of the loop for awhile) With many businesses using products like Clean Slate and Deepfreeze this client auto update would be a “useless” tool. Just to take you through the process. The pc gets client installed --> server gets updated along with new client update --> pc gets booted and the client sees a new update is on the server --> client downloads update and installs --> pc shuts down and Deepfreeze wipes out all changed made while in frozen state --> pc boots client sees new update and installs. This loop will continue until the client has been “thawed” and changes allowed to be made to the hard drive. This seems like wasted bandwidth. Don’t get me wrong auto update feature is awesome. Just some people (like me) will want auto updates disabled for hosts that are frozen.
Might I suggest a “Disable Client Auto updates” tick in the global settings and also for Host/Group settings.
SOOooooo then.
Try another OPtiplex 5040. This maybe directly related to this particular machine.
Could already be registered with blank info in the database. But we’ll rule that out later.
IF same error occurs on the same model but different machine then try installing an earlier version of the kernels.
This was a feature implemented in May-ish
./installfog.sh --help
Usage: ./installfog.sh [-hdUuHSCKY] [-f <filename>] [-D </directory/to/document/root/>]
[-W <webroot/to/fog/after/docroot/>] [-B </backup/path/>]
[-s <192.168.1.10>] [-e 192.168.1.254] [-b <undionly.kpxe>]
-h -? --help Display this info
-d --no-defaults Don’t guess defaults
-U --no-upgrade Don’t attempt to upgrade
-H --no-htmldoc No htmldoc, means no PDFs
-S --force-https Force HTTPS redirect
-C --recreate-CA Recreate the CA Keys
-K --recreate-keys Recreate the SSL Keys
-Y -y --autoaccept Auto accept defaults and install
-f --file Use different update file
-D --docroot Specify the Apache Docroot for fog
defaults to OS DocumentRoot
-W --webroot Specify the web root url want fog to use
(E.G. http://127.0.0.1/fog,
http://127.0.0.1/)
Defaults to /fog/
-B --backuppath Specify the backup path
–uninstall Uninstall FOG
-s --startrange DHCP Start range
-e --endrange DHCP End range
-b --bootfile DHCP Boot file
