@msi I am wondering why you have two IP addresses within the same subnet assigned to your FOG server? Any good reason to do this?

I also noticed that it is using enp0s31f6 IP address instead of p2p3 IP (192.168.1.230). is it normal since both IP’s are working when accessing the web console?

FOS uses the IP set as FOG_WEB_HOST (FOG Configuration) to call out to the FOG webserver. I suppose you have set 192.168.1.230 in that field, right? That shouldn’t matter from my point of view.

If you have checked all the passwords and resynced as described by George I may ask you to do a simple FTP test: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@msi Just to let you know, we have worked on the replication code and fixed a couple of issues. The new release is on the door step and should work fairly well.

We’ll put that into the release notes as well but just to let you know beforehand:
Nodes being on different versions (1.5.4 vs. 1.5.5) will replicate images over and over again as some of the hashing code needed to be changed. Therefore we advise you to update all nodes in one go! Please make sure you stop replication on the master first (systemctl stop FOGImageReplicator), then update the storage node(s) and then update master node as a last step.

@msi said in 503 Service Unavailable:

didn’t change routeraddress, plainrouter, and dns address.

Those settings only affect DHCP on the fog server (If you’re using fog for DHCP). They would not affect web gui operation.

@sebastian-roth I disabled legacy. It works. thanks.

@msi Never mind. After I re-ran the installation from the Git. Problem solved.

@tom-elliott said in Can't login to FOG web Interface:

@msi when you login guess what page it automatically takes you too?

Hi,
Make sense… Please close the discussion with satisfaction. Just to recap, below solved the problem for now. Hopefully, newer version will solve all the problem, including delays.
@msi said in Can't login to FOG web Interface:

[root@caor-fogmain ~]#sudo -i [root@caor-fogmain ~]#yum -y install git [root@caor-fogmain ~]# sudo -i [root@caor-fogmain ~]# cd /root [root@caor-fogmain ~]# git clone https://github.com/FOGProject/fogproject.git [root@caor-fogmain ~]# cd fogproject/ [root@caor-fogmain fogproject]# git checkout working-1.5.1 Branch working-1.5.1 set up to track remote branch working-1.5.1 from origin. Switched to a new branch 'working-1.5.1' [root@caor-fogmain fogproject]# git pull Already up-to-date. [root@caor-fogmain fogproject]# cd bin/ [root@caor-fogmain bin]# ./installfog.sh -y

@msi Shouldn’t be. However you should backup your systems before changes simply as good practice.

@wayne-workman it’s alright… Close this one please. Thanks.

@msi said in Snapin not running:

I checked the port 445. its open.

Then it’s likely just a DNS configuration issue: if the FOG server can’t resolve hostnames, then it can’t ping them. If you’d like help with that please open a new thread, though this is ultimately not a FOG issue, so it may be best to search other resources on how to configure DNS (assuming this is the issue).

@wayne-workman said in Image not syncing:

As far as the “error contacting server” message, can you visit https://sourceforge.net/ at your work? If not, that’s probably why.

I can access it on my network. I have perform below command in order to try and fix the syncing issue. Than I re-ran the fog installtion file to re-install. When I was checking the master fog storage under storage. I noticed password for the user fog was simply password and wasn’t matching the password in the .fogsettings file.

sudo mv /opt/fog/.fogsettings /opt/fog/fogsettings-firstInstall

@msi said in Image capture task did not complete:

By the way, love the new look on the FOG

@Joe-Schmitt

@wayne-workman It’s working

Look at these threads:

https://forums.fogproject.org/topic/9624/control-access-plugin/7 https://forums.fogproject.org/topic/10918/access-control-plugin

@george1421 Same problem.
0_1518010916911_fog.jpg

@wayne-workman said in Image not syncing between nodes:

If you run this command from your Master Node, it will prompt you for the storage node’s local fog user’s password. You can find that in that node’s storage management area or from this file on it: /opt/fog/.fogsettings

rsync <options> <source> <destination>

rsync -r --bwlimit=6250 fog@10.134.200.230:/images/Laptop2.1 /images rsync -r --bwlimit=6250 fog@10.134.200.230:/images/Laptop /images

The 6250 is supposed to be 6250Kbps, or 50Mbps. If you want slower, you can do the math to figure out what you need with the calculator I reference below.

It took some times but it is working after issuing the rsync command. I had to delete the image from the NJED node after rsync completion.

@wayne-workman Correct… Thanks for your help

@george1421 it looks like replication activity has stopped as I don’t see any movement on the graph. I have another imaging to do next week. I will try to stopping it to test your theory.

@msi Well, this has nothing to do with FOG in general. Tell your DNS admins to add entries for the IP to name resolution within your local network and you will be able to use the name instead of IP for the web management. Though the clients will still use the IP but that doesn’t matter to you I reckon.

@Sebastian-Roth I wanted to put my 2 cents on generating barcodes for individual hosts. It’s definitely possible to add a barcode feature for each host, which could be printed using a Zebra label maker and stuck on the PCs.

@george1421 Good News! I got it to work. I noticed that I got bunch of alert about some host is trying to access the tftpd and httpd service. It was the firewall. At the beginning, while I was setting up the node, I typed systemctl stop firewalld; while I should have typed systemstl disable firewalld since I rebooted once.