I check the /etc/quantum/nf and /etc/quantum/quantum/rootwrap.d/ and /etc/sudoers.d/quantum, it seems no problem, I check with controller node's nova setting, it seems all are OK. I meet some problem when I put Quantum packages scripts in /etc/init.d directory and try to start Quantum packages by quantum user, when I start agent: service quantum-openvswitch-agent start, I find error in /var/log/quantum/quantum-openvswitch-agent.log: confĪfter I add them in, the quantum packages start without SUDO error. Rootwrap_ config= /etc/quantum/ rootwrap. Root_helper = sudo quantum-rootwrap /etc/quantum/ rootwrap. d/quantum, it seems no problem, I check with controller node's nova setting, it seems all are OK.įinally I find I miss below two lines in /etc/quantum/ quantum. conf and /etc/quantum/ quantum/ rootwrap. Stderr: 'sudo: no tty present and no askpass program specified\n' I meet some problem when I put Quantum packages scripts in /etc/init.d directory and try to start Quantum packages by quantum user, when I start agent: service quantum- openvswitch- agent start, I find error in /var/log/ quantum/ quantum- openvswitch- agent.log: 7/dist- packages/ quantum/ agent/linux/ utils.py", line 61, in execute py", line 407, in executeįile "/usr/lib/ python2. 7/dist- packages/ quantum/ agent/linux/ ip_lib. py", line 55, in enableįile "/usr/lib/ python2. 7/dist- packages/ quantum/ agent/linux/ external_ process. zabbixs ALL (ALL) NOPASSWD: /usr/bin/nmap -O. 7/dist- packages/ quantum/ agent/dhcp_ agent.py", line 329, in enable_ isolated_ metadata_ proxyįile "/usr/lib/ python2. Im using the 2.4 appliance and was getting this error, Ive resolved it: The issue was the Zabbix server is actually running as user zabbixs and not zabbix (the agent user) You can add teh following to /etc/sudoers or create /etc/sudoers.d/zabbixs with the following. Since options 2 and 3 require a TTY (sudo wont read from a pipe) it wont run if it cant. the user entered the correct source password. the user entered the correct target password. enable_ isolated_ metadata_ proxy(network)įile "/usr/lib/ python2. sudo will only run a program as a different user if one of these 3 conditions has been met (as far as passwords are concerned): the NOPASSWD option is specified. 7/dist- packages/ quantum/ agent/dhcp_ agent.py", line 188, in enable_dhcp_helper 7/dist- packages/ quantum/ agent/dhcp_ agent.py", line 234, in network_create_endįile "/usr/lib/ python2. py", line 242, in innerįile "/usr/lib/ python2. 7/dist- packages/ quantum/ openstack/ common/ lockutils. Return getattr(proxyobj, method)(ctxt, **kwargs)įile "/usr/lib/ python2. 7/dist- packages/ quantum/ openstack/ common/ rpc/dispatcher. dispatch( ctxt, version, method, **args)įile "/usr/lib/ python2. 7/dist- packages/ quantum/ openstack/ common/ rpc/amqp. If you installed your gitlab runner from the official apt repositories then your gitlab-runner process will run under the gitlab-runner user. And add your gitlab runner user to the bottom. 19:59:54 ERROR Exception during message handlingįile "/usr/lib/ python2. Open up the sudoers file for editing in your favorite editor. Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' I’ve tried reverting to 3.21.0 by changing the ‘’‘current’’’ link - but the error persists.19:59:54 DEBUG Ĭommand: Node: sudo: no tty present and no askpass program specified Node: #3) With great power comes great responsibility. It usually boils down to these three things: Node: We trust you have received the usual lecture from the local System If I create a link sudo ln -s /usr/bin/ghost /usr/local/bin/ghost then ghost start still fails - with a different error: node: + sudo node current/index.js Instead of running the commands sudo is trying to request the users password. Node: at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)Īnd sure enough - there is no such file - which shows that I have /usr/bin/ghost Node: at startup (internal/bootstrap/node.js:283:19) Node: at (internal/modules/cjs/loader.js:831:12) This is both secure and what you need in the majority of the use cases. Node: at Function.Module._load (internal/modules/cjs/loader.js:562:25) In the stock sudoers configuration, the following line is usually present. > sudo vim /etc/sudoers Depending on the user add at the bottom of the file: Apache can check lsof as root for cronlocalbatch.php apache ALLNOPASSWD:/. Node: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15) Syslog says: node: Error: Cannot find module '/usr/local/bin/ghost' I’ve upgraded about 20 blogs today… and all seemed peachy for a while… but now, ghost start is not returning - it loops at the sudo systemctl start ghost_.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |