I have a fog server which was installed as default with image stored in a local mount (from an iSCSI link).
I wanted to move the images from the server to a storage node.

So I built a storage node, unmounted images LUN from the server and mounted it on the storage node.

I wanted to move the images from the storage node to another using the WebUI and it does not seem to be possible.
So I exported image infos for a specific image. tried to reimport it, but storage info remain the same.
So I delete it again and recreated the image manually.
Using exactly the same parameters but the storage node. (choosing the new one)

unfortunately this did not worked either always getting this error :

Could not mount images folder (/bin/fog.download)

On another hand I can create new image and deploy them without any issue. (they are stored on the new storage)

I tried the plugin location the enforce the use of the new storage node on my test PC but it did not helped.
Any idea of what could be my problem?

@george1421

Thanks, I’ll give a look at it this weekend.

@george1421

I have only one capture on the branch with which we are doing tests, we will see if the image is deleted or not.
Do you know if it’s possible to schedule replications at specific times? because we have about 2.5To to sync and I would like to do it on night shifts.

@george1421

I read that putting a node as master with empty storage could wipe all nodes in this storage group. does this mean that a new capture should only be done on master storage node otherwise it will be erased on the node where it has been created?

@george1421

Forget it was a right issue on branch server.

@george1421
Hi,
This seems to be the best for our case. I did what you suggested but something is not working as expected.
I configured a new node on default storage group on main server.

This how configured it :

• ip : ip of the branch server
• image path : /mnt/FOG same as it is configured on the branch server
• ftp path : same
• interface : ens160 (outgoing interface of the main server)
• management username : fogproject
• management password : same as it is configured on branch server.

All other settings left as default.

On the branch server default storage node : master is now unchecked.

I can see the new storage on main server dashboard with space available.

But the replication is not working as expected this is what I can see in the logs :

[06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.mbr (FR3-FOG-01)
[06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.minimum.partitions (FR3-FOG-01)
[06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.original.fstypes (FR3-FOG-01)
[06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.original.swapuuids (FR3-FOG-01)
[06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1.partitions (FR3-FOG-01)
[06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1p1.img (FR3-FOG-01)
[06-18-19 9:09:06 pm] # W10_Remote-20190523-HS-745-755: File does not exist d1p2.img (FR3-FOG-01)
[06-18-19 9:09:06 pm] | CMD: lftp -e 'set xfer:log 1; set xfer:log-file /opt/fog/log/fogreplicator.W10_Remote-20190523-HS-745-755.transfer.FR3-FOG-01.log;set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; mirror -c --parallel=20 -R --ignore-time -vvv --exclude ".srvprivate" "/mnt/linux_iSCSI/FOG/W10_Remote-20190523" "/mnt/FOG/W10_Remote-20190523"; exit' -u fogproject,[Protected] 10.69.0.11
[06-18-19 9:09:06 pm] | Started sync for Image W10_Remote-20190523-HS-745-755 - Resource id #93271
[06-18-19 9:09:06 pm] * Found Image to transfer to 1 node

Any idea of what is going wrong?

@Junkhacker @george1421

Thank you both for your answers.
Sorry if it’s a silly question but would it be possible to configure a normal server as a storage node?
If yes is there any advantage in doing this?
Or : having a normal server on each site, syncing them out of FOG services and export/import images using web ui is the best solution for us?

Hi,

I’m using FOG on our main site for few weeks now. We are very confident about the potential of the service, that’s why we are thinking how to deploy it correctly on our branches offices.

So we have a main site and 2 or more branches. Is there a way for us :

• to pilot everything from the main site.
• to make the deploy done by local nodes.
• to have a local management server for branch offices in case of cut with HQ site.

Thanks by advance.

Proc.

@Quazz
My setup is now updated from 1.5.5 to 1.5.6.
It’s very strange, once created, some are now belonging to fogproject:root and other to root:root.
And no matter whom they belong to, a delete through the webui does not remove them from the drive.

Any Idea?

@Sebastian-Roth

Hi,

Thanks works better with TCP port 445. I was referring this wiki :

https://wiki.fogproject.org/wiki/index.php/Troubleshooting_Host_Management_Showing_Hosts_as_Down

It’s solved.

Hi Sebastian,

I have about 300 hosts.

Hi,

I’m using a fog upgraded from 1.5.5 to 1.5.6 on a Ubuntu 16.04.

All my machines in hosts management appear with a red dot.
Before today the DNS which FOG refers did not had any register for my machines.
Today I corrected this. Now I can see all hosts on my DNS, and a ping from the FOG server show me that the machines names are well resolved.

I made a snapin that open ICMPv4 and UDP port 7 inbound on each machines.

the command :

systemctl -l status FOGPingHosts

output this :

● FOGPingHosts.service - FOGPingHosts
   Loaded: loaded (/lib/systemd/system/FOGPingHosts.service; enabled; vendor preset: enabled)
   Active: active (running) since mar. 2019-05-28 16:31:04 CEST; 3h 29min ago
 Main PID: 2027 (FOGPingHosts)
    Tasks: 2
   Memory: 16.3M
      CPU: 16.586s
   CGroup: /system.slice/FOGPingHosts.service
           ├─2027 /usr/bin/php -q /opt/fog/service/FOGPingHosts/FOGPingHosts &
           └─2066 /usr/bin/php -q /opt/fog/service/FOGPingHosts/FOGPingHosts &

mai 28 16:31:04 FR2-FOG-01 systemd[1]: Started FOGPingHosts.

What could be wrong and what should I do? At which frequency the fog server check the existence of the hosts?

Many thanks by advance.

Proc.

Hi,

I’m using FOG server 1.5.5 on ubunbtu 16.04.
My storage is made of iSCSI LUNS.

I can create image without any issue but deleting them via the webUI won’t delete them on the filesystem.

I found this in the apache log, but not sure it’ll help :

[Thu May 23 09:13:45.814151 2019] [proxy_fcgi:error] [pid 29322] [client 10.33.0.63:32884] AH01071: Got error 'PHP message: PHP Warning:  trim() expects parameter 1 to be string, array given in /var/www/html/fog/lib/fog/fogbase.class.php on line 1382\n', referer: http://10.33.0.11/fog/management/index.php?node=image&sub=deletemulti

Another strange thing :

the images folder are sometimes own by fog:root, 1002:root or root:root.
The folder containing all other images folder belong to 1002:root.

I suppose my problem is a owner issue, so what should be the right owner.

@Sebastian-Roth

I did not found the option in FOG configuration -> fog settings , but I just found the faulty host had as primary MAC the Windows vNIC mac. I put the MAC of the physical NIC as primary and then everything back to normal.

I don’t have a idea to make the research better as I just had to search in the host section of FOG the MAC addresses found in the client log to see what was going on.

Ok,
I guess I found what happened. A windows virtual interface present in a Win10 master image with the same mac as a physical interface on another host.
I don’t even now how it could happen.

But the mac of the virtual in do not appear in the DB that’s why I did no saw it in it.
Disable the interface in the host seem to solve the situation.

I guess this case is clear now.

Do you know if it’s possible the client to use only physical interface and not the virtuals ?

@Sebastian-Roth

Ok So I re-read it carefully. I was pretty sure of the result but the command (with the right MAC) gave only 1 row so I guess there is no duplicates for the 2 tested PC :

SELECT hmHostID FROM hostMAC where hmMAC IN (‘b8:70:f4:c3:4d:7f’,‘e0:ca:94:1e:3a:7e’);

I take any other idea.

I also already read this post : https://forums.fogproject.org/topic/11382/http-500-internal-server-error/4 and tried to relaunch the installer but the problem remains.

Just for info, this is what I get in the client fog log :

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 19/05/2019 21:42 Client-Info Client Version: 0.11.16
 19/05/2019 21:42 Client-Info Client OS:      Windows
 19/05/2019 21:42 Client-Info Server Version: 1.5.5
 19/05/2019 21:42 Middleware::Response ERROR: Unable to get subsection
 19/05/2019 21:42 Middleware::Response ERROR: La référence d'objet n'est pas définie à une instance d'un objet.
 19/05/2019 21:42 Service Sleeping for 70 seconds
 19/05/2019 21:43 Middleware::Communication URL: http://10.33.0.11/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 19/05/2019 21:43 Middleware::Response Success
 19/05/2019 21:43 Middleware::Communication URL: http://10.33.0.11/fog/management/index.php?sub=requestClientInfo&mac=00:FF:5D:1A:66:B7|00:50:66:AF:33:17|00:50:77:C0:00:01|00:50:65:C0:00:08||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
 19/05/2019 21:43 Middleware::Communication ERROR: Could not contact FOG server
 19/05/2019 21:43 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (500) Erreur interne du serveur.
 19/05/2019 21:43 Middleware::Response Success
 19/05/2019 21:43 Middleware::Communication URL: http://10.33.0.11/fog/service/getversion.php?clientver&newService&json
 19/05/2019 21:43 Middleware::Communication URL: http://10.33.0.11/fog/service/getversion.php?newService&json

 19/05/2019 21:43 Service Creating user agent cache
 19/05/2019 21:43 Middleware::Response ERROR: Unable to get subsection
 19/05/2019 21:43 Middleware::Response ERROR: La référence d'objet n'est pas définie à une instance d'un objet.
 19/05/2019 21:43 Middleware::Response ERROR: Unable to get subsection
 19/05/2019 21:43 Middleware::Response ERROR: La référence d'objet n'est pas définie à une instance d'un objet.
 19/05/2019 21:43 Middleware::Response ERROR: Unable to get subsection
 19/05/2019 21:43 Middleware::Response ERROR: La référence d'objet n'est pas définie à une instance d'un objet.

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 19/05/2019 21:43 Client-Info Client Version: 0.11.16
 19/05/2019 21:43 Client-Info Client OS:      Windows
 19/05/2019 21:43 Client-Info Server Version: 1.5.5
 19/05/2019 21:43 Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 19/05/2019 21:43 Client-Info Client Version: 0.11.16
 19/05/2019 21:43 Client-Info Client OS:      Windows
 19/05/2019 21:43 Client-Info Server Version: 1.5.5
 19/05/2019 21:43 Middleware::Response ERROR: Unable to get subsection
 19/05/2019 21:43 Middleware::Response ERROR: La référence d'objet n'est pas définie à une instance d'un objet.

Hi,

Thank you for your answer. I guess I already read it. I’ll look a it more closely.
I also ran this in mysql :

SELECT * FROM `hostMAC` WHERE `hmMAC` IN (SELECT `hmMAC` FROM `hostMAC` GROUP BY `hmMAC` HAVING COUNT(`hmMAC`) > 1);

And I see no duplicates. What is weird is it’s not one pc that is impacted but the all the PCs.

I ran the Database Maintenance Commands seen in the wiki but it did not helped either.

For info I don’t think it’s related to my images move as they are now back to their legacy drive and the problem remains. But I had a doubt as it appear when I changed the default storage.

I’ll check the recommended post and tell you if it helped.

Thanks Proc.

Hi,

I’m using FOG 1.5.5 on Ubuntu 16.04.

Till now everything worked well. I don’t know if it’s related but yesterday I had to change the storage location.
This is how I did it :

-Mount my new drive
-Format as ext4
-Copied everything from my old to my new drive.
-set the new path in Storage>default member
-edited storagelocation in /opt/fog/.fogsettings
-edited /etc/exports and run exportfs -ra

I can deploy and capture without any issue but now client plugin is not working anymore on all of my host.
I’m unable the reboot the machines or run any snapins.
Get several errors :

On the client :
17/05/2019 10:47 Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&mac= …

-But then Could not contact server.
-Internal error (500)
-unable to get subsection

in apache

[Fri May 17 10:44:47.951092 2019] [proxy_fcgi:error] [pid 18681] [client 10.33.136.155:57557] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught Exception: Error multiple hosts returned for list of mac addresses in /var/www/html/fog/lib/fog/hostmanager.class.php:209\nStack trace:\n#0 /var/www/html/fog/lib/fog/fogbase.class.php(571): HostManager->getHostByMacAddresses(Array)\n#1 /var/www/html/fog/lib/client/registerclient.class.php(46): FOGBase::getHostItem(true, false, false, true)\n#2 /var/www/html/fog/lib/fog/fogpage.class.php(3013): RegisterClient->json()\n#3 /var/www/html/fog/lib/fog/fogpage.class.php(249): FOGPage->requestClientInfo()\n#4 /var/www/html/fog/lib/pages/dashboardpage.class.php(76): FOGPage->__construct('Dashboard')\n#5 /var/www/html/fog/lib/fog/loadglobals.class.php(64): DashboardPage->__construct()\n#6 /var/www/html/fog/lib/fog/loadglobals.class.php(78): LoadGlobals::_init()\n#7 /var/www/html/fog/commons/base.inc.php(49): LoadGlobals->__construct()\n#8 /var/www/html/fog/management/index.php(22): require('/var/www/html/f...')\n#9 {main}\n  thrown in /var/www/html/fog/lib/fog/hostmanager.class.php on li...\n'

Many thanks by advance for any help.

@Sebastian-Roth

Hi Sebastien, I just did the test again and put the new ini files create the FTP error and put back the original 1.5.5 ini file correct it.

So you confirm the 1.5.6 include the fix? then I should just upgrade from 1.5.5 to 1.5.6, no?

Proc

@Sebastian-Roth
Hi Sebastien,

I’m using FOG 1.5.5 with init files included with it.
As suggested in a previous post (https://forums.fogproject.org/post/123192), I backed up init files stored in /var/www/html/fog/service/ipxe/ and put instead the last ini files.

I had the behavior described : shrinking OK but FTP error then. I put back the 1.5.5 ini files and then everything worked back. It’s may be just a coincidence I can try again.