TrueNAS Scale. Syncthing stuck on 'deploying'

[vlad-infra-admin]

Hello friends,
I recently updated TrueNAS from 22.02.3 to 22.12.0 and my syncthing app stuck on deploying.
At first I had to change some old settings and thought this is it, but then it still not allow me to deploy and then I saw this error message.

This is correct, I have SMB Share for the same folder as mount for Syncthing app, but It was never a problem in the past.

So what I figure out so far:
1. Stop the app
2. Disable all SMB shares
3. Enable app
4. Enable shares

It works to the next reboot.

Is there some permanent solution except the one where I need separate mount for app and SMB?

 

[Daisuke]

This is a known issue in Bluefin, see SMB Shares section in Bluefin Upgrade Checklist.

 

[vlad-infra-admin]

I see, good to know.
I hope it could be fixed. Not sure how I can do it differently. Once in the while I would go to my phone sync folder to see photos or move them in to archive folder via smb.

 

[truecharts]

It looks like you're running a TrueCharts App.
Sadly enough, we're not providing support on this forum. If you need any help, please be sure to:
- Checkout the website at: https://truecharts.org
- Reach out to our support staff on Discord: https://discord.gg/tVsPTHWTtr
- and check the announcements on Discord, Twitter and Facebook

 

[vlad-infra-admin]

It doesn't matter if I use TrueChart or Default repository. Error still will be the same...

 

[vlad-infra-admin]

There is a solution for others who is trying to find a fix

Shared host paths are considered insecure and are not recommended. Review host paths used by Apps and Sharing services and adjust paths to be unique. As a last resort that can result in system and app instability, Host Path Safety Checks can be disabled in Apps > Settings > Advanced Settings.

 

[Daisuke]

There is a solution for others who is trying to find a fix

Please don't do that, I don't understand why everyone is recommending this fix. I have zero issues in Bluefin and I did not disabled the option. And shared hostPaths are not considered insecure, see post. Look at SMB Shares section in this thread.

 

[vlad-infra-admin]

Please don't do that, I don't understand why everyone is recommending this fix. I have zero issues in Bluefin and I did not disabled the option. And shared hostPaths are not considered insecure, see post. Look at SMB Shares section in this thread.

I understand, but I don't use my TrueNAS in production. Besides I need mount for both syncthing and smb at home to sort my pictures directly via samba.
In the production I would probably set NFS and run apps on the separate machine with Portainer or Rancher.

 

[Daisuke]

Did you read my SMB Shares info?

 

[kofeyh]

Please don't do that, I don't understand why everyone is recommending this fix. I have zero issues in Bluefin and I did not disabled the option. And shared hostPaths are not considered insecure, see post. Look at SMB Shares section in this thread.

One user experience is != global outcomes. It keeps being referred to, simply as it's the path of least resistance. I have 1 host path that is also shared via SMB and it is absolutely blocking all apps that use a host path (regardless of where to) from deploying when the option is enabled.

This is as expected as this is specifically called out in the release notes as by ix-systems. The remaining solutions are to either not use SMB with a host path presented to an app (as per this example) or disable the check. Guess which one is going to be more commonly used.

Meanwhile, any number of people will hit this issue due to services and apps using the same host paths, so the issue isn't just going to go away of it's own volition. The decision whilst making sense from a security standpoint, reduces functionality that has existed.

 

[vlad-infra-admin]

Did you read my SMB Shares info?

I appreciate your input. Always informative. But we need something that simply working, especially for home

 

[truecharts]

One user experience is != global outcomes. It keeps being referred to, simply as it's the path of least resistance. I have 1 host path that is also shared via SMB and it is absolutely blocking all apps that use a host path (regardless of where to) from deploying when the option is enabled.

This is as expected as this is specifically called out in the release notes as by ix-systems. The remaining solutions are to either not use SMB with a host path presented to an app (as per this example) or disable the check. Guess which one is going to be more commonly used.

Meanwhile, any number of people will hit this issue due to services and apps using the same host paths, so the issue isn't just going to go away of it's own volition. The decision whilst making sense from a security standpoint, reduces functionality that has existed.

We recently wrote a whole blog about the 3 options for users having issues with hostPath and shares.
It might be worth checking out.