I'm guessing you mis-configured a master flag/environment-variable somewhere. Since it looks like you're using systemd, can you run this command, "journalctl -xe", right after you try to start the service? That should show you more info on why your master aborted.
On Fri, Jun 10, 2016 at 8:50 AM, Jie Yu <yujie....@gmail.com> wrote: > Can u create a jira ticket and paste the master log? Thanks for reporting! > > Sent from my iPhone > > On Jun 10, 2016, at 8:44 AM, Stefano Bianchi <jazzist...@gmail.com> wrote: > > Hi all > i'm re installing my platform on another openstack tenant. > I downloaded all the needed softwares, zookeeper-server, mesos 0.28.2 > marathon 1.1.1 and chronos 2.4.0. > i have configured all correctly the i started zookeeper-server and it > works fine. > when i type: service mesos-master start > it seems to start but if i check the status with: service mesos-master > status > i obtain the following: > > [root@master ~]# service mesos-master status > > Redirecting to /bin/systemctl status mesos-master.service > > ● mesos-master.service - Mesos Master > > Loaded: loaded (/usr/lib/systemd/system/mesos-master.service; enabled; > vendor preset: disabled) > > Active: activating (auto-restart) (Result: signal) since ven 2016-06-10 > 15:39:36 UTC; 3s ago > > Process: 12163 ExecStart=/usr/bin/mesos-init-wrapper master *(code=killed, > signal=ABRT)* > > Main PID: 12163 (code=killed, signal=ABRT) > > > Any one knows why i have this issue? > > Thanks in advance. > >
