GithubHelp home page GithubHelp logo

mage2_vagrant's People

Contributors

mattdunbar avatar morgon avatar mzeis avatar rgranadino avatar rikwillems avatar schrank avatar steig avatar steverobbins avatar therouv avatar tonegolf71 avatar vinai avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mage2_vagrant's Issues

error during install (Step 6) and successful fix

Thanks for your very clear readme file @rgranadino ! This is my first vagrant install outside of work.
So here's the deal:
Everything worked just fine until I did the Magento install process, and according to the console.log below the progress bar ( at mage2.dev/install ), We failed during catalog products installation. There was an error but I don't recall the exact wording. At this point I didn't think to try pressing the "Try Again" button at the top.

Oh, and also the "install sample data" checkbox was grayed out (I remember getting a sick feeling that something was going to go wrong...)

Then I found this video:
https://www.youtube.com/watch?v=d_31MyPT1YI - and go to 11:21 on the time

You'll see he's adding "magento/sample-data" and "magento/sample-data-media" in the require portion of composer.json. So I did that in your composer.json file as well.

Ran the entire process from scratch just to be sure, and this time:

  1. I still got a halt in the progress bar at Installing catalog data at about 67%, but with no error message
  2. I then had the bright idea to try the "Try again" button. This got me to like 96% and it stopped with "Installing catalog search" and stopped again
  3. One more click of the "Try Again" button and it was successfully installed.

Perhaps adding these two sample-data required lines will be helpful, but the Readme should also mention the "Try Again" button. Typical Magento ;) ..

Could not find declared class composer

Hi beep,

I'm a bit of a newbie with Vagrant but getting this error on OS X. Do you know if this is a system issue or box issue?

Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:75 on node mage2.dev

Thanks!
Wilson

nfs mount error on mac osx

hi-

when running vagrant up, i'm seeing the following errors:

[default] Setting hostname...
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /tmp/vagrant-puppet/manifests
[default] -- /tmp/vagrant-puppet/modules-0
[default] Exporting NFS shared folders...
Preparing to edit /etc/exports. Administrator privileges will be required...
[default] Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o 'vers=3,udp' 192.168.56.1:'/Users/lfolco/Sites/study/magento/magento2/vagrant' /vagrant

Stdout from the command:


Stderr from the command:

stdin: is not a tty
mount: wrong fs type, bad option, bad superblock on 192.168.56.1:/Users/lfolco/Sites/study/magento/magento2/vagrant,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

it seems as if it's attempting to mount the folder before nfs-common is installed?

Please Update Your Database - Error

Hi,

I am trying to get this set up, I am on Mac OSX 10.10.1, and this is the error I am getting when I visit mage2.dev

Please update your database: Run "php –f index.php update" from the Magento root/setup directory.
The following modules are outdated:
Magento_Store schema: current version - 2.0.0.0, required version - 2.0.0
Magento_Store data: current version - 2.0.0.0, required version - 2.0.0
Magento_Cms schema: current version - 2.0.0.1, required version - 2.0.0
Magento_Cms data: current version - 2.0.0.1, required version - 2.0.0
Magento_AdminNotification schema: current version - 2.0.0.0, required version - 2.0.0
Magento_AdminNotification data: current version - 2.0.0.0, required version - 2.0.0
#0 [internal function]: Magento\Framework\Module\Plugin\DbStatusValidator->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#1 /vagrant/data/magento2/lib/internal/Magento/Framework/Interception/Chain/Chain.php(62): call_user_func_array(Array, Array)
#2 /vagrant/data/magento2/lib/internal/Magento/Framework/Interception/Chain/Chain.php(57): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\\Framewo...', 'dispatch', Object(Magento\Framework\App\FrontController\Interceptor), Array, 'front-controlle...')
#3 /vagrant/data/magento2/app/code/Magento/PageCache/Model/App/FrontController/VarnishPlugin.php(53): Magento\Framework\Interception\Chain\Chain->Magento\Framework\Interception\Chain\{closure}(Object(Magento\Framework\App\Request\Http))
#4 [internal function]: Magento\PageCache\Model\App\FrontController\VarnishPlugin->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#5 /vagrant/data/magento2/lib/internal/Magento/Framework/Interception/Chain/Chain.php(62): call_user_func_array(Array, Array)
#6 /vagrant/data/magento2/var/generation/Magento/Framework/App/FrontController/Interceptor.php(90): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\\Framewo...', 'dispatch', Object(Magento\Framework\App\FrontController\Interceptor), Array, 'front-controlle...')
#7 /vagrant/data/magento2/app/code/Magento/PageCache/Model/App/FrontController/BuiltinPlugin.php(71): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\App\FrontController\{closure}(Object(Magento\Framework\App\Request\Http))
#8 [internal function]: Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch(Object(Magento\Framework\App\FrontController\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#9 /vagrant/data/magento2/var/generation/Magento/Framework/App/FrontController/Interceptor.php(95): call_user_func_array(Array, Array)
#10 /vagrant/data/magento2/var/generation/Magento/Framework/App/FrontController/Interceptor.php(119): Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', Array, Array)
#11 /vagrant/data/magento2/lib/internal/Magento/Framework/App/Http.php(114): Magento\Framework\App\FrontController\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#12 /vagrant/data/magento2/lib/internal/Magento/Framework/App/Bootstrap.php(244): Magento\Framework\App\Http->launch()
#13 /vagrant/data/magento2/index.php(38): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http))
#14 {main}

I went into /setup/ and ran php -f index.php update and it ran through the list with no errors, but this error message continues to stay up.

Any ideas?

Following setup - images, js, css, fonts missing

Hi,

I have followed the setup instructions.
At the step 7 I realised that composer was not installed so installed it manually following the instructions on composer homepage.
Than I was able to finish all the steps of the setup.
At the step 8 I installed Magento 2 with sample data (reinstall -s). I am able to access the frontend and backend. Unfortunately images, js, css, fonts are missing in both systems.
Did anybody else had this problem?

