Re: [ClusterLabs] restarting resources
On 11/02/2015 05:59 PM, - - wrote: Hi, I need to be able to restart a resource (e.g apache) whenever a configuration file is updated. I have been using the 'crm resource restart ' command to to it, which does restart the resource BUT also restarts my other resources also. Is this normal behaviour? Is there a way to just/force restart only the resource whose config file is changed. I have the following resources configured in a group (ew) Hi, i had the same problem with Apache and a virtual IP together in a group. I wasn't able to restart / reload just Apache. The only way was to bring down the whole group including IP, and then start the group again. Is there a way to just start Website8086 or just reload it, without affecting the other resources. I removed the group configuration and instead just inserted a colocation rule to make sure that Apache and IP are running on the same node. This works fine for me, now it's possible to crm resource restart res_apache without affecting the IP, and it works fast and smoothly. best regards.. ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] restarting resources
On 11/02/2015 12:59 PM, - - wrote: > Is there a way to just start Website8086 or just reload it, without > affecting the other resources. Hi, Try: crm resource restart Website8086 or crm resource stop Website8086 crm resource start Website8086 It works for me (without stopping all other resources in the same group). -- Jorge ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] restarting resources
On Mon, Nov 2, 2015 at 7:59 PM, - - wrote: > Hi, >I need to be able to restart a resource (e.g apache) whenever a > configuration > file is updated. I have been using the 'crm resource restart ' command to to > it, > which does restart the resource BUT also restarts my other resources also. > Is this normal behaviour? Yes. If resource is restarted, all dependent resources are also restarted. > Is there a way to just/force restart only the > resource whose config file is changed. > Set resource to unmanaged, reload its configuration outside of pacemaker, manage resource again. ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] restarting resources
Hi, I need to be able to restart a resource (e.g apache) whenever a configuration file is updated. I have been using the 'crm resource restart ' command to to it, which does restart the resource BUT also restarts my other resources also. Is this normal behaviour? Is there a way to just/force restart only the resource whose config file is changed. I have the following resources configured in a group (ew) Resource Group: ew fs_drbd(ocf::heartbeat:Filesystem):Started ew-2 VirtualIP (ocf::heartbeat:IPaddr2): Started ew-2 mysqld-1 (ocf::heartbeat:mysql): Started ew-2 mysqld-2 (ocf::heartbeat:mysql): Started ew-2 Website8084(ocf::heartbeat:apache):Started ew-2 Website8083(ocf::heartbeat:apache):Started ew-2 Website8085(ocf::heartbeat:apache):Started ew-2 Website8086(ocf::heartbeat:apache):Started ew-2 tomcat8-9092 (ocf::heartbeat:tomcat):Started ew-2 tomcat7-9091 (ocf::heartbeat:tomcat):Started ew-2 tomcat5-9090 (ocf::heartbeat:tomcat):Started ew-2 pgsqld-1 (ocf::heartbeat:pgsql): Started ew-2 Website8080(ocf::heartbeat:apache):Started ew-2 mail (ocf::heartbeat:MailTo):Started ew-2 p_sym_cron_rsync (ocf::heartbeat:symlink): Started ew-2 Now, if I restart say 'Website8086', all the other resources defined after Website8086 in the listing above (tomcat8-9092 ... to p_sym_cron_rsync) gets restarted as well. This can take a while to complete. Is there a way to just start Website8086 or just reload it, without affecting the other resources. Thanks krishan ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] restarting resources after configuration changes
Hi, On Wed, Oct 28, 2015 at 10:21:26AM +, - - wrote: > Hi, > I am having problems restarting resources (e.g apache) after a > configuration file change. I have tried 'pcs resource restart resourceid', > which says 'resource successfully restarted', but the httpd process > does not restart and hence my configuration changes in httpd.conf > does not take effect. > I am sure this scenario is quite common as administrators needs to > update httpd.config files often - how is it done in an HA cluster? Exactly as you tried. Something apparently went wrong, but hard to say what. Thanks, Dejan > I can send a HUP signal to the httpd process to achieve this, but I hope > there will be a cluster (pcs/crm) method to do this. > Many Thanks > > krishan > ___ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] restarting resources after configuration changes
Centos/redhat: try `service httpd configtest` to validate the config changes first …. Regards, Andrew Gray. RHCSA, Professional Unix Administration. Ph: (07) 3664 5112 From: - - [mailto:kri...@googlemail.com] Sent: Wednesday, 28 October 2015 8:21 PM To: users@clusterlabs.org Subject: [ClusterLabs] restarting resources after configuration changes Hi, I am having problems restarting resources (e.g apache) after a configuration file change. I have tried 'pcs resource restart resourceid', which says 'resource successfully restarted', but the httpd process does not restart and hence my configuration changes in httpd.conf does not take effect. I am sure this scenario is quite common as administrators needs to update httpd.config files often - how is it done in an HA cluster? I can send a HUP signal to the httpd process to achieve this, but I hope there will be a cluster (pcs/crm) method to do this. Many Thanks krishan To report this email as spam, please forward to a...@websense.com<mailto:a...@websense.com> * This email message (including any file attachments transmitted with it) is for the sole use of the intended recipient(s) and may contain confidential and legally privileged information. Any unauthorised review, use, alteration, disclosure or distribution of this email (including any attachments) by an unintended recipient is prohibited. If you have received this email in error, please notify the sender by return email and destroy all copies of the original message. Any confidential or legal professional privilege is not waived or lost by any mistaken delivery of the email. SPARQ Solutions accepts no responsibility for the content of any email which is sent by an employee which is of a personal nature. Sender Details: SPARQ Solutions PO Box 15760 City East, Brisbane QLD Australia 4002 +61 7 4931 SPARQ Solutions policy is to not send unsolicited electronic messages. Suspected breaches of this policy can be reported by replying to this message including the original message and the word "UNSUBSCRIBE" in the subject. * ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] restarting resources after configuration changes
Hi, I am having problems restarting resources (e.g apache) after a configuration file change. I have tried 'pcs resource restart resourceid', which says 'resource successfully restarted', but the httpd process does not restart and hence my configuration changes in httpd.conf does not take effect. I am sure this scenario is quite common as administrators needs to update httpd.config files often - how is it done in an HA cluster? I can send a HUP signal to the httpd process to achieve this, but I hope there will be a cluster (pcs/crm) method to do this. Many Thanks krishan ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
