Windows clients not joining to AD Domain.
-
I recently upgaded to FOG Trunk 6541. Joining active directory was working before the upgrade took place. Now, it is not. All settings on the fog server look proper and the hosts are set to join the domain after the image task. The hosts restart to get renamed but do not join our AD Domain. Is there any troubleshooting steps that i can take to help resolve this problem?
Any help is greatly appreciated
-
What did you update from? What version of the FOG Client are you using?
-
I updated from 1.2.0
I used the client on the fog server. It says “New FOG Client (Recommended)”0.1 is the version of the fog tray. if that helps.
-
@cojohnson Ok. Now, can you please provide us with the
c:\fog.logfrom the troublesome target host, please? -
Why are you updated to such a STRANGE version? What I mean by that is it seems strange, to me, that you would’ve upgraded to that particular version. Or when you did the upgrade that was the version you put on (latest at that time?). You willing to try updating to current latest and see if maybe it’s just fixed now?
-
Ok. I am in the process of upgrading to the latest version of Trunk (7212).
We did find a work around by using the legacy password for out AD Account. Once the server upgrade completes, I will install updated clients on a few test computers to see if that resolves the issue.
-
Issue!!!
It says you need to Install/Update your Database Schema.
You can do it by going to 10.21.0.105/fog/management/which i did over 30 minutes ago using Firefox browser from the server. It is still sitting there on a blank white page. The HDD light indicator does not show much activity.
-
On the fog server, the php5-fpm service is not running. could this be the issue below?
From another machine this is what i get. A PHP error?
-
@cojohnson If you are getting a white (blank) page any time you interact with the fog management GUI then the apache web server has had an error in the php code. Please review the apache error log (for rhel based systems) /var/log/http/error_log for debian based systems (guess) /var/log/apache2/error.log?
-
also ensure the db is running.
-
I could not figure it out. Consequently, I reinstalled ubuntu on the master. Is there any way to either transfer the images from one of the Storage nodes back to the master or Turn a storage node into the master?
-
@cojohnson The easiest method is to just use scp and copy them back to the master node. DON"T make the slave node a slave node to the (blank) master node first or all of your images will be gone.
Once you have all of the images back on the master node, you will have to manually create the image definitions in the database. (another option would have been to export the image defintions before you rebuilt the master node).
-
After a fresh install of ubuntu, I updated ubuntu then i proceeded by installing fog as a normal server by using the commands
sudo apt-get update && apt-get install git
sudo -i
git clone https://github.com/FOGProject/fogproject.git /root/fogproject
cd /root/fogproject/bin
./installfog.shAccording to Upgrade to trunk
Now, i am still getting that same “500” error when trying to access it via a web browser. What is going on??!!??
-
@cojohnson Anything in the apache error log? /var/log/apache2/error.log
-
sounds like an IP conflict.
-
Sorry, Sebastian. Right after the error occured I reinstalled the OS again. This time I put on FOG 1.2.0 first and then upgraded to Trunk 7254. The basic fog server is working now.
All i have left to do is move the images that i copied off of one of the Storage Nodes /images/ directory to the Servers Image directory and then attach my storage nodes. Correct?
-
@cojohnson and re-creating your image definitions.
For future record, blasting and reinstalling in the future will leave all fog clients in your environment uncontrolled, because the fog server’s certificate would have been reset. There are steps on how to migrate the certs to a new server in the wiki, here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client
-
@cojohnson You have a very unique troubleshooting style.
