Databases
StackOverflow2013
Postsdbo
POvagrant up fails with sed error message
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POvagrant up fails with sed error message
    primarykey
    data
    text
    <p>Hello my vagrant starts failing boot with this message</p> <p>The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!</p> <p>sed -e '/^#VAGRANT-BEGIN/,/^#VAGRANT-END/ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces.</p> <p>The vagrant boots, but the puppet manifests are not applied.</p> <p>any suggestions how to fix it</p> <p>Update: The vagrant up command fails before starting applying puppet manifests.</p> <blockquote> <p>INFO interface: info: Configuring and enabling network interfaces... [default] Configuring and enabling network interfaces... DEBUG ssh: Checking whether SSH is ready... DEBUG ssh: Re-using SSH connection. INFO ssh: SSH is ready! INFO guest: Detect guest for machine:</p> <h1> DEBUG guest: Trying: pld DEBUG ssh: Re-using SSH connection. INFO ssh: Execute: cat /etc/pld-release</h1> <p>(sudo=false) DEBUG ssh: stderr: cat: /etc/pld-release DEBUG ssh: stderr: : No such file or directory</p> <p>DEBUG ssh: Exit status: 1 DEBUG guest: Trying: suse DEBUG ssh: Re-using SSH connection. INFO ssh: Execute: cat /etc/SuSE-release (sudo=false) DEBUG ssh: stderr: cat: /etc/SuSE-release DEBUG ssh: stderr: : No such file or directory</p> <p>DEBUG ssh: Exit status: 1 DEBUG guest: Trying: fedora DEBUG ssh: Re-using SSH connection. INFO ssh: Execute: grep 'Fedora release 1[678]' /etc/redhat-release (sudo=false) DEBUG ssh: stderr: grep: /etc/redhat-release DEBUG ssh: stderr: : No such file or directory</p> <p>DEBUG ssh: Exit status: 2 DEBUG guest: Trying: ubuntu DEBUG ssh: Re-using SSH connection. INFO ssh: Execute: cat /proc/version | grep 'Ubuntu' (sudo=false) DEBUG ssh: stdout: Linux version 3.2.0-32-generic (buildd@batsu) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012</p> <p>DEBUG ssh: Exit status: 0 INFO guest: Detected: ubuntu! INFO guest: Full guest chain: [[:ubuntu,</p> <h1>], [:debian, #], [:linux, #]] INFO guest: Execute capability: configure_networks (ubuntu) DEBUG guest: Searching for</h1> <p>cap: configure_networks DEBUG guest: Checking in: ubuntu DEBUG guest: Checking in: debian DEBUG guest: Found cap: configure_networks in debian DEBUG ssh: Re-using SSH connection. INFO ssh: Execute: sed -e '/^#VAGRANT-BEGIN/,/^#VAGRANT-END/ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces (sudo=true) DEBUG ssh: stderr: sudo: no tty present and no askpass program specified</p> <p>DEBUG ssh: stderr: Sorry, try again.</p> <p>DEBUG ssh: stderr: sudo: no tty present and no askpass program specified</p> <p>DEBUG ssh: stderr: Sorry, try again. sudo: no tty present and no askpass program specified Sorry, try again. sudo: 3 incorrect password attempts</p> <p>DEBUG ssh: Exit status: 1 ERROR warden: Error occurred: The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed!</p> <p>sed -e '/^#VAGRANT-BEGIN/,/^#VAGRANT-END/ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USedwinallenz
    1. USedwinallenz
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COHave you tried `VAGRANT_LOG=debug vagrant up` and see more output? What kind of Puppet manifests are you running, better put them in the question.
      singulars
      1. POvagrant up fails with sed error message
      1. USTerry Wang
    2. COSame error as => http://stackoverflow.com/questions/18644693/vagrant-does-not-start-correctly-and-not-mount-shared-folders
      singulars
      1. POvagrant up fails with sed error message
      1. USTerry Wang
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload