strcpy_chk: symbol not found #180

Lilja · 2024-02-17T11:47:24Z

I'm trying to package my API into a docker image, using node:20-alpine.

Running my app leads to

2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] node:internal/modules/cjs/loader:1473
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] return process.dlopen(module, path.toNamespacedPath(filename));
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] ^
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] Error: Error relocating /app/node_modules/@libsql/linux-x64-musl/index.node: __strcpy_chk: symbol not found
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Module._extensions..node (node:internal/modules/cjs/loader:1473:18)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Module.load (node:internal/modules/cjs/loader:1207:32)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Module._load (node:internal/modules/cjs/loader:1023:12)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Module.require (node:internal/modules/cjs/loader:1235:19)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at require (node:internal/modules/helpers:176:18)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Object.<anonymous> (/app/node_modules/libsql/index.js:41:24)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Module._compile (node:internal/modules/cjs/loader:1376:14)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Module.load (node:internal/modules/cjs/loader:1207:32)
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] at Module._load (node:internal/modules/cjs/loader:1023:12) {
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] code: 'ERR_DLOPEN_FAILED'
2024-02-17T11:15:12.739 app[080e513b19e298] ams [info] }

It might be an issue with glibc/musl. See this issue

Do the libsql team have an opinion of what type of distribution I should use?

Dockerfile

FROM node:20-alpine as base

WORKDIR /app
COPY ./dist /app/dist

ARG GIT_SHA
ENV GIT_REVISION=$GIT_SHA

RUN npm install @libsql/client

EXPOSE 4000
CMD [ "node", "--no-warnings=ExperimentalWarning", "dist/index.js" ]

The text was updated successfully, but these errors were encountered:

lovell · 2024-02-25T21:02:24Z

I've just hit this when upgrading from v0.2.0 to v0.3.x.

It looks like the @libsql/linux-x64-musl/index.node binaries since v0.3.1 might have been built/linked against glibc rather than musl.

v0.2.0:

# ldd node_modules/@libsql/linux-x64-musl/index.node
	/lib/ld-musl-x86_64.so.1 (0x7f2fdf705000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f2fdf052000)
	libc.so => /lib/ld-musl-x86_64.so.1 (0x7f2fdf705000)

v0.3.1:

# ldd node_modules/@libsql/linux-x64-musl/index.node 
	/lib/ld-musl-x86_64.so.1 (0x7f3343052000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7f33423d0000)
	libc.so => /lib/ld-musl-x86_64.so.1 (0x7f3343052000)
Error relocating node_modules/@libsql/linux-x64-musl/index.node: __strcpy_chk: symbol not found
Error relocating node_modules/@libsql/linux-x64-musl/index.node: __memcpy_chk: symbol not found
Error relocating node_modules/@libsql/linux-x64-musl/index.node: __memset_chk: symbol not found
Error relocating node_modules/@libsql/linux-x64-musl/index.node: fcntl64: symbol not found

v0.3.2:

# ldd node_modules/@libsql/linux-x64-musl/index.node 
	/lib/ld-musl-x86_64.so.1 (0x7fb7d2869000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7fb7d1be1000)
	libc.so => /lib/ld-musl-x86_64.so.1 (0x7fb7d2869000)
Error relocating node_modules/@libsql/linux-x64-musl/index.node: __strcpy_chk: symbol not found
Error relocating node_modules/@libsql/linux-x64-musl/index.node: fcntl64: symbol not found
Error relocating node_modules/@libsql/linux-x64-musl/index.node: __memcpy_chk: symbol not found
Error relocating node_modules/@libsql/linux-x64-musl/index.node: __memset_chk: symbol not found
Error relocating node_modules/@libsql/linux-x64-musl/index.node: fcntl64: symbol not found

Symbols such as __strcpy_chk are glibc-only and provided by its _FORTIFY_SOURCE feature.

Checking the commit history I suspect tursodatabase/libsql-js@e325e78 that introduced neon-bindings/neon-rs@9903c95 is a possible cause.

yrke · 2024-03-01T09:19:01Z

As a workaround we downgrading from v5.x to v0.4.3 tested to work with node:18-alpine and node:20-alpine (at least for now)

This reverts commit e325e78, which is suspected to cause problems with musl: tursodatabase/libsql-client-ts#180

penberg · 2024-03-07T09:41:55Z

Thanks for looking into this, @lovell! Unfortunately, the @neon-rs/cli bump was not related to the problem. Instead it's this libsql issue related to the new encryption feature: tursodatabase/libsql#1155

…ts#180 waiting for fix

penberg · 2024-03-11T12:56:43Z

