Got it. So now I just need to fix my scripts. Thanks for clarifying. -- Mateus Caruccio / Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017
2018-07-01 14:18 GMT-03:00 Clayton Coleman <[email protected]>: > That’s the one the installer lays down. Ansible has never used the one in > the RPMs (and the one in the RPMs is being removed in 3.10 to prevent > confusion). > > On Jul 1, 2018, at 10:03 AM, Mateus Caruccio <mateus.caruccio@getupcloud. > com> wrote: > > Yep, I copy/paste from an old buffer. It's /bin/nice already. Same results. > > Anyway, I believe have found the reason. Looks like > /etc/systemd/system/multi-user.target.wants is linking to the wrong unit > file (or am I editing the wrong one?). > > # ls -l /etc/systemd/system/multi-user.target.wants/origin-node.service > lrwxrwxrwx. 1 root root 39 Jul 1 13:42 /etc/systemd/system/multi- > user.target.wants/origin-node.service -> > */etc/systemd/system/origin-node.service* > > # cat /etc/systemd/system/origin-node.service > [Unit] > Description=OpenShift Node > After=docker.service > After=chronyd.service > After=ntpd.service > Wants=openvswitch.service > After=ovsdb-server.service > After=ovs-vswitchd.service > Wants=docker.service > Documentation=https://github.com/openshift/origin > Wants=dnsmasq.service > After=dnsmasq.service > > [Service] > Type=notify > EnvironmentFile=/etc/sysconfig/origin-node > Environment=GOTRACEBACK=crash > ExecStartPre=/usr/bin/cp /etc/origin/node/node-dnsmasq.conf > /etc/dnsmasq.d/ > ExecStartPre=/usr/bin/dbus-send --system --dest=uk.org.thekelleys.dnsmasq > /uk/org/thekelleys/dnsmasq uk.org.thekelleys.SetDomainServers > array:string:/in-addr.arpa/127.0.0.1,/cluster.local/127.0.0.1 > ExecStopPost=/usr/bin/rm /etc/dnsmasq.d/node-dnsmasq.conf > ExecStopPost=/usr/bin/dbus-send --system --dest=uk.org.thekelleys.dnsmasq > /uk/org/thekelleys/dnsmasq uk.org.thekelleys.SetDomainServers > array:string: > ExecStart=/usr/bin/openshift start node --config=${CONFIG_FILE} $OPTIONS > LimitNOFILE=65536 > LimitCORE=infinity > WorkingDirectory=/var/lib/origin/ > SyslogIdentifier=origin-node > Restart=always > RestartSec=5s > TimeoutStartSec=300 > OOMScoreAdjust=-999 > > [Install] > WantedBy=multi-user.target > > > After remove it, the link points to where I expect being the right unit > file: > > > # rm -f /etc/systemd/system/origin-node.service > > # systemctl disable origin-node > Removed symlink /etc/systemd/system/multi-user.target.wants/origin-node. > service. > > # systemctl enable origin-node > Created symlink from /etc/systemd/system/multi- > user.target.wants/origin-node.service to /usr/lib/systemd/system/ > origin-node.service. > > *# systemctl restart origin-node* > > # ps ax -o pid,nice,comm|grep openshift > 4994 0 openshift > 5036 -5 openshift > > > The question now is: where /etc/systemd/system/origin-node.service comes > from? > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > 2018-07-01 8:06 GMT-03:00 Tobias Florek <[email protected]>: > >> Hi! >> >> > ExecStart=nice -n -5 /usr/bin/openshift start node [...] >> >> That won't work. You need the full path to the executable in systemd >> units. >> >> Cheers, >> Tobias Florek >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
