This may be related to the systemd support we added in 0.25. If the agent detects it is running on systemd it will try to launch a systemd slice under which to run the executors. If your non-root user does not have sufficient permissions to perform these operations that will be a problem. Can you share the agent logs to verify this? You should be able to access them using journalctl.
Joris — *Joris Van Remoortere* Mesosphere On Wed, Oct 28, 2015 at 12:33 PM, haosdent <[email protected]> wrote: > does mesos slave have any log? > > On Wed, Oct 28, 2015 at 11:42 PM, Rodrick Brown <[email protected]> > wrote: > >> After I upgraded the first thing I notice is that permissions on wrapper >> script >> >> # ls -al /usr/bin/mesos-init-wrapper >> -rwxr-x---. 1 root root 5202 Oct 12 21:08 /usr/bin/mesos-init-wrapper >> >> So systemd was unable to EXEC this script >> >> So I changed the perms on this wrapper >> # chmod a+x /usr/bin/mesos-init-wrapper >> >> >> However I’m still unable to bring up the process via systemd >> >> Oct 28 15:39:27 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> Started Mesos Slave. >> Oct 28 15:39:27 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> Starting Mesos Slave... >> Oct 28 15:39:27 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> mesos-slave.service: main process exited, code=exited, status=126/n/a >> Oct 28 15:39:27 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: Unit >> mesos-slave.service entered failed state. >> Oct 28 15:39:27 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> mesos-slave.service failed. >> Oct 28 15:39:47 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> mesos-slave.service holdoff time over, scheduling restart. >> Oct 28 15:39:47 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> Started Mesos Slave. >> Oct 28 15:39:47 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> Starting Mesos Slave... >> Oct 28 15:39:47 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> mesos-slave.service: main process exited, code=exited, status=126/n/a >> Oct 28 15:39:47 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: Unit >> mesos-slave.service entered failed state. >> Oct 28 15:39:47 prod-mesos-s-1.aws.orchardplatform.com systemd[1]: >> mesos-slave.service failed. >> >> # cat /usr/lib/systemd/system/mesos-slave.service >> [Unit] >> Description=Mesos Slave >> After=network.target >> Wants=network.target >> >> [Service] >> User=mesos >> ExecStart=/usr/bin/mesos-init-wrapper slave >> KillMode=process >> Restart=always >> RestartSec=20 >> LimitNOFILE=16384 >> CPUAccounting=true >> MemoryAccounting=true >> >> [Install] >> WantedBy=multi-user.target >> >> The only change I made to the unit file was add User=mesos this worked in >> previous versions of mesos. >> >> If remove User=mesos and have systemd bring the process up as root the >> slave joins the cluster and everything works as designed. >> Was something changed in 0.24.1 and 0.25 ? >> >> Thanks. >> >> >> -- >> >> [image: Orchard Platform] <http://www.orchardplatform.com/> >> >> Rodrick Brown / DevOPs Engineer >> +1 917 445 6839 / [email protected] >> <[email protected]> >> >> Orchard Platform >> 101 5th Avenue, 4th Floor, New York, NY 10003 >> http://www.orchardplatform.com >> >> Orchard Blog <http://www.orchardplatform.com/blog/> | Marketplace >> Lending Meetup <http://www.meetup.com/Peer-to-Peer-Lending-P2P/> >> >> >> *NOTICE TO RECIPIENTS*: This communication is confidential and intended >> for the use of the addressee only. If you are not an intended recipient of >> this communication, please delete it immediately and notify the sender >> by return email. Unauthorized reading, dissemination, distribution or >> copying of this communication is prohibited. This communication does not >> constitute >> an offer to sell or a solicitation of an indication of interest to purchase >> any loan, security or any other financial product or instrument, nor is it >> an offer to sell or a solicitation of an indication of interest to purchase >> any products or services to any persons who are prohibited from receiving >> such information under applicable law. The contents of this communication >> may not be accurate or complete and are subject to change without notice. >> As such, Orchard App, Inc. (including its subsidiaries and affiliates, >> "Orchard") makes no representation regarding the accuracy or >> completeness of the information contained herein. The intended recipient is >> advised to consult its own professional advisors, including those >> specializing in legal, tax and accounting matters. Orchard does not >> provide legal, tax or accounting advice. >> > > > > -- > Best Regards, > Haosdent Huang >
