I just used the image builder to build 22.03 for my RT3200 with samba4-server samba4-utils samba4-libs as custom packages from snapshots. No problems so far.
Awesome work!
1 Like
Something I can't seem to solve is that samba4 is totally missing from the menuconfig but the samba4 directory and contents is in buildroot/feeds/packages/net.
I've totally removed the cloned openwrt directory, recloned and updated/installed all feeds without being able to solve the issue.
It's just me right?
Anyone have this happen before?
I would expect luci-app-samba4 to be there, looking into it on my end too.
For my target I use luci-app-samba4 from this folder:
https://downloads.openwrt.org/snapshots/packages/arm_cortex-a9_vfpv3-d16/luci/
1 Like
I'm not sure why but the 4.17 update to the samba package removes any reference to samba in menuconfig.
If I locally revert the samba4 make file it appears again.
I can't seem to nail what the problem is, maybe you can take a look and see if the same happens to you.
My HDD external enclosure currently broken which in one of the HDDs reside the OpenWRT VM for building, probably need around 3-4 days for replacement coming through, will try in here once I've get it.
1 Like
No probs.
I've temporarily reverted back to 4.14.14 to test and the issue resolves itself.
Could it be possibly caused by some other package that has received an update that samba depends on?
Managed to turning on the VM, the issue seems reproducible if user is at the beginning of .config / without .config and perl not being selected as module or built-in.
Adding "+perlbase-json-pp" into samba4-libs dependencies is the wrong approach as afaik it's only a perl helper to building samba4, perlbase-json-pp seems already included in perl/host so the fix is removing "+perlbase-json-pp" from samba4-libs and adding perl/host into PKG_BUILD_DEPENDS .
Complete fixed Makefile in here. Please try and test it before opening a PR.
2 Likes
Tested and is fixed.
Nice work
2 Likes
Tested the Makefile on my Xiaomi R3G build, all ok. thanks.
2 Likes
The samba4 package always had experimental AD-DC support, but you need to build your own package/fw, since its a menuconfig option. It also was only tested a couple of times, so its more of a concept and not something you should use as a production system.
ACL support should be enabled by default or its a menuconfig option (cant remember).
1 Like
Is anyone else using timemachine? I noticed that while backing up with timemachine my log is getting spammed with 4.17 (either snapshots or 22.03 build with image-builder). This is not happening with 4.12 or 4.14. I noticed that initial connection to the share is slower aswell with 4.17 on my mac.
logread:
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.433023, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/e6c:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.437592, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/115e:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.441723, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/10b2:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.445742, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/mapped/1158:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.449196, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/mapped/10e0:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.453562, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/mapped/e0c:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.457701, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/10f0:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.462127, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/1158:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.466250, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/10e0:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.469933, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/e0c:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.477748, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/1154:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.494870, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/mapped/e74:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.506898, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/bands/e74:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.519210, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/lock:AFP_AfpInfo] failed
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: [2022/10/17 23:51:22.537520, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)
Mon Oct 17 23:51:22 2022 daemon.err smbd[11529]: synthetic_pathref: opening [air.sparsebundle/Info.plist:AFP_AfpInfo] failed
EDIT: Seems like this is an Issue with 4.17. Unraid got the update to 4.17 and people are complaining in their forums aswell.
Not sure what SMBD 6.11 is but for Apple did you check that box "Enables Apple's AAPL extension globally and adds macOS compatibility options to all shares." not sure what it does but it's an option in LuCI. I don't have an Apple device to test it with other than iPhone but don't think I can browse shares on that.
1 Like
6.11 refers to the Unraid version. Yes i checked all the boxes and it seems that timemachine is working fine. In the linked thread they are thinking that there is a change in logging since 4.17 and that this is a debug message. Like one person suggested, i added logging = 0 to the config and the messages are (obviously) gone.
1 Like
I checked the changes and there are quite a few changes referenced to logging and logs in 4.15 and 4.16. Since this is a jump from 4.14 to 4.17 it may be related. For example search for "logs" here and you'll see some changes:
https://wiki.samba.org/index.php/Samba_4.15_Features_added/changed
Looks like you found the fix for now, but it could be relate to those.
1 Like
Could be, but i think the "bug" is introduced with with the change from 4.16.x to 4.17. With Unraid the version changed from 4.16.x to 4.17 and then they got these messages in sys-log. Lets see how they solve the problem without disabling logging completely.
@echelon @Gingernut
Can you help me build Samba 4.16.5? I would like to test this version, but i am failing with my makefile. (Still a noob in building openwrt)
Samba 4.17.1 was just released, bunch of bug fixes but nothing related to logging. I'm not sure it's a Samba issue honestly because this package worked well for me, although I'm back on 22.03.2 for the time being so can't use this new package I don't think.
Thanks for the info. Maybe I try building this version in the next few days and have a look.
FYI: Image-Builder is great for including custom packages in the firmware images, e.g. Samba 4.17 from snapshots in 22.03.
2 Likes