"Installation is incomplete." during Step 6: Install

Hello!

Operations go smoothly until the final step of the setup, failing at 65%
Console Log doesn't speak so much, last line being "Installing user configuration..."

image

Have you any idea what it could be? My host environment is Windows 8.1

I also have a strange issue while trying to use "reinstall" command
image

Have good day,

Henry

Extremely slow

Loading the frontend is taking (with demo data) over 10 seconds. Also seems to not load/render page using correct css. no 404's that i can find.

Admin is responding quickly.... Not sure what has caused this.

Installing NFS client stack process

Im using Mac Os X Yosemite and cloned magento 2 from repository on git.
When im going to run vagrant up executing command stack at installing nfs client ....

Thank you

Sample data Disabled Problem

After install your image , then check our site. It shows without sample data, then I check Admin page ,It show sample data are disabled.

disable sample data

I try to enable this sample data, but it throw some Configuration Problem,

error

error2

But, couple of week before I install same image, but no error.

Now, show errors and some php Setting problem ,if php problem means how work magento 2? and How to solve this problem.

Thanks in advance.

It is not mounting etc/ folder

I have Vagrant 1.9, and MacOS Sierra.
I run the bash init_project.sh on the step of "Initializing vagrant box [init_project.sh]" it stays for some minutes and then it displays this error:

