yupthatguy

Hey Tom... FYI I eventually went with your solution and ditched the daemon... I did experiment by changing teh ACL and giving non-root-user full access to /backup-dir but the rsync daemon -always- fails with @ERROR chdir if the user is not root and tries to manipulate system item. /home/user/directory no problem at all... /system directory forget it.. I just hate managing the cpu usage that comes without the daemon... in any case.. thanks for the help

This post seems to nail my problem... testing now... stackoverflow.com/questions/22726183/…

Hey there... Thanks for the tips. I understand that "-e" seems to go against my goal... but the fundamental problem is that I can't get rsync to pass ~/.ssh/id_rsa without using "-e"... according to docs rsync -should- read the config file for the identity credential but doesn't, it just times out

I have been operating under the assumption that I need to use the daemon in order to use sshd_config Match User / ForceCommand / rsync[..] If can still use ForceCommand with :, then ditching the daemon approach seems to eliminate headaches...

command="rsync --server --daemon .",no-port-forwarding,no-agent-forwarding,no-X11-forwarding,‌​no-pty ssh-rsa is in my authorized_keys.. I am editing sshd_config now

Something seems off about this version of rsync 1.) the hosts allow option that I mentioned, simply doesn't work and 2.) without using the -e option rysnc doesn't read the ssh config and fails to connect, although #ssh non-root-username@ip-addr connects perfectly fine (reads config file) basically with your suggestion, I have to fiddle with the ACL to grant a non-root-user direct permissions to a system directory, which exactly what I am trying to avoid, hence I gave non-root-username passwordless access to rsync... :-/

@heynnema saw your comments.. I will need time to post the information, silly distractions called employment, rent, bills, and food, slowing my intellectual playtime. :-) But I definitely need to test my external backup drive, which I have been assuming is healthy.

@matigo and Nmath may be correct about the location of my VM. It has been 24+ hours since I moved the VM back to the internal HDD with the VDI still on the internal SSD (hybrid machine) and I have not had a corrupt file system / write only file system error, which is a small miracle. Also, something of note. Previously, when I had the VM on the internal hard drive, I was able to identify one source of disk corruption. A gnome-shell plugin called "Internet Radio" was destroying my VDI if I played music while working. You can imagine how hours of frustration it took to figure that out.

FYI, I switched Off power saving a long time ago. I use an external for my CPU. And I have today, moved my VM back to the home folder (internall HDD) with the VDI on the internal SSD, though I agree with Terrance location of VM has never previously been a factor. And I always move VM with Vbox' own tools.

@matigo I am only using the VM to run a Virtualmin Test Server, perfect my installations before heading to production.

@Terrance If you know if specific items of hardware that I should benchmark & test, definitely clue me in and how to test. At this point, I am just ready to drop VBox

@Terrance I will add my machine profile to my original post. But, my machine is less than 2 years old. I maxed out the RAM with manufacturer recommended memory. In theory, I should be cruising at high speed right now.

I added a note to my original posts, don't know if it is relevant information.

@Nmath The external drive checks out as healthy. I only moved the VM there to so save on space. But again. This problem happens with the VM fully on the host system.

@Nmath I setup bash aliases to use VBoxManage to bootup, save state, and shutdown machines. I primarily shutdown my machines from within the OS using old fashion "shutdown" to guard against corruption.

@cocomac A little over my head. I boot to Ubuntu LiveCD , I use the disks tool to and smarttools to check my hdd and ssd and all tests show my drives as healthy. No other files on my machine get corrupted, just my VDI files. super slow boots on a SSD drive annoying.

thanks again

post the same to question and I will vote up your solution, get you some rep points...

Dear god... it was the double firewall issue.. I wasted hours on a silly problem... at least I finish my week on a good note... everything works perfectly now... THANKS YOU

brilliant... I think you nailed it.. forgot about the double firewall.. let me test

VPS server

[23] 51820/udp ALLOW IN Anywhere

yup..

hey hey.. thanks for the invite

ok.. let me go back and edit the post.. I already changed the subnet addresses on local and remote... so the last set of conf files that I posted are correct.

I don't see "10.0.0.0/24"... are you referring to AllowedIPs = 0.0.0.0/0? Will clean up the post after I figure out the answer

Confirmed my suspicion client is trying to connect on ssh port 22. Does anyone know how to force client to connect on a different designated ssh port?

@DanielB give me a few minutes.. I will post what you requested... I went ahead changed the ssh port back to 22 to test and wg still failed.. and dmesg gave me a different message: [ +0.714353] wireguard: module verification failed: signature and/or required key missing - tainting kernel

I have double checked my configs.. inside and out.. everything is correct according to this tutorial.. linuxbabe.com/ubuntu/wireguard-vpn-server-ubuntu#comment-208‌​230 ... Does it matter if SSH is on port 22 or different port? That is only difference that I can find.

buenos noches

must go get coffee... life draining from body...

rebooted

installing

linux-firmware/bionic-updates,bionic-updates,now 1.173.19 all [installed,automatic]

Yikes! implies I need new hardware... on a new compueer....???

yeah dual boot.... I just checked the log, output below, now worries.. I am typo king...

will do... because that is one hell of annoying problem.. to 2nd reboot becuz wifi didn't load..

got it... you just earned your own simplenote for wifi connectivity tricks..thx oddly enough my wifi problems seem to mostly crop up at night, when I rushing through a last few tasks, to feel less guilty trying to sleep...:-/ everything things good now... but I will have to reboot several times and wait until night time to confirm

so permanently switching wouldn't be a problem

no i don't... once I get back to China.. I'd rather handle that... never leaving China again.

Avoiding the US like the plague... (pun accurate, these days)

yeah.. stranded in Taiwan... trying to get back to Beijing

gotcha

One more thing that I did not see in your list of tricks... on my previous machine I had a realtek wifi card that was buggy as well... and it helped to change the wifi antenna being used by realtek... is that even an option for intel?

appreciate te tips..

The problems with my router are intermittent... so let's wait a while and see if the router changes helped... not really loving the country change suggestion, I travel around a lot and expect to travel soon as a certain border opens...

set channel to 6... will reboot router... now (u r obviously getting play by play action)

i.imgur.com/54VSqs2.png it is in fact AES