Hello There,
I am facing some strange issues with a new artifactory setup. We are moving to docker-compose based installation and running artifactory in container this time.
JF_PRODUCT_DATA_INTERNAL (inside container refers to /var/opt/jfrog/artifactory) directory is mounteed to /opt/artifactory on local host.
First problem, I see artifactory.home_IS_UNDEFINED folder created under /opt/artifactory when I start my container.
[root#guvcdapartifa04 artifactory]# ls -ltr artifactory.home_IS_UNDEFINED/
total 8
drwxr-x---. 3 artifactory artifactory 4096 May 19 15:24 access
drwxr-x---. 2 artifactory artifactory 4096 May 19 15:24 logs
ls -ltr from one level up lists these directories...
[root#guvcdapartifa04 artifactory]# ls -ltr
total 44
drwxr-xr-x. 6 artifactory artifactory 4096 Apr 16 17:02 var
drwxr-xr-x. 5 artifactory artifactory 4096 Apr 16 21:11 app
drwxr-xr-x. 4 artifactory artifactory 4096 Apr 16 21:22 bootstrap
drwxr-xr-x. 6 artifactory artifactory 4096 Apr 16 21:22 work
drwxr-xr-x. 6 artifactory artifactory 4096 Apr 16 21:22 data
drwxr-x---. 3 artifactory artifactory 4096 May 9 13:07 access
drwxr-xr-x. 6 artifactory artifactory 4096 May 10 18:08 backup
drwxr-x---. 2 artifactory artifactory 4096 May 13 18:33 logs
drwxr-xr-x. 4 artifactory artifactory 4096 May 19 00:23 log
drwxr-xr-x. 9 artifactory artifactory 4096 May 19 14:23 etc
drwxr-x---. 4 artifactory artifactory 4096 May 19 14:23 artifactory.home_IS_UNDEFINED
I have tried setting both JF_ARTIFACTORY_HOME and artifactory.home to /var/opt/jfrog/artifactory in my compose defination for artifactory service but it didn't help and results were same.
artifactory.home_IS_UNDEFINED folder is created after everytime I start the artifactory container after deleting it.
Service defination in compose.yml ...
artifactory:
container_name: artifactory
image: docker.bintray.io/jfrog/artifactory-pro:7.3.2
links: [ postgres ]
expose: [ '8081','8082' ]
restart: unless-stopped
user: artifactory
ulimits:
nproc: 65535
nofile:
soft: 32000
hard: 40000
logging:
driver: json-file
options:
max-size: "50m"
max-file: "30"
environment:
JF_ROUTER_ENTRYPOINTS_EXTERNALPORT: '8082'
JF_ARTIFACTORY_HOME: '/var/opt/jfrog/artifactory'
# JF_SYSTEM_YAML: '/opt/jfrog/artifactory/var/etc/system.yaml'
# JF_ARTIFACTORY_PID: '/opt/jfrog/artifactory/app/run/artifactory.pid'
# JF_PRODUCT_DATA_INTERNAL: '/var/opt/jfrog/artifactory'
# JF_PRODUCT_HOME: '/opt/jfrog/artifactory'
# JF_SHARED_NODE_IP: '192.168.76.180'
# JF_SHARED_NODE_NAME: 'guvcdapartifa04'
# JF_SHARED_NODE_ID: 'guvcdapartifa04'
# JF_ARTIFACTORY_USER: 'artifactory'
volumes:
- type: bind
source: /etc/localtime
target: /etc/localtime
read_only: true
- type: bind
source: /opt/artifactory
target: /var/opt/jfrog/artifactory
read_only: false
Please note the value of JF_ARTIFACTORY_HOME, Artifactory Home below.
artifactory | ========================
artifactory | JF Environment variables
artifactory | ========================
artifactory |
artifactory | JF_SHARED_NODE_NAME : efec1fe35cdd
artifactory | JF_SYSTEM_YAML : /opt/jfrog/artifactory/var/etc/system.yaml
artifactory | JF_ARTIFACTORY_PID : /opt/jfrog/artifactory/app/run/artifactory.pid
artifactory | JF_SHARED_EXTRAJAVAOPTS : -Xms2g
artifactory | -Xmx8g :
artifactory | JF_PRODUCT_DATA_INTERNAL : /var/opt/jfrog/artifactory
artifactory | JF_PRODUCT_HOME : /opt/jfrog/artifactory
artifactory | JF_ROUTER_TOPOLOGY_LOCAL_REQUIREDSERVICETYPES : jfrt,jfac,jfmd,jffe
artifactory | JF_ROUTER_ENTRYPOINTS_EXTERNALPORT : 8082
artifactory | JF_ARTIFACTORY_HOME : /var/opt/jfrog/artifactory
artifactory | JF_SHARED_NODE_IP : 172.20.0.3
artifactory | JF_SHARED_NODE_ID : efec1fe35cdd
artifactory | JF_ARTIFACTORY_USER : artifactory
artifactory | Starting router...
artifactory | router not running. Proceed to start it up.
artifactory | router started. PID: 2732
.
.
.
artifactory | _ _ __ _ _____
artifactory | /\ | | (_)/ _| | | | __ \
artifactory | / \ _ __| |_ _| |_ __ _ ___| |_ ___ _ __ _ _ | |__) | __ ___
artifactory | / /\ \ | '__| __| | _/ _` |/ __| __/ _ \| '__| | | | | ___/ '__/ _ \
artifactory | / ____ \| | | |_| | || (_| | (__| || (_) | | | |_| | | | | | | (_) |
artifactory | /_/ \_\_| \__|_|_| \__,_|\___|\__\___/|_| \__, | |_| |_| \___/
artifactory | Version: 7.3.2 __/ |
artifactory | Revision: 70302900 |___/
artifactory | Artifactory Home: '/opt/jfrog/artifactory'
artifactory | Node ID: 'abd383aec9fd'
Second Problem, I see these errors reported for plugings in the logs.
artifactory | ==================Plugins Status===================
artifactory | # propertySetsConfig.groovy --> Loaded
artifactory | # haClusterDump.groovy --> Loaded
artifactory | # httpSsoConfig.groovy --> Loaded
artifactory | # repoLayoutsConfig.groovy --> Loaded
artifactory | # storageSummary.groovy --> Loaded
artifactory | # ldapGroupsConfig.groovy --> Loaded
artifactory | # ldapSettingsConfig.groovy --> Loaded
artifactory | # pluginsConfig.groovy --> Error
artifactory | # proxiesConfig.groovy --> Loaded
artifactory | # requestRouting.groovy --> Error
artifactory | ===================================================
.
.
.
[root#guvcdapartifa04 artifactory]# services logs artifactory | grep ERROR
artifactory | 2020-05-19 08:54:07,221 [art-init] [ERROR] (o.a.a.p.GroovyRunnerImpl:349) - Error loading script from '/opt/jfrog/artifactory/var/etc/artifactory/plugins/pluginsConfig.groovy'.
artifactory | 2020-05-19 08:54:07,994 [art-init] [ERROR] (o.a.a.p.GroovyRunnerImpl:349) - Error loading script from '/opt/jfrog/artifactory/var/etc/artifactory/plugins/requestRouting.groovy'.
[root#guvcdapartifa04 artifactory]#
Third Problem, I want to get rid of "artifactory" context in url: https://node.org.local/artifactory/. I would like it to be simple as https://node.org.local/. Is it possible ?
Fourth Problem, the container instance starts with following new "ALL-UNNAMED" settings in start command - I am concerned and we would like to understand their purpose please.
--add-opens java.base/java.util=ALL-UNNAMED
--add-opens java.base/java.lang.reflect=ALL-UNNAMED
--add-opens java.base/java.lang.invoke=ALL-UNNAMED
--add-opens java.base/java.text=ALL-UNNAMED
--add-opens java.base/java.nio=ALL-UNNAMED
--add-opens java.desktop/java.awt.font=ALL-UNNAMED
[root#guvcdapartifa04 artifactory]# ps -ef | grep artifactory | grep Bootstrap
artifac+ 8670 5699 35 15:24 ? 00:01:33 /opt/jfrog/artifactory/app/third-party/java/bin/java -Djava.util.logging.config.file=/opt/jfrog/artifactory/app/artifactory/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -server -Xss256k -XX:+UseG1GC -XX:OnOutOfMemoryError=kill -9 %p --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang.reflect=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/java.text=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.desktop/java.awt.font=ALL-UNNAMED -Dfile.encoding=UTF8 -Djruby.compile.invokedynamic=false -Djruby.bytecode.version=1.8 -Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true -Djava.security.egd=file:/dev/./urandom -Dartdist=zip -Djf.product.home=/opt/jfrog/artifactory -Xms2g -Xmx8g -Djruby.bytecode.version=1.8 -Dartifactory.metadata.native.ui=true -Dignore.endorsed.dirs= -classpath /opt/jfrog/artifactory/app/artifactory/tomcat/bin/bootstrap.jar:/opt/jfrog/artifactory/app/artifactory/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/jfrog/artifactory/app/artifactory/tomcat -Dcatalina.home=/opt/jfrog/artifactory/app/artifactory/tomcat -Djava.io.tmpdir=/opt/jfrog/artifactory/var/work/artifactory/tomcat/temp org.apache.catalina.startup.Bootstrap start
Awaiting your response
For the first issue, I would suggest to remove the old logback.xml - you accepted thank you.
Second issue is resolved after you installed latest groovy.
For the third issue, Artifactory can no longer be configured as the Tomcat root application. To remove the /artifactory context, you'll need to set the relevant configuration in your reverse proxy (load-balancer). refer: https://www.jfrog.com/confluence/display/JFROG/HTTP+Settings
For the fourth issue. refer details on add-opens: https://www.oreilly.com/library/view/java-9-building/9781788832823/40494528-393d-49e4-a216-d7a2d4d7e95c.xhtml
Related
OSX 10.13.6
I installed mariadb sever with homebrew a few years ago, and I use it infrequently. Today, I tried to start mariadb using the command:
$ mysql.server start
and I got a bunch of errors. So, I did:
$ brew update
then:
$ brew uprade mariadb
That completed fine, and now I can start mariadb with:
$ mysql.server start
and I can access all my old db's.
The problem I'm having is that I cannot stop mysql. Both these commands hang:
$ mysql.server stop
and(in another terminal window):
$ mysql.server status
According to the MariaDB docs for mysql.server, both those commands should work.
Currently, I'm killing the server like this:
$ killall mysqld mysqld_safe
then checking that the server was killed with this:
$ ps aux | grep mysqld
When I run the ps command when mysql is running, I get:
~$ ps aux | grep mysqld
7stud 3707 0.0 1.0 4808208 79948 s005 S 1:26PM 0:00.47
/usr/local/Cellar/mariadb/10.3.15/bin/mysqld
--basedir=/usr/local/Cellar/mariadb/10.3.15 --datadir=/usr/local/var/mysql --plugin-dir=/usr/local/Cellar/mariadb/10.3.15/lib/plugin --log-error=/usr/local/var/mysql/My-MacBook-Pro-2.local.err --pid-file=/usr/local/var/mysql/My-MacBook-Pro-2.local.pid
7stud 3643 0.0 0.0 4287792 1460 s005 S 1:26PM 0:00.02 /bin/sh
/usr/local/Cellar/mariadb/10.3.15/bin/mysqld_safe
--datadir=/usr/local/var/mysql --pid-file=/usr/local/var/mysql/My-MacBook-Pro-2.local.pid
7stud 4544 0.0 0.0 4267752 880 s000 S+ 1:41PM 0:00.00
grep mysqld
What is the proper way to shut down the mariadb server?
mysql> SHOW VARIABLES LIKE '%vers%';
+---------------------------------+------------------------------------------+
| Variable_name | Value |
+---------------------------------+------------------------------------------+
| innodb_version | 10.3.15 |
| protocol_version | 10 |
| slave_type_conversions | |
| system_versioning_alter_history | ERROR |
| system_versioning_asof | DEFAULT |
| thread_pool_oversubscribe | 3 |
| version | 10.3.15-MariaDB |
| version_comment | Homebrew |
| version_compile_machine | x86_64 |
| version_compile_os | osx10.13 |
| version_malloc_library | system |
| version_source_revision | 07aef9f7eb936de2b277f8ae209a1fd72510c011 |
| version_ssl_library | OpenSSL 1.0.2r 26 Feb 2019 |
| wsrep_patch_version | wsrep_25.24 |
+---------------------------------+------------------------------------------+
14 rows in set (0.01 sec)
I had the same issue, tried to use mysql.server stop and mysql.server status after running mysql.server start but they will just run indefinitely.
If you are using a Mac seems that mysql.server stop won't work... I installed mariadb with homebrew and found out that I can use brew services to start and stop it in this link:
https://dba.stackexchange.com/questions/214883/homebrew-mariadb-server-start-error-with-mysql-server-start
The commands are pretty simple and they work for me
brew services start mariadb
brew services stop mariadb
It may be a little late but I hope this helps you to figure out your problem.
See https://stackoverflow.com/a/59938033/4579271 for details.
To fix, run:
cp /usr/local/bin/mysql.server /usr/local/bin/mysql.server.backup
sed -i "" "s/user='mysql'/user=\`whoami\`/g" /usr/local/bin/mysql.server
I'm trying to deploy a CDN using nginx container with docker swarm.
For now, i have manager in host, and one worker on VM created using docker-machine:
pierpaolo#pierpaolo-Lenovo-G580:~$ docker-machine create -d virtualbox worker1
Running pre-create checks...
Creating machine...
(worker1) Copying /home/pierpaolo/.docker/machine/cache/boot2docker.iso to /home/pierpaolo/.docker/machine/machines/worker1/boot2docker.iso...
(worker1) Creating VirtualBox VM...
(worker1) Creating SSH key...
(worker1) Starting the VM...
(worker1) Check network to re-create if needed...
(worker1) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env worker1
pierpaolo#pierpaolo-Lenovo-G580:~$ docker-machine ssh worker1
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/
_ _ ____ _ _
| |__ ___ ___ | |_|___ \ __| | ___ ___| | _____ _ __
| '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|
| |_) | (_) | (_) | |_ / __/ (_| | (_) | (__| < __/ |
|_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|
Boot2Docker version 1.12.5, build HEAD : fc49b1e - Fri Dec 16 12:44:49 UTC 2016
Docker version 1.12.5, build 7392c3b
I run manager on host:
pierpaolo#pierpaolo-Lenovo-G580:~$ docker swarm init
Swarm initialized: current node (99rr4i1w7wgn5usak9s20fikb) is now a manager.
To add a worker to this swarm, run the following command:
docker swarm join \
--token SWMTKN-1-0tfvpvdlmugavn3fyqtjn9wkd3oeqze6nmw547shp07y73whix-4dqc404txwg58zibnz3lmp30w \
192.168.1.101:2377
To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
Then, on worker1, i run:
docker#worker1:~$ docker swarm join \
> --token SWMTKN-1-0tfvpvdlmugavn3fyqtjn9wkd3oeqze6nmw547shp07y73whix-4dqc40
4txwg58zibnz3lmp30w \
> 192.168.1.101:2377
This node joined a swarm as a worker.
On host, i created overlay network:
pierpaolo#pierpaolo-Lenovo-G580:~$ docker network create -d overlay mynetwork
cb9plmvxn6twjt5lm7xgnq4ha
And created my services, with 10 replicas:
docker service create --name nginx-cdn --network mynetwork --replicas 10 -p 9999:80 nginx-new:latest
dt1rfrix71cawpr8czzy4jje4
But, as shown as following:
pierpaolo#pierpaolo-Lenovo-G580:~$ docker service ls
ID NAME REPLICAS IMAGE COMMAND
dt1rfrix71ca nginx-cdn 0/10 nginx-new:latest
pierpaolo#pierpaolo-Lenovo-G580:~$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1a64270ac470 nginx-new:latest "nginx -g 'daemon off" 5 minutes ago Up 5 minutes 80/tcp, 443/tcp nginx-cdn.6.dhtgs9ilcj6jngxify7ko05e9
4a230d618e81 nginx-new:latest "nginx -g 'daemon off" 5 minutes ago Up 5 minutes 80/tcp, 443/tcp nginx-cdn.4.7pnxf19kpyhf3ex31zs39q884
01a76327729e nginx-new:latest "nginx -g 'daemon off" 5 minutes ago Up 5 minutes 80/tcp, 443/tcp nginx-cdn.5.b12cp73a078mjw55gsr0x6hfn
3a940f28c532 nginx-new:latest "nginx -g 'daemon off" 5 minutes ago Up 5 minutes 80/tcp, 443/tcp nginx-cdn.10.8grve8nw9fmk3tydhimh1xgng
d0e1970380d5 nginx-new:latest "nginx -g 'daemon off" 5 minutes ago Up 5 minutes 80/tcp, 443/tcp nginx-cdn.1.aval6w0ol357x8obxgjzlxnxv
On manager (host) there are only 5 of 10 replicas, and on worker1
docker#worker1:~$ docker ps --all
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
There are no containers.
Why?
If i cmd docker service ps nginx-cdn
there are some lines like these:
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR
aval6w0ol357x8obxgjzlxnxv nginx-cdn.1 nginx-new:latest pierpaolo-Lenovo-G580 Shutdown Shutdown 7 seconds ago
48ovjs0rvh6xceaydfjo1nx7j nginx-cdn.2 nginx-new:latest worker1 Shutdown Preparing 58 seconds ago
ayhw38h74o4m503q08gbbg3v1 \_ nginx-cdn.2 nginx-new:latest worker1 Shutdown Rejected about a minute ago "No such image: nginx-new:lateā¦"
But i created an image named "nginx-new:latest" and if i created a container from this image, it works.
I changed pulling intervals in /etc/ceilometer/pipeline.yaml file from 600 to 60 and can't make the service to use new values. I restarted everything that relates to ceilometer in openstack-status command, but that did not work. Can somebody tell me the proper way how to do it?
I am using Openstack Liberty on Ubuntu 14.04 LTS
root#OS1:~# openstack service list
+----------------------------------+------------+---------------+
| ID | Name | Type |
+----------------------------------+------------+---------------+
| 056fcccaad5c4991a8a0da199ed1d737 | cinderv2 | volumev2 |
| 483a0cd1ba79430690a8960ae3d40222 | glance | image |
| 5c704fc9253e4c15895589eb19fab2ac | keystone | identity |
| 92bfcfb417314e80a43e6e7d4d21f99b | nova | compute |
| a7a3809d73674d3da3fbe8030b47055a | horizon | dashboard |
| c21b5e3c9d68417cb11df60d72f9bb58 | heat | orchestration |
| c7030edb082346328a715b00098b974a | neutron | network |
| d331f5360e2b4d3a854e7f47107a9421 | ec2 | ec2 |
| f0a22f827bed43dbbc43822abfc3e3e0 | ceilometer | metering |
+----------------------------------+------------+---------------+
root#OS11:~# openstack-status
.
.
.
== Ceilometer services ==
ceilometer-api: active
ceilometer-agent-central: active
ceilometer-agent-compute: inactive (disabled on boot)
ceilometer-collector: active
ceilometer-alarm-notifier: active
ceilometer-alarm-evaluator: active
ceilometer-agent-notification:active
.
.
.
Well, you need to restart ceilometer-agent-notification service because this service is responsible for transforming the data into samples in the ceilometer database.
Thus, systemctl restart ceilometer-agent-notification.service will help along with restarting other services.
Since ceilometer-agent-compute service is disabled, you just need to restart ceilometer-agent-central service on the node you have modified the config file.
sudo service ceilometer-agent-central restart
You might want to auto reload pipelines after you modify it, for that, you can set refresh_pipeline_cfg=True and a proper time for pipeline_polling_interval such as 120 seconds in /etc/ceilometer/ceilometer.conf.
Note, be careful when you enable auto reload, and only save pipeline config file after you are sure about the content is right (otherwise it might lose 1 polling period data)
I can check a bundle state from Karaf Console by doing:-
karaf#root>bundle:list | grep camel-test
246 | Active | 50 | 2.16.1 | camel-test
Is there a way I can do this programatically via some script running on the same machine as Karaf or via some REST End Point that Karaf exposes?
I am using Karaf 3.0.5 running under ServiceMix 6.0.1.
As discussed in Karaf User Forum I am able to achieve it using the karaf client:-
jabong#jabong1143:~/Downloads/apache-servicemix-6.1.0/bin$ ./client -l 0 -u karaf "bundle:list" | grep camel-test
246 | Active | 50 | 2.16.1 | camel-test
I m installing orocrm so i have an error during the installation process
this is my command php app/console oro:install error is [Symfony\Component\Process\Exception\RuntimeException]
The process timed-out.
i have check the oro_install.log file there is no any error
here is the instrucktion page i have followed http://www.orocrm.com/documentation/index/current/book/installation
thanks
this is my console
root#efttt-Intron-5t59:/home/eures/tance/crm-application/orocrm# php app/console oro:install
Installing Oro Application.
Oro requirements check:
+---------+------------------------------------------------------------------------------------------+ | Check | Mandatory requirements
|
+---------+------------------------------------------------------------------------------------------+ | OK | Vendor libraries must be installed
| | OK | app/cache/ directory must be writable
| | OK | app/logs/ directory must be writable
| | OK | Configured default timezone "Asia/Colombo" must be
supported by your installation of PHP | | OK | json_encode() must
be available
| | OK | session_start() must be available
| | OK | ctype_alpha() must be available
| | OK | token_get_all() must be available
| | OK | simplexml_import_dom() must be available
| | OK | PCRE extension must be available
| | OK | Cache folder should not be inside encrypted directory
|
+---------+------------------------------------------------------------------------------------------+
+---------+--------------------------------------------+ | Check | PHP settings |
+---------+--------------------------------------------+ | OK | date.timezone setting must be set | | OK |
detect_unicode must be disabled in php.ini | | OK | memory_limit
should be at least 512M |
+---------+--------------------------------------------+
+---------+------------------------------------------------------------------+ | Check | Oro specific requirements
|
+---------+------------------------------------------------------------------+ | OK | PHP version must be at least 5.4.9 (5.6.11-1ubuntu3.1
installed) | | OK | GD extension must be at least 2.0
| | OK | cURL extension must be at least 7.0
| | OK | mcrypt_encrypt() should be available
| | OK | intl extension should be available
| | OK | icu library must be at least 3.8
| | OK | web/uploads/ directory must be writable
| | OK | web/media/ directory must be writable
| | OK | web/bundles/ directory must be writable
| | OK | app/attachment/ directory must be writable
| | OK | web/js directory must be writable
| | OK | web/css directory must be writable
| | OK | app/config/parameters.yml file must be writable
|
+---------+------------------------------------------------------------------+
+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Check | Optional recommendations
|
+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | OK | Requirements file should be up-to-date
| | OK | When using the logout handler from the Symfony Security
Component, you should have at least PHP 5.4.11 due to PHP bug #63379
(as a workaround, you can also set invalidate_session to false in the
security logout handler configuration) | | OK | PCRE extension
should be at least version 8.0 (8.35 installed)
| | OK | PHP-XML module should be installed
| | OK | mb_strlen() should be available
| | OK | iconv() should be available
| | OK | utf8_decode() should be available
| | OK | posix_isatty() should be available
| | OK | intl extension should be available
| | OK | intl extension should be correctly configured
| | OK | intl ICU version should be at least 4+
| | OK | a PHP accelerator should be installed
| | OK | short_open_tag should be disabled in php.ini
| | OK | magic_quotes_gpc should be disabled in php.ini
| | OK | register_globals should be disabled in php.ini
| | OK | session.auto_start should be disabled in php.ini
| | OK | PDO should be installed
| | OK | PDO should have some drivers installed (currently
available: dblib, mysql, odbc)
| | OK | SOAP extension should be installed (API calls)
| | OK | A JS Engine (node) is installed
|
+---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Dropping database schema... Database schema dropped successfully!
Clear the entity config cache Clear the extended entity cache Setting
up database. Process migrations...
Oro\Bundle\MigrationBundle\Migration\CreateMigrationTableMigration
Oro\Bundle\OrganizationBundle\Migrations\Schema\OroOrganizationBundleInstaller
Oro\Bundle\SecurityBundle\Migrations\Schema\v1_0\OroSecurityBundle
Oro\Bundle\AttachmentBundle\Migrations\Schema\OroAttachmentBundleInstaller
Oro\Bundle\EmailBundle\Migrations\Schema\OroEmailBundleInstaller
Oro\Bundle\UserBundle\Migrations\Schema\OroUserBundleInstaller
Oro\Bundle\SSOBundle\Migrations\Schema\OroUserBundleInstaller
Oro\Bundle\EntityConfigBundle\Migrations\Schema\OroEntityConfigBundleInstaller
Oro\Bundle\EntityConfigBundle\Migrations\Schema\v1_3\OroEntityConfigBundle
Oro\Bundle\EntityConfigBundle\Migrations\Schema\v1_4\FixOptionSetObjects
Oro\Bundle\EntityConfigBundle\Migrations\Schema\v1_5\DropFieldConfig
Oro\Bundle\EntityExtendBundle\Migrations\Schema\OroEntityExtendBundleInstaller
Oro\Bundle\EntityExtendBundle\Migrations\Schema\v1_3\OroEntityExtendBundle
Oro\Bundle\IntegrationBundle\Migrations\Schema\OroIntegrationBundleInstaller
Oro\Bundle\ActivityBundle\Migrations\Schema\OroActivityBundleInstaller
Oro\Bundle\ActivityListBundle\Migrations\Schema\OroActivityListBundleInstaller
Oro\Bundle\AddressBundle\Migrations\Schema\OroAddressBundleInstaller
Oro\Bundle\BatchBundle\Migrations\Schema\OroBatchBundleInstaller
Oro\Bundle\CalendarBundle\Migrations\Schema\OroCalendarBundleInstaller
Oro\Bundle\CalendarBundle\Migrations\Schema\v1_9\OroCalendarBundle
Oro\Bundle\ConfigBundle\Migrations\Schema\OroConfigBundleInstaller
Oro\Bundle\CronBundle\Migrations\Schema\v1_0\OroCronBundle
Oro\Bundle\CronBundle\Migrations\Schema\v1_0\JmsJob
Oro\Bundle\CronBundle\Migrations\Schema\v1_1\JmsJob
Oro\Bundle\DataAuditBundle\Migrations\Schema\OroDataAuditBundleInstaller
Oro\Bundle\DataGridBundle\Migrations\Schema\OroDataGridBundleInstaller
Oro\Bundle\EmbeddedFormBundle\Migrations\Schema\OroEmbeddedFormBundleInstaller
Oro\Bundle\ImapBundle\Migrations\Schema\v1_0\OroImapBundle
Oro\Bundle\ImapBundle\Migrations\Schema\v1_1\OroImapBundle
Oro\Bundle\ImapBundle\Migrations\Schema\v1_2\OroImapBundle
Oro\Bundle\InstallerBundle\Migrations\Schema\OroInstallerBundle
Oro\Bundle\MigrationBundle\Migrations\Schema\v1_0\OroMigrationBundle
Oro\Bundle\MigrationBundle\Migrations\Schema\v1_1\OroMigrationBundle
Oro\Bundle\NoteBundle\Migrations\Schema\v1_0\OroNoteBundle
Oro\Bundle\NoteBundle\Migrations\Schema\v1_1\OroNoteBundle
Oro\Bundle\NotificationBundle\Migrations\Schema\OroNotificationBundleInstaller
Oro\Bundle\ReportBundle\Migrations\Schema\OroReportBundleInstaller
Oro\Bundle\SearchBundle\Migrations\Schema\OroSearchBundleInstaller
Oro\Bundle\SegmentBundle\Migrations\Schema\OroSegmentBundleInstaller
Oro\Bundle\SidebarBundle\Migrations\Schema\v1_0\OroSidebarBundle
Oro\Bundle\SidebarBundle\Migrations\Schema\v1_1\OroSidebarBundle
Oro\Bundle\TagBundle\Migrations\Schema\OroTagBundleInstaller
Oro\Bundle\TranslationBundle\Migrations\Schema\OroTranslationBundleInstaller
Oro\Bundle\WindowsBundle\Migrations\Schema\v1_0\OroWindowsBundle
Oro\Bundle\WorkflowBundle\Migrations\Schema\OroWorkflowBundleInstaller
Oro\Bundle\CommentBundle\Migrations\Schema\v1_0\OroCommentBundle
Oro\Bundle\DashboardBundle\Migrations\Schema\OroDashboardBundleInstaller
Oro\Bundle\NavigationBundle\Migrations\Schema\v1_0\OroNavigationBundle
Oro\Bundle\NavigationBundle\Migrations\Schema\v1_1\OroNavigationBundle
Oro\Bundle\NavigationBundle\Migrations\Schema\v1_2\OroNavigationBundle
Oro\Bundle\NavigationBundle\Migrations\Schema\v1_3\OroNavigationBundle
OroCRM\Bundle\ContactBundle\Migrations\Schema\OroCRMContactBundleInstaller
OroCRM\Bundle\AccountBundle\Migrations\Schema\OroCRMAccountBundleInstaller
-------------------------------------------------------------------- >"Symfony\Component\Process\Exception\RuntimeException The process
timed-out."
probably due to dev log messages, try with the prod symfony env:
php app/console oro:install --env=prod
In the installation instruction on the github project page mention this note also:
Note: If the installation process times out, add the --timeout=0
argument to the command.
Hope this help