By tusharSquid
Failed actions:
tomcat7_start_0 (node=MASTER, call=56, rc=1, status=complete, last-rc-change=Mon Apr 6 16:34:42 2020
, queued=5039ms, exec=0ms
I tried crm resource stop tomcat7 and then crm resource cleanup tomcat7 and then crm resource start tomcat7 but does not help in majority of the cases this solution works.
tail -f /var/log/corosync/corosync.log
Apr 06 16:40:18 [52111] OSCAR-MASTER lrmd: info: log_finished: finished - rsc:tomcat7 action:stop call_id:72 pid:55049 exit-code:0 exec-time:21ms queue-time:0ms
Apr 06 16:40:18 [52114] OSCAR-MASTER crmd: notice: process_lrm_event: LRM operation tomcat7_stop_0 (call=72, rc=0, cib-update=67, confirmed=true) ok
Apr 06 16:40:18 [52109] OSCAR-MASTER cib: info: cib_process_request: Completed cib_modify operation for section status: OK (rc=0, origin=local/crmd/67, version=0.1355.7)
Apr 06 16:40:18 [52114] OSCAR-MASTER crmd: info: match_graph_event: Action tomcat7_stop_0 (1) confirmed on OSCAR-MASTER (rc=0)
Apr 06 16:40:18 [52114] OSCAR-MASTER crmd: notice: run_graph: Transition 14 (Complete=4, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-1385.bz2): Complete
Apr 06 16:40:18 [52114] OSCAR-MASTER crmd: info: do_log: FSA: Input I_TE_SUCCESS from notify_crmd() received in state S_TRANSITION_ENGINE
Apr 06 16:40:18 [52114] OSCAR-MASTER crmd: notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ]
Apr 06 16:41:09 [52109] OSCAR-MASTER cib: info: crm_client_new: Connecting 0x556f9b05b260 for uid=0 gid=0 pid=55094 id=6d1ffd67-7745-41ba-b3c0-e4b836fb58db
Apr 06 16:41:09 [52109] OSCAR-MASTER cib: info: cib_process_request: Completed cib_query operation for section 'all': OK (rc=0, origin=local/crm_mon/2, version=0.1355.7)
Apr 06 16:41:09 [52109] OSCAR-MASTER cib: info: crm_client_destroy: Destroying 0 events
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Heya,
Just came across this answer and decided to write some general guidelines for anyone who comes across this in the future despite the old question.
It seems like you’re facing issues with Tomcat7 and Corosync on your server. Based on the logs you provided, the stop command for Tomcat7 was successful (exit-code: 0) and the cluster is in an idle state. However, you seem to be running into issues with starting Tomcat7 again.
To troubleshoot this issue, I recommend checking the Tomcat logs to see if there are any errors or issues preventing it from starting. The logs are usually located in the /var/log/tomcat7 directory (or a similar path based on the installation). You can check the catalina.out file or other log files in the folder for any error messages.
If you need more information on managing your DigitalOcean server, you can refer to the DigitalOcean documentation.
Hope that this helps!
Heya,
Apart from what has been said, here are a couple more ways to troubleshoot this:
-
Check dependencies: Make sure that all dependencies required by tomcat7 or by the resources depending on it are correctly configured and working. This could be a database, filesystem, or another service that needs to be running for tomcat7 to work.
-
Check the Tomcat logs: The problem may be inside the application that runs on Tomcat, and not related to the Pacemaker configuration. Look at the Tomcat logs, usually located in
/var/log/tomcat7or inside the Tomcat installation folder. -
Verify resource configuration: Check the configuration of the resources that depend on tomcat7. There could be something wrong in their configuration that causes them to fail when tomcat7 is restarted. You can check resource configuration with
crm configure show. -
Resource Monitoring: Make sure you have enabled resource monitoring for tomcat7 and the resources depending on it. Pacemaker can then restart them if they fail. You can enable monitoring in the resource configuration with the
op monitorcommand. -
Pacemaker configuration: The problem may also be due to misconfiguration of Pacemaker. Make sure you have correctly configured colocation and order constraints for the resources that depend on tomcat7.
-
Try to isolate the problem: If possible, try to start the resources that depend on tomcat7 manually (without Pacemaker) after stopping them in Pacemaker. This could help determine whether the problem is with Pacemaker or with the resources themselves.
Remember to always carefully review the logs for any error or warning messages, as they often provide key information for troubleshooting.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.