Skip to content
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.

Wrong libc version on Debian Stretch #117

Open
turb opened this issue Jun 10, 2019 · 4 comments
Open

Wrong libc version on Debian Stretch #117

turb opened this issue Jun 10, 2019 · 4 comments
Labels

Comments

@turb
Copy link

turb commented Jun 10, 2019

After upgrading with apt on Debian 9 (stretch) from 1.5.1-2.0.1 to 1.5.3-2.0.1.debian9, mesos cannot start anymore due to:

mesos-master: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by /usr/local/lib/libmesos-1.5.3.so)

The libc version on Debian Stretch is 2.24. Debian testing is on 2.28. I think Mesos should stick to the stable version.

It's the same with 1.5.2. Downgrading to 1.5.1 fixes the issue.

Did not try with mesos 1.6+.

@tillt tillt added the bug label Jun 19, 2019
@tillt
Copy link

tillt commented Jun 19, 2019

@turb thanks for this report - have rendered a ticket out of this, so we keep it on our radar.
https://jira.mesosphere.com/browse/DCOS_OSS-5299

@lava
Copy link

lava commented Jun 20, 2019

This might be fixed by a simply rebuilding the package. I fixed Debian 9 packages pulling in stuff from debian/testing in a series of pull requests here:

https://github.com/mesosphere/mesos-ci/pull/66
https://github.com/mesosphere/mesos-ci/pull/68
https://github.com/mesosphere/mesos-ci/pull/69

but only rebuilt the Mesos 1.8 package after doing that, since that was the only version we heard complaints about at the time. Since 1.5.3 was released two months before 1.8.0, it probably suffers from the same problems.

I'll run the package build job again and ping you once it's finished, so you can test the new package.

@turb
Copy link
Author

turb commented Jun 20, 2019

Great, thanks! I will test it.

@lava
Copy link

lava commented Jul 3, 2019

Hey, sorry for dropping the ball here: The 1.5.3 rebuild was not successful due to a completely unrelated issue in our internal CI, and after that I was disrupted and kinda forgot about this. I'll probably have a bit of time to look more into this in the coming days, so hopefully this can finally be resolved then.

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

No branches or pull requests

3 participants