Directory '/my/path/vagrant-magento/etc' was not mounted as expected by Vagrant.
        Please make sure that 'paliarush/magento2.ubuntu' Vagrant box was downloaded successfully (if not, this may help http://stackoverflow.com/questions/35519389/vagrant-cannot-find-box)
        And that Vagrant is able to mount VirtualBox shared folders on your environment (see https://www.vagrantup.com/docs/synced-folders/basic_usage.html )

I removed the symlink as described on http://stackoverflow.com/questions/35519389/vagrant-cannot-find-box, and I have even downloaded the box by running vagrant box add paliarush/magento2 but I still get the error. Any guesses?

Upgrade to debian jessie, puppet 4, php7

Find a new base vagrant box that's based on the latest stable version of Debian (jessie) which includes puppet 4.

The main bit of work will be migrating the existing puppet manifests to new format.

Cannot access database through Sequel Pro

I seem to have a problem accessing the database with the box running. This is the error I get when trying to connect using Sequel Pro. Do you have any suggestions?

screen shot 2015-12-02 at 16 52 12

Installation Exception - 'Area code is not set' in

I am trying to install Magento2 by using command line.

I did execute this command reinstall -s

I am getting following exception and can not install sample data.

Please help me to fix this issue.

[SUCCESS]: Magento installation complete.
/vagrant/data/magento2
Installing sample data...
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files
exception 'Magento\Framework\Exception\LocalizedException' with message 'Area code is not set' in /vagrant/data/magento2/lib/internal/Magento/Framework/App/State.php:154
Stack trace:
#0 /vagrant/data/magento2/lib/internal/Magento/Framework/Session/SessionManager.php(173): Magento\Framework\App\State->getAreaCode()
#1 /vagrant/data/magento2/lib/internal/Magento/Framework/Session/SessionManager.php(130): Magento\Framework\Session\SessionManager->start()
#2 /vagrant/data/magento2/app/code/Magento/Backend/Model/Auth/Session.php(98): Magento\Framework\Session\SessionManager->__construct(Object(Magento\Framework\App\Request\Http), Object(Magento\Framework\Session\SidResolver\Proxy), Object(Magento\Framework\Session\Config), Object(Magento\Framework\Session\SaveHandler), Object(Magento\Framework\Session\Validator), Object(Magento\Framework\Session\Storage), Object(Magento\Framework\Stdlib\Cookie\PhpCookieManager), Object(Magento\Framework\Stdlib\Cookie\CookieMetadataFactory), Object(Magento\Framework\App\State))
#3 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(148): Magento\Backend\Model\Auth\Session->__construct(Object(Magento\Framework\App\Request\Http), Object(Magento\Framework\Session\SidResolver\Proxy), Object(Magento\Framework\Session\Config), Object(Magento\Framework\Session\SaveHandler), Object(Magento\Framework\Session\Validator), Object(Magento\Framework\Session\Storage), Object(Magento\Framework\Stdlib\Cookie\PhpCookieManager), Object(Magento\Framework\Stdlib\Cookie\CookieMetadataFactory), Object(Magento\Framework\App\State), Object(Magento\Framework\Acl\Builder\Proxy), Object(Magento\Backend\Model\Url), Object(Magento\Backend\App\Config))
#4 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(91): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Magento\Backend...', Array)
#5 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Backend...')
#6 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(236): Magento\Framework\ObjectManager\ObjectManager->get('Magento\Backend...')
#7 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\Backend...', NULL, 'session', 'Magento\Tools\S...')
#8 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(84): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('Magento\Tools\S...', Array, Array)
#9 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Tools\S...')
#10 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(236): Magento\Framework\ObjectManager\ObjectManager->get('Magento\Tools\S...')
#11 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\Tools\S...', NULL, 'installer', 'Magento\Tools\S...')
#12 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(84): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('Magento\Tools\S...', Array, Array)
#13 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(57): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Tools\S...', Array)
#14 /vagrant/data/magento2/lib/internal/Magento/Framework/App/Bootstrap.php(220): Magento\Framework\ObjectManager\ObjectManager->create('Magento\Tools\S...', Array)
#15 /vagrant/data/magento2/dev/tools/Magento/Tools/SampleData/install.php(29): Magento\Framework\App\Bootstrap->createApplication('Magento\Tools\S...', Array)
#16 {main}

Next exception 'Magento\Framework\Exception\SessionException' with message 'Area code not set: Area code must be set before starting a session.' in /vagrant/data/magento2/lib/internal/Magento/Framework/Session/SessionManager.php:175
Stack trace:
#0 /vagrant/data/magento2/lib/internal/Magento/Framework/Session/SessionManager.php(130): Magento\Framework\Session\SessionManager->start()
#1 /vagrant/data/magento2/app/code/Magento/Backend/Model/Auth/Session.php(98): Magento\Framework\Session\SessionManager->__construct(Object(Magento\Framework\App\Request\Http), Object(Magento\Framework\Session\SidResolver\Proxy), Object(Magento\Framework\Session\Config), Object(Magento\Framework\Session\SaveHandler), Object(Magento\Framework\Session\Validator), Object(Magento\Framework\Session\Storage), Object(Magento\Framework\Stdlib\Cookie\PhpCookieManager), Object(Magento\Framework\Stdlib\Cookie\CookieMetadataFactory), Object(Magento\Framework\App\State))
#2 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(148): Magento\Backend\Model\Auth\Session->__construct(Object(Magento\Framework\App\Request\Http), Object(Magento\Framework\Session\SidResolver\Proxy), Object(Magento\Framework\Session\Config), Object(Magento\Framework\Session\SaveHandler), Object(Magento\Framework\Session\Validator), Object(Magento\Framework\Session\Storage), Object(Magento\Framework\Stdlib\Cookie\PhpCookieManager), Object(Magento\Framework\Stdlib\Cookie\CookieMetadataFactory), Object(Magento\Framework\App\State), Object(Magento\Framework\Acl\Builder\Proxy), Object(Magento\Backend\Model\Url), Object(Magento\Backend\App\Config))
#3 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(91): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Magento\Backend...', Array)
#4 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Backend...')
#5 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(236): Magento\Framework\ObjectManager\ObjectManager->get('Magento\Backend...')
#6 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\Backend...', NULL, 'session', 'Magento\Tools\S...')
#7 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(84): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('Magento\Tools\S...', Array, Array)
#8 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(71): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Tools\S...')
#9 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/AbstractFactory.php(236): Magento\Framework\ObjectManager\ObjectManager->get('Magento\Tools\S...')
#10 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(53): Magento\Framework\ObjectManager\Factory\AbstractFactory->resolveArgument(Array, 'Magento\Tools\S...', NULL, 'installer', 'Magento\Tools\S...')
#11 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/Factory/Dynamic/Developer.php(84): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->_resolveArguments('Magento\Tools\S...', Array, Array)
#12 /vagrant/data/magento2/lib/internal/Magento/Framework/ObjectManager/ObjectManager.php(57): Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create('Magento\Tools\S...', Array)
#13 /vagrant/data/magento2/lib/internal/Magento/Framework/App/Bootstrap.php(220): Magento\Framework\ObjectManager\ObjectManager->create('Magento\Tools\S...', Array)
#14 /vagrant/data/magento2/dev/tools/Magento/Tools/SampleData/install.php(29): Magento\Framework\App\Bootstrap->createApplication('Magento\Tools\S...', Array)
#15 {main}vagrant@mage2:/vagrant/data/magento2$ clear

vagrant@mage2:/vagrant/data/magento2$ clear

~/bin/reinstall Throws Error - Mac Users

I stumbled upon not being able to run the "reinstall" command from the instructions in my mac and had to run a ":set fileformat=unix" in vim on the file to make it work. Looks like it's using Windows line endings.

Error retrieved was as follows:
vagrant@mage2:~$ reinstall
-bash: /home/vagrant/bin/reinstall: /bin/bash^M: bad interpreter: No such file or directory

Can't update/install submodule

➜ mage2_vagrant git:(master) ✗ git submodule update --init
Cloning into 'data/webgrind'...
Warning: Permanently added the RSA host key for IP address '192.30.252.129' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Clone of '[email protected]:jokkedk/webgrind.git' into submodule path 'data/webgrind' failed

failed: Operation timed out.

After I installed the vm and magento by following the instructions in the README, everything went smoothly, but when trying to access http://mage2.dev in my browser I got Operation timed out.
I have also tried wget -d from the host machine and I got this:
URI encoding = ‘US-ASCII’
--2014-12-29 15:12:07-- http://mage2.dev/
Resolving mage2.dev (mage2.dev)... 192.168.56.19
Caching mage2.dev => 192.168.56.19
Connecting to mage2.dev (mage2.dev)|192.168.56.19|:80... Closed fd 4
failed: Operation timed out.
Releasing 0x00007fa949f01750 (new refcount 1).
Retrying.

Force uninstalling on reinstall step

I've got the following error in the 8th step:

Console:
vagrant@mage2:~/.composer$ reinstall -s
rm: cannot remove `var/.maintenance.flag': No such file or directory
[+] Composer...
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating autoload files
Deprecation Notice: The callback MagentoHackathon\Composer\Magento\Plugin::onNewCodeEvent declared at /vagrant/data/magento2/vendor/ magento/magento-composer-installer/src/MagentoHackathon/Composer/Magento/Plugin.php accepts a Composer\Script\CommandEvent but post- install-cmd events use a Composer\Script\Event instance. Please adjust your type hint accordingly, see https://getcomposer.org/doc/a rticles/scripts.md#event-classes in phar:///usr/local/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:289
[+] Uninstalling...
Starting Magento uninstallation:
Cache cleared successfully
No database connection defined - skipping database cleanup
File system cleanup:
/vagrant/data/magento2/var/cache
/vagrant/data/magento2/var/composer_home
/vagrant/data/magento2/var/generation
/vagrant/data/magento2/var/page_cache
The file '/vagrant/data/magento2/app/etc/config.php' doesn't exist - skipping cleanup
The file '/vagrant/data/magento2/app/etc/env.php' doesn't exist - skipping cleanup
[SUCCESS]: Magento uninstallation complete.
[+] Installing...
/home/vagrant/bin/reinstall: line 68: ./bin/magento: Permission denied
/home/vagrant/.composer

Anybody with this issue? Any help? Thanks

Sample data installation no longer works

The method of installing the sample data has changed. It no longer works as with Magento 1.
It first has to be added as a composer dependency, and after the package is installed an install script needs to be executed

composer config repositories.magento composer http://packages.magento.com
composer require magento/sample-data:0.42.0-beta6 magento/sample-data-media:0.42.0-beta1 --dev
php -f dev/tools/Magento/Tools/SampleData/install.php -- --admin_username=admin

More information:
http://devdocs.magento.com/guides/v1.0/install-gde/install/sample-data.html

Error in composer install;

Failed to download magento/zendframework1 from dist: Could not delete /vagrant/data/magento2/vendor/magento/zendframework1/b8d6ff6d1ec1eb071287a0d71a425387: date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.
Now trying to download from source

  • Installing magento/zendframework1 (1.12.10)
    Cloning d1e5cd8c9f83229bcdd9bb485c3ce25259c77884

    [RuntimeException]
    Failed to clone [email protected]:magento/zf1.git, git was not found, check that it is installed and in your PATH env.
    sh: 1: git: not found

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-plugins] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [--ignore-platform-reqs] [packages1] ... [packagesN]

01

VBox Guest Additions

I get this error after vagrant up:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'mage2_dev'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: mage2_vagrant_default_1490177510475_12013
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> 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: 22 (guest) => 2200 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2200
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
[default] GuestAdditions versions on your host (5.1.16) and guest (4.1.18) do not match.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version.
dkms set to manually installed.
linux-headers-3.2.0-4-amd64 is already the newest version.
linux-headers-3.2.0-4-amd64 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Copy iso file C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
mount: warning: /mnt seems to be mounted read-only.
Installing Virtualbox Guest Additions 5.1.16 - guest version is 4.1.18
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.16 Guest Additions for Linux...........
VirtualBox Guest Additions installer
You appear to have a version of the VirtualBox Guest Additions
on your system which was installed from a different source or using a
different type of installer.  If you installed it from a package from your
Linux distribution or if it is a default part of the system then we strongly
recommend that you cancel this installation and remove it properly before
installing this version.  If this is simply an older or a damaged
installation you may safely proceed.

Do you wish to continue anyway? [yes or no]

Cancelling installation.
An error occurred during installation of VirtualBox Guest Additions 5.1.16. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.


==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.1.18
    default: VirtualBox Version: 5.1
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/agarrido/Projects/mage2_vagrant
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o dmode=777,fmode=777,uid=1000,gid=1000 vagrant /vagrant

The error output from the command was:

: No such file or directory`

indexer:reindex error

Recieving the following two errors when trying to reindex from CLI
$ php bin/magento indexer:reindex

[Zend_Db_Adapter_Exception]
SQLSTATE[HY000] [2002] No such file or directory

[PDOException]
SQLSTATE[HY000] [2002] No such file or directory

If I change the db host in app/etc/env.php to 127.0.0.1 instead of local host I get

[Zend_Db_Adapter_Exception]
SQLSTATE[HY000] [2002] Connection refused

[PDOException]
SQLSTATE[HY000] [2002] Connection refused

Where did I go wrong?

I don't understand the setup instruction for installing mage2_vagrant

I could partially install it by mixing your instruction with another instruction I had for installing a program in vagrant. But when I open 'http://mage2.dev/setup' it says: "page is not available."

Your instruction misses the following:
(1) It doesn't have "vagrant init ubuntu/trusty64", and "vagrant up --provider virtualbox"
(2) It says nothing regarding installing php7 (or php 5.6); I installed it myself; I don't know if I should have added php.
(3) It doesn't have anything regarding installing composer. I added the command myself and installed composer; I don't know if I should have added composer.
(4) It says nothing regarding "composer init". I added the command myself.
(5) I ended up with two "Vagrantfile" files, (1) in the main directory, i.e., magento, that I created myself and filled the "Vagrantfile" in that directory with my own info, which is more likely incorrect, and (2) in mage2_vagrant directory, which already had info inside. Should I have two "Vagrantfile" files?
(6) It says nothing regarding creating "composer.json". I created it myself.

Also the instruction itself is vague, I don't understand the following:

(1) In paragraph 5, should I copy and paste the following after vagrant up, but before vagrant ssh? "echo '192.168.56.10 mage2.dev' >> /etc/hosts"
(2) In paragraph 7, it says open or create the file "~/.composer/auth.json". No such file exist so I created it myself. But it doesn't say in what directory I should create the ".composer" hidden folder. I created the ".composer" folder in the directory of mag2_vagrant, as follows: "mag2_vagrant/.composer/auth.json". I don't know if it is in a correct directory.
(3) In paragraph 8, it says install Magento 2 by running Via CLI (recommended), but it doesn't say what is the command line that I have to enter. So I chose the second option. However, after going through a long process of installation, including entering the Public key, Private Key, and Token Key, and downloading the large Magento 2 application, when I open "http://mage2.dev/set", it says page is not available.

Update to Magento 2 stable release

Thanks for jumping right on the M2 stable release. Tried to update the box today, but something went wrong. I went to the dir I cloned this repo on my Mac and ran:

git pull && git submodule update --init && vagrant provision

This is the output I got back:

remote: Counting objects: 16, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 16 (delta 5), reused 5 (delta 5), pack-reused 8
Unpacking objects: 100% (16/16), done.
From github.com:rgranadino/mage2_vagrant
   97f2355..a8d69b7  master     -> origin/master
Fetching submodule data/magento2
remote: Counting objects: 121899, done.
remote: Compressing objects: 100% (2874/2874), done.
remote: Total 121899 (delta 46358), reused 44573 (delta 44573), pack-reused 74010
Receiving objects: 100% (121899/121899), 17.84 MiB | 1.75 MiB/s, done.
Resolving deltas: 100% (74485/74485), completed with 8198 local objects.
From https://github.com/magento/magento2
   c077da6..4cae5d0  develop    -> origin/develop
   9d4c58e..4cae5d0  master     -> origin/master
 * [new branch]      merchant_beta -> origin/merchant_beta
 * [new tag]         2.0.0      -> 2.0.0
 * [new tag]         1.0.0-beta2 -> 1.0.0-beta2
 * [new tag]         1.0.0-beta3 -> 1.0.0-beta3
 * [new tag]         1.0.0-beta4 -> 1.0.0-beta4
 * [new tag]         1.0.0-beta5 -> 1.0.0-beta5
 * [new tag]         1.0.0-beta6 -> 1.0.0-beta6
 * [new tag]         2.0.0-rc   -> 2.0.0-rc
 * [new tag]         2.0.0-rc2  -> 2.0.0-rc2
Updating 97f2355..a8d69b7
Fast-forward
 .gitmodules               |  3 +++
 README.md                 | 15 +++++++++++----
 Vagrantfile               |  5 ++---
 data/magento2             |  2 +-
 data/magento2-sample-data |  1 +
 files/reinstall.sh        | 14 +++++---------
 6 files changed, 23 insertions(+), 17 deletions(-)
 create mode 160000 data/magento2-sample-data
Submodule 'data/magento2-sample-data' (https://github.com/magento/magento2-sample-data.git) registered for path 'data/magento2-sample-data'
error: Your local changes to the following files would be overwritten by checkout:
    composer.json
    composer.lock
Please, commit your changes or stash them before you can switch branches.
error: The following untracked working tree files would be overwritten by checkout:
    app/code/Magento/SampleData/README.md
    app/code/Magento/SampleData/composer.json
    app/code/Magento/SampleData/etc/di.xml
    app/code/Magento/SampleData/etc/module.xml
Please move or remove them before you can switch branches.
Aborting
Cloning into 'data/magento2-sample-data'...
remote: Counting objects: 4771, done.
remote: Compressing objects: 100% (171/171), done.
remote: Total 4771 (delta 96), reused 0 (delta 0), pack-reused 4579
Receiving objects: 100% (4771/4771), 77.37 MiB | 1.07 MiB/s, done.
Resolving deltas: 100% (1560/1560), done.
Checking connectivity... done.
Submodule path 'data/magento2-sample-data': checked out '4987f3fbde8279b9366a859b760cad13e89a9354'
Unable to checkout '4cae5d058b7ad877b2ec7d2b6fa0a500f7c16860' in submodule path 'data/magento2'

There are no loose files in my working directory for this repo, but I'm a little hazy how git submodules work and fit into all this. This ENV was setup with sample data before.

Provision notices

During the vagrant up I got this error (twice actually):

Error: /bin/rm /vagrant/data/magento2/app/etc/local.xml returned 1 instead of one of [0]
Error: /Stage[main]//Exec[remove-local-xml]/returns: change from notrun to 0 failed: /bin/rm /vagrant/data/magento2/app/etc/local.xml returned 1 instead of one of [0]

But overall it seem to provisioned succesfully

"Fatal error: Class 'Locale' not found" Error

Hey there, I was hoping for some words of wisdom here. When executing the task grunt exec:luma I get an error as such "Fatal error: Class 'Locale' not found in /Users/aromero/Sites/frontend/magento2/data/magento2/lib/internal/Magento/Framework/Locale/Bundle/DataBundle.php on line 64".

Any ideas on why I would get this error? Is there a system dependency missing?

Puppet fails on install (vagrant up)

ssh-agent is running on my host machine, github is using the correct key. Still the intial vagrant up fails with the error below. Am I missing something?

==> default: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:33 on node mage2.dev
==> default: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:33 on node mage2.dev
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Dropbox host returning 509

In your Vagrantfile, you've set the Debian box URL to a Dropbox location. This is (at least currently) returning a '509 Bandwidth error'

Are there any other places this can be sourced from?
Thanks!

reinstall -s generates "Integrity contraint violation"

Reported here: magento/magento2#1308

I just tried to use mage2_vagrant for the first time and it errored out. I found the issue reported above, so I expect it's not caused by your project, but figured I'd report it, in case it's due to a server config issue. Sorry I don't have time to work on researching this further right now so I'm not contributing much that's useful.

Backend still show Magento ver. 0.74.0-beta12

I just downloaded your package … fresh … from scratch … and after all these setup routines … it says … Magento ver. 0.74.0-beta12 … WHY??? :( Is it just me? Is it Magento? Did they forget to change this string? Thanks for your help …

Rico

vagrant up needs password

i'm trying to run vagrant up but it keeps asking me for admin password at:

Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
Password:

None of the passwords in the readme works here...

mage-setup

I am building a custom website using magento 2. I am following all the instructions mentioned here. Instead of cloning magento 2 from git,can i download from magento.com and use it here? Please help me out.

Mounting NFS shared folders not working

Hello rgranadino,

I follow your way to install magento 2 using your vagrant, but its not working for me

one i think i change. i download .box image before so, i added to vagrant , its successfully added, next I give vagrant up command now, default: Mounting NFS shared folders... its taking for long time say error in

         he following SSH command responded with a non-zero exit status. 
         Vagrant assumes that this means the command failed!

         mount -o 'vers=3,udp' 192.168.56.1:'/u01/ChennaiBox/mage2_vagrant' /vagrant

         Stdout from the command:
         Stderr from the command:
        stdin: is not a tty
        mount.nfs: Connection timed out

Next i added /etc/sudoers

       vagrant ALL=(ALL) NOPASSWD:ALL
       Defaults:vagrant !requiretty

Now, also show same problem:

This is my vagrant File:
# -- mode: ruby --
# vi: set ft=ruby :

Vagrant.configure("2") do |config|

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "ame"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  #config.vm.box_url = "https://s3.amazonaws.com/magenation/debian-wheezy.box"

  config.ssh.username = "vagrant"
  config.vm.hostname = "www.chennaibox.com"
  config.ssh.forward_agent = "true"

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  config.vm.network :private_network, ip: "192.168.56.12"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider :virtualbox do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
  #   vb.customize ["modifyvm", :id, "--memory", "1024"]
  # end
  #
  # View the documentation for the provider you're using for more
  # information on available options.
  config.vm.provider :virtualbox do |vb|
    vb.customize ["modifyvm", :id, "--memory", "2048"]
  end

  if Vagrant::Util::Platform.windows?
    config.vm.synced_folder ".", "/vagrant", :mount_options => ["dmode=777", "fmode=777"]
  else
    config.vm.synced_folder ".", "/vagrant", :nfs => { :mount_options => ["dmode=777", "fmode=777"] }

    #rsync_args = ['--verbose', '--archive', '-z']
    #config.vm.synced_folder ".", "/vagrant",
    #  rsync__args: rsync_args, rsync__exclude: ['.vagrant/'], rsync__auto: true, type: 'rsync'

  end

  # Enable provisioning with Puppet stand alone.  Puppet manifests
  # are contained in a directory path relative to this Vagrantfile.
  # You will need to create the manifests directory and a manifest in
  # the file base.pp in the manifests_path directory.
  #
  # An example Puppet manifest to provision the message of the day:
  #
  # # group { "puppet":
  # #   ensure => "present",
  # # }
  # #
  # # File { owner => 0, group => 0, mode => 0644 }
  # #
  # # file { '/etc/motd':
  # #   content => "Welcome to your Vagrant-built virtual machine!
  # #               Managed by Puppet.\n"
  # # }
  #
  # config.vm.provision :puppet do |puppet|
  #   puppet.manifests_path = "manifests"
  #   puppet.manifest_file  = "init.pp"
  # end

  # Enable provisioning with chef solo, specifying a cookbooks path, roles
  # path, and data_bags path (all relative to this Vagrantfile), and adding
  # some recipes and/or roles.
  #
  # config.vm.provision :chef_solo do |chef|
  #   chef.cookbooks_path = "../my-recipes/cookbooks"
  #   chef.roles_path = "../my-recipes/roles"
  #   chef.data_bags_path = "../my-recipes/data_bags"
  #   chef.add_recipe "mysql"
  #   chef.add_role "web"
  #
  #   # You may also specify custom JSON attributes:
  #   chef.json = { :mysql_password => "foo" }
  # end

  # Enable provisioning with chef server, specifying the chef server URL,
  # and the path to the validation key (relative to this Vagrantfile).
  #
  # The Opscode Platform uses HTTPS. Substitute your organization for
  # ORGNAME in the URL and validation key.
  #
  # If you have your own Chef Server, use the appropriate URL, which may be
  # HTTP instead of HTTPS depending on your configuration. Also change the
  # validation key to validation.pem.
  #
  # config.vm.provision :chef_client do |chef|
  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
  #   chef.validation_key_path = "ORGNAME-validator.pem"
  # end
  #
  # If you're using the Opscode platform, your validator client is
  # ORGNAME-validator, replacing ORGNAME with your organization name.
  #
  # If you have your own Chef Server, the default validation client name is
  # chef-validator, unless you changed the configuration.
  #
  #   chef.validation_client_name = "ORGNAME-validator"
  config.vm.provision :puppet do |puppet|
    puppet.manifests_path = "manifests"
    puppet.manifest_file = "mage.pp"
    puppet.module_path   = "puppet_modules"
  end
end

This is output:

      [chennaibox@mb mage2_vagrant]$ vagrant reload
==> default: Clearing any previously set forwarded ports...
==> 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: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: 
    default: Guest Additions Version: 4.1.18
    default: VirtualBox Version: 5.0
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for chennaibox: 
Redirecting to /bin/systemctl status  nfs-server.service
● nfs-server.service - NFS server and services
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled; vendor preset: disabled)
   Active: active (exited) since Sat 2016-05-21 09:48:05 IST; 46min ago
  Process: 18196 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/SUCCESS)
  Process: 18194 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
 Main PID: 18196 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/nfs-server.service
==> default: Mounting NFS shared folders...
default: Mounting NFS shared folders...The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o 'vers=3,udp' 192.168.56.1:'/u01/ChennaiBox/mage2_vagrant' /vagrant

Stdout from the command:



Stderr from the command:

stdin: is not a tty
mount.nfs: Connection timed out

[chennaibox@mb mage2_vagrant]$ 

Suggest me how to solve this problem...

THANK YOU VERY MUCH :-)

My biggest Issue is: I have no way to say thank you here :-) So I'm creating an issue to say Thank you for all your work!

Best,
Rico

Setup instructions not working

A couple of issues with the setup instructions. Things seem to go fine until step 7. Logged into ssh as "vagrant"

Once I enter composer.phar global config http-basic.repo.magento.com <public_key> <private_key> (with the appropriate public and private keys substituted) I get:

~bash: composer.phar: command not found

No global auth.json file can be found at ~/.composer/auth.json either.

Step 8 also seems pretty unclear. There's a reinstall found in ~/bin - this is the correct one to be run? When attempting to do so I just seem to get bad interpreter: No such file or directory

Vagrant Provision Errors

Notice: /Stage[main]//Package[php5-mcrypt]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]//Package[php5-xdebug]/ensure: ensure changed 'purged' to 'latest'
Error: Could not set 'file' on ensure: No such file or directory - /etc/php5/fpm/conf.d/21-xdebug.ini.puppettmp_2247 at 146:/tmp/vagrant-puppet-1/manifests/mage.pp
Error: Could not set 'file' on ensure: No such file or directory - /etc/php5/fpm/conf.d/21-xdebug.ini.puppettmp_2247 at 146:/tmp/vagrant-puppet-1/manifests/mage.pp
Wrapped exception:
No such file or directory - /etc/php5/fpm/conf.d/21-xdebug.ini.puppettmp_2247
Error: /Stage[main]//File[/etc/php5/fpm/conf.d/21-xdebug.ini]/ensure: change from absent to file failed: Could not set 'file' on ensure: No such file or directory - /etc/php5/fpm/conf.d/21-xdebug.ini.puppettmp_2247 at 146:/tmp/vagrant-puppet-1/manifests/mage.pp
Notice: /Stage[main]//Package[php5-fpm]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]//File[/etc/php5/fpm/pool.d/www.conf]/content: content changed '{md5}003c13820a1174b7f04471d8b62a3bb3' to '{md5}a79cf7c2769dce647e8008642c92d199'
Notice: /Stage[main]//File[/etc/php5/fpm/pool.d/www.conf]/owner: owner changed 'root' to 'vagrant'
Notice: /Stage[main]//File[/etc/php5/fpm/pool.d/www.conf]/group: group changed 'root' to 'vagrant'
Notice: /Stage[main]//Apache2mod[authz_user]/Exec[/usr/sbin/a2dismod authz_user]/returns: executed successfully
Notice: /Stage[main]//Package[mysql-server]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]//Package[php5-curl]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]//File[/etc/apache2/sites-enabled/000-default]/ensure: removed
Notice: /Stage[main]//Apache2mod[authz_groupfile]/Exec[/usr/sbin/a2dismod authz_groupfile]/returns: executed successfully
Notice: /Stage[main]//Package[php-codesniffer]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]//File[/etc/apache2/sites-enabled/001-stats]/ensure: defined content as '{md5}dd14b9cd2d7d21ee7641b765903c672c'
Notice: /Stage[main]//Apache2mod[rewrite]/Exec[/usr/sbin/a2enmod rewrite]/returns: executed successfully
Notice: /Stage[main]//Service[php5-fpm]: Dependency File[/etc/php5/fpm/conf.d/21-xdebug.ini] has failures: true
Warning: /Stage[main]//Service[php5-fpm]: Skipping because of failed dependencies
Notice: /Stage[main]//Exec[set-mysql-password]/returns: executed successfully
Notice: /Stage[main]//Exec[create-mage-db]/returns: executed successfully
Notice: /Stage[main]//Exec[remove-local-xml]: Triggered 'refresh' from 1 events
Notice: /Stage[main]//Exec[reload-php5-fpm]: Triggered 'refresh' from 6 events
Notice: /Stage[main]//Apache2mod[actions]/Exec[/usr/sbin/a2enmod actions]/returns: executed successfully
Notice: /Stage[main]//Package[rsync]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]//Apache2mod[cgid]/Exec[/usr/sbin/a2dismod cgid]/returns: executed successfully
Notice: /Stage[main]//Package[php5-intl]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]//Package[phpunit]/ensure: ensure changed 'purged' to 'latest'
Notice: /Stage[main]//File[/etc/apache2/sites-enabled/000-mage2]/ensure: defined content as '{md5}8b780930ae7f15b2e17050186448ebb3'
Notice: /Stage[main]//Service[apache2]: Triggered 'refresh' from 2 events
Notice: /Stage[main]//Apache2mod[auth_basic]/Exec[/usr/sbin/a2dismod auth_basic]/returns: executed successfully
Notice: /Stage[main]//Exec[reload-apache2]: Triggered 'refresh' from 10 events
Notice: Finished catalog run in 734.51 seconds
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --manifestdir /tmp/vagrant-puppet-1/manifests --detailed-exitcodes /tmp/vagrant-puppet-1/manifests/mage.pp || [ $? -eq 2 ]

