I am trying to figure out what daemons are running on the Opennms (version 1.12.8) for the purpose of debugging. Is there any good way to do it?
Figured out the way to check it. Just goto the /opennms/bin directory and run
sudo ./opennms -v status
Related
I am trying to integrate flocker with docker, for that I found plugin flocker-docker-plugin. I installed it by using the commands on my flocker agents.-
$ yum install -y clusterhq-flocker-docker-plugin
$ systemctl enable flocker-docker-plugin
$ systemctl restart flocker-docker-plugin
It shows flocker-docker-plugin is running. However after few seconds when I checked status by using $ systemctl status flocker-docker-plugin, I got error saying
flocker-docker-plugin.service: main process exited, code=killed, status=11/SEGV
Based on the information you have given there could be multiple reasons for this error:
Check if you can reach the flocker control service and more so if your node-agents can reach the control-service.
Check if the flocker-dataset-agent and the flocker-container-agent are running on your nodes.
Check if you have provided certificates for the flocker-docker-plugin as mentioned on their site (https://docs.clusterhq.com/en/latest/docker-integration/generate-api-plugin.html).
While installing flocker i also got the same error as we have just installed the docker plugin and by default it does't start's up.
First use the command systemctl start flocker-docker-plugin and then check the running status of flocker using systemctl status flocker-docker-plugin
Make sure the control service and dataset agent are running correctly first, you can find logs by looking in /var/log/flocker/, journalctl -u flocker-dataset-agent or running flocker-diagnostics.
Read through any error in these logs such as communication with control service issues, certificates issues, agent.yml config issues etc, or feel free to post them for more help.
You can also find flocker-docker-plugin logs the same way to see specific errors that may be occurring.
Here is more information about how to debug flocker.
The rundeck instance is up and running but when I execute the following command it shows:
$/etc/init.d/rundeckd status
Status rundeckd: rundeckd is running (pid=37296, port=4440) dead
Kindly help me out here on how to get this glitch fixed/?
Thanks !
You can run /etc/init.d/rundeckd stop and it should clear out the old pid file.
You can check for java version (exact with subversion) in /app/rundeck/etc/Profile and java installed on the particular server where rundeck is installed. Both should be identical, if not update the java version from the server to the file/app/rundeck/etc/Profile. Then restart rundeck, this should fix the issue .
I am trying to install CDR-STATS on Exiting CentOS 6.4 server where FreeSWITCH is already running well, i read all available documentation and mailing list but i didn;t find any notes where can i install step by step.
Please any one know help me to get ride on it.
I appreciate your support.
Thanks in Advance.
CDR-Stats comes with a script install-all-cdr-stats-freeswitch.sh which will install FreeSWITCH with CDR-Stats. In the scenario where you have already FreeSWITCH installed, you can execute the install-cdr-stats.sh, it will prompt you with a question to know if you want to run an installation for FreeSWITCH or Asterisk.
cd /usr/src/ ; wget --no-check-certificate https://raw.github.com/Star2Billing/cdr-stats/master/install/install-cdr-stats.sh -O install-cdr-stats.sh ; bash install-cdr-stats.sh
I will also advice you to read carefully the install-freeswitch script, cause it does few things apart installing FreeSWITCH for instance configuring it to be used with mongodb_cdr.
https://github.com/Star2Billing/cdr-stats/blob/master/install/install-freeswitch.sh#L166
I'm not sure if this is more of a sysadmin question but in order to use x-debug, I have to run the following from my terminal everytime I boot up the machine.
setsebool httpd_can_network_connect=1
Does anyone know how I can make this permanent so that I don't have to run this command everytime I start my machine?
Thank you.
----EDIT----
setsebool -P httpd_can_network_connect=1
Now I can debug as soon as the machine boots thanks to Ulrich Schmidt-Goertz
Try running the command with the -P flag. That should make the setting permanent.
Sometimes my Eclipse hangs and I need to kill it violently. However, I have been unable to do it properly. It seems that kill -9 does not actually shut it down in a proper way since I can still see the hanged window. What command sequence would kill my Eclipse properly so I could restart it?
I am running Ubuntu 12.10 and Eclipse 4.2(Juno).
You can also use jps -l to get all of the process id's of java processes
You need to kill the javaw process on which Eclipse runs (usually it is the one with about 1GB memory usage :) )
Based on the answer of Uku and Michael you can do the following:
On your terminal first run:
jps -l
Check the pid of the process that is running Eclipse and copy the pid.
Then kill the process id by running:
// use the actual process id
kill -p {the_copied_pid}