Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatibility with Solaris and Berkeley DB 6.x #8

Closed
VeloAddict opened this issue Mar 18, 2015 · 6 comments
Closed

Incompatibility with Solaris and Berkeley DB 6.x #8

VeloAddict opened this issue Mar 18, 2015 · 6 comments

Comments

@VeloAddict
Copy link

Mar 18 16:44:38 gurde afpd[1817]: [ID 702911 daemon.notice] Login by admin (AFP3.4)
Mar 18 16:44:38 gurde cnid_dbd[1818]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:38 gurde cnid_metad[454]: [ID 702911 daemon.error] error in sendmsg: Broken pipe
Mar 18 16:44:38 gurde afpd[1817]: [ID 702911 daemon.error] read: Connection reset by peer
Mar 18 16:44:39 gurde cnid_dbd[1819]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:40 gurde cnid_dbd[1820]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:41 gurde cnid_dbd[1821]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:42 gurde cnid_dbd[1822]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:43 gurde cnid_dbd[1823]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:44 gurde cnid_dbd[1824]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:45 gurde cnid_dbd[1825]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:46 gurde cnid_dbd[1826]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:47 gurde cnid_dbd[1827]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:48 gurde cnid_dbd[1828]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:49 gurde cnid_dbd[1829]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:50 gurde cnid_dbd[1830]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:51 gurde cnid_dbd[1831]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:52 gurde cnid_dbd[1832]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:53 gurde cnid_dbd[1833]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:54 gurde cnid_dbd[1834]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:55 gurde cnid_dbd[1836]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:56 gurde cnid_dbd[1837]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:57 gurde cnid_dbd[1838]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:58 gurde cnid_dbd[1839]: [ID 702911 daemon.error] error setting flags for database name.db: Unknown error
Mar 18 16:44:59 gurde afpd[1817]: [ID 702911 daemon.error] transmit: Request to dbd daemon (volume tank) timed out.
Mar 18 16:44:59 gurde afpd[1817]: [ID 702911 daemon.error] afp_openvol(/tank): Fatal error: Unable to get stamp value from CNID backend
Mar 18 16:45:01 gurde afpd[1817]: [ID 702911 daemon.notice] AFP logout by admin
Mar 18 16:45:01 gurde afpd[1817]: [ID 702911 daemon.error] dsi_stream_read: len:0, unexpected EOF
Mar 18 16:45:01 gurde afpd[1817]: [ID 702911 daemon.notice] afp_over_dsi: client logged out, terminating DSI session
Mar 18 16:45:01 gurde afpd[1817]: [ID 702911 daemon.notice] AFP statistics: 0.59 KB read, 0.44 KB written
@VeloAddict VeloAddict changed the title Can not connect to an AFP share where netatalk runs on a Solaris build Can not connect to an AFP share where netatalk (3.1.7) runs on a Solaris build Mar 18, 2015
JensKSP pushed a commit to JensKSP/Netatalk that referenced this issue Apr 15, 2022
Maintain AFP 3.x compliance while preserving file dates during GS/OS folder copies.
@rdmark rdmark closed this as completed Feb 11, 2023
@rdmark rdmark reopened this Apr 10, 2023
@rdmark
Copy link
Member

rdmark commented Apr 10, 2023

Further analysis in https://sourceforge.net/p/netatalk/bugs/592/ ; quoting:

It seems to be related to Berkley DB 6.x. After I downgraded my Berkley DB to 4.8, all connections to netatalk / afp shares are working perfectly.

@rdmark rdmark changed the title Can not connect to an AFP share where netatalk (3.1.7) runs on a Solaris build Incompatibility with Solaris and Berkley DB 6.x. Apr 10, 2023
@rdmark rdmark changed the title Incompatibility with Solaris and Berkley DB 6.x. Incompatibility with Solaris and Berkeley DB 6.x Apr 10, 2023
@rdmark
Copy link
Member

rdmark commented Aug 30, 2023

I propose the action here is to make v5 of BDB the recommended version, since it's the last version under the permissive Sleepycat license, and therefore the version that's shipped with the most operating systems.

A mirror of the final Sleepycat release here: https://github.com/berkeleydb/libdb/releases/tag/v5.3.28

Some discussion on the licensing in https://en.wikipedia.org/wiki/Berkeley_DB

If we all agree, I propose updating the documentation, e.g.

Additionally, we may want to update the autoconf check to warn when v6 or later is detected.

@rdmark
Copy link
Member

rdmark commented Sep 1, 2023

Interestingly, I was able to compile and use netatalk3 with db18 on FreeBSD when hacking db3-check.m4 to check for db18:

checking for Berkeley DB headers in /usr/local/include/... no
checking for Berkeley DB headers in /usr/local/include/db18... yes
checking /usr/local/include/db18/db.h version >= 4.6.0... yes
checking Berkeley DB library (-ldb181)... no
checking Berkeley DB library (-ldb18.1)... no
checking Berkeley DB library (-ldb-181)... no
checking Berkeley DB library (-ldb-18.1)... 18.1.40 ... yes

It seems to work but is error prone and slow, but not sure if that's due to other environmental factors right now, since FreeBSD is not what I usually run.

@rdmark
Copy link
Member

rdmark commented Sep 1, 2023

BDB 6.x checks were added in 2015 with d30a3e7

@rdmark
Copy link
Member

rdmark commented Sep 1, 2023

Made the recommended BDB version 5.3.x in #446 and #447

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants