Détail du message 81937.32

Message numéro 32 dans le sujet RBS Change version V4.0.

  • 81937.32 en réponse à 81937.31 écrit par Mathias

    21/03/2014 12:33


    edwige.lr@wanadoo.fr
    Rang : Adepte
    Bonjour,

    Nous avons suivi à la lettre vos conseils.
    Nous rencontrons une difficulté pour finaliser l'installation après avoir exécuter 'vaganrt up'.

    Avez-vous une idée du problème?

    Nous sommes sous windows 8.1 pro

    Par avance merci, cordialement

    edwige@STATIONIBM ~/Doc/rbschange/c4vagrant (master)
    $ vagrant up
    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Importing base box 'saucy64change'...
    ==> default: Matching MAC address for NAT networking...
    ==> default: Setting the name of the VM: c4vagrant_default_1395400183200_93624
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
    ==> default: Forwarding ports...
    default: 80 => 8080 (adapter 1)
    default: 9200 => 9200 (adapter 1)
    default: 22 => 2222 (adapter 1)
    ==> default: Booting VM...
    ==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Error: Connection timeout. Retrying....
    ........................
    default: Error: Connection refused. Retrying...
    ..........................
    default: Error: Connection refused. Retrying...
    ..........................
    default: Error: Connection refused. Retrying...
    Timed out while waiting for the machine to boot. This means that
    Vagrant was unable to communicate with the guest machine within
    the configured ("config.vm.boot_timeout" value) time period.

    If you look above, you should be able to see the error(s) that
    Vagrant had when attempting to connect to the machine. These errors
    are usually good hints as to what may be wrong.

    If you're using a custom box, make sure that networking is properly
    working and you're able to connect to the machine. It is a common
    problem that networking isn't setup properly in these boxes.
    Verify that authentication configurations are also setup properly,
    as well.

    If the box appears to be booting properly, you may want to increase
    the timeout ("config.vm.boot_timeout") value.

    edwige@STATIONIBM ~/Documents/rbschange/c4vagrant (master)
    $
 
1471 membres
Aucun membre connecté