You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jean-Baptiste (JIRA)" <ji...@apache.org> on 2017/10/05 12:44:00 UTC

[jira] [Comment Edited] (MESOS-2923) fetcher.cpp - problem with certificates..?

    [ https://issues.apache.org/jira/browse/MESOS-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192712#comment-16192712 ] 

Jean-Baptiste edited comment on MESOS-2923 at 10/5/17 12:43 PM:
----------------------------------------------------------------

Hi guys, FYI I've opened a pull request to fix it on Debian:

https://github.com/mesosphere/mesos-deb-packaging/pull/111 

Maybe it can be reviewed by [~bernd-mesos] :D


was (Author: jibek):
Hi guys, FYI I've opened a pull request to fix it on Debian:

https://github.com/mesosphere/mesos-deb-packaging/pull/111 

> fetcher.cpp - problem with certificates..?
> ------------------------------------------
>
>                 Key: MESOS-2923
>                 URL: https://issues.apache.org/jira/browse/MESOS-2923
>             Project: Mesos
>          Issue Type: Bug
>    Affects Versions: 0.22.0, 0.22.1
>         Environment: Ubuntu 14.04 (build + test)
>            Reporter: Tomasz Mieszkowski
>            Assignee: Bernd Mathiske
>              Labels: bugs, fetcher, https, mesosphere
>
> Mesos 0.22.0/0.22.1 built and installed from sources accordingly to the instructions given [here|http://mesos.apache.org/gettingstarted/] has some problem with certificates.
> Every time I try to deploy something that requires downloading any resource via HTTPS (with URI specified via Marathon), such deployment fails and I get this message in failed app's sandbox:
> {code}
> E0617 09:58:44.339409 12380 fetcher.cpp:138] Error downloading resource: Problem with the SSL CA cert (path? access rights?)
> {code}
> Trying to download the same resource on the same slave with {{curl}} or {{wget}} works without problems.
> Moreover, when I install exactly the same version of Mesos from Mesosphere's debs on identical machines (i.e., set up by the same Ansible scripts), everything works fine as well.
> I guess it must be something related to the way how Mesos is built - maybe some missing switch for {{configure}} or {{make}}..?
> Any ideas..?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)