File Write Fails on Solaris 10 (current main branch) #629
Replies: 6 comments 12 replies
-
The first obvious thing to ask... are the FWIW I merged some improved error handling for this to the |
Beta Was this translation helpful? Give feedback.
-
There were two cnid processes running, cnid_met and cnid_dbd. I re-pulled the source from main and built it. I also ran dbd -f to rebuild the database. I'm still having the same issue. Note the permissions on the shared directory are 2770 and g+s. The directory has the devusers group assigned and the login account is a member of that group. Thanks, |
Beta Was this translation helpful? Give feedback.
-
I can reproduce the same problem in my Solaris 10 VM. Something derails when it tries to write to the Berkeley DB I think, but the logging isn't entirely helpful (yet.) In a few hours I'm taking off for a trip overseas, but I'll come back in a week or so to look deeper in what's going on here! |
Beta Was this translation helpful? Give feedback.
-
I'll setup with a newer version of Berkeley (5.3 compiles on my box) and try a few other things on my end. You have have been wonderfully responsive and this is a home hobbyist setup. Ergo no rush. Enjoy your trip! |
Beta Was this translation helpful? Give feedback.
-
@Michael-Wohlstadter Happy new year! I took another stab at this today, but didn't really make any progress. I starting to suspect something to do with file system permissions / ACLs. I tried setting up a test volume, chmod 2775, then set If you search the mailing list archives there are countless threads with people trying to solve file system permissions issues on Solaris: https://sourceforge.net/p/netatalk/mailman/ There might be some configuration required in Solaris that I am not aware of! |
Beta Was this translation helpful? Give feedback.
-
@rdmark I also didn't have much luck with the current development stream. However, I did compile 3.1.8 and that works as expected. While I'm not suggesting that ACLs aren't involved, it appears that there is at least some interaction with a change from 3.1.8 to the current version. That said, I will look through the mailing list to see if I can't find something helpful. Thanks, |
Beta Was this translation helpful? Give feedback.
-
I am attempting to build the current 3.1 stream on Solaris 10 (sparc). After a couple initial errors preventing the build, I can now build Netatalk. Huge thanks to Mark for amazingly rapid response! However, I am unable to copy any files to the mounted share.
As a couple reality checks, I build Netatalk 3.1.8 on the Solaris 10 box and I built Netatalk (current main branch) on Ubuntu 20.04. In both cases I tried to keep the configurations as close as possible. Both Solaris 10 / Netatalk 3.1.8 and Ubuntu 20.04 / Netatalk main build, install, and run as expected. When I copied a file to the mounted share, it worked correctly in both of the test cases.
So I don't know if there is still an issue with the current branch on Solaris 10 or if I have a configuration issue.
For both Solaris 10 builds, I had previously installed appropriate libraries and tools from OpenCSW. These include: autoconf, libtool, automake, gsed, pkgconfig, ggrep, libgcrypt, berkeley48devel, binutils, and libevent_dev.
Solaris 10 / Netatalk main
afp.conf
Solaris 10 / Netatalk 3.1.8
afp.conf
Ubuntu 20.04 / Netatalk main
afp.conf
Thoughts, comments? I'm not sure what to check next. If it seems to be a bug in the current stream, I'll submit and issue.
Thanks!
Attached are the log files with level set to default:debug.
netatalk-solaris-main.log
netatalk-solaris-3.1.8.log
netatalk-ubuntu-main.log
Beta Was this translation helpful? Give feedback.
All reactions