RabbitMQ not working on OS X Mountain Lion - macos
I can't seem to make RabbitMQ work on a fresh OS X Mountain Lion.
It simply fails to start.
System config below:
OS X 10.8.4
Xcode 4.6.3
Brew 0.9.4
I've upgraded brew and updated all packages:
brew upgrade
brew update
Installed RabbitMQ using the following command (I've also tried reinstalling it a couple of times without any luck):
brew install rabbitmq
Install output below:
server1:~ server1$ brew install rabbitmq
==> Downloading http://www.rabbitmq.com/releases/rabbitmq-server/v3.1.3/rabbitmq
Already downloaded: /Library/Caches/Homebrew/rabbitmq-3.1.3.tar.gz
==> /usr/bin/unzip -qq -j /usr/local/Cellar/rabbitmq/3.1.3/plugins/rabbitmq_mana
==> Caveats
Management Plugin enabled by default at http://localhost:15672
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
To have launchd start rabbitmq at login:
ln -sfv /usr/local/opt/rabbitmq/*.plist ~/Library/LaunchAgents
Then to load rabbitmq now:
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.rabbitmq.plist
Or, if you don't want/need launchctl, you can just run:
rabbitmq-server
==> Summary
šŗ /usr/local/Cellar/rabbitmq/3.1.3: 964 files, 23M, built in 2 seconds
Tried to start the server using the following command:
sudo rabbitmq-server start
Which gives me the following output:
Password:
RabbitMQ 3.1.3. Copyright (C) 2007-2013 VMware, Inc.
## ## Licensed under the MPL. See http://www.rabbitmq.com/
## ##
########## Logs: /usr/local/var/log/rabbitmq/rabbit#localhost.log
###### ## /usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
##########
Starting broker...
BOOT FAILED
===========
Error description:
{badmatch,{error,{no_such_vhost,<<"/">>}}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
Stack trace:
[{rabbit_error_logger,boot,0,
[{file,"src/rabbit_error_logger.erl"},{line,42}]},
{rabbit,'-run_boot_step/1-lc$^1/1-1-',1,
[{file,"src/rabbit.erl"},{line,488}]},
{rabbit,run_boot_step,1,[{file,"src/rabbit.erl"},{line,487}]},
{rabbit,'-start/2-lc$^0/1-0-',1,[{file,"src/rabbit.erl"},{line,453}]},
{rabbit,start,2,[{file,"src/rabbit.erl"},{line,453}]},
{application_master,start_it_old,4,
[{file,"application_master.erl"},{line,274}]}]
BOOT FAILED
===========
Error description:
{could_not_start,rabbit,
{bad_return,
{{rabbit,start,[normal,[]]},
{'EXIT',
{rabbit,failure_during_boot,
{badmatch,{error,{no_such_vhost,<<"/">>}}}}}}}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
{"init terminating in do_boot",{rabbit,failure_during_boot,{could_not_start,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot,{badmatch,{error,{no_such_vhost,<<1 byte>>}}}}}}}}}}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
server1:~ server1$
server1:~ server1$ sudo rabbitmq-server start
RabbitMQ 3.1.3. Copyright (C) 2007-2013 VMware, Inc.
## ## Licensed under the MPL. See http://www.rabbitmq.com/
## ##
########## Logs: /usr/local/var/log/rabbitmq/rabbit#localhost.log
###### ## /usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
##########
Starting broker...
BOOT FAILED
===========
Error description:
{badmatch,{error,{no_such_vhost,<<"/">>}}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
Stack trace:
[{rabbit_error_logger,boot,0,
[{file,"src/rabbit_error_logger.erl"},{line,42}]},
{rabbit,'-run_boot_step/1-lc$^1/1-1-',1,
[{file,"src/rabbit.erl"},{line,488}]},
{rabbit,run_boot_step,1,[{file,"src/rabbit.erl"},{line,487}]},
{rabbit,'-start/2-lc$^0/1-0-',1,[{file,"src/rabbit.erl"},{line,453}]},
{rabbit,start,2,[{file,"src/rabbit.erl"},{line,453}]},
{application_master,start_it_old,4,
[{file,"application_master.erl"},{line,274}]}]
BOOT FAILED
===========
Error description:
{could_not_start,rabbit,
{bad_return,
{{rabbit,start,[normal,[]]},
{'EXIT',
{rabbit,failure_during_boot,
{badmatch,{error,{no_such_vhost,<<"/">>}}}}}}}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
{"init terminating in do_boot",{rabbit,failure_during_boot,{could_not_start,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot,{badmatch,{error,{no_such_vhost,<<1 byte>>}}}}}}}}}}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
I also get the following output when running the rabbitmqctl status:
server1:~ server1$ rabbitmqctl status
Status of node rabbit#localhost ...
Error: unable to connect to node rabbit#localhost: nodedown
DIAGNOSTICS
===========
nodes in question: [rabbit#localhost]
hosts, their running nodes and ports:
- localhost: [{rabbitmqctl1391,49583}]
current node details:
- node name: rabbitmqctl1391#server1
- home dir: /Users/server1
- cookie hash: 5K+867WqzDShyhtWE7X49Q==
Related
go application build with bazel can't link when running inside container
I am trying to containerize my application build, though, when running the build that uses bazel with bazel-gazelle inside a container I will get this error: $ bazel run --spawn_strategy=local //:gazelle --verbose_failures INFO: Analyzed target //:gazelle (0 packages loaded, 0 targets configured). INFO: Found 1 target... ERROR: /home/workstation/.cache/bazel/_bazel_workstation/fb227af4c7b6aa39cc5b15d7fd9b737a/external/go_sdk/BUILD.bazel:43:15: GoToolchainBinary external/go_sdk/builder [for host] failed: (Exit 1): go failed: error executing command (cd /home/workstation/.cache/bazel/_bazel_workstation/fb227af4c7b6aa39cc5b15d7fd9b737a/execroot/__main__ && \ exec env - \ GOROOT_FINAL=GOROOT \ external/go_sdk/bin/go tool link -o bazel-out/host/bin/external/go_sdk/builder bazel-out/host/bin/external/go_sdk/builder.a) # Configuration: e0f1106e28100863b4221c55fca6feb935acec078da5376e291cf644e275dae5 # Execution platform: #local_config_platform//:host /opt/go/pkg/tool/linux_amd64/link: mapping output file failed: invalid argument Target //:gazelle failed to build INFO: Elapsed time: 2.302s, Critical Path: 0.35s INFO: 2 processes: 2 internal. FAILED: Build did NOT complete successfully FAILED: Build did NOT complete successfully I tried to run it standalone: $ /home/workstation/.cache/bazel/_bazel_workstation/fb227af4c7b6aa39cc5b15d7fd9b737a/external/go_sdk/bin/go tool link -o bazel-out/host/bin/external/go_sdk/builder bazel-out/host/bin/external/go_sdk/builder.a /opt/go/pkg/tool/linux_amd64/link: mapping output file failed: invalid argument and still got no success. Never had this kind of link problem and the linker don't provide much more information. Tried to install all packages I could think of and still no luck. For context: Running Ubuntu 20.04 LTS Docker 20.10.9 Bazel 4.2.2 Rules GO v0.31.0 Bazel Gazelle v0.25.0 Also tried to run it with the strace, though I don't think I am skilled enough to find meaningful information from the tool output. #edit For more context: e$ /home/workstation/.cache/bazel/_bazel_workstation/fb227af4c7b6aa39cc5b15d7fd9b737a/external/go_sdk/bin/go tool link -v -o bazel-out/host/bin/external/go_sdk/builder bazel-out/host/bin/external/go_sdk/builder.a HEADER = -H5 -T0x401000 -R0x1000 searching for runtime.a in /opt/go/pkg/linux_amd64/runtime.a /opt/go/pkg/tool/linux_amd64/link: mapping output file failed: invalid argument
ansible-galaxy install ahuffman.resolv does not work
I thought I had found something that would make managing the /etc/resolv.conf file easy. https://galaxy.ansible.com/ahuffman/resolv but when I try to install this role as per the documentation like so ... bash-3.2$ ansible-galaxy install ahuffman.resolv I get this error ... Starting galaxy role install process [WARNING]: - ahuffman.resolv was NOT installed successfully: Unknown error when attempting to call Galaxy at 'https://galaxy.ansible.com/api/': <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)> ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list. I have never used ansible-galaxy before ... and probably won't ever again :( Please help. If I run with -vvvv I see this additional output: ansible-galaxy 2.10.5 config file = None configured module search path = ['/Users/red/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/ansible executable location = /Library/Frameworks/Python.framework/Versions/3.6/bin/ansible-galaxy python version = 3.6.8 (v3.6.8:3c6b436a57, Dec 24 2018, 02:04:31) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] No config file found; using defaults Starting galaxy role install process Processing role ahuffman.resolv Initial connection to galaxy_server: https://galaxy.ansible.com Opened /Users/red/.ansible/galaxy_token Calling Galaxy at https://galaxy.ansible.com/api/ [WARNING]: - ahuffman.resolv was NOT installed successfully: Unknown error when attempting to call Galaxy at 'https://galaxy.ansible.com/api/': <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)> ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list. Running with --ignore-certs seems to have fixed the problem but the usage from anisble-galaxy does mention a --ignore-certs option: usage: ansible-galaxy [-h] [--version] [-v] TYPE ... Perform various Role and Collection related operations. positional arguments: TYPE collection Manage an Ansible Galaxy collection. role Manage an Ansible Galaxy role. optional arguments: --version show program's version number, config file location, configured module search path, module location, executable location and exit -h, --help show this help message and exit -v, --verbose verbose mode (-vvv for more, -vvvv to enable connection debugging)
Error installing Elasticsearch 7 - Failed dependencies
On my dedicated server I currently have Elasticsearch 6 installed. I would like to upgrade to Elasticsearch 7. I'm using the "Download and install the RPM Manually" method. Here's the link that explains the steps: https://www.elastic.co/guide/en/elasticsearch/reference/current/rpm.html Here are my terminal steps: [root#server ~]# wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.0.0-x86_64.rpm --2019-04-18 17:19:20-- https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.0.0-x86_64.rpm Resolving artifacts.elastic.co (artifacts.elastic.co)... 2a04:4e42:2e::734, 151.101.198.222 Connecting to artifacts.elastic.co (artifacts.elastic.co)|2a04:4e42:2e::734|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 346827255 (331M) [application/octet-stream] Saving to: āelasticsearch-7.0.0-x86_64.rpmā 100%[=============================================================================================================================================>] 346,827,255 106MB/s in 3.3s 2019-04-18 17:19:43 (102 MB/s) - āelasticsearch-7.0.0-x86_64.rpmā saved [346827255/346827255] [root#server ~]# wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.0.0-x86_64.rpm.sha512 --2019-04-18 17:20:01-- https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.0.0-x86_64.rpm.sha512 Resolving artifacts.elastic.co (artifacts.elastic.co)... 2a04:4e42:2e::734, 151.101.198.222 Connecting to artifacts.elastic.co (artifacts.elastic.co)|2a04:4e42:2e::734|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 160 [application/octet-stream] Saving to: āelasticsearch-7.0.0-x86_64.rpm.sha512ā 100%[=============================================================================================================================================>] 160 --.-K/s in 0s 2019-04-18 17:20:01 (22.7 MB/s) - āelasticsearch-7.0.0-x86_64.rpm.sha512ā saved [160/160] [root#server ~]# shasum -a 512 -c elasticsearch-7.0.0-x86_64.rpm.sha512 elasticsearch-7.0.0-x86_64.rpm: OK [root#server ~]# sudo rpm --install elasticsearch-7.0.0-x86_64.rpm warning: elasticsearch-7.0.0-x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID d88e42b4: NOKEY error: Failed dependencies: elasticsearch < 7.0.0 is obsoleted by elasticsearch-0:7.0.0-1.x86_64 Here are my server specifications: Centos: 7.6 Java: openjdk version "1.8.0_201" OpenJDK Runtime Environment (build 1.8.0_201-b09) OpenJDK 64-Bit Server VM (build 25.201-b09, mixed mode)
Did you add the RPM repository previously? I'm not sure where else the obsoleted by elasticsearch-0:7.0.0-1.x86_64 would be coming from otherwise. If so I'd clean the cache directory, fetch all available versions, and then install the desired one: yum clean all yum --showduplicate list elasticsearch yum install elasticsearch-0:7.0.0-1.x86_64
When rsyslog (v8.39.0) mmnormalize is not recognized. How can this be fixed?
I am trying to use mmnormalize to structure text logs. Both with rsyslog 8.16.x and with 8.39.0 when trying to use mmnormalize as an action logs show that the module was not recognized. Below are details. How can I set up to use mmnormalize with rsyslog? remediation already tried Installed separately liblognorm, libstr, json-c,libfastjson Upgraded rsyslog from 8.16.x to 8.39.0 rsyslog .conf module(load="mmnormalize") # text parsing syslog log messages Dec 3 11:33:55 sys1 systemd[1]: Starting System Logging Service... Dec 3 11:33:55 sys1 systemd[1]: Started System Logging Service. Dec 3 11:33:55 sys1 rsyslogd: could not load module 'mmnormalize', errors: trying to load module /usr/lib/rsyslog/mmnormalize.so: /usr/lib/rsyslog/mmnormalize.so: cannot open shared object file: No such file or directory [v8.39.0 try http://www.rsyslog.com/e/2066 ] Dec 3 11:33:55 sys1 rsyslogd: module name 'mmnormalize' is unknown [v8.39.0 try http://www.rsyslog.com/e/2209 ] Dec 3 11:33:55 sys1 rsyslogd: error during parsing file /etc/rsyslog.d/52-tomcat.conf, on or before line 52: errors occured in file '/etc/rsyslog.d/52-tomcat.conf' around line 52 [v8.39.0 try http://www.rsyslog.com/e/2207 ]
The following way to install mmnormalize worked for me. I was running this on Ububutu (Xenial) sudo apt-get install rsyslog-mmnormalize Rich Megginson (thank you) answered as below to the same question I posted to rsyslog mailing list (rsyslog#lists.adiscon.com). As mentioned above it worked for me. "On RHEL/CentOS/Fedora and similar platforms, the rsyslog-mmnormalize is a separate RPM that must be installed separately e.g. yum install rsyslog rsyslog-mmnormalize .... "
VirtualBox And Genymotion launch from command line issue
I have installed latests Genymotion version 2.4.0 and Virtual Box 4.3.26 r98988. When i run genymotion from Jenkins or command line on MacOSX Yosemite: /Applications/Genymotion.app/Contents/MacOS/player --vm-name "Google Nexus 5 - 4.4.4 - API 19 - 1080x1920" i have this issues: Logging activities to file: .Genymobile/genymotion.log Logging activities to file: .Genymobile/Genymotion/deployed/Google Nexus 5 - 4.4.4 - API 19 - 1080x1920/genymotion-player.log OpenGL connected to 192.168.56.101:25000 Port 22468 will be used for OpenGL data connections Unknown TCPCLI command 1003 Jenkins waits indefinitely and the calabash tests are not running. Logs of genymotion have no particular errors, but virtualbox's log (VBoxSVC.log) have this error: 00:00:00.130196 nspr-2 HostDnsMonitorProxy::notify 00:00:00.130211 nspr-2 HostDnsMonitorProxy: Host's DNS information updated: 00:00:00.130214 nspr-2 server 1: 10.10.0.30 00:00:00.130217 nspr-2 server 2: 10.10.0.31 00:00:00.130221 nspr-2 no search string entries 00:00:00.130223 nspr-2 no domain set 00:00:00.134010 nspr-2 failed to create vboxnet0, error (0x80004005) 00:00:00.134189 nspr-2 VDInit finished
You may want to try "--quiet" while running the player. I have the same error "Unknown TCPCLI command 1003" but it still seems to work fine. This is how I run mine. File: run.sh vboxmanage snapshot "Google Nexus S - 2.3.7 - API 10 - 480x800" restore "factory" /Applications/Genymotion.app/Contents/MacOS/player --quiet --vm-name "Google Nexus S - 2.3.7 - API 10 - 480x800" & echo "going to sleep" sleep 30 echo "wake up"