Install hangs at "Ensuring node username and passwords match"
-
@george1421 Things seem to be running well now. Thank you so much for your help! I am going to go back read the docs for adding a storage node and attempt to attach a clean install of a storage node to my working primary installation. Should I mark this thread resolved and start a new one if I have an issue with the storage node? Or, perhaps you/moderator mark as resolved? I don’t see that option. Thanks again!
-
@mpmackenna Lets keep working through on this one.
Now when/if you have a storage node. If you are going to change modes on that Normal Node -> Storage Node. You need to delete the /opt/fog/.fogsettings file. Understand when you do that you may have issues with the local linux
foguser accont. The fog installer script should keep everything sane, but if things go wrong then you have a place to look.Also you will need to make the edits to the www.conf file on every storage node too. Also you will need to downgrade the FOS kernel. I know its a pain, but it is what we have until 1.5.5 is released.
You can copy from your master node to the storage nodes. The files are in /var/www/html/fog/service/ipxe You can use scp to copy and the files you need to copy are bzImage and bzImage32 to all of your storage nodes in the same location.
-
@george1421 said in Install hangs at "Ensuring node username and passwords match":
To see if php-fpm is hooked into apache correctly, launch top from the linux console. Then sort by CPU usage by keying in P. The top 2 or 3 processes should be php-fpm. If it is apache then something isn’t hooked correctly.
I checked this and it seems to be correct. Top processes are php-fpm7.1. Thanks!
-
@george1421 said in Install hangs at "Ensuring node username and passwords match":
@mpmackenna Lets keep working through on this one.
Now when/if you have a storage node. If you are going to change modes on that Normal Node -> Storage Node. You need to delete the /opt/fog/.fogsettings file. Understand when you do that you may have issues with the local linux
foguser accont. The fog installer script should keep everything sane, but if things go wrong then you have a place to look.Also you will need to make the edits to the www.conf file on every storage node too. Also you will need to downgrade the FOS kernel. I know its a pain, but it is what we have until 1.5.5 is released.
You can copy from your master node to the storage nodes. The files are in /var/www/html/fog/service/ipxe You can use scp to copy and the files you need to copy are bzImage and bzImage32 to all of your storage nodes in the same location.
That sounds great! I am going to run the installer on my Storage Node. This server will be the Normal/Master install. I will make the edits listed and let you know how it goes. Thank you!
-
@george1421 I followed your instructions and the new Storage Node seems to be working. I put them in the same storage group and I am replicating the images to the new node. Thank you for your help!
-
@george1421 I checked my storage node this morning and it appears some of my images did not sync. I have a number of them that did but there are definitely some that are missing. Syncing has stopped so it’s not matter of not enough time to sync. Can you point me to a document or offer assistance as to how I can troubleshoot this issue? My first thought was to just use rsync but I am concerned that perhaps there are files in the folder that are supposed to differ between a master node in a storage group and a slave node in the same group? Thank you!
-
@mpmackenna If there is an image definition for the image and its set to replicate, then it should replicate for you. You CAN use rsync if you want to seed the remote repository.
There are replication log files in /opt/fog/log that might give you a clue to why certain images were skipped.
IMO rsync might be a better tool for FOG to use in the future for moving files than its current replication method. But that’s not up to me to decide.
-
@george1421 Use to be all the FOG services were listed with a “service --status-all” command with previous versions of FOG, but now I don’t see them. If I want to stop the replication service while I run rsync how would I do that? Thank you!
-
@mpmackenna If you have a systemd based system then its.
sudo systemctl stop FOGImageReplicatorIf you have a systemv based system its
sudo system FOGImageReplicator stop -
@george1421 Got it. I am on a systemd based system. I am still getting used to systemd. Why would services that are listed in systemd not be listed under the output of the services command (not really asking, I can Google that on my own)? Just venting as I continue to relearn all that I thought I knew about Linux. Thanks again! Don’t think I ever would have got this sorted out without your help.
-
@george1421 I replicated my images using rsync and verified that all images are in both locations. I also have a backup of my images off of both of the nodes. I went in and I created a new Storage Group. I associated the Storage Node that is not the Master Server with the new Storage Group. I then associated a number of my images with that Storage Group. My goal is to have some images only reside on the node in the new Storage Group and some only reside on the other Storage Group. I set both servers to be the Master Node for their Storage Group. Based on the warning I read about setting a server to the Master Node I half-way expected for any images that were not associated with that Storage Group to be purged from the Master Node but that didn’t seem to happen, which is fine. Is it now safe to go back and purge images from servers via cli if they reside in an image store on a node that is not in the Storage Group that is associated with that image? Thank you!