[
https://issues.apache.org/jira/browse/MESOS-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167933#comment-16167933
]
Martin Tapp commented on MESOS-7518:
------------------------------------
I've isolated that a new pip package (installed to both pip2 and pip3) causes
the problem.
Any idea why a mesos-slave or mesos-master would become invalidated, even
having their apt packages uninstalled by Ubuntu 16.04? This never happens on
nodes that don't have pip2/pip3 packages installed.
> Mesos master and slave get uninstalled by ubuntu 16.04
> ------------------------------------------------------
>
> Key: MESOS-7518
> URL: https://issues.apache.org/jira/browse/MESOS-7518
> Project: Mesos
> Issue Type: Bug
> Components: agent, master
> Affects Versions: 1.2.0
> Environment: Ubuntu 16.04
> Reporter: Martin Tapp
>
> Since we've upgraded to Mesos 1.2 (from 1.0) on Ubuntu 16.04, the master and
> agent/slave sometimes get uninstalled automatically. This always happens
> after a reboot, when you restart the service, and maybe every other day
> otherwise on it's own. We're running on bare metal servers and VMs with the
> same result.
> sudo service mesos-master status yields
> Warning: mesos-master.service changed on disk. Run 'systemctl daemon-reload'
> to reload units.
> Same for mesos-slave.
> Solution is to re-run our mesos provisioning automatically. apt-get install
> mesos re-installs it all the time.
> We're using apt source 'deb http://repos.mesosphere.io/ubuntu xenial main'
> with key
> 'http://keyserver.ubuntu.com/pks/lookup?op=get&fingerprint=on&search=0xE56151BF'
> Any idea?
> Thanks
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