Stdout from the command:

Notice: /Stage[first]/Dotdeb/Exec[Import dotdeb to apt keystore]/returns: executed successfully
Notice: /Stage[first]/Dotdeb/File[/etc/apt/sources.list]/content: content changed '{md5}264af6d55e9a03f834368ecbb7874377' to '{md5}9cd21a7ce0abfa157ea34f5430ad0411'
Notice: /Stage[first]/Dotdeb/Exec[apt-get update]/returns: executed successfully
Notice: /Stage[first]/Dotdeb/Exec[apt-get update]: Triggered 'refresh' from 1 events
[...]

Received errors above during vagrant provisioning process - on completion recd the following:

Notice: Finished catalog run in 734.51 seconds


Stderr from the command:

stdin: is not a tty
Error: Could not set 'file' on ensure: No such file or directory - /etc/php5/fpm/conf.d/21-xdebug.ini.puppettmp_2247 at 146:/tmp/vagrant-puppet-1/manifests/mage.pp
Error: Could not set 'file' on ensure: No such file or directory - /etc/php5/fpm/conf.d/21-xdebug.ini.puppettmp_2247 at 146:/tmp/vagrant-puppet-1/manifests/mage.pp
Wrapped exception:
No such file or directory - /etc/php5/fpm/conf.d/21-xdebug.ini.puppettmp_2247
Error: /Stage[main]//File[/etc/php5/fpm/conf.d/21-xdebug.ini]/ensure: change from absent to file failed: Could not set 'file' on ensure: No such file or directory - /etc/php5/fpm/conf.d/21-xdebug.ini.puppettmp_2247 at 146:/tmp/vagrant-puppet-1/manifests/mage.pp
Warning: /Stage[main]//Service[php5-fpm]: Skipping because of failed dependencies

