Heroku + MiniMagick + ImageMagick error loading libraries
I am on Heroku using a RoR app.
I am using carrierwave and with mini_magick (imagemagick).
Everything works fine on my local server.
On heroku I get the following error:
Icon Failed to manipulate with MiniMagick, maybe it is not an image? Original Error: `identify /tmp/mini_magick20181115-4-12nnpxw.png` failed with error: identify: error while loading shared libraries: libdjvulibre.so.21: cannot open shared object file: No such file or directory
It seems libdjvulibre.so.21 is not present. I have added the buildpack for imagemagick: https://github.com/ello/heroku-buildpack-imagemagick
Any suggestions?
heroku imagemagick minimagick
asked Nov 15 '18 at 17:40
unknownunknown
285
add a comment |
I am on Heroku using a RoR app.
I am using carrierwave and with mini_magick (imagemagick).
Everything works fine on my local server.
On heroku I get the following error:
Icon Failed to manipulate with MiniMagick, maybe it is not an image? Original Error: `identify /tmp/mini_magick20181115-4-12nnpxw.png` failed with error: identify: error while loading shared libraries: libdjvulibre.so.21: cannot open shared object file: No such file or directory
It seems libdjvulibre.so.21 is not present. I have added the buildpack for imagemagick: https://github.com/ello/heroku-buildpack-imagemagick
Any suggestions?
heroku imagemagick minimagick
asked Nov 15 '18 at 17:40
unknownunknown
285
What was the command that failed? If you call convert in mini-magick, then perhaps you need to provide the full path to convert.
– fmw42
Nov 15 '18 at 21:07
I'm hitting this as well on a heroku-18 stack, with both imagemagick and image-optim buildpacks in place using carrierwave. I have a variety of versions that are using the following directives: process :resize_to_fit => [400, 400] process :convert => 'jpg' process optimize: [{ quality: 60 }]
– John Athayde
Nov 18 '18 at 0:52
devcenter.heroku.com/articles/stack-packages libdjvulibre-21 is installed as a package on heroku stacks, but it's only available at build time, not runtime.
– John Athayde
Nov 18 '18 at 1:48
fmw42 - specific command that fails (and it does so at the command line as well) isidentify.
– John Athayde
Nov 18 '18 at 16:52
If mini-magics is using ImageMagick 7, then "identify" is replace by "magick identify" and "convert" is replace by "magick"
– fmw42
Nov 20 '18 at 17:47
add a comment |
I am on Heroku using a RoR app.
I am using carrierwave and with mini_magick (imagemagick).
Everything works fine on my local server.
On heroku I get the following error:
Icon Failed to manipulate with MiniMagick, maybe it is not an image? Original Error: `identify /tmp/mini_magick20181115-4-12nnpxw.png` failed with error: identify: error while loading shared libraries: libdjvulibre.so.21: cannot open shared object file: No such file or directory
It seems libdjvulibre.so.21 is not present. I have added the buildpack for imagemagick: https://github.com/ello/heroku-buildpack-imagemagick
Any suggestions?
heroku imagemagick minimagick
asked Nov 15 '18 at 17:40
unknownunknown
285
I am on Heroku using a RoR app.
I am using carrierwave and with mini_magick (imagemagick).
Everything works fine on my local server.
On heroku I get the following error:
Icon Failed to manipulate with MiniMagick, maybe it is not an image? Original Error: `identify /tmp/mini_magick20181115-4-12nnpxw.png` failed with error: identify: error while loading shared libraries: libdjvulibre.so.21: cannot open shared object file: No such file or directory
It seems libdjvulibre.so.21 is not present. I have added the buildpack for imagemagick: https://github.com/ello/heroku-buildpack-imagemagick
Any suggestions?
heroku imagemagick minimagick
heroku imagemagick minimagick
asked Nov 15 '18 at 17:40
unknownunknown
285
asked Nov 15 '18 at 17:40
unknownunknown
285
asked Nov 15 '18 at 17:40
unknownunknown
285
asked Nov 15 '18 at 17:40
unknownunknown
285
asked Nov 15 '18 at 17:40
unknownunknown
285
285
What was the command that failed? If you call convert in mini-magick, then perhaps you need to provide the full path to convert.
– fmw42
Nov 15 '18 at 21:07
I'm hitting this as well on a heroku-18 stack, with both imagemagick and image-optim buildpacks in place using carrierwave. I have a variety of versions that are using the following directives: process :resize_to_fit => [400, 400] process :convert => 'jpg' process optimize: [{ quality: 60 }]
– John Athayde
Nov 18 '18 at 0:52
devcenter.heroku.com/articles/stack-packages libdjvulibre-21 is installed as a package on heroku stacks, but it's only available at build time, not runtime.
– John Athayde
Nov 18 '18 at 1:48
fmw42 - specific command that fails (and it does so at the command line as well) isidentify.
– John Athayde
Nov 18 '18 at 16:52
If mini-magics is using ImageMagick 7, then "identify" is replace by "magick identify" and "convert" is replace by "magick"
– fmw42
Nov 20 '18 at 17:47
add a comment |
What was the command that failed? If you call convert in mini-magick, then perhaps you need to provide the full path to convert.
– fmw42
Nov 15 '18 at 21:07
I'm hitting this as well on a heroku-18 stack, with both imagemagick and image-optim buildpacks in place using carrierwave. I have a variety of versions that are using the following directives: process :resize_to_fit => [400, 400] process :convert => 'jpg' process optimize: [{ quality: 60 }]
– John Athayde
Nov 18 '18 at 0:52
devcenter.heroku.com/articles/stack-packages libdjvulibre-21 is installed as a package on heroku stacks, but it's only available at build time, not runtime.
– John Athayde
Nov 18 '18 at 1:48
fmw42 - specific command that fails (and it does so at the command line as well) isidentify.
– John Athayde
Nov 18 '18 at 16:52
If mini-magics is using ImageMagick 7, then "identify" is replace by "magick identify" and "convert" is replace by "magick"
– fmw42
Nov 20 '18 at 17:47
What was the command that failed? If you call convert in mini-magick, then perhaps you need to provide the full path to convert.
– fmw42
Nov 15 '18 at 21:07
What was the command that failed? If you call convert in mini-magick, then perhaps you need to provide the full path to convert.
– fmw42
Nov 15 '18 at 21:07
I'm hitting this as well on a heroku-18 stack, with both imagemagick and image-optim buildpacks in place using carrierwave. I have a variety of versions that are using the following directives: process :resize_to_fit => [400, 400] process :convert => 'jpg' process optimize: [{ quality: 60 }]
– John Athayde
Nov 18 '18 at 0:52
I'm hitting this as well on a heroku-18 stack, with both imagemagick and image-optim buildpacks in place using carrierwave. I have a variety of versions that are using the following directives: process :resize_to_fit => [400, 400] process :convert => 'jpg' process optimize: [{ quality: 60 }]
– John Athayde
Nov 18 '18 at 0:52
devcenter.heroku.com/articles/stack-packages libdjvulibre-21 is installed as a package on heroku stacks, but it's only available at build time, not runtime.
– John Athayde
Nov 18 '18 at 1:48
devcenter.heroku.com/articles/stack-packages libdjvulibre-21 is installed as a package on heroku stacks, but it's only available at build time, not runtime.
– John Athayde
Nov 18 '18 at 1:48
fmw42 - specific command that fails (and it does so at the command line as well) is
identify.– John Athayde
Nov 18 '18 at 16:52
fmw42 - specific command that fails (and it does so at the command line as well) is
identify.– John Athayde
Nov 18 '18 at 16:52
If mini-magics is using ImageMagick 7, then "identify" is replace by "magick identify" and "convert" is replace by "magick"
– fmw42
Nov 20 '18 at 17:47
If mini-magics is using ImageMagick 7, then "identify" is replace by "magick identify" and "convert" is replace by "magick"
– fmw42
Nov 20 '18 at 17:47
add a comment |
1 Answer
1
active
oldest
votes
Okay, so after contacting support ("we don't deal with third party build packs") and lots of help from some friends, the solution is frustratingly simple (on heroku-18 stacks):
Delete the build pack.
Unless you need a different version than what ships (https://devcenter.heroku.com/articles/stack-packages), which is 8:6.9.7.4+dfsg-16ubuntu6.4, then just remove the pack. This worked for me on my staging environment.
answered Nov 20 '18 at 14:36
John AthaydeJohn Athayde
325110
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325112%2fheroku-minimagick-imagemagick-error-loading-libraries%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Okay, so after contacting support ("we don't deal with third party build packs") and lots of help from some friends, the solution is frustratingly simple (on heroku-18 stacks):
Delete the build pack.
Unless you need a different version than what ships (https://devcenter.heroku.com/articles/stack-packages), which is 8:6.9.7.4+dfsg-16ubuntu6.4, then just remove the pack. This worked for me on my staging environment.
answered Nov 20 '18 at 14:36
John AthaydeJohn Athayde
325110
add a comment |
Okay, so after contacting support ("we don't deal with third party build packs") and lots of help from some friends, the solution is frustratingly simple (on heroku-18 stacks):
Delete the build pack.
Unless you need a different version than what ships (https://devcenter.heroku.com/articles/stack-packages), which is 8:6.9.7.4+dfsg-16ubuntu6.4, then just remove the pack. This worked for me on my staging environment.
answered Nov 20 '18 at 14:36
John AthaydeJohn Athayde
325110
add a comment |
Okay, so after contacting support ("we don't deal with third party build packs") and lots of help from some friends, the solution is frustratingly simple (on heroku-18 stacks):
Delete the build pack.
Unless you need a different version than what ships (https://devcenter.heroku.com/articles/stack-packages), which is 8:6.9.7.4+dfsg-16ubuntu6.4, then just remove the pack. This worked for me on my staging environment.
answered Nov 20 '18 at 14:36
John AthaydeJohn Athayde
325110
Okay, so after contacting support ("we don't deal with third party build packs") and lots of help from some friends, the solution is frustratingly simple (on heroku-18 stacks):
Delete the build pack.
Unless you need a different version than what ships (https://devcenter.heroku.com/articles/stack-packages), which is 8:6.9.7.4+dfsg-16ubuntu6.4, then just remove the pack. This worked for me on my staging environment.
answered Nov 20 '18 at 14:36
John AthaydeJohn Athayde
325110
answered Nov 20 '18 at 14:36
John AthaydeJohn Athayde
325110
answered Nov 20 '18 at 14:36
John AthaydeJohn Athayde
325110
answered Nov 20 '18 at 14:36
John AthaydeJohn Athayde
325110
325110
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325112%2fheroku-minimagick-imagemagick-error-loading-libraries%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What was the command that failed? If you call convert in mini-magick, then perhaps you need to provide the full path to convert.
– fmw42
Nov 15 '18 at 21:07
I'm hitting this as well on a heroku-18 stack, with both imagemagick and image-optim buildpacks in place using carrierwave. I have a variety of versions that are using the following directives: process :resize_to_fit => [400, 400] process :convert => 'jpg' process optimize: [{ quality: 60 }]
– John Athayde
Nov 18 '18 at 0:52
devcenter.heroku.com/articles/stack-packages libdjvulibre-21 is installed as a package on heroku stacks, but it's only available at build time, not runtime.
– John Athayde
Nov 18 '18 at 1:48
fmw42 - specific command that fails (and it does so at the command line as well) is
identify.– John Athayde
Nov 18 '18 at 16:52
If mini-magics is using ImageMagick 7, then "identify" is replace by "magick identify" and "convert" is replace by "magick"
– fmw42
Nov 20 '18 at 17:47