f61e2c1 should fix this.

lovell · 2024-03-11T19:32:00Z

Thanks for the updates, the fcntl64: symbol not found error remains with the new version when testing with latest Alpine Edge:

# cat node_modules/@libsql/linux-x64-musl/package.json | grep version
  "version": "0.3.9",

# ldd node_modules/@libsql/linux-x64-musl/index.node 
	/lib/ld-musl-x86_64.so.1 (0x76c8197f6000)
	libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x76c818f42000)
	libc.so => /lib/ld-musl-x86_64.so.1 (0x76c8197f6000)
Error relocating node_modules/@libsql/linux-x64-musl/index.node: fcntl64: symbol not found

The fcntl64 symbol is glibc-only and was introduced in glibc 2.28.

RA9 · 2024-03-21T08:19:46Z

@lovell is the issue fixed?

lovell · 2024-03-21T08:35:22Z

@RA9 This problem remains and now there are duplicate reports appearing e.g. tursodatabase/libsql-js#91

The summary is that the @libsql/linux-x64-musl package provided from v0.3.1 onwards, including the latest v0.3.10, does not work on musl-based systems.

ruohki · 2024-03-23T21:40:43Z

Ran into this problem while trying to build a astro application with the db integration. Wont build using node:lts-alpine

#0 2.037 node:internal/modules/cjs/loader:1473
#0 2.037   return process.dlopen(module, path.toNamespacedPath(filename));
#0 2.037                  ^
#0 2.037
#0 2.037 Error: Error relocating /app/node_modules/@libsql/linux-x64-musl/index.node: fcntl64: symbol not found
#0 2.037     at Module._extensions..node (node:internal/modules/cjs/loader:1473:18)
#0 2.037     at Module.load (node:internal/modules/cjs/loader:1207:32)
#0 2.037     at Module._load (node:internal/modules/cjs/loader:1023:12)
#0 2.037     at Module.require (node:internal/modules/cjs/loader:1235:19)
#0 2.037     at require (node:internal/modules/helpers:176:18)
#0 2.037     at Object.<anonymous> (/app/node_modules/libsql/index.js:42:5)
#0 2.037     at Module._compile (node:internal/modules/cjs/loader:1376:14)
#0 2.037     at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
#0 2.037     at Module.load (node:internal/modules/cjs/loader:1207:32)
#0 2.037     at Module._load (node:internal/modules/cjs/loader:1023:12) {
#0 2.037   code: 'ERR_DLOPEN_FAILED'
#0 2.037 }
#0 2.037
#0 2.037 Node.js v20.11.1

flexchar · 2024-04-07T17:44:43Z

@lovell does it mean we (Alpine users) must stick to v0.3.0 version?

lovell · 2024-04-07T18:20:10Z

@flexchar That is my understanding, yes, but I'm only the messenger here. You'll need to ask one of the maintainers about the future possible re-introduction of support for musl-based Linux.

IsaiahByDayah · 2024-04-17T17:14:02Z

Hey @penberg, should this issue be reopened? It doesn’t seem like the above proposed fix actually solved whatever the issue is for musl builds :/

LukaGiorgadze · 2024-04-23T18:52:57Z

Same problem.
/node_modules/@libsql/linux-x64-musl/index.node: fcntl64: symbol not found

node 18 alpine.

steschi · 2024-04-23T22:06:29Z

@LukaGiorgadze not sure if it works for your setup, but I am using yarn v3 and as such can ensure I am using a version of libsql that works with alpine by adding this to the root package.json of my monorepo.

"resolutions": {
    "@libsql/linux-x64-musl@npm:0.3.15": "0.2.0"
},

For npm-users i guess overrides should be the equivalent -> https://docs.npmjs.com/cli/v10/configuring-npm/package-json#overrides

MikeTeddyOmondi · 2024-05-28T10:39:20Z

When is the release for this issue scheduled??
@penberg

LukaGiorgadze · 2024-05-28T11:04:02Z

@LukaGiorgadze not sure if it works for your setup, but I am using yarn v3 and as such can ensure I am using a version of libsql that works with alpine by adding this to the root package.json of my monorepo.
"resolutions": {
    "@libsql/linux-x64-musl@npm:0.3.15": "0.2.0"
},
For npm-users i guess overrides should be the equivalent -> https://docs.npmjs.com/cli/v10/configuring-npm/package-json#overrides

Tried, but did not work :/

MikeTeddyOmondi · 2024-05-28T11:20:58Z

@LukaGiorgadze
thats true .....

fix hanging querings needed to switch image base because of tursodatabase/libsql-client-ts#180