host does not work

After install and vagrant up
Can not open hosts "192.168.56.10 mage2.dev" on browser.
/etc/hosts file was effected
Ssh working fine.

In install I get error
==> default: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:33 on node mage2.dev
==> default: Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Could not find declared class composer at /tmp/vagrant-puppet/manifests-a11d1078b1b1f2e3bdea27312f6ba513/mage.pp:33 on node mage2.dev
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I do not know if it depend to problem.
Please advise I try in win7 and ios system

Apache 2.4

needs to have this with php 7 for developing to be efficient, otherwise unuseable.

many provisioning errors / packages not installed

I got a whole load of provisioning notices, and it seems that things have not installed as expected

==> default: Notice: /Stage[main]//Package[libapache2-mod-fastcgi]/ensure: ensure changed 'purged' to 'latest'
==> default: Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install apache2-suexec' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: The following NEW packages will be installed:
==> default: apache2-suexec
==> default: 0 upgraded, 1 newly installed, 0 to remove and 60 not upgraded.
==> default: Need to get 107 kB of archives.
==> default: After this operation, 184 kB of additional disk space will be used.
==> default: WARNING: The following packages cannot be authenticated!
==> default: apache2-suexec
==> default: E: There are problems and -y was used without --force-yes
==> default:
==> default:
==> default: Error: /Stage[main]//Package[apache2-suexec]/ensure: change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install apache2-suexec' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: The following NEW packages will be installed:
==> default: apache2-suexec
==> default: 0 upgraded, 1 newly installed, 0 to remove and 60 not upgraded.
==> default: Need to get 107 kB of archives.
==> default: After this operation, 184 kB of additional disk space will be used.
==> default: WARNING: The following packages cannot be authenticated!
==> default: apache2-suexec
==> default: E: There are problems and -y was used without --force-yes
==> default:
==> default: Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install vim' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: The following extra packages will be installed:
==> default: libgpm2 vim-runtime
==> default: Suggested packages:
==> default: gpm ctags vim-doc vim-scripts
==> default: The following NEW packages will be installed:
==> default: libgpm2 vim vim-runtime
==> default: 0 upgraded, 3 newly installed, 0 to remove and 60 not upgraded.
==> default: Need to get 5484 kB of archives.
==> default: After this operation, 24.9 MB of additional disk space will be used.
==> default: WARNING: The following packages cannot be authenticated!
==> default: libgpm2 vim-runtime vim
==> default: E: There are problems and -y was used without --force-yes
==> default:
==> default: Error: /Stage[main]//Package[vim]/ensure: change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install vim' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: The following extra packages will be installed:
==> default: libgpm2 vim-runtime
==> default: Suggested packages:
==> default: gpm ctags vim-doc vim-scripts
==> default: The following NEW packages will be installed:
==> default: libgpm2 vim vim-runtime
==> default: 0 upgraded, 3 newly installed, 0 to remove and 60 not upgraded.
==> default: Need to get 5484 kB of archives.
==> default: After this operation, 24.9 MB of additional disk space will be used.
==> default: WARNING: The following packages cannot be authenticated!
==> default: libgpm2 vim-runtime vim
==> default: E: There are problems and -y was used without --force-yes
==> default:
==> default: Notice: /Stage[main]//File[/home/vagrant/bin/reinstall]/ensure: defined content as '{md5}77f9d6ccbd2563fba6d15f0b9725c5f5'

