Posts made by FallingWax

Running Version 1.3.4
SVN Revision: 6066

I have been dealing with issues with the Image Replication process blowing up my networks. I have a large number of images that need to transfer down to two storage nodes. I gave up on the one and brought it back in house from the remote location and synced up the images. The other unit I have is set with most of the images but around 100 GB of image data still needs to transfer across the net. Whenever the replication service starts it goes full bore and wrecks the local network to the point that its unusable. I want to configure image replication to only run between 5 pm and 8 am. I think i figured this part out but my question is in the behavior of the service. If the service stops mid transfer of an image when it starts up again, does it continue where it left off? From what i can tell, it does not. It sees that something did not complete, deletes it from the node and starts over again. If some can clarify the process it would be make this set up easier to solve.

In addition to this, am I correct that this process is done strictly through ftp? I can change the QoS on my firewall to throttle down traffic on a specific port but I am using 21 for other applicationa as well. If i change the default ftp port in the GUI do I need to change it anywhere else? That would solve my issue as well.

Any help is appreciated.

Thanks!

@Raymond-Bell It was permissions issue. I thought i had everything set properly but these two changes fixed the issue.

chown -R fog:root /images
chmod -R 777 /images

I got this figured out. Found another post with the same issue…

@Raymond-Bell I removed the protection but still no good. These images do not exist on node now.

Running Version 1.3.4
SVN Revision: 6066

Just re-added a storage node and replication is not working. I am seeing the following in the image replication log and I am not sure what its pointing too. Other storage node is working and replicating fine. I know the ftp password is good as I was able to use filezilla to connect. Reset permissions on the /images folder and double checked the fogstorage password. Any help would be appreciated.

[02-02-17 6:35:23 pm] * Deleting remote file: /images/Dell7040Win10x64/d1.mbr
[02-02-17 6:35:23 pm] | Files do not match.
mirror: Access failed: 550 Failed to change directory. (/images/Dell_7040_Win10x64_Update)
[02-02-17 6:35:22 pm] | Image Name: Dell_7040_Win10_x64
[02-02-17 6:35:22 pm] * Found Image to transfer to 1 node
[02-02-17 6:35:22 pm] * Started sync for Image Dell_7040_Win10x64_Update
lftp -e ‘set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-rate 0:64000; mirror -c -R --ignore-time -vvv --exclude “dev/” --exclude “ssl/” --exclude “CA” --delete-first ‘/images/Dell_7040_Win10x64_Update’ ‘’/images/Dell_7040_Win10x64_Update’‘; exit’ -u fog,[Protected] 192.168.3.109
[02-02-17 6:35:22 pm] | CMD:
[02-02-17 6:35:22 pm] * Starting Sync Actions
mirror: Access failed: 550 Failed to change directory. (/images/Dell_3040_Win7_x64_Update)
[02-02-17 6:35:20 pm] | Image Name: Dell_7040_Win10x64_Update
[02-02-17 6:35:20 pm] * Found Image to transfer to 1 node
[02-02-17 6:35:20 pm] * Started sync for Image Dell_3040_Win7_x64_Update
lftp -e ‘set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-rate 0:64000; mirror -c -R --ignore-time -vvv --exclude “dev/” --exclude “ssl/” --exclude “CA” --delete-first ‘/images/Dell_3040_Win7_x64_Update’ ‘’/images/Dell_3040_Win7_x64_Update’‘; exit’ -u fog,[Protected] 192.168.3.109
[02-02-17 6:35:20 pm] | CMD:
[02-02-17 6:35:20 pm] * Starting Sync Actions
mirror: Access failed: 550 Failed to change directory. (/images/Dell_3040_Win7_x64)
[02-02-17 6:35:19 pm] | Image Name: Dell_3040_Win7_x64_Update
[02-02-17 6:35:19 pm] * Found Image to transfer to 1 node
[02-02-17 6:35:19 pm] * Started sync for Image Dell_3040_Win7_x64
lftp -e ‘set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-rate 0:64000; mirror -c -R --ignore-time -vvv --exclude “dev/” --exclude “ssl/” --exclude “CA” --delete-first ‘/images/Dell_3040_Win7_x64’ ‘’/images/Dell_3040_Win7_x64’‘; exit’ -u fog,[Protected] 192.168.3.109
[02-02-17 6:35:19 pm] | CMD:
[02-02-17 6:35:19 pm] * Starting Sync Actions
mirror: Access failed: 550 Failed to change directory. (/images/Dell_3040_Win10_x64)
[02-02-17 6:35:17 pm] | Image Name: Dell_3040_Win7_x64
[02-02-17 6:35:17 pm] * Found Image to transfer to 1 node
[02-02-17 6:35:17 pm] * Started sync for Image Dell_3040_Win10_x64
lftp -e ‘set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-rate 0:64000; mirror -c -R --ignore-time -vvv --exclude “dev/” --exclude “ssl/” --exclude “CA” --delete-first ‘/images/Dell_3040_Win10_x64’ ‘’/images/Dell_3040_Win10_x64’‘; exit’ -u fog,[Protected] 192.168.3.109
[02-02-17 6:35:17 pm] | CMD:

@Wayne-Workman Thanks! That cleared it up.

Running Version 1.3.0
SVN Revision: 6050

Dashboard has been stuck showing 4 active tasks and 1 queued for a few weeks now. Even with no running or scheduled tasks the dashboard view does not update. Any way to refresh this?

Looks like i found three images that don’t finish replicating or don’t replicate properly and are consistently writing/deleting over and over. Those images work correctly on the Main machine so I would hesitate to remove them.

This is what i see in the log

| Image Name: Dell_7040_Win10_x64
[01-06-17 5:48:56 pm] | Dell_7040_Win10_x64: No need to sync d1.mbr file to 19$
[01-06-17 5:48:56 pm] | Dell_7040_Win10_x64: No need to sync d1.partitions fil$
[01-06-17 5:48:56 pm] | Dell_7040_Win10_x64: No need to sync d1p1.ebr file to $
[01-06-17 5:48:57 pm] | Dell_7040_Win10_x64: No need to sync d1p2.img file to $
[01-06-17 5:48:57 pm] | Files do not match.
[01-06-17 5:48:57 pm] * Deleting remote file: /images/Dell7040Win10x64/d1p3.img
[01-06-17 5:48:58 pm] | Files do not match.
[01-06-17 5:48:58 pm] * Deleting remote file: /images/Dell7040Win10x64/d1p4.img
[01-06-17 5:48:58 pm] | Dell_7040_Win10_x64: No need to sync d1p5.ebr file to $
[01-06-17 5:48:59 pm] | Dell_7040_Win10_x64: No need to sync d1p5.img file to $
[01-06-17 5:48:59 pm] * Starting Sync Actions
[01-06-17 5:48:59 pm] | CMD:
lftp -e 'set ftp:list-options -a;set net:max-retries 10$

@Tom-Elliott said in Can not Register Host at remote location:

I am wondering the same thing, but it looks like they are communicating at least on some level. I am going to look through the firewall logs a little further. Is there any logging in FOG that might help indicate an issue?

@Tom-Elliott Is there any logging that i might look at for the Image Replicator to see if that is what is happening?

@Tom-Elliott said in Can not Register Host at remote location:

We are using the location plugin and the node does see the main server, as far as i can tell. Image replication worked so I assume communication is ok.

Running Version 1.3.0
SVN Revision: 6050

While I was troubleshooting some network speed issues came across this error in the wireshark:

[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]

This was communication between my main fog and a storage node. I went and looked at the image files and it looks like they are rewriting the same images. I haven’t created anything new but the date on the images has changed everyday. This is crushing my network speeds so badly I have stop the ImageReplicator service, which immediately fixed the problem. Any help would be appreciated!

Thanks

using dnsmasq on the storage node and the main. dnsmasq on the storage node is pointing to the node for the boot file.

Running Version 1.3.0
SVN Revision: 6050

Attempting to register a new host at remote location. Have a storage node at location, using location plugin, and all images replicated perfectly to storage node. However, when trying to register host its goes to:

• Starting Boot registration
  An error has been detected.
  Unable to register host (/bin/fog.man.reg)
  Args Passed:

I have looked at everything i can think of and can’t come up with a fix. Any help would be appreciated. Host register fine at the main location. I thought networking but communication is good with image replication so i am a little lost as to what else to check.

Thanks,

1.3.0-RC-33

Storage Node appears to have a corrupted image. Is there an easy way to delete that image on the Node and replicate it again?

@Wayne-Workman Thanks! I ended up needing rename /opt/fog/.fogsettings and run the installer fresh but it was able to update successfully.

@Wayne-Workman I am trying to update from RC-17 to the newest.

FOG Version
1.3.0-RC-17

OS
Ubuntu 16.04

I have a storage node that I am trying to update trunk version on and it stops at * Adding needed repository. Internet is good and I was able to update the master from the same version/same os this morning. I looked at the error_logs and the thing i see that looks off is this line.

Cannot add PPA: ‘ppa:~ondrej/ubuntu/php-7.0’.
The user named ‘~ondrej’ has no PPA named ‘ubuntu/php-7.0’

I remember having some issues with this machine during the initial update to 16.04 but it was all working fine.

Any help would be appreciated

@Wayne-Workman Thanks for your responses! I have a working environment set up now. We may have some leg work to do to get to more ideal environment for our business, but I got everything working for our current needs. Abandoning the notion of dual nic’s was all i needed to do. We will probably work with the vlans to make it separate network sub but for now all is well.

@Wayne-Workman ideally I don’t want to run imaging tasks on my main network. 192.168.0.0/24 is main at HQ and 192.168.5.0/24 is main at remote. At each location I want to have these two on let’s say a 192.168.6.0/24 remote and 192.168.1.0/24 main. This way all clients connect and image on the secondary network only really want the internal (main) for communication between nodes. What have other people set up to do remote offices? I am imagine if I run dnsmasq (already have dhcp for main networks) and just run imaging on the main networks everything will work but this is not ideal. Our dhcp is maxed out at main and could only image one or two machines.