git checkout dev-branch
git pull

now running 1.5.0 RC11
Interesting new GUI.

I added a location - it said it was successful however it seems no location was created.
When i clicked to list locations none appeared.

I uninstalled the plugin and re-installed it and it now works.

Thank-You for the quick reply 🙂

@JJ-Fullmer Well it wasn’t actually phpipam that was slowing it down.
I had some ssl logs running for a website running on that server. It was tracking access logs for every access of the ssl cert and site. Which was also adding up to over 400 GB of logs. I changed the apache configuration of the site to log much less. That solved the problem. So again, nothing wrong with zstd. Just wanted to have the right answer in case someone else happens to see a constant 5-8 Mbps transmit and receive on a storage node.

Code 87 threads. I glanced through these, most are configuration issues - people not re-assigning settings to the individual hosts.

https://forums.fogproject.org/topic/3846/domain-join-not-working-since-moving-to-v1-2-0-error-87/4

https://forums.fogproject.org/topic/8341/the-parameter-is-incorrect-code-87

https://forums.fogproject.org/topic/1937/help-with-domain-joing

https://forums.fogproject.org/topic/5812/samba-domain-integration/61

https://forums.fogproject.org/topic/6879/i-can-t-join-machines-on-domain

https://forums.fogproject.org/topic/7126/hosts-unable-to-join-domain

https://forums.fogproject.org/topic/3140/domain-join-is-not-working-fog-server-1-1-1

25% Packetloss… Guess China’s firewall doesn’t like it…

It’s definitely the place to start though.

The code just probably needs updated to work with the current versions.

Should also make sure the receiving server is still operational…

any of the developers can maybe confirm if there has been any changes made to the way storage nodes operate between 0.32 and 1.2… if it hasn’t and the process is exactly the same then would be even more useful.

Testing 1.2 in my environment, but will be on 0.32 for a while yet.

I just ran into this problem also. The download took 8 hours to complete downloading at roughly 184MB/m. When I took the Host drive out and popped it into a Sata reader, Hard Disk Sentenal showed 282 bad sectors. Threw the drive out and put in a new drive. Image pulled down at 2.64GB/m again.

My issue was a bad drive but don’t let that account for possible other issues.

does each site have it’s own tftp server as well?

updated to latest btsync, now deploys properly.

well… if the user wanted to use bittorrent sync an easy way to avoid hassle would be to have a way of just turning off the current replication system. As long as the permissions will be correct in the folder then the images should just sync across.

The user would have to generate their own key and tell bittorrent sync where to sync the images.

I suppose the biggest advantage would be many to many replication. I would have to check if bittorrent sync can take parts of files from different hosts but at a minimum if you had 10 images and were putting in your 11th host… you could get away with transferring one image from each of the others. which could save you a ton of time if your doing things over a WAN.

Is there currently a way to easily disable replication and i’ll throw a couple of VMs on 0.33b and see if I can make it do something.