Posts made by msi

@sebastian-roth Because I am seeing below graph even after replication

Hi!
I am keep getting below error. Not sure if it is good or bad:
[10-09-17 9:51:58 pm] | CMD:
lftp -e ‘set xfer:log 1; set xfer:log-file “/opt/fog/log/fogreplicator…transfer.NJED45.log”;set ftp:li
st-options -a;set net:max-retries 10;set net:timeout 30; mirror -c -r -R --ignore-time -vvv --exclude “.srvprivate” “/images/d
ev/postinitscripts” “/images/dev/postinitscripts”; exit’ -u fog,[Protected] 192.168.134.230

@wayne-workman @george1421 I just thought, since we already have a database for list of host, why not add another column for asset tag. It is not for registering the device with the fog. However, it isn’t a bad idea. I am sorry if I offended you @Sebastian-Roth . It is already an awesome software, just thought it could serve both purpose. It is just an idea.

Is it possible to convert fog web management address from IP based to a valid name. So that instead of going to http://192.168.1.1/fog/management, we can go to http://intranet.myfogserver.com?
This is just an idea as it will helpful for business organization.

Is it possible to add a barcode feature for each individual hosts? So that we can print it using Zebra label maker to stick it 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.

@george1421 Correct. pointing to 192.168.134.230

@george1421 Trying to PXE boot at the remote site. Below is the settings from /opt/fog/.fogsettings:

Install time: Fri 06 Oct 2017 02:51:32 PM EDT

ipaddress=‘192.168.134.230’
copybackold=‘0’
interface=‘bond0’
submask=‘255.255.255.0’
routeraddress=‘’
plainrouter=‘’
dnsaddress=‘’
username=‘fog’
password=‘rqx9gmtivQyiLLA3sn70T0El1iXdr3V59kX/boTCgUs=’
osid=‘1’
osname=‘Redhat’
dodhcp=‘’
bldhcp=‘’
dhcpd=‘dhcpd’
blexports=‘1’
installtype=‘S’
snmysqluser=‘fogstorage’
snmysqlpass=‘fs13096747298’
snmysqlhost=‘192.168.1.230’
installlang=‘0’
storageLocation=‘/images’
fogupdateloaded=1
docroot=‘/var/www/html/’
webroot=‘/fog/’
caCreated=‘yes’
startrange=‘’
endrange=‘’
bootfilename=‘undionly.kpxe’
packages=‘bc curl gcc gcc-c++ gzip httpd lftp m4 make mariadb mariadb-server mod_ssl net-tools nfs-utils php php-bcmath php-cli php-common php-fpm php-gd php-ldap php-mbstring php-mcrypt php-mysqlnd php-process tar tftp-server unzip vsftpd wget xinetd ’
noTftpBuild=’’
notpxedefaultfile=‘’
sslpath=‘/opt/fog/snapins/ssl/’
backupPath=‘/home/’
php_ver=‘’
php_verAdds=‘’
sslprivkey=‘/opt/fog/snapins/ssl//.srvprivate.key’

@george1421 yes! option 67 is ipxe.efi. FYI: Main Fog server is a Hyper-V

@wayne-workman I think, I would rather create a storage group and assign the storage node under that group. According to your video tutorial, it shouldn’t replicate it.

Hi!
Just got below error after installing a main fog server and a storage node. Both of these are located different geographic locations. I also installed the location plugin.
NBP filesize is 0 Bytes
PXE-E23: Client Received TFTP error from server

@george1421 I just want send two that is corresponds to that particular branch. Can you give me one example of Cron task in this case?

@george1421 Also, how can I start replication time and image at my choice? For example, I have 12 images but I want to replicate only two of them to a particular storage node at night time. So that I don’t disturb the day time traffic.

Sorry that I am asking too many question, but I have to answer to my boss.

@george1421 @Wayne-Workman Yes, I have. George helped with that before. I am kind of suspecting the switch. I noticed those are catalyst 2950 switch. Speed is 10/100 Mbps

@george1421 yes to first two question. Not sure what do you mean by adding a target computer to a location.

@george1421 @Sebastian-Roth You understood me right. What if the master node went down for some odd reason, can we still be able to deploy from the branch storage node? Another scenario is that I have a main machine in Newark city , and my storage is at Elizabeth city. The locations are connected through MPLS. When I deployed a machine at Elizabeth, it took an hour to deploy. However, when I did it at Newark where main FOG machine is, it took only half an hour with the same image. Is there a network issue here? DHCP at Newark pointing to Newark Fog machine, and Elizabeth pointing to Elizabeth node as below:
Newark: next-server 200.134.200.230
bootfile ipxe.efi
Elizabeth: next-server 200.135.200.230
bootfile ipxe.efi

Hi!
How can I achieve below scenario? all of those beta and alpha node would branches at different states. Alpha and Beta would divide all US locations into two group.

@wayne-workman jus perform the reset encryption procedure. I had the same problem. Than I remove and reinstalled the client. Now its working.

@wayne-workman Just tried, it works! thanks

@wayne-workman Below is the error I am getting it on client.