After updating RabbitMQ to version 3.3.3-1 using their APT repository, it will no longer start:
Setting up rabbitmq-server (3.3.3-1) ...
* Starting message broker rabbitmq-server * FAILED - check /var/log/rabbitmq/startup_{log, _err}
[fail]
invoke-rc.d: initscript rabbitmq-server, action "start" failed.
dpkg: error processing package rabbitmq-server (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
rabbitmq-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
startup_log:
{"init terminating in do_boot",{{case_clause,{ok,[]}},[{rabbit_prelaunch,dist_port_set_check,0,[]},{rabbit_prelaunch,start,0,[]},{init,start_it,1,[]},{init,start_em,1,[]}]}}
startup_err:
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
erl_crash.dump
I'm running Ubuntu 14.04 LTS (GNU/Linux 3.13.0-29-generic x86_64)
Erlang version: 1:17.0
I can't seem to find any information on why it is failing to start. Any help would be much appreciated.
Looking at rabbit_prelaunch I think this could happen if you have a config file but it is completely empty. That's not allowed (not a legal Erlang term), but this exception certainly sucks. I'll file a bug to fix that.
EDIT: fixed in 3.3.4.
Related
after i installed wxWidgets libs and reinstall my version of erlang otp to can i run ":observer.start", my application come fails with this error:
i'm use evm to manage my erlang otp versions.
[info] GET /dashboard/admin
[error] #PID<0.1290.0> running DashboardWeb.Endpoint (cowboy_protocol) terminated
Server: test.lvh.me:5000 (http)
Request: GET /dashboard/admin
** (exit) exited in: :gen_server.call(#PID<0.797.0>, {:checkout, #Reference<0.3971714438.3053715457.259419>, true, 15000}, 5000)
** (EXIT) time out
i researched to try solve error and i finded this link "https://github.com/elixir-ecto/db_connection/issues/127", but i can't solve error, i use elixir 1.6.6 and erlang otp 20.3, i install erlang otp 21.0 like link mention but not work, anyone solved this issue?
I am installing and configuring a very basic Jenkins installation using Chef. When i attempt to run the following recipe:
include_recipe "apt::default"
apt_repository "jenkins" do
uri "http://pkg.jenkins-ci.org/debian"
key "http://pkg.jenkins-ci.org/debian/jenkins-ci.org"
components ["binary/"]
action :add
end
package "jenkins" do
version '2.62'
end
service "jenkins" do
supports [:stop, :start, :restart]
action [:start, :enable]
end
I receive the following errors (displayed in the terminal):
192.168.9.207 [2017-05-25T10:50:58-04:00] ERROR: Running exception handlers
192.168.9.207 Running handlers complete
192.168.9.207 [2017-05-25T10:50:58-04:00] ERROR: Exception handlers complete
192.168.9.207 Chef Client failed. 2 resources updated in 20 seconds
192.168.9.207 [2017-05-25T10:50:58-04:00] INFO: Sending resource update report (run-id: 2b59b80e-b787-4e93-805b-837b4d3264fb)
192.168.9.207 [2017-05-25T10:50:58-04:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
192.168.9.207 [2017-05-25T10:50:58-04:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
192.168.9.207 [2017-05-25T10:50:58-04:00] ERROR: apt_package[jenkins] (jenkins-installation::default line 21) had an error: Chef::Exceptions::Package: No candidate version available for jenkins
192.168.9.207 [2017-05-25T10:50:58-04:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
The error explains that there is no candidate version available for Jenkins. After the run fails, if I run sudo apt-get update on the managed node I receive the following error:
Err http://pkg.jenkins-ci.org trusty/binary/ amd64 Packages
404 Not Found
Err http://pkg.jenkins-ci.org trusty/binary/ i386 Packages
404 Not Found
Ign http://pkg.jenkins-ci.org trusty/binary/ Translation-en_US
Ign http://pkg.jenkins-ci.org trusty/binary/ Translation-en
Fetched 5,976 kB in 3s (1,528 kB/s)
W: Failed to fetch http://pkg.jenkins-ci.org/debian/dists/trusty/binary//binary-amd64/Packages 404 Not Found
W: Failed to fetch http://pkg.jenkins-ci.org/debian/dists/trusty/binary//binary-i386/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
I am fairly new to Chef. This error appears to be related to retrieving a Jenkins package, however I am not sure how to remedy this error. Please let me know if additional information is required to troubleshoot this issue.
Thank you to everybody in advance for any guidance you are able to provide. I have searched through the Chef documentation but haven't seen much aside from specifying the package version: https://docs.chef.io/resource_package.html.
Specify distribution 'binary/' instead of components 'binary/'. This will fix the 404s that you get because of trusty/binary/.
At least, this is what I see from the "official" Jenkins cookbook, which I btw. suggest to use.
EDIT: So the result would be:
apt_repository "jenkins" do
uri "http://pkg.jenkins-ci.org/debian"
key "http://pkg.jenkins-ci.org/debian/jenkins-ci.org"
distribution "binary/"
end
I am working through the openlayers custom build tutorial and I am getting the following error
info ol Parsing dependencies
info ol Compiling 345 sources
events.js:141
throw er; // Unhandled 'error' event
^
Error: spawn java ENOENT
at exports._errnoException (util.js:870:11)
at Process.ChildProcess._handle.onexit
(internal/child_process.js:178:32)
at onErrorNT (internal/child_process.js:344:16)
at nextTickCallbackWith2Args (node.js:441:9)
at process._tickCallback (node.js:355:17)
Exit 1
when I run:
node tasks/build.js build/ol-custom.json build/ol-custom.js
Googling the error gives a solution where it could be another node instance running in the background (there isnt)
also the tutorial says closure-util should be in:
node_modules/openlayers/node_modules
but it is actually in:
node_modules/closure-util
Any idea why this is happening?
It turns out java wasn't set up properly on my path and so it couldn't build. Remember to check your environment with java -version.
On Ubuntu you can install install java 11 (working with this version):
sudo apt install openjdk-11-jre-headless
It should return:
openjdk version "11.0.8" 2020-07-14
OpenJDK Runtime Environment (build 11.0.8+10-post-Ubuntu-0ubuntu118.04.1)
OpenJDK 64-Bit Server VM (build 11.0.8+10-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
Then you can run again:
node tasks/build.js build/ol-custom.json build/ol-custom.js
installed neo4j 2.2.1 after first removing the previous version.
service neo4j-service start
produces the error:
Failed to start neo4j-service.service: Unit neo4j-service.service failed to load: No such file or directory.
System is:
system: os => {"name"=>"Ubuntu", "family"=>"Debian", "release"=>{"major"=>"15.04", "full"=>"15.04"}, "lsb"=>{"distcodename"=>"vivid", "distid"=>"Ubuntu", "distdescription"=>"Ubuntu 15.04", "distrelease"=>"15.04", "majdistrelease"=>"15.04"}}
Output of the install script:
root#cb-8:~# aptitude install neo4j -y # Install Neo4j, community edition
The following NEW packages will be installed:
daemon{a} neo4j
0 packages upgraded, 2 newly installed, 0 to remove and 0 not to upgrade.
Need to get 0 B/53.2 MB of archives. After unpacking 62.4 MB will be used.
Selecting previously unselected package daemon.
(Reading database ... 183856 files and directories currently installed.)
Preparing to unpack .../daemon_0.6.4-1_amd64.deb ...
Unpacking daemon (0.6.4-1) ...
Selecting previously unselected package neo4j.
Preparing to unpack .../archives/neo4j_2.2.1_all.deb ...
Unpacking neo4j (2.2.1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (219-7ubuntu3) ...
Setting up daemon (0.6.4-1) ...
Setting up neo4j (2.2.1) ...
update-rc.d: error: initscript does not exist: /etc/init.d/neo4j-service
dpkg: error processing package neo4j (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
neo4j
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to recover:
Setting up neo4j (2.2.1) ...
update-rc.d: error: initscript does not exist: /etc/init.d/neo4j-service
dpkg: error processing package neo4j (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
neo4j
root#cb-8:~# service neo4j-service status
● neo4j-service.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
/etc/init.d/neo4j-service does in fact exist.
lrwxrwxrwx 1 root root 36 Mar 5 17:28 /etc/init.d/neo4j-service -> /opt/neo4j-community-2.1.7/bin/neo4j
I'm out of ideas and hoping someone might be able to point me in the right direction.
~ Ross
I had the same exact error. However, if installing newer version (3.3.0 in my case) of neo4j the syntax is different. It should be:
service neo4j start
not
service neo4j-service start
To double check you can do:
ls /etc/init.d | grep neo4j
In my case it finds neo4j
Problem solved.
2.2.1 was still linking to 2.1.7 somehow.
removed the spurious link and it all worked.
Just setting up rails and RVM on a new laptop and i'm getting this error when running
Error running 'requirements_osx_port_update_system ruby-2.0.0-p247',
please read /Users/#####/.rvm/log/1380821805_ruby-2.0.0-p247/update_system.log
Requirements installation failed with status: 1.
When running this
sudo rvm install ruby
Which produces this code.
[2013-10-03 13:36:45] requirements_osx_port_update_system
requirements_osx_port_update_system ()
{
__rvm_try_sudo port -dv selfupdate || return $?
}
current path: /Users/matthewpetitt
command(2): requirements_osx_port_update_system ruby-2.0.0-p247
DEBUG: Copying /Users/matthewpetitt/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
DEBUG: MacPorts sources location: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
---> Updating MacPorts base sources using rsync
rsync: failed to connect to rsync.macports.org: Operation timed out (60)
rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync- 42/rsync/clientserver.c(105) [receiver=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
Exit code: 10
DEBUG: Error synchronizing MacPorts sources: command execution failed
while executing
"macports::selfupdate [array get global_options] base_updated"
Error: Error synchronizing MacPorts sources: command execution failed
To report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.tickets
Error: /Users/matthewpetitt/.rvm/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed
I already have Xcode and Xcode command line tools installed. Anyone fixed something like this before.
Realized that it was just some network configuration at work that must have been blocking the ports. Check your network permissions or try a different network.
You need to make sure this command can be run first:
sudo port -dv selfupdate
This can be temporary network problem - if it is not follow the displayed instructions.