Submitted by jonkristian on Thu, 03/09/2017 - 07:20
When doing a Virtual Server Replication all files that has æøå letters in them are ignored, which is kind of a big deal especially for WordPress sites, since it doesn't normalize filenames.
Status:
Closed (fixed)
Comments
Submitted by andreychek on Thu, 03/09/2017 - 08:28 Comment #1
Howdy -- yeah that's definitely not good if it's missing files!
If you perform a Virtual Server backup using Virtualmin, are those files included in that?
Submitted by jonkristian on Thu, 03/09/2017 - 10:28 Comment #2
Yes, backing up to amazon aws for instance, no problems at all.
Submitted by JamieCameron on Thu, 03/09/2017 - 19:40 Comment #3
Are these filenames under the domain's home directory that have æøå in them? Or does the domain name contain those characters?
Submitted by jonkristian on Fri, 03/10/2017 - 17:03 Comment #4
No domains with æøå, these are files under the home directory.
Submitted by JamieCameron on Fri, 03/10/2017 - 18:48 Comment #5
I just did a test, and a file with those characters was transferred just fine.
Which Linux distribution and version are the source and dest systems running?
Submitted by jonkristian on Sat, 03/11/2017 - 05:33 Comment #6
Running debian 8 host and vm.
That is really strange. I can't think of anything else that could've caused this. All files with æøå on all 30 or so domains were missing after running a replication.
Submitted by JamieCameron on Sat, 03/11/2017 - 15:07 Comment #7
Does the same thing happen if you just backup and restore a domain on the same system?
Submitted by andreychek on Sat, 03/11/2017 - 17:44 Comment #8
Jamie, he had mentioned in Comment #2 above that he does backups (to AWS) using Virtualmin and that those are working properly.
Submitted by JamieCameron on Sat, 03/11/2017 - 19:35 Comment #9
Ah .. interesting. Ok, let me try a transfer to see if there's anything special about it.
Submitted by JamieCameron on Sat, 03/11/2017 - 19:38 Comment #10
jonkristian - on the transfer form, what do you have the "Over-write existing domain?" option set to?
Submitted by jonkristian on Mon, 03/13/2017 - 14:46 Comment #11
Hm, which form? I can't find the "Over-write existing domain" in the replication form.
Submitted by JamieCameron on Mon, 03/13/2017 - 18:33 Comment #12
Are you setting up Virtualmin domain replication in Cloudmin?
Submitted by jonkristian on Wed, 03/15/2017 - 04:34 Comment #13
Yes that's what I did.
Submitted by JamieCameron on Thu, 03/16/2017 - 00:51 Comment #14
So there are a few small differences in the way replication is done vs. backup and restore, so I re-tested this specifically to try to re-produce this bug ... but it still worked fine on test systems!
Are both systems running the same linux distribution and version?
Submitted by jonkristian on Thu, 03/16/2017 - 06:34 Comment #15
Yes.
Host is running debian 8, and both source+target vm is running your cloudmin kvm debian image.
Submitted by JamieCameron on Fri, 03/17/2017 - 00:09 Comment #16
Is it Debian 8 on the VMs as well? Also, do they share home directory contents in any way, such as via NFS?
Submitted by jonkristian on Fri, 03/17/2017 - 11:57 Comment #17
Yes debian 8. No special setup, and not sharing home.
Submitted by JamieCameron on Fri, 03/17/2017 - 20:50 Comment #18
Ok, I finally found the cause of this - it's due to the tar command outputting filenames in an odd format sometimes. This will be fixed in the next Webmin release.
Submitted by JamieCameron on Fri, 03/17/2017 - 20:50 Comment #19
Submitted by jonkristian on Mon, 03/20/2017 - 05:04 Comment #20
Thank you Jamie, I'm glad you found it.
Was beginning to think about anything else that could've caused this.
Submitted by JamieCameron on Mon, 03/20/2017 - 19:06 Comment #21
It was tricky as it ONLY happens during replication, not during backup and restore, even though they mostly use the same code.
Submitted by IssueBot on Mon, 04/03/2017 - 19:07 Comment #22
Automatically closed - issue fixed for 2 weeks with no activity.