...

==> default: Notice: /Stage[main]//Exec[remove-local-xml]/returns: /bin/rm: cannot remove `/vagrant/data/magento2/app/etc/local.xml': No such file or directory
==> default: Error: /bin/rm /vagrant/data/magento2/app/etc/local.xml returned 1 instead of one of [0]
==> default: Error: /Stage[main]//Exec[remove-local-xml]/returns: change from notrun to 0 failed: /bin/rm /vagrant/data/magento2/app/etc/local.xml returned 1 instead of one of [0]
==> default: Notice: /Stage[main]//Exec[reload-php5-fpm]: Triggered 'refresh' from 6 events

...

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --manifestdir /tmp/vagrant-puppet-4/manifests --detailed-exitcodes /tmp/vagrant-puppet-4/manifests/mage.pp

and once provisioning has completed :

stdin: is not a tty
Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install apache2-suexec' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
apache2-suexec
0 upgraded, 1 newly installed, 0 to remove and 60 not upgraded.
Need to get 107 kB of archives.
After this operation, 184 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
apache2-suexec
E: There are problems and -y was used without --force-yes

Error: /Stage[main]//Package[apache2-suexec]/ensure: change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install apache2-suexec' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
apache2-suexec
0 upgraded, 1 newly installed, 0 to remove and 60 not upgraded.
Need to get 107 kB of archives.
After this operation, 184 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
apache2-suexec
E: There are problems and -y was used without --force-yes

Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install vim' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
libgpm2 vim-runtime
Suggested packages:
gpm ctags vim-doc vim-scripts
The following NEW packages will be installed:
libgpm2 vim vim-runtime
0 upgraded, 3 newly installed, 0 to remove and 60 not upgraded.
Need to get 5484 kB of archives.
After this operation, 24.9 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
libgpm2 vim-runtime vim
E: There are problems and -y was used without --force-yes

