Hi Stephen,
You can see all the launch flags here:
http://mesos.apache.org/documentation/latest/configuration/
(or just running .../mesos-slave.sh --help)
If you launch it via systemd (which is actually how we run it ourselves in
DCOS) you will have to configure your nodes (master/agents) via
Hi, @Stephen From your slave log, could not see the restart log about
slave. Are you sure you restart slave after reboot?
On Thu, Aug 6, 2015 at 5:54 PM, Stephen Knight skni...@pivotal.io wrote:
Hi Klaus, I have attached all from a master and a slave.
I've replicated the problem over and over
My system doesn't support cat with systemctl for some reason but here is
the contents of /usr/lib/systemd/system/mesos-slave.service
[Unit]
Description=Mesos Slave
After=network.target
Wants=network.target
[Service]
ExecStart=/usr/bin/mesos-init-wrapper slave
KillMode=process
Hi Stephen,
Would you share the log of master slave?
Thanks
Klaus
On 2015年08月06日 16:07, Stephen Knight wrote:
Hi,
I was wondering if anyone can help me. I have a test setup, 1
master/zookeeper and 2 slaves on Ubuntu 14.04.
When I initialize the slaves the first time it all works and they
From this message, I think systemctl status mesos-slave.service -l run
mesos-slave with uncorrect flags. And the status out of it is the help
message of slave. Could you try to start mesos-slave in manual way? Not
through systemctl.
On Thu, Aug 6, 2015 at 6:41 PM, Stephen Knight
Hi Klaus, I have attached all from a master and a slave.
I've replicated the problem over and over again, not sure what to make of
it. First registration is fine but then if I reboot the service for
mesos-slave (process restart of full server restart) it never connects
again.
The VM's are in the
Or you could try systemctl cat mesos-slave.service and show us the file
content.
On Thu, Aug 6, 2015 at 6:49 PM, haosdent haosd...@gmail.com wrote:
From this message, I think systemctl status mesos-slave.service -l run
mesos-slave with uncorrect flags. And the status out of it is the help
The work_dir was set to /tmp/mesos by default, I've deleted it and tried to
start the slave again. The dir is not being recreated now, just a continual
service failure.
On Thu, Aug 6, 2015 at 2:59 PM, craig w codecr...@gmail.com wrote:
Have you tried clearing out the data in the slave's
Maybe you could report a issue to
https://github.com/mesosphere/mesos-deb-packaging , I afraid the package
way have some problem.
On Thu, Aug 6, 2015 at 7:12 PM, Stephen Knight skni...@pivotal.io wrote:
Ok, that's working if I run it like this: /usr/sbin/mesos-slave
Hm, need pass your master location, for example:
/usr/sbin/mesos-slave --master=x.x.x.x:5050
if you use zookeeper, need use the format like:
/usr/sbin/mesos-slave --master=zk://host1:port1,host2:port2,.../path
On Thu, Aug 6, 2015 at 6:55 PM, Stephen Knight skni...@pivotal.io wrote:
My system
10 matches
Mail list logo