This reverts commit e325e78, which is suspected to cause problems with musl: tursodatabase/libsql-client-ts#180

jeremybarbet · 2024-08-13T20:09:26Z

Can this be reopened, because this issue is still happening

jeremybarbet · 2024-08-13T20:20:34Z

FYI, node-sqlite3 had the same issue and the fix for it

erehwonmi · 2024-08-27T09:14:54Z

Issue still persists up to this date

brunodasilvalenga · 2024-08-29T05:19:39Z

Same here, getting the error in a nextjs app usign the @libsql/client version 0.6.0

5.703   ▲ Next.js 14.2.7
5.703   - Environments: .env
5.704
6.055    Creating an optimized production build ...
139.0  ✓ Compiled successfully
139.0    Linting and checking validity of types ...
199.6    Collecting page data ...
202.7 Error: Error relocating /app/node_modules/.pnpm/@libsql+linux-x64-musl@0.3.19/node_modules/@libsql/linux-x64-musl/index.node: fcntl64: symbol not found
202.7     at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
202.7     at Module.load (node:internal/modules/cjs/loader:1119:32)
202.7     at Module._load (node:internal/modules/cjs/loader:960:12)
202.7     at Module.require (node:internal/modules/cjs/loader:1143:19)
202.7     at mod.require (/app/node_modules/.pnpm/next@14.2.7_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/require-hook.js:65:28)
202.7     at require (node:internal/modules/cjs/helpers:121:18)
202.7     at requireNative (/app/node_modules/.pnpm/libsql@0.3.19/node_modules/libsql/index.js:22:10)
202.7     at Object.<anonymous> (/app/node_modules/.pnpm/libsql@0.3.19/node_modules/libsql/index.js:42:5)
202.7     at Module._compile (node:internal/modules/cjs/loader:1256:14)
202.7     at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) {
202.7   code: 'ERR_DLOPEN_FAILED'
202.7 }

erehwonmi · 2024-08-29T08:33:23Z

If some of you are using the Alpine distribution of Node for docker-izing an app with Libsql, I suggest migrating to the Bookworm distribution that fixed my issue and I can now use the latest version of libsql client. I am currently using Node 20 Bookworm for a docker-ized NextJS app with libsql client.

jeremybarbet · 2024-08-29T08:39:51Z

It's a workaround, but not a solution. Bookworm, bullseye or even distroless images work but are consuming more RAM compare to Alpine (15/20% more). In environment where you want to control cost on memory usage, Alpine is still the most optimised.

PS: You can probably use slim rather than the whole bookworm as well

ahtcx · 2024-09-05T20:56:49Z

I'm getting this currently with libsql@0.4.1 and the alpine:latest Docker image.

jonathannorris · 2024-09-09T14:00:25Z

We are also getting this with the node:22.7-alpine3.20 docker image

ahtcx · 2024-09-09T14:30:59Z

I resolved it by overriding @libsql/linux-x64-musl's version to be 0.2.0 as specified above, here's how I did this with pnpm.

{
	// ...
	"pnpm": {
		"overrides": {
			"@libsql/linux-x64-musl": "0.2.0"
		}
	}
}

LucioFranco · 2024-09-09T17:43:34Z

I did some digging it looks like there were some larger issues with our Rust/C code that we built the js library (which TS uses). This PR should fix those issues and subsequent TS/Js issues tursodatabase/libsql#1724

LucioFranco · 2024-09-10T14:55:25Z

v0.4.3 of libsql is out so if you run an npm update you should pick it up and should solve both the strcpy issue and the recent fcntl64 issues.

penberg added a commit to tursodatabase/libsql-js that referenced this issue Mar 7, 2024

Revert "Bump @neon-rs/cli"

9a430e9

This reverts commit e325e78, which is suspected to cause problems with musl: tursodatabase/libsql-client-ts#180

penberg mentioned this issue Mar 7, 2024

sqlite3mc build enables stack protector tursodatabase/libsql#1155

Closed

BrianUribe6 added a commit to jot-it/jotter that referenced this issue Mar 11, 2024

Downgrade @libsql/client to v0.4.3 until tursodatabase/libsql-client-…

0cf0438

…ts#180 waiting for fix

BrianUribe6 added a commit to jot-it/jotter that referenced this issue Mar 11, 2024

Downgrade @libsql/client to v0.4.3 until tursodatabase/libsql-client-…

bc2c982

…ts#180 waiting for fix

penberg closed this as completed Mar 11, 2024

lovell mentioned this issue Mar 21, 2024

