ejabberd my browser client is not connecting to server - ejabberd
I am trying to connect my ejabberd but it is not connecting.I checked the ejabberd.log file but i am not getting the issue what it is exactly? I am new here so if anybody knows then please help me in starting the ejabberd on ubuntu 16.04.
ejabberd.log:
2017-03-16 10:00:09.903 [info] <0.481.0>#ejabberd_listener:accept:333 (#Port<0.12667>) Accepted connection ::FFFF:127.0.0.1:53524 -> ::FFFF:127.0.0.1:5280
2017-03-16 10:00:09.904 [info] <0.554.0>#ejabberd_http:init:158 started: {p1_tls,{tlssock,#Port<0.12667>,#Port<0.12668>}}
2017-03-16 10:00:09.906 [info] <0.481.0>#ejabberd_listener:accept:333 (#Port<0.12669>) Accepted connection ::FFFF:127.0.0.1:53526 -> ::FFFF:127.0.0.1:5280
2017-03-16 10:00:09.907 [info] <0.555.0>#ejabberd_http:init:158 started: {p1_tls,{tlssock,#Port<0.12669>,#Port<0.12670>}}
2017-03-16 10:00:09.919 [info] <0.481.0>#ejabberd_listener:accept:333 (#Port<0.12671>) Accepted connection ::FFFF:127.0.0.1:53528 -> ::FFFF:127.0.0.1:5280
2017-03-16 10:00:09.920 [info] <0.556.0>#ejabberd_http:init:158 started: {p1_tls,{tlssock,#Port<0.12671>,#Port<0.12672>}}
Related
gcloud function: Could not find local artifact: How to solve?
My cloud function code, is a maven-jar-project. It depends on other internal maven jar, so I have added that dependency to the pom.xml. Expected: I expect that the dependent jars will be automatically included in the cloud function deployment, however I get an error "could not find artifact". Local compilation & running does not have any issue. I don't want to copy paste those dependency sourcecode directly to my gcloud maven project. [bad ] [INFO] Installing <removed>-0.0.1-SNAPSHOT.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.659 s [INFO] Finished at: 2021-04-10T16:31:39-04:00 [INFO] ------------------------------------------------------------------------ >gcloud functions deploy response-adapter --entry-point fun.pubsub.<removed> --runtime java11 --memory 512MB --trigger-topic <removed> --env-vars-file env.yml Deploying function (may take a while - up to 2 minutes)...- For Cloud Build Stackdriver Logs, visit: Deploying function (may take a while - up to 2 minutes)...failed. ERROR: (gcloud.functions.deploy) OperationError: code=3, message=Build failed: ...maven-plugin-2.2.0.jar [INFO] Downloading from central: https://repo.maven.apache.org/maven2/com/google/cloud/tools/appengine-plugins-core/0.8.1/appengine-plugins-core-0.8.1.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/com/google/inject/guice/4.2.1/guice-4.2.1-no_aop.jar (521 kB at 375 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/yaml/snakeyaml/1.21/snakeyaml-1.21.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-lang3/3.8.1/commons-lang3-3.8.1.jar (502 kB at 357 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/glassfish/javax.json/1.0.4/javax.json-1.0.4.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/com/google/cloud/tools/appengine-maven-plugin/2.2.0/appengine-maven-plugin-2.2.0.jar (76 kB at 53 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-compress/1.19/commons-compress-1.19.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/com/google/cloud/tools/appengine-plugins-core/0.8.1/appengine-plugins-core-0.8.1.jar (236 kB at 164 kB/s) [INFO] Downloading from central: https://repo.maven.apache.org/maven2/commons-io/commons-io/2.5/commons-io-2.5.jar [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/glassfish/javax.json/1.0.4/javax.json-1.0.4.jar (85 kB at 59 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/yaml/snakeyaml/1.21/snakeyaml-1.21.jar (299 kB at 205 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/commons/commons-compress/1.19/commons-compress-1.19.jar (615 kB at 416 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/commons-io/commons-io/2.5/commons-io-2.5.jar (209 kB at 141 kB/s) [INFO] Downloaded from central: https://repo.maven.apache.org/maven2/com/google/cloud/functions/invoker/java-function-invoker/1.0.2/java-function-invoker-1.0.2.jar (4.2 MB at 2.6 MB/s) [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 17.127 s [INFO] Finished at: 2021-04-10T20:35:09Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project gcf-removed-adapter: Could not resolve dependencies for project gcf-demo:gcf-removed-adapter:jar:0.0.1-SNAPSHOT: Could not find artifact myadaptor:removed-mapper:jar:1.0- SNAPSHOT -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException; Error ID: efa79f31
To achieve this, you need to deploy from JAR. Like that, you create a JAR with all the dependency already included in it (maven shade). No resolution at deployment time, only get your JAR and put it in Cloud Functions.
IBM APIC starting loopback
I am new to API Connect, and I have installed npm, node and apic in my local MacBook. Now I have created a loopback directory and trying to run the loopback application using apic Start. However, I am not understanding the error received from the logs: MacBook-Pro-2:socialreviews Work$ apic start Error: Service socialreviews started but did not initialize within the timeout period. Dumping log buffer. [Tue Apr 30 12:02:42 2019] com.ibm.diagnostics.healthcenter.loader INFO: Node Application Metrics 3.1.3.201810251210 (Agent Core 3.2.6) [Tue Apr 30 12:02:42 2019] com.ibm.diagnostics.healthcenter.mqtt INFO: Connecting to broker localhost:1883 strong-supervisor attaching dashboard at /appmetrics-dash 2019-04-30T09:02:42.694Z pid:44844 worker:0 INFO supervisor starting (pid 44844) 2019-04-30T09:02:42.697Z pid:44844 worker:0 INFO supervisor reporting metrics to internal: 2019-04-30T09:02:42.709Z pid:44844 worker:0 INFO supervisor size set to undefined 2019-04-30T09:02:42.905Z pid:44848 worker:1 [Tue Apr 30 12:02:42 2019] com.ibm.diagnostics.healthcenter.loader INFO: Node Application Metrics 3.1.3.201810251210 (Agent Core 3.2.6) 2019-04-30T09:02:42.959Z pid:44848 worker:1 [Tue Apr 30 12:02:42 2019] com.ibm.diagnostics.healthcenter.mqtt INFO: Connecting to broker localhost:1883 2019-04-30T09:02:42.995Z pid:44848 worker:1 strong-supervisor attaching dashboard at /appmetrics-dash 2019-04-30T09:02:45.017Z pid:44848 worker:1 Web server listening at: http://0.0.0.0:4004 2019-04-30T09:24:29.148Z pid:44844 worker:0 WARN received SIGTERM, shutting down 2019-04-30T09:24:29.148Z pid:44844 worker:0 INFO supervisor size set to undefined 2019-04-30T09:24:29.148Z pid:44844 worker:0 INFO supervisor stopped Can someone help me with this issue please?
This issue is solved, however I am not 100% sure what was the exact issue. What I have done is ran apic edit command then when clicking on start it suddenly asked me to install docker. I have done so, then I started to have readable errors of some packages not installed. So I used npm commands to install them and my issue is fixed now! :)
Jenkins error: Authorization failed to svn in sonarqube.
I am using Jenkins 2.8 with Sonarqube Plugin 2.2.1. A week ago we had a problem with the sonar server and we get this error. To solve the problem we decided to create a new mysql schema and link it with sonar server. We did something like this: mysql –u root -plinux; create database sonarqube2 character set utf8; grant all privileges on sonarqube2.* to 'sonarsuer'#'localhost' identified by 'linux'; grant all privileges sonarqube2.* to 'sonaruser'#'%' identified by 'linux'; flush privileges; Note: We used the same user we had in the old database After update sonar.jdbc.url with the new data in sonar.properties and in Jenkins configuration we manage to deploy sonarqube again. Then, we tried to launch a SONAR job that we have already created before and we get this error: [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project cas: The svn blame command [svn blame --xml --non-interactive -x -w src/main/java/net/mycompany/cas/CookieRetrievingCookieGeneratorPatch.java] failed: svn: OPTIONS of 'https://my_svn_server/svn/mycompanyxf/cas/trunk/src/main/java/net/mycompany/cas/CookieRetrievingCookieGeneratorPatch.java': authorization failed: Could not authenticate to server: rejected Basic challenge (https://my_svn_server) -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project cas: The svn blame command [svn blame --xml --non-interactive -x -w src/main/java/net/mycompany/cas/CookieRetrievingCookieGeneratorPatch.java] failed: svn: OPTIONS of 'https://my_svn_server/svn/mycompanyxf/cas/trunk/src/main/java/net/mycompany/cas/CookieRetrievingCookieGeneratorPatch.java': authorization failed: Could not authenticate to server: rejected Basic challenge (https://my_svn_server) This is the whole stacktrace: [INFO] --- sonar-maven-plugin:2.6:sonar (default-cli) # cas --- [INFO] SonarQube version: 5.0.1 [WARNING] Invalid POM for org.samba.jcifs:jcifs-ext:jar:0.9.4, transitive dependencies (if any) will not be available, enable debug logging for more details INFO: Default locale: "es_ES", source code encoding: "UTF-8" (analysis is platform dependent) INFO: Work directory: /u01/jenkins_home/jobs/SONAR - MC - Cas/workspace/trunk/target/sonar INFO: SonarQube Server 5.0.1 [INFO] [13:47:05.297] Load global referentials... [INFO] [13:47:05.751] Load global referentials done: 458 ms [INFO] [13:47:05.771] User cache: /home/tomcat/.sonar/cache [INFO] [13:47:05.801] Install plugins [INFO] [13:47:07.792] Install JDBC driver [INFO] [13:47:07.802] Create JDBC datasource for jdbc:mysql://myserver:3306/sonarqube2?useUnicode=true&characterEncoding=utf8 [INFO] [13:47:11.353] Initializing Hibernate [ERROR] [13:47:15.591] No license for plugin views [INFO] [13:47:16.958] Load project referentials... [INFO] [13:47:18.003] Load project referentials done: 1045 ms [INFO] [13:47:18.003] Load project settings [INFO] [13:47:19.038] Loading technical debt model... [INFO] [13:47:19.097] Loading technical debt model done: 59 ms [INFO] [13:47:19.115] Apply project exclusions [INFO] [13:47:19.336] ------------- Scan CAS (Central Authentication Service) [INFO] [13:47:19.339] Load module settings [INFO] [13:47:21.334] Loading rules... [INFO] [13:47:23.049] Loading rules done: 1715 ms [INFO] [13:47:23.115] Configure Maven plugins [INFO] [13:47:23.367] No quality gate is configured. [INFO] [13:47:29.435] Initializer FindbugsMavenInitializer... [INFO] [13:47:29.437] Initializer FindbugsMavenInitializer done: 2 ms [INFO] [13:47:29.437] Base dir: /u01/jenkins_home/jobs/SONAR - MC - Cas/workspace/trunk [INFO] [13:47:29.437] Working dir: /u01/jenkins_home/jobs/SONAR - MC - Cas/workspace/trunk/target/sonar [INFO] [13:47:29.438] Source paths: src/main/webapp, pom.xml, src/main/java [INFO] [13:47:29.438] Test paths: src/test/java [INFO] [13:47:29.439] Binary dirs: target/classes [INFO] [13:47:29.439] Source encoding: UTF-8, default locale: es_ES [INFO] [13:47:29.439] Index files [INFO] [13:47:30.480] 36 files indexed [INFO] [13:47:31.213] Quality profile for java: Sonar way [INFO] [13:47:31.213] Quality profile for js: Sonar way [INFO] [13:47:31.300] JIRA issues sensor will not run as some parameters are missing. [INFO] [13:47:31.392] Sensor JavaSquidSensor... [INFO] [13:47:32.089] Java Main Files AST scan... [INFO] [13:47:32.094] 25 source files to be analyzed [INFO] [13:47:36.733] Java Main Files AST scan done: 4643 ms [INFO] [13:47:36.733] 25/25 source files analyzed [INFO] [13:47:36.746] Java bytecode scan... [INFO] [13:47:37.302] Java bytecode scan done: 556 ms [INFO] [13:47:37.305] Java Test Files AST scan... [INFO] [13:47:37.306] 5 source files to be analyzed [INFO] [13:47:37.626] 5/5 source files analyzed [INFO] [13:47:37.627] Java Test Files AST scan done: 321 ms [INFO] [13:47:37.633] Package design analysis... [INFO] [13:47:37.684] Package design analysis done: 51 ms [INFO] [13:47:37.801] Sensor JavaSquidSensor done: 6409 ms [INFO] [13:47:37.813] Sensor QProfileSensor... [INFO] [13:47:37.819] Sensor QProfileSensor done: 6 ms [INFO] [13:47:37.819] Sensor Maven dependencies... [INFO] [13:47:40.023] Sensor Maven dependencies done: 2204 ms [INFO] [13:47:40.026] Sensor JavaScriptSquidSensor... [INFO] [13:47:40.205] 6 source files to be analyzed [INFO] [13:47:45.590] 6/6 source files analyzed [INFO] [13:47:48.499] Sensor JavaScriptSquidSensor done: 8473 ms [INFO] [13:47:48.506] Sensor CoverageSensor... [INFO] [13:47:48.507] Sensor CoverageSensor done: 1 ms [INFO] [13:47:48.507] Sensor InitialOpenIssuesSensor... [INFO] [13:47:48.525] Sensor InitialOpenIssuesSensor done: 18 ms [INFO] [13:47:48.525] Sensor ProjectLinksSensor... [INFO] [13:47:48.557] Sensor ProjectLinksSensor done: 32 ms [INFO] [13:47:48.558] Sensor VersionEventsSensor... [INFO] [13:47:48.600] Sensor VersionEventsSensor done: 42 ms [INFO] [13:47:48.600] Sensor FileHashSensor... [INFO] [13:47:48.608] Sensor FileHashSensor done: 8 ms [INFO] [13:47:48.610] Sensor CoberturaSensor... [INFO] [13:47:48.616] parsing /u01/jenkins_home/jobs/SONAR - MC - Cas/workspace/trunk/target/site/cobertura/coverage.xml [INFO] [13:47:49.078] Sensor CoberturaSensor done: 468 ms [INFO] [13:47:49.078] Sensor SCM Sensor... [INFO] [13:47:49.089] SCM provider for this project is: svn [INFO] [13:47:49.089] Retrieve SCM blame information... [INFO] [13:47:49.218] 36 files to be analyzed [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1:04.240s [INFO] Finished at: Fri Aug 12 13:47:54 CEST 2016 [INFO] Final Memory: 58M/955M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project cas: The svn blame command [svn blame --xml --non-interactive -x -w src/main/java/net/mycompany/cas/CookieRetrievingCookieGeneratorPatch.java] failed: svn: OPTIONS of 'https://my_svn_server/svn/mycompanyxf/cas/trunk/src/main/java/net/mycompany/cas/CookieRetrievingCookieGeneratorPatch.java': authorization failed: Could not authenticate to server: rejected Basic challenge (https://my_svn_server) -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project cas: The svn blame command [svn blame --xml --non-interactive -x -w src/main/java/net/mycompany/cas/CookieRetrievingCookieGeneratorPatch.java] failed: svn: OPTIONS of 'https://my_svn_server/svn/mycompanyxf/cas/trunk/src/main/java/net/mycompany/cas/CookieRetrievingCookieGeneratorPatch.java': authorization failed: Could not authenticate to server: rejected Basic challenge (https://my_svn_server) Should I change aditional credential in Jenkins? Any help would be appreciated.
See SonarQube 5.0 SCM support documentation for details on how to configure SVN authentication (which is what is failing here) using sonar.svn.username and sonar.svn.password.secured. (side-note: SonarQube 5.0 is pretty old and known for having performance issues, you should really upgrade to latest/LTS version)
eJabberd with Riak
I have configured a Riak cluster and all is well. I configured ejabberd.yml to talk to it but the last few lines I see in the logs are as below and I can't figure out how to debug it any further.
Anyone able to help?
Change ejabberd install user to root...
Missing ssl cert for your host. Generating snakeoil ssl cert for xmpp.alchemy.local...
Generating a 4096 bit RSA private key
..............................................++
..............................................++
writing new private key to '/tmp/selfsigned.key'
-----
Writing ssl cert and private key to '/opt/ejabberd/ssl/host.pem'...
Missing ssl cert for your xmpp domain. Generating snakeoil ssl cert for alchemy.local...
Generating a 4096 bit RSA private key
................................................++
........................++
writing new private key to '/tmp/selfsigned.key'
-----
Writing ssl cert and private key to '/opt/ejabberd/ssl/alchemy.local.pem'...
Generating ejabberd config file...
Generating ejabberdctl config file...
Starting ejabberd...
tail: cannot open ‘/var/log/ejabberd/crash.log’ for reading: No such file or directory
tail: cannot open ‘/var/log/ejabberd/error.log’ for reading: No such file or directory
tail: cannot open ‘/var/log/ejabberd/erlang.log’ for reading: No such file or directory
tail: ‘/var/log/ejabberd/crash.log’ has been replaced with a remote file. giving up on this name
tail: ‘/var/log/ejabberd/error.log’ has been replaced with a remote file. giving up on this name
09:57:16.424 [info] Application lager started on node ejabberd#xmpp
09:57:16.431 [info] Application crypto started on node ejabberd#xmpp
09:57:16.442 [info] Application sasl started on node ejabberd#xmpp
09:57:16.452 [info] Application asn1 started on node ejabberd#xmpp
09:57:16.452 [info] Application public_key started on node ejabberd#xmpp
09:57:16.466 [info] Application ssl started on node ejabberd#xmpp
09:57:16.474 [info] Application p1_yaml started on node ejabberd#xmpp
09:57:16.485 [info] Application p1_tls started on node ejabberd#xmpp
09:57:16.493 [info] Application p1_xml started on node ejabberd#xmpp
09:57:16.507 [info] Application p1_stringprep started on node ejabberd#xmpp
09:57:16.511 [info] Application p1_zlib started on node ejabberd#xmpp
09:57:16.519 [info] Application cache_tab started on node ejabberd#xmpp
09:57:16.677 [info] Application mnesia started on node ejabberd#xmpp
09:57:17.179 [info] Application inets started on node ejabberd#xmpp
09:57:17.558 [notice] Changed loglevel of //var/log/ejabberd/ejabberd.log to debug
09:57:17.567 [debug] Supervisor ejabberd_sup started ejabberd_hooks:start_link() at pid <0.239.0>
09:57:17.575 [debug] Supervisor kernel_safe_sup started pg2:start_link() at pid <0.241.0>
09:57:17.575 [debug] Supervisor ejabberd_sup started ejabberd_node_groups:start_link() at pid <0.240.0>
09:57:17.575 [debug] Supervisor ejabberd_sup started ejabberd_system_monitor:start_link() at pid <0.242.0>
09:57:17.577 [debug] Supervisor ejabberd_sup started ejabberd_router:start_link() at pid <0.243.0>
09:57:17.579 [debug] Supervisor ejabberd_sup started ejabberd_router_multicast:start_link() at pid <0.249.0>
09:57:17.582 [debug] Supervisor ejabberd_sup started ejabberd_s2s:start_link() at pid <0.255.0>
09:57:17.584 [debug] Supervisor ejabberd_sup started ejabberd_local:start_link() at pid <0.265.0>
09:57:17.585 [debug] The option captcha_cmd is not configured, but some module wants to use the CAPTCHA feature.
09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_captcha:start_link() at pid <0.271.0>
09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_s2s_in_sup, ejabberd_s2s_in) at pid <0.273.0>
09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_s2s_out_sup, ejabberd_s2s_out) at pid <0.274.0>
09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_service_sup, ejabberd_service) at pid <0.275.0>
09:57:17.587 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_iq_sup, gen_iq_handler) at pid <0.276.0>
09:57:17.588 [debug] Supervisor ejabberd_sup started ejabberd_tmp_sup:start_link(ejabberd_frontend_socket_sup, ejabberd_frontend_socket) at pid <0.277.0>
09:57:17.588 [debug] Supervisor ejabberd_sup started ejabberd_listener:start_link() at pid <0.278.0>
09:57:17.591 [info] Application protobuffs started on node ejabberd#xmpp
09:57:17.591 [info] Application riak_pb started on node ejabberd#xmpp
09:57:17.591 [info] Application riakc started on node ejabberd#xmpp
09:57:17.600 [debug] Supervisor inet_gethost_native_sup started undefined at pid <0.289.0>
09:57:17.600 [debug] Supervisor kernel_safe_sup started inet_gethost_native:start_link() at pid <0.288.0>
I managed to get a bit more detail by ejabberdctl debug. It seems to be having an issue with the node name, but the exact same config works fine if i don't add Riak to the ejabberd.yml file.
tail: cannot open ‘/var/log/ejabberd/crash.log’ for reading: No such file or directory
tail: cannot open ‘/var/log/ejabberd/error.log’ for reading: No such file or directory
tail: cannot open ‘/var/log/ejabberd/erlang.log’ for reading: No such file or directory
{error_logger,{{2016,2,4},{19,30,38}},"Invalid node name: ~p~n",['debug-not a tty-ejabberd#xmpp']}
{error_logger,{{2016,2,4},{19,30,38}},crash_report,[[{initial_call,{net_kernel,init,['Argument__1']}},{pid,<0.20.0>},{registered_name,[]},{error_info,{exit,{error,badarg},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line,322}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}},{ancestors,[net_sup,kernel_sup,<0.10.0>]},{messages,[]},{links,[<0.17.0>]},{dictionary,[{longnames,false}]},{trap_exit,true},{status,running},{heap_size,987},{stack_size,27},{reductions,902}],[]]}
{error_logger,{{2016,2,4},{19,30,38}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfargs,{net_kernel,start_link,[['debug-not a tty-ejabberd',shortnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2016,2,4},{19,30,38}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}},{offender,[{pid,undefined},{name,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2016,2,4},{19,30,38}},crash_report,[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.9.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,133}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}},{ancestors,[<0.8.0>]},{messages,[{'EXIT',<0.10.0>,normal}]},{links,[<0.8.0>,<0.7.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,27},{reductions,117}],[]]}
{error_logger,{{2016,2,4},{19,30,38}},std_info,[{application,kernel},{exited,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}},{type,permanent}]}
{"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{kernel,start,[normal,[]]}}}"}
Crash dump was written to: //var/log/ejabberd/erl_crash_20160204-193037.dump
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,net_sup,{shutdown,{failed_to_start_child,net_kernel,{'EXIT',nodistribution}}}}},{k
**** Update ****
The reason that this was happening was because I hadn't specified the --net network connection in my Docker run command and so it couldn't find the network. Unfortunately there is no debug to indicate this it just hangs forever (this would happen in the general case where the network that hosts the Riak cluster cannot be found and is a nightmare to debug).
I still don't know why the "debug" flag causes tty to be added to the node name but i suspect it is somehow related as when i fixed it that also stopped appearing.
Anyone interested in knowing the detail can view it here https://github.com/rroemhild/docker-ejabberd/issues/81#issuecomment-181133336
You are starting the Erlang VM with an invalid node name:
{error_logger,{{2016,2,4},{19,30,38}},"Invalid node name: ~p~n",['debug-not a tty-ejabberd#xmpp']}
Check where you have configured this: 'debug-not a tty-ejabberd#xmpp', as it is indeed not a valid Erlang VM cluster node name.
Jenkins-Sonar communication on Openshift
I am making a development environnement based on Jenkins and Sonar. Both are placed on isolated gears. The Jenkins gear has been created with the Instant App option. The Sonar gear has been created thanks to these github indications. I created a Jenkins free-style job in order to analysis a Maven project. The script used on that job is based on this wordpress article. # Build script of the Job settingsPath=$OPENSHIFT_DATA_DIR/settings.xml settings="<settings>\n <localRepository>$OPENSHIFT_DATA_DIR</localRepository>\n</settings>\n" echo $settings > $settingsPath # Cleaning of the workspace mvn --global-settings $settingsPath clean test # Preparation of Sonar informations export SONAR_JDBC="-Dsonar.jdbc.url=jdbc:mysql://xxx.xxx.xxx.xxx:3306/sonar?useUnicode=true&characterEncoding=utf8" export SONAR_DRIVER=-Dsonar.jdbc.driver=com.mysql.jdbc.Driver export SONAR_DBUSER=-Dsonar.jdbc.username=xxx export SONAR_DBPASS=-Dsonar.jdbc.password=xxx export SONAR_URL=-Dsonar.host.url=http://sonar-alc.rhcloud.com export SONAR_OPTS="$SONAR_JDBC $SONAR_DRIVER $SONAR_DBUSER $SONAR_DBPASS $SONAR_URL" # Sonar analysis mvn --global-settings $settingsPath sonar:sonar $SONAR_OPTS On the execution of the mvn sonar:sonar command, I have the following error: Can not execute SonarQube analysis: Fail to connect to database: Cannot create PoolableConnectionFactory (Communications link failure Here is the stacktrace corresponding to this error: [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building ClientEvalcolor 1.0 [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- sonar-maven-plugin:2.1:sonar (default-cli) # ClientEvalcolor --- [INFO] SonarQube version: 3.3.1 [INFO] [03:28:09.324] Create JDBC datasource for jdbc:mysql://xxx.xxx.xxx.xxx:3306/sonar?useUnicode=true&characterEncoding=utf8 [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 12.634s [INFO] Finished at: Mon Nov 25 03:28:10 EST 2013 [INFO] Final Memory: 12M/182M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.1:sonar (default-cli) on project ClientEvalcolor: Can not execute SonarQube analysis: Fail to connect to database: Cannot create PoolableConnectionFactory (Communications link failure [ERROR] [ERROR] The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.): No route to host [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException Build step 'Execute shell' marked build as failure Finished: FAILURE I know that an Openshift mysql database isn't accessible from a remote server, but Sonar seems to be runnable on Openshift, and the article that I previously linked successfully did it. Do you have any idea about how to fix that ? Thank you, Alvaro C.
I finally succeeded on making my Jenkins gear send data to my Sonar gear ! I'll explain the solution I found here, maybe it will help some people. There a three ways to access an Openshift database: The gear that contains that database can access it easily on localhost:3306. That's the usual case. From your own computer, you can bind ports (with the rhc tool) in order to access the database. This can't be applied from another gear, and requires the rhc tool to keep running. Any gear from your account can access the database of a scalable application. Usage: When creating the Sonar gear, it's necessary to set the gear as scalable (this can't be done with jenkins/diy gears). Adding a database cartridge to this gear will consume 1 gear, but this database can be accessed from any Openshift application. Notice that this new database will have a port different than 3306 (in my case, 39536). If you don't have this, that's probably that the embedded app isn't set scalable. The Jenkins job script that I put in my question is correct. Changing all these "xxxxx" and the port with your database info will permit Jenkins to do his job !