Error: /Stage[main]//Package[vim]/ensure: change from purged to latest failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install vim' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
libgpm2 vim-runtime
Suggested packages:
gpm ctags vim-doc vim-scripts
The following NEW packages will be installed:
libgpm2 vim vim-runtime
0 upgraded, 3 newly installed, 0 to remove and 60 not upgraded.
Need to get 5484 kB of archives.
After this operation, 24.9 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
libgpm2 vim-runtime vim
E: There are problems and -y was used without --force-yes

Error: /bin/rm /vagrant/data/magento2/app/etc/local.xml returned 1 instead of one of [0]
Error: /Stage[main]//Exec[remove-local-xml]/returns: change from notrun to 0 failed: /bin/rm /vagrant/data/magento2/app/etc/local.xml returned 1 instead of one of [0]

NFS sync

"flock(2) does not lock files over NFS."
Magento use it.
So I think many people will have some problem with NFS sync.

Installation fails on step #6 (DB setup)

Still trying to get M2 installed. I got past the composer / GitHub oAuth part but unchecked all boxes. It didn't seem right granted access to my private repos to install this. Seemed to still work.

Step 6 should be changed to http://mage2.dev/setup/ because accessing the root directory gives a permissions error.

I got through to the DB setup page, but it failed using the credentials supplied in the readme. Kind of a weird error response too. See attached.

All the server readiness checks did pass.

screen shot 2015-09-23 at 4 18 03 pm

More explicit setup instructions needed

To make this more accessible, we should add more detailed instructions on how to set up the VM using Vagrant along with common pitfalls. I ran into an issue that Vagrant could not find a provider and it ended up being that Virtual Box was not installed. I had to install VirtualBox and then restart my computer before it worked.

I think a list of prerequisites would be sufficient to solve this - Vagrant, Git Bash (for Windows users), and VirtualBox.

The instructions should also include this link for setting up the repo.magento.com http auth creds:
http://devdocs.magento.com/guides/v2.0/install-gde/prereq/connect-auth.html

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.