/tmp/instdir/program/soffice.bin: error while loading shared libraries: libmergedlo.so: cannot open shared object file: No such file or directory
See original GitHub issueHello, I am having problems when converting files to pdf in lambda using the eu-west-1 layer (https://github.com/shelfio/libreoffice-lambda-layer, tried both gzip and brotli options). I am using the 3.0.0 version of @shelf/aws-lambda-libreoffice. I use AWS SAM to deploy the lambda to AWS and the strange thing is that there are no problems locally. This is the error that I get when trying to convert a file:
{
"errorType": "Error",
"errorMessage": "Command failed: cd /tmp && /tmp/instdir/program/soffice.bin --headless --invisible --nodefault --view --nolockcheck --nologo --norestore --nofirststartwizard --convert-to pdf --outdir /tmp /tmp/dog.png\n/tmp/instdir/program/soffice.bin: error while loading shared libraries: libmergedlo.so: cannot open shared object file: No such file or directory\n",
"trace": [
"Error: Command failed: cd /tmp && /tmp/instdir/program/soffice.bin --headless --invisible --nodefault --view --nolockcheck --nologo --norestore --nofirststartwizard --convert-to pdf --outdir /tmp /tmp/dog.png",
"/tmp/instdir/program/soffice.bin: error while loading shared libraries: libmergedlo.so: cannot open shared object file: No such file or directory",
"",
" at checkExecSyncError (child_process.js:629:11)",
" at execSync (child_process.js:666:13)",
" at convertTo (/var/task/node_modules/@shelf/aws-lambda-libreoffice/lib/convert.js:39:40)",
" at process._tickCallback (internal/process/next_tick.js:68:7)"
]
}
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Error while loading shared libraries · Issue #41 - GitHub
Lambda says /tmp/instdir/program/soffice.bin: error while loading shared libraries: libmergedlo.so: cannot open shared object file: No such ...
Read more >cannot open shared object file: No such file or directory
Your library is a dynamic library. You need to tell the operating system where it can locate it at runtime. To do so,...
Read more >error while loading shared libraries: libssacsc.so - Search
"error while loading shared libraries: libssacsc.so: cannot open shared object file: No such file or directory" while running the "dblist" ...
Read more >Open a case - IBM
Support Forums. Back to forums home ./example: error while loading shared libraries: libodbc.so: cannot open shared object file: No such file or directory....
Read more >libsslcosa.so: cannot open shared object file: No such file or ...
srvrupgwiz Fails With "error while loading shared libraries: libsslcosa.so: cannot open shared object file: No such file or directory" (Doc ID ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Upgrading to node 12.x did not change anything, error remains the same.
10x version can’t run this code, sorry, try 12+ 😉 if you want to use it with node10, you can fork this repo and simply rework unpacking function, or even use the old one, from brotli unpacker for older version.