network Rsync fail after 22.12.1/22.12.2 update

[TinyWorkshop]

I've updated a couple of days ago to the last bluefin, prior to that the Backup Rsync was working correctly and no other changes have being done.
the task is configured like that:

fails immediately after launch

any idea/workaround?

a think is linked to the SMB changes (I had to switch off the security check on order to make my apps working too)

 

[TinyWorkshop]

Switching back to the old 22.12.0, and the task works flawlessly

I think to stay there for the time being, but I'm happy to thinker if anyone interested in investigate

 

[TinyWorkshop]

Tried again the last update and the rsync started again failing.

I’m the only one with this problem?

 

[sretalla]

Seems it would not be too complicated to simply re-create that task item.

Does a newly created task fail too?

 

[TinyWorkshop]

Seems it would not be too complicated to simply re-create that task item.

Does a newly created task fail too?

Yes already tried, tried also to recreate the BK rsync module with no luck, fails immediately.

there's a way to have at least a complete log to understand what's wrong? the alert just tell that's failling

 

[sretalla]

there's a way to have at least a complete log to understand what's wrong?

If that's anywhere it would either be in /var/log/messages or /var/log/middlewared.log

 

[TinyWorkshop]

var/log/messages there's nothing

var/log/middlewared.log sais:

[2023/04/24 15:44:04] (ERROR) middlewared.job.run():438 - Job <bound method accepts.<locals>.wrap.<locals>.nf of <middlewared.plugins.rsync.RsyncTaskService object at 0x7fe4c8788b80>> failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 426, in run
await self.future
File "/usr/lib/python3/dist-packages/middlewared/job.py", line 463, in __run_body
rv = await self.middleware.run_in_thread(self.method, *([self] + args))
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1252, in run_in_thread
return await self.run_in_executor(self.thread_pool_executor, method, *args, **kwargs)
File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1249, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1322, in nf
return func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1192, in nf
res = f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/middlewared/plugins/rsync.py", line 810, in run
raise CallError(msg)
middlewared.service_exception.CallError: [EFAULT] rsync command returned 1 - SYNTAX. Check logs for further information.

 

[sretalla]

Not sure if I saw it for rsync tasks, but the task status for cloud sync has the option to view logs for the job from the status in the job list, maybe check that.

 

[TinyWorkshop]

I haven't find anything unfortunately.
I have to switch back to 22.12.0 again, but I think that that's something wrong with my installation

docker's apps where behaving weirdly
for example after updating, my qbittorrent installation, was unable to run if I was using the VPN, even with a fresh reinstallation.

but after switching back truenas the VPN was working normally again... (so it's not a problem of the docker app I think)

 

[f!sch]

Running 22.12.2 and I was running into an issue where rsync was running, network traffic showed files being transferred but no files were being written.

I could see the .tmp files being created then disappearing in the file shares.

no log messages to speak of that helped narrow down the problem. But after a few other troubleshooting steps, I ended up disabling delayed updates, working like a champ now.

Hope this helps

 

[jgreco]

I could see the .tmp files being created then disappearing in the file shares.

no log messages to speak of that helped narrow down the problem. But after a few other troubleshooting steps, I ended up disabling delayed updates, working like a champ now.

Delayed updates are supposed to do that. From the manual page:

--delay-updates
This option puts the temporary file from each updated file into
a holding directory until the end of the transfer, at which time
all the files are renamed into place in rapid succession. This
attempts to make the updating of the files a little more atomic.

It was working just fine for you. You just had to wait for the transfer to finish, at which point rsync would batch move the files into their final destinations. This isn't quite as good as an atomic update, but it's really close in most cases.

 

[f!sch]

Delayed updates are supposed to do that. From the manual page:



It was working just fine for you. You just had to wait for the transfer to finish, at which point rsync would batch move the files into their final destinations. This isn't quite as good as an atomic update, but it's really close in most cases.

In my case I had a successful run report and no files appeared, similar to the OP reported behavior.

when digging on this, I could see the .~tmp~ directory and verified files were present but they had not been moved to the destination.

Removing the .~tmp~ directory, unchecking delayed updates and re-running the task, files appear as expected.

Just reporting on my experience with this on latest build, no issues with the same job in prior builds.

 

[jgreco]

If rsync was unable to perform the file moves, it should have exited with an error status. You didn't get anything in the alerts or notifications?