-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect & warn about old data on install #155
Comments
@vfbsilva answered you on forum. It's compaining that you don't have |
@rodolfobandeira I have it in many places: In many places:
` All owned by the apache user. |
If I understand your setup correctly |
@mbessolov the files are just copies of the same install sorry I forgot to supress it from the ls output this was due a suggestion from a guy here on the support forum. At the official docs listed here it does not explicitly asks me to run composer install inside the app folder. Instead it asks for an update there. According to this. The following exception is caused by a lack of memory and not having swap configured PHP Fatal error: Uncaught exception 'ErrorException' with message 'proc_open(): fork failed - Cannot allocate memory' in phar:///usr/bin/composer/vendor/symfony/console/Application.php:954 Fatal error: Uncaught exception 'ErrorException' with message 'proc_open(): fork failed - Cannot allocate memory' in phar:///usr/bin/composer/vendor/symfony/console/Application.php:954 |
According to the installation instructions at http://www.orocrm.com/documentation/index/current/book/installation here is the list of what has to be done to install the latest version of OroCRM:
or, if you are using a downloaded archive instead of GitHub:
|
Oki done as suggested. Still a problem:
|
I would remove this folder and reinstall everything again following the instructions they gave to you. |
I've done it. Started with a folder from scratch same result.
|
looks like database contains data from previous installation attempts
please drop and recreate database before install |
@SergeyZ I've selected on the gui installer to do such thing I've dropped the database manually now and it did work. So I think part of the problem was that the guy installer is not dropping the DB. Maybe it could pop a bigger warning? |
Will check drop database for gui installer, thanks for report! |
Thanks to @SergeyZ 's suggestion of oro-crom, you have excellent experience and identify the root cause is "database contains data from previous installation" Some suggestions to oro-crm development teams: It's important that without these information and experiences that will waste your time and our time to figure out the root cause. I am Magento2 users and I faced the same case. |
@woei66 I have created a ticket in our backlog, but it's hard to say now when we will be able to provide a permanent fix. I am marking this as open for community contribution for now, and will change the status as soon as we'll schedule the fix for some version. I've also updated the issue title to make it more clear. Thanks for your contribution! |
Folks seems some files are missing on the commit from 1.9.0. I have an open discussion on the forums
I was able to find the mentioned files in other versions of the package but just adding them did not solve the problem.
The text was updated successfully, but these errors were encountered: