The problem is that a sudo password prompt is appearing, but open nebula can't respond. Try adding a NOPASSWD clause to your sudoers file.
Tharsan On Nov 12, 2012 3:54 PM, "Bruno Parreira" <[email protected]> wrote: > Hi, > > I'm having the same problem and I've tried the proposed solution, this is > the log: > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 sudo: no tty > present and no askpass program specified > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 Sorry, try > again. > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 sudo: no tty > present and no askpass program specified > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 Sorry, try > again. > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 sudo: no tty > present and no askpass program specified > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 Sorry, try > again. > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 sudo: 3 > incorrect password attempts > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 > /var/tmp/one/vnm/802.1Q/../OpenNebulaNetwork.rb:136:in `get_interfaces': > undefined method `each' for nil:NilClass (NoMethodError) > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 from > /var/tmp/one/vnm/802.1Q/HostManaged.rb:24:in `initialize' > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 from > /var/tmp/one/vnm/802.1Q/../OpenNebulaNetwork.rb:100:in `new' > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 from > /var/tmp/one/vnm/802.1Q/../OpenNebulaNetwork.rb:100:in `from_base64' > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 from > /var/tmp/one/vnm/802.1Q/pre:24 > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 ExitCode: 1 > > Mon Nov 12 22:25:02 2012 [VMM][D]: Message received: LOG I 22 Failed to > execute network driver operation: pre. > > cheers, > Bruno > > A 2012/11/12, às 18:44, Tharsan Bhuvanendran escreveu: > > Jaime, > > It turns out this was the problem. The combination of the NOPASSWD clause > for the oneadmin user, and omitting the 'requiretty' option was the trick. > Thanks for the suggestion! > > Tharsan > > > On Mon, Nov 12, 2012 at 12:17 PM, Jaime Melis <[email protected]>wrote: > >> Hi Tharsan >> >> I think the problem is: >> Mon Nov 12 16:14:01 2012 [VMM][I]: sudo: sorry, you must have a tty to >> run sudo >> >> Can you try and remove the requiretty directive from /etc/sudoers? >> >> cheers, >> Jaime >> >> >> On Mon, Nov 12, 2012 at 6:03 PM, Tharsan Bhuvanendran < >> [email protected]> wrote: >> >>> Mon Nov 12 16:14:01 2012 [VMM][I]: sudo: sorry, you must have a tty to >>> run sudo >> >> >> >> >> -- >> Jaime Melis >> Project Engineer >> OpenNebula - The Open Source Toolkit for Cloud Computing >> www.OpenNebula.org | [email protected] >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