Error relocating @libsql/linux-x64-musl/index.node: fcntl64: symbol not found tursodatabase/libsql-js#91

Closed

nichtsam added a commit to nichtsam/nichtsam.com that referenced this issue Jul 1, 2024

update libsql client

5e1e95f

fix hanging querings needed to switch image base because of tursodatabase/libsql-client-ts#180

nichtsam added a commit to nichtsam/nichtsam.com that referenced this issue Jul 1, 2024

update libsql client

06ecbaf

fix hanging querings needed to switch image base because of tursodatabase/libsql-client-ts#180

nichtsam added a commit to nichtsam/nichtsam.com that referenced this issue Jul 1, 2024

update libsql client

b927e45

fix hanging querings needed to switch image base because of tursodatabase/libsql-client-ts#180

nichtsam added a commit to nichtsam/nichtsam.com that referenced this issue Jul 1, 2024

update libsql client

efc8bd2

fix hanging querings needed to switch image base because of tursodatabase/libsql-client-ts#180

ainsleyclark mentioned this issue Aug 5, 2024

fix: #7488, cant deploy SQLite to Vercel payloadcms/payload#7490

Merged

1 task

LucioFranco pushed a commit to tursodatabase/libsql-js that referenced this issue Aug 6, 2024

Revert "Bump @neon-rs/cli"

862abd8

This reverts commit e325e78, which is suspected to cause problems with musl: tursodatabase/libsql-client-ts#180

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

strcpy_chk: symbol not found #180

strcpy_chk: symbol not found #180

Lilja commented Feb 17, 2024 •

edited

Loading

lovell commented Feb 25, 2024 •

edited

Loading

yrke commented Mar 1, 2024

penberg commented Mar 7, 2024

penberg commented Mar 11, 2024

lovell commented Mar 11, 2024

RA9 commented Mar 21, 2024

lovell commented Mar 21, 2024

ruohki commented Mar 23, 2024

flexchar commented Apr 7, 2024

lovell commented Apr 7, 2024

IsaiahByDayah commented Apr 17, 2024 •

edited

Loading

LukaGiorgadze commented Apr 23, 2024

steschi commented Apr 23, 2024

MikeTeddyOmondi commented May 28, 2024

LukaGiorgadze commented May 28, 2024

MikeTeddyOmondi commented May 28, 2024

jeremybarbet commented Aug 13, 2024

jeremybarbet commented Aug 13, 2024

erehwonmi commented Aug 27, 2024

brunodasilvalenga commented Aug 29, 2024 •

edited

Loading

erehwonmi commented Aug 29, 2024 •

edited

Loading

jeremybarbet commented Aug 29, 2024

ahtcx commented Sep 5, 2024

jonathannorris commented Sep 9, 2024

ahtcx commented Sep 9, 2024

LucioFranco commented Sep 9, 2024

LucioFranco commented Sep 10, 2024

strcpy_chk: symbol not found #180

strcpy_chk: symbol not found #180

Comments

Lilja commented Feb 17, 2024 • edited Loading

lovell commented Feb 25, 2024 • edited Loading

yrke commented Mar 1, 2024

penberg commented Mar 7, 2024

penberg commented Mar 11, 2024

lovell commented Mar 11, 2024

RA9 commented Mar 21, 2024

lovell commented Mar 21, 2024

ruohki commented Mar 23, 2024

flexchar commented Apr 7, 2024

lovell commented Apr 7, 2024

IsaiahByDayah commented Apr 17, 2024 • edited Loading

LukaGiorgadze commented Apr 23, 2024

steschi commented Apr 23, 2024

MikeTeddyOmondi commented May 28, 2024

LukaGiorgadze commented May 28, 2024

MikeTeddyOmondi commented May 28, 2024

jeremybarbet commented Aug 13, 2024

jeremybarbet commented Aug 13, 2024

erehwonmi commented Aug 27, 2024

brunodasilvalenga commented Aug 29, 2024 • edited Loading

erehwonmi commented Aug 29, 2024 • edited Loading

jeremybarbet commented Aug 29, 2024

ahtcx commented Sep 5, 2024

jonathannorris commented Sep 9, 2024

ahtcx commented Sep 9, 2024

LucioFranco commented Sep 9, 2024

LucioFranco commented Sep 10, 2024

Lilja commented Feb 17, 2024 •

edited

Loading

lovell commented Feb 25, 2024 •

edited

Loading

IsaiahByDayah commented Apr 17, 2024 •

edited

Loading

brunodasilvalenga commented Aug 29, 2024 •

edited

Loading

erehwonmi commented Aug 29, 2024 •

edited

Loading