I get an error trying to start activemq 5.11.
Perhaps it's related to this issue:
https://issues.apache.org/jira/browse/AMQ-4299
dave#vishnu.local:~/Downloads/apache-activemq-5.11.0/data$ cat wrapper.log
STATUS | wrapper | 2015/02/09 11:29:01 | --> Wrapper Started as Daemon
STATUS | wrapper | 2015/02/09 11:29:01 | Launching a JVM...
INFO | jvm 1 | 2015/02/09 11:29:02 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:29:02 | JVM exited while loading the application.
STATUS | wrapper | 2015/02/09 11:29:06 | Launching a JVM...
INFO | jvm 2 | 2015/02/09 11:29:06 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:29:07 | JVM exited while loading the application.
STATUS | wrapper | 2015/02/09 11:29:11 | Launching a JVM...
INFO | jvm 3 | 2015/02/09 11:29:11 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:29:12 | JVM exited while loading the application.
STATUS | wrapper | 2015/02/09 11:29:16 | Launching a JVM...
INFO | jvm 4 | 2015/02/09 11:29:16 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:29:17 | JVM exited while loading the application.
STATUS | wrapper | 2015/02/09 11:29:21 | Launching a JVM...
INFO | jvm 5 | 2015/02/09 11:29:21 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:29:21 | JVM exited while loading the application.
FATAL | wrapper | 2015/02/09 11:29:21 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | 2015/02/09 11:29:21 | There may be a configuration problem: please check the logs.
STATUS | wrapper | 2015/02/09 11:29:21 | <-- Wrapper Stopped
STATUS | wrapper | 2015/02/09 11:32:28 | --> Wrapper Started as Daemon
STATUS | wrapper | 2015/02/09 11:32:28 | Launching a JVM...
INFO | jvm 1 | 2015/02/09 11:32:29 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:32:29 | JVM exited while loading the application.
STATUS | wrapper | 2015/02/09 11:32:34 | Launching a JVM...
INFO | jvm 2 | 2015/02/09 11:32:34 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:32:34 | JVM exited while loading the application.
STATUS | wrapper | 2015/02/09 11:32:38 | Launching a JVM...
INFO | jvm 3 | 2015/02/09 11:32:39 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:32:39 | JVM exited while loading the application.
STATUS | wrapper | 2015/02/09 11:32:43 | Launching a JVM...
INFO | jvm 4 | 2015/02/09 11:32:43 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:32:44 | JVM exited while loading the application.
STATUS | wrapper | 2015/02/09 11:32:48 | Launching a JVM...
INFO | jvm 5 | 2015/02/09 11:32:48 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp
ERROR | wrapper | 2015/02/09 11:32:49 | JVM exited while loading the application.
FATAL | wrapper | 2015/02/09 11:32:49 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | 2015/02/09 11:32:49 | There may be a configuration problem: please check the logs.
STATUS | wrapper | 2015/02/09 11:32:49 | <-- Wrapper Stopped
as suggested, your issue is not related to AMQ per your log:
Error: Could not find or load main class
org.tanukisoftware.wrapper.WrapperSimpleApp
I solved this problem by adding activeMQ bin directory to the PATH environment variable.
C:\Tools\apache-activemq-5.14.2\bin
Related
I am trying to install and configure sonarqube to use it in small poroyect in my machine (Ubuntu 18.04.2 LTS) y have already download the zip Sonarqube 7.7 community edition from the oficial web and unzipped in /opt/. I tryed to do as is say in the guide from sonar and execute ./sonar.sh console in the path /opt/sonarqube/bin/linux-x86-64 and I get problems with the log permisions .
Running SonarQube...
wrapper | ERROR: Could not write pid file /opt/sonarqube/bin/linux-x86-64/./SonarQube.pid: Permission denied
Unable to open logfile ../../logs/sonar.log: Permission denied
So I try the same as superuser and I get
Running SonarQube...
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
jvm 1 |
jvm 1 | 2019.04.05 19:55:48 INFO app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
jvm 1 | 2019.04.05 19:55:48 INFO app[][o.s.a.es.EsSettings] Elasticsearch listening on /127.0.0.1:9001
jvm 1 | 2019.04.05 19:55:48 INFO app[][o.s.a.p.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
jvm 1 | 2019.04.05 19:55:48 INFO app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1 | 2019.04.05 19:55:48 INFO app[][o.e.p.PluginsService] no modules loaded
jvm 1 | 2019.04.05 19:55:48 INFO app[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
jvm 1 | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
jvm 1 | 2019.04.05 19:55:51 WARN app[][o.s.a.p.AbstractProcessMonitor] Process exited with exit value [es]: 1
jvm 1 | 2019.04.05 19:55:51 INFO app[][o.s.a.SchedulerImpl] Process [es] is stopped
jvm 1 | 2019.04.05 19:55:51 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped
jvm 1 | 2019.04.05 19:55:51 INFO app[][o.e.c.t.TransportClientNodesService] failed to get node info for {#transport#-1}{pr4ED0vsRgCYZjgn1jbLlQ}{127.0.0.1}{127.0.0.1:9001}, disconnecting...
jvm 1 | java.lang.IllegalStateException: Future got interrupted
jvm 1 | at org.elasticsearch.common.util.concurrent.FutureUtils.get(FutureUtils.java:60)
jvm 1 | at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:34)
jvm 1 | at org.elasticsearch.transport.ConnectionManager.internalOpenConnection(ConnectionManager.java:226)
jvm 1 | at org.elasticsearch.transport.ConnectionManager.openConnection(ConnectionManager.java:85)
jvm 1 | at org.elasticsearch.transport.TransportService.openConnection(TransportService.java:367)
jvm 1 | at org.elasticsearch.client.transport.TransportClientNodesService$SimpleNodeSampler.doSample(TransportClientNodesService.java:410)
jvm 1 | at org.elasticsearch.client.transport.TransportClientNodesService$NodeSampler.sample(TransportClientNodesService.java:361)
jvm 1 | at org.elasticsearch.client.transport.TransportClientNodesService.addTransportAddresses(TransportClientNodesService.java:202)
jvm 1 | at org.elasticsearch.client.transport.TransportClient.addTransportAddress(TransportClient.java:342)
jvm 1 | at org.sonar.application.es.EsConnectorImpl$MinimalTransportClient.<init>(EsConnectorImpl.java:108)
jvm 1 | at org.sonar.application.es.EsConnectorImpl.buildTransportClient(EsConnectorImpl.java:89)
jvm 1 | at org.sonar.application.es.EsConnectorImpl.getTransportClient(EsConnectorImpl.java:74)
jvm 1 | at org.sonar.application.es.EsConnectorImpl.getClusterHealthStatus(EsConnectorImpl.java:61)
jvm 1 | at org.sonar.application.process.EsProcessMonitor.checkStatus(EsProcessMonitor.java:90)
jvm 1 | at org.sonar.application.process.EsProcessMonitor.checkOperational(EsProcessMonitor.java:75)
jvm 1 | at org.sonar.application.process.EsProcessMonitor.isOperational(EsProcessMonitor.java:60)
jvm 1 | at org.sonar.application.process.SQProcess.refreshState(SQProcess.java:161)
jvm 1 | at org.sonar.application.process.SQProcess$EventWatcher.run(SQProcess.java:220)
jvm 1 | Caused by: java.lang.InterruptedException: null
jvm 1 | at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1038)
jvm 1 | at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1343)
jvm 1 | at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:251)
jvm 1 | at org.elasticsearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:94)
jvm 1 | at org.elasticsearch.common.util.concurrent.FutureUtils.get(FutureUtils.java:57)
jvm 1 | ... 17 common frames omitted
wrapper | <-- Wrapper Stopped
I do not understand the error I get and why it does not start the sonarqube.
Don't try to use superuser. Just change the access rights on the complete SonarQube folder for the user you use.
I am trying to build a Docker image with Apache (httpd) and PHP 5.3.3. The image is based on a CentOS 6 && Supervisord that I have made. So far everything is working "fine" (and this means no issues during build process) but I am having some issues with Apache and Supervisord. Why? Because I think the image based on reynierpm/centos6-supervisord is already starting Apache and then Supervisord is trying to do the same thing. Here is a log of what I am getting when I start my stack using docker-compose up:
webserver_1 | 2018-02-03 19:29:52,882 CRIT Supervisor running as root (no user in config file)
webserver_1 | 2018-02-03 19:29:52,882 INFO Included extra file "/etc/supervisor.d/httpd.conf" during parsing
webserver_1 | 2018-02-03 19:29:52,913 INFO RPC interface 'supervisor' initialized
webserver_1 | 2018-02-03 19:29:52,920 INFO supervisord started with pid 8
webserver_1 | 2018-02-03 19:29:53,923 INFO spawned: 'httpd' with pid 11
webserver_1 | 2018-02-03 19:29:53,928 INFO spawned: 'httpd-reload' with pid 12
webserver_1 | 2018-02-03 19:29:53,964 DEBG 'httpd' stderr output:
webserver_1 | httpd: Could not reliably determine the server's fully qualified domain name, using 172.18.0.2 for ServerName
webserver_1 |
webserver_1 | 2018-02-03 19:29:53,965 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 41891168 for <Subprocess at 140421355793008 with name httpd in state STARTING> (stderr)>
webserver_1 | 2018-02-03 19:29:53,979 DEBG fd 7 closed, stopped monitoring <POutputDispatcher at 41890736 for <Subprocess at 140421355793008 with name httpd in state STARTING> (stdout)>
webserver_1 | 2018-02-03 19:29:53,980 INFO exited: httpd (exit status 0; not expected)
webserver_1 | 2018-02-03 19:29:53,981 DEBG received SIGCLD indicating a child quit
webserver_1 | 2018-02-03 19:29:54,983 INFO spawned: 'httpd' with pid 23
webserver_1 | 2018-02-03 19:29:54,985 INFO success: httpd-reload entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
I have created a gist having the Dockerfile and the httpd.conf file read by Supervisord, what I am doing wrong here?
I'm quite new with Docker and I'm trying to use docker-compose in order to set up Apache with PostgreSQL all together.
This is my docker-compose.yml:
version: '2'
services:
db:
image: postgres
apache2:
image: webdevops/apache:latest
ports:
- 8084:80
- 443:443
links:
- db
And every time I execute docker-compose up, it usually gets stuck in
AH00094: Command line: 'apache2 -D FOREGROUND -D APACHE_LOCK_DIR'
This is the output when I execute it.
First gets stuck with some LOG: autovacuum launcher started while installing postgres, and when I Ctrl+C it, and re-execute docker-compose, it get stuck in the apache2 -D FOREGROUND -D APACHE_LOCK_DIR line.
Here is the ouput
docker-compose up
Pulling db (postgres:latest)...
latest: Pulling from library/postgres
cd0a524342ef: Pull complete
9c784d04dcb0: Pull complete
d99dddf7e662: Pull complete
e5bff71e3ce6: Pull complete
cb3e0a865488: Pull complete
31295d654cd5: Pull complete
fc930a4e09f5: Pull complete
8650cce8ef01: Pull complete
61949acd8e52: Pull complete
527a203588c0: Pull complete
26dec14ac775: Pull complete
0efc0ed5a9e5: Pull complete
40cd26695b38: Pull complete
Digest: sha256:fd6c0e2a9d053bebb294bb13765b3e01be7817bf77b01d58c2377ff27a4a46dc
Status: Downloaded newer image for postgres:latest
Pulling apache2 (webdevops/apache:latest)...
latest: Pulling from webdevops/apache
aafe6b5e13de: Pull complete
0a2b43a72660: Pull complete
18bdd1e546d2: Pull complete
8198342c3e05: Pull complete
f56970a44fd4: Pull complete
7d255d8cc29c: Pull complete
6b76599eeb74: Pull complete
ac6a5bdae794: Pull complete
bfe65de9caf3: Pull complete
45f407574293: Pull complete
5f28b0c8228a: Pull complete
ceb4b3de72bc: Pull complete
Digest: sha256:acf3049ddc1cf7f615eb4751250881d31dccfc50752ac3a1261169b684f430cb
Status: Downloaded newer image for webdevops/apache:latest
Creating dockertest7_db_1
Creating dockertest7_apache2_1
Attaching to dockertest7_db_1, dockertest7_apache2_1
apache2_1 | 2017-05-09 01:36:54,332 CRIT Set uid to user 0
apache2_1 | 2017-05-09 01:36:54,332 WARN Included extra file "/opt/docker/etc/supervisor.d/apache.conf" during parsing
apache2_1 | 2017-05-09 01:36:54,332 WARN Included extra file "/opt/docker/etc/supervisor.d/cron.conf" during parsing
apache2_1 | 2017-05-09 01:36:54,332 WARN Included extra file "/opt/docker/etc/supervisor.d/dnsmasq.conf" during parsing
apache2_1 | 2017-05-09 01:36:54,332 WARN Included extra file "/opt/docker/etc/supervisor.d/postfix.conf" during parsing
apache2_1 | 2017-05-09 01:36:54,332 WARN Included extra file "/opt/docker/etc/supervisor.d/ssh.conf" during parsing
apache2_1 | 2017-05-09 01:36:54,332 WARN Included extra file "/opt/docker/etc/supervisor.d/syslog.conf" during parsing
apache2_1 | 2017-05-09 01:36:54,340 INFO RPC interface 'supervisor' initialized
apache2_1 | 2017-05-09 01:36:54,340 INFO supervisord started with pid 1
db_1 | The files belonging to this database system will be owned by user "postgres".
db_1 | This user must also own the server process.
db_1 |
db_1 | The database cluster will be initialized with locale "en_US.utf8".
db_1 | The default database encoding has accordingly been set to "UTF8".
db_1 | The default text search configuration will be set to "english".
db_1 |
db_1 | Data page checksums are disabled.
db_1 |
db_1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok
db_1 | creating subdirectories ... ok
db_1 | selecting default max_connections ... 100
db_1 | selecting default shared_buffers ... 128MB
db_1 | selecting dynamic shared memory implementation ... posix
db_1 | creating configuration files ... ok
apache2_1 | 2017-05-09 01:36:55,345 INFO spawned: 'apached' with pid 17
apache2_1 | 2017-05-09 01:36:55,404 INFO success: apached entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
apache2_1 | [Tue May 09 01:36:55.414084 2017] [mpm_event:notice] [pid 17:tid 140039054796672] AH00489: Apache/2.4.18 (Ubuntu) OpenSSL/1.0.2g configured -- resuming normal operations
apache2_1 | [Tue May 09 01:36:55.414134 2017] [core:notice] [pid 17:tid 140039054796672] AH00094: Command line: 'apache2 -D FOREGROUND -D APACHE_LOCK_DIR'
db_1 | running bootstrap script ... ok
db_1 | performing post-bootstrap initialization ... ok
db_1 | syncing data to disk ...
db_1 | WARNING: enabling "trust" authentication for local connections
db_1 | You can change this by editing pg_hba.conf or using the option -A, or
db_1 | --auth-local and --auth-host, the next time you run initdb.
db_1 | ok
db_1 |
db_1 | Success. You can now start the database server using:
db_1 |
db_1 | pg_ctl -D /var/lib/postgresql/data -l logfile start
db_1 |
db_1 | ****************************************************
db_1 | WARNING: No password has been set for the database.
db_1 | This will allow anyone with access to the
db_1 | Postgres port to access your database. In
db_1 | Docker's default configuration, this is
db_1 | effectively any other container on the same
db_1 | system.
db_1 |
db_1 | Use "-e POSTGRES_PASSWORD=password" to set
db_1 | it in "docker run".
db_1 | ****************************************************
db_1 | waiting for server to start....LOG: database system was shut down at 2017-05-09 01:36:56 UTC
db_1 | LOG: MultiXact member wraparound protections are now enabled
db_1 | LOG: database system is ready to accept connections
db_1 | LOG: autovacuum launcher started
db_1 | done
db_1 | server started
db_1 | ALTER ROLE
db_1 |
db_1 |
db_1 | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
db_1 |
db_1 | LOG: received fast shutdown request
db_1 | LOG: aborting any active transactions
db_1 | waiting for server to shut down...LOG: autovacuum launcher shutting down
db_1 | .LOG: shutting down
db_1 | LOG: database system is shut down
db_1 | done
db_1 | server stopped
db_1 |
db_1 | PostgreSQL init process complete; ready for start up.
db_1 |
db_1 | LOG: database system was shut down at 2017-05-09 01:36:58 UTC
db_1 | LOG: MultiXact member wraparound protections are now enabled
db_1 | LOG: database system is ready to accept connections
db_1 | LOG: autovacuum launcher started
Here I cancel it, cause it got stuck, and execute docker-compose again:
docker-compose up
Starting dockertest7_db_1
Starting dockertest7_apache2_1
Attaching to dockertest7_db_1, dockertest7_apache2_1
db_1 | LOG: database system was interrupted; last known up at 2017-05-09 01:37:00 UTC
db_1 | LOG: database system was not properly shut down; automatic recovery in progress
db_1 | LOG: invalid record length at 0/14EE238: wanted 24, got 0
db_1 | LOG: redo is not required
db_1 | LOG: MultiXact member wraparound protections are now enabled
db_1 | LOG: database system is ready to accept connections
db_1 | LOG: autovacuum launcher started
apache2_1 | 2017-05-09 01:41:17,903 CRIT Set uid to user 0
apache2_1 | 2017-05-09 01:41:17,903 WARN Included extra file "/opt/docker/etc/supervisor.d/apache.conf" during parsing
apache2_1 | 2017-05-09 01:41:17,903 WARN Included extra file "/opt/docker/etc/supervisor.d/cron.conf" during parsing
apache2_1 | 2017-05-09 01:41:17,903 WARN Included extra file "/opt/docker/etc/supervisor.d/dnsmasq.conf" during parsing
apache2_1 | 2017-05-09 01:41:17,903 WARN Included extra file "/opt/docker/etc/supervisor.d/postfix.conf" during parsing
apache2_1 | 2017-05-09 01:41:17,903 WARN Included extra file "/opt/docker/etc/supervisor.d/ssh.conf" during parsing
apache2_1 | 2017-05-09 01:41:17,903 WARN Included extra file "/opt/docker/etc/supervisor.d/syslog.conf" during parsing
apache2_1 | Unlinking stale socket /.supervisor.sock
apache2_1 | 2017-05-09 01:41:18,226 INFO RPC interface 'supervisor' initialized
apache2_1 | 2017-05-09 01:41:18,226 INFO supervisord started with pid 1
apache2_1 | 2017-05-09 01:41:19,230 INFO spawned: 'apached' with pid 17
apache2_1 | 2017-05-09 01:41:19,307 INFO success: apached entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
apache2_1 | [Tue May 09 01:41:19.316042 2017] [mpm_event:notice] [pid 17:tid 139733962508160] AH00489: Apache/2.4.18 (Ubuntu) OpenSSL/1.0.2g configured -- resuming normal operations
apache2_1 | [Tue May 09 01:41:19.316085 2017] [core:notice] [pid 17:tid 139733962508160] AH00094: Command line: 'apache2 -D FOREGROUND -D APACHE_LOCK_DIR'
Am I missing something? Maybe a basic stuff, configuration or something?
There are couple things with this installation.
One is obviously postgres that did not start up properly, and is now left in unstable state. Following article shows how to fix that.
For the rest, I cannot tell if you are having some incompatibility issues with systemd, or it is a consequence of the stalled db install, and then compose not starting up the dependencies (apache) properly.
Either way, I would remove all images, all temporary files, and try to rebuild and restart.
I have an app that worked fine last year on the earlier versions of sdk but now Titanium SDK 5.2.2.GA won't find iOS devices. I tried cleaning everything about appcelerator and reinstall but no luck. I also tried installing node-ios-device as a global package and in the titanium sdk 5.2.2 folder. What else can I do?
I get the following error:
2016-05-11T09:34:54.590Z | DEBUG | [PLUGIN-LOAD] 0ms /Users/adi/.appcelerator/install/5.2.2/package/appc.js
(node:2212) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
2016-05-11T09:34:54.651Z | DEBUG | [PLUGIN-LOAD] 61ms /Users/adi/.appcelerator/install/5.2.2/package/node_modules/appc-cli-titanium/appc.js
2016-05-11T09:34:54.651Z | DEBUG | run plugin: /Users/adi/.appcelerator/install/5.2.2/package/node_modules/appc-cli-titanium
2016-05-11T09:34:54.652Z | DEBUG | [PLUGIN-LOAD] 0ms /Users/adi/.appcelerator/install/5.2.2/package/node_modules/arrow/appc.js
2016-05-11T09:34:54.654Z | DEBUG | run plugin: /Users/adi/.appcelerator/install/5.2.2/package/node_modules/arrow
2016-05-11T09:34:54.656Z | TRACE | plugin "arrow" failed its "when" function check, skipping...
2016-05-11T09:34:54.657Z | TRACE | loading plugin "titanium" for command "run" CLI options via function
2016-05-11T09:34:54.658Z | TRACE | loading plugin "titanium" for command "run" CLI options via array
2016-05-11T09:34:54.660Z | TRACE | executing command "run" with the following plugins:
["titanium"]
2016-05-11T09:34:54.661Z | TRACE | Attempting to load session info from config file
2016-05-11T09:34:54.662Z | TRACE | check if session is invalidated
2016-05-11T09:34:55.350Z | TRACE | session expiry 1463560847951 false
2016-05-11T09:34:55.351Z | TRACE | session already loaded in opts.session
2016-05-11T09:34:55.352Z | DEBUG | Titanium Downloads Last Checked: 1462957150130
2016-05-11T09:34:55.480Z | TRACE | No project alloy hook; skipping update to 1.0.0
2016-05-11T09:34:56.100Z | ERROR | An uncaught exception was thrown!
Cannot read property 'devices' of undefined
2016-05-11T09:34:56.101Z | ERROR | Cannot read property 'devices' of undefined
2016-05-11T09:34:56.101Z | TRACE | TypeError: Cannot read property 'devices' of undefined
at iOSBuilder.<anonymous> (/Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/iphone/cli/commands/_build.js:298:11)
at /Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/ioslib/index.js:115:12
at /Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/async/lib/async.js:721:13
at /Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/async/lib/async.js:52:16
at done (/Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/async/lib/async.js:241:17)
at /Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/async/lib/async.js:44:16
at /Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/async/lib/async.js:718:17
at /Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/async/lib/async.js:167:37
at /Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/ioslib/index.js:85:6
at /Users/adi/Library/Application Support/Titanium/mobilesdk/osx/5.2.2.GA/node_modules/ioslib/lib/device.js:51:12
For anybody who encounters this, the problem is the NodeJS version, I had v6.2.0 and downgraded to v4.4.4. All works now.
Thanks Adi, I had the exact same issue v6.2.0 of Node and downgraded to v4.4.x and all works for me as well.
I try to use rabbit on ubuntu 12.04. After installation rabbitmq-server works fine. Than I stop it and add my configuration file.
root#rabbit1:~# tail /etc/rabbitmq/rabbitmq-env.conf
RABBITMQ_CONFIG_FILE=/etc/rabbitmq/myrabbitmq
root#rabbit1:~# tail /etc/rabbitmq/myrabbitmq.config
[{rabbit,
[{cluster_nodes, {['rabbit#rabbit1', 'rabbit#rabbit2'], disc}}]}].
With this files rabbitmq-server says on start:
root#rabbit1:~# rabbitmq-server
Activating RabbitMQ plugins ...
0 plugins activated:
+---+ +---+
| | | |
| | | |
| | | |
| +---+ +-------+
| |
| RabbitMQ +---+ |
| | | |
| v2.7.1 +---+ |
| |
+-------------------+
AMQP 0-9-1 / 0-9 / 0-8
Copyright (C) 2007-2011 VMware, Inc.
Licensed under the MPL. See http://www.rabbitmq.com/
node : rabbit#rabbit1
app descriptor : /usr/lib/rabbitmq/lib/rabbitmq_server-2.7.1/sbin/../ebin/rabbit.app
home dir : /var/lib/rabbitmq
config file(s) : /etc/rabbitmq/myrabbitmq.config
cookie hash : 31CaH3BCSDNL1hDIFQzH2Q==
log : /var/log/rabbitmq/rabbit#rabbit1.log
sasl log : /var/log/rabbitmq/rabbit#rabbit1-sasl.log
database dir : /var/lib/rabbitmq/mnesia/rabbit#rabbit1
erlang version : 5.8.5
-- rabbit boot start
starting file handle cache server ...done
starting worker pool ...done
starting database ...BOOT ERROR: FAILED
Reason: function_clause
Stacktrace: [{lists,usort,[{[rabbit#rabbit1,rabbit#rabbit2],disc}]},
{rabbit_mnesia,init_db,3},
{rabbit_mnesia,init,0},
{rabbit,'-run_boot_step/1-lc$^1/1-1-',1},
{rabbit,run_boot_step,1},
{rabbit,'-start/2-lc$^0/1-0-',1},
{rabbit,start,2},
{application_master,start_it_old,4}]
Erlang has closed
{"Kernel pid terminated",application_controller,"{application_start_failure,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot}}}}})
Have any suggestion what's wrong with my rabbit?
Configuration file should be like this:
root#rabbit1:~# cat /etc/rabbitmq/myrabbitmq.config
[{rabbit,
[{cluster_nodes, ['rabbit#rabbit1', 'rabbit#rabbit2'] }]}].
It seems, that disc or ram node configures in different way than in documentation to latest version of rabbit. In this configuration two disc nodes will be created. If somebody wants ram node this node should be ommitted in configuration of this node (not in other config files).