date:20170125

Re: [ClusterLabs] [Question] About log collection of crm_report.

2017-01-25 Thread Ken Gaillot

On 01/24/2017 04:41 PM, renayama19661...@ybb.ne.jp wrote:
> Hi Ken,
> 
> Thank you for comment.
> 
> For example, our user does not use pacemaker.log and corosync.log.
> 
> Via a syslog, the user makes setting to output all log to /var/log/ha-log.
> 
> -
> (/etc/corosycn/corosync.conf)
> logging {
> syslog_facility: local1
> debug: off
> }
> 
> (/etc/sysconfig/pacemaker)
> PCMK_logfile=none
> PCMK_logfacility=local1
> PCMK_logpriority=info
> PCMK_fail_fast=yes
> 
> (/etc/rsyslog.conf)
> # Log anything (except mail) of level info or higher.
> # Don't log private authentication messages!
> *.info;mail.none;authpriv.none;cron.none;local1.none
> /var/log/messages
> (snip)
> # Save boot messages also to boot.log
> local7.*/var/log/boot.log
> local1.info /var/log/ha-log
> -
> 
> In present crm_report, in the case of the user who output log in a different 
> file, the log is not collected in sosreport.
> 
> Is this not a problem?
> Possibly is all /var/log going to collect it in future in sosreport?
> 
> Of course I know that "/var/log/ha-log" is collected definitely when I carry 
> out crm_report alone.
> I want to know why collection of log of this crm_report was stopped in 
> sosreport.
> 
> For REDHAT, will it be to be enough for collection of sosreport contents?
> If it is such a thing, we can understand.
> 
> - And I test crm_report at the present, but seem to have some problems.
> - I intend to report the problem by Bugzilla again.
> 
> Best Regards,
> Hideo Yamauchi.

Hi Hideo,

You are right, that is a problem. I've opened a Red Hat bug for sosreport:

https://bugzilla.redhat.com/show_bug.cgi?id=1416535

> - Original Message -
>> From: Ken Gaillot 
>> To: users@clusterlabs.org
>> Cc: 
>> Date: 2017/1/24, Tue 08:15
>> Subject: Re: [ClusterLabs] [Question] About log collection of crm_report.
>>
>> On 01/23/2017 04:17 PM, renayama19661...@ybb.ne.jp wrote:
>>>  Hi All,
>>>
>>>  When I carry out Pacemaker1.1.15 and Pacemaker1.1.16 in RHEL7.3, log in 
>> conjunction with pacemaker is not collected in the file which I collected in 
>> sosreport.
>>>   
>>>
>>>  This seems to be caused by the next correction and pacemaker.py script of 
>> RHEL7.3.
>>>
>>>   - 
>> https://github.com/ClusterLabs/pacemaker/commit/1bcad6a1eced1a3b6c314b05ac1d353adda260f6
>>>   - 
>> https://github.com/ClusterLabs/pacemaker/commit/582e886dd8475f701746999c0093cd9735aca1ed#diff-284d516fab648676f5d93bc5ce8b0fbf
>>>
>>>
>>>  ---
>>>  (/usr/lib/python2.7/site-packages/sos/plugins/pacemaker.py)
>>>  (snip)
>>>  if not self.get_option("crm_scrub"):
>>>  crm_scrub = ""
>>>  self._log_warn("scrubbing of crm passwords has been 
>> disabled:")
>>>  self._log_warn("data collected by crm_report may 
>> contain"
>>> " sensitive values.")
>>>  self.add_cmd_output('crm_report --sos-mode %s -S -d '
>>>  ' --dest %s --from "%s"' %
>>>  (crm_scrub, crm_dest, crm_from),
>>>  chroot=self.tmp_in_sysroot())
>>>  (snip)
>>>  ---
>>>
>>>
>>>  When a user carries out crm_report in sosreport, what is the reason that 
>> set search_logs to 0?
>>>
>>>  We think that the one where search_logs works with 1 in sosreport is right.
>>>
>>>
>>>  Best Regards,
>>>  Hideo Yamauchi.
>>
>> Hi Hideo,
>>
>> The --sos-mode option is intended for RHEL integration, so it is only
>> guaranteed to work with the combination of pacemaker and sosreport
>> packages delivered with a particular version of RHEL (and its derivatives).
>>
>> That allows us to make assumptions about what sosreport features are
>> available. It might be better to detect those features, but we haven't
>> seen enough usage of sosreport + pacemaker outside RHEL to make that
>> worth the effort.
>>
>> In this case, the version of sosreport that will be in RHEL 7.4 will
>> collect pacemaker.log and corosync.log on its own, so the crm_report in
>> pacemaker 1.1.16 doesn't need to collect the logs itself.
>>
>> It might work if you build the latest sosreport:
>> https://github.com/sosreport/sos
>>

___
Users mailing list: Users@clusterlabs.org
http://lists.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] How to Fence Virtualbox VM with Windows 10 as host.

2017-01-25 Thread durwin

I found the place where UUID is specified (Virtual Media Manager).

Thank you.

Durwin

> From: Marek Grac 
> To: Cluster Labs - All topics related to open-source clustering 
> welcomed 
> Date: 01/25/2017 01:34 AM
> Subject: Re: [ClusterLabs] How to Fence Virtualbox VM with Windows 10 as 
host.
> 
> Hi,
> 
> On Tue, Jan 24, 2017 at 9:06 PM,  wrote:
> This is my first attempt at clustering, just so you know the level 
> required to convey ideas. 
> 
> I have Windows 10 running Virtualbox with 2 VMs running Fedora 25.  
> I have followed 'Pacemaker 1.1 Clusters from Scratch' 9th edition up
> through chapter 7.  It works.  I am uncertain as how to fence the 
> VMs with Windows 10 as host.  The output from 'pcs stonith describe 
> fence_vbox' is below. 
> 
> I have Cygwin installed with sshd configured and running.  I can 
> remotely ssh into the Windows 10 machine.  I can add the keys from 
> the machines into Windows authorized_keys so no user/password is 
> required.  I however do not know which of the options are 
> *required*.  Nor do I know what the options should be set to.  Some 
> of the options *are* obvious.  If I use *only* required ones, ipaddr
> is obvious, login is obvious, but not sure what port is.  Would it 
> be the name of the VM as Virtualbox knows it? 
> 
> ipaddr (required): IP address or hostname of fencing device 
> login (required): Login name 
> port (required): Physical plug number on device, UUID or 
> identification of machine 
> 
> Does the host require anything running on it to support the fence?  
> Do I require any other options in addition to 'required'?  How do I 
> test it from a nodes commandline? 
> 
> You can take  a look at manual page of fence_vbox (or run 
fence_vbox--help). 
> 
> In your case it should be enough to set:
> * ipaddr
> * login
> * port (= node to shutdown)
> * identity_file (= private key)
> 
> m,___
> Users mailing list: Users@clusterlabs.org
> http://lists.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



This email message and any attachments are for the sole use of the 
intended recipient(s) and may contain proprietary and/or confidential 
information which may be privileged or otherwise protected from 
disclosure. Any unauthorized review, use, disclosure or distribution is 
prohibited. If you are not the intended recipient(s), please contact the 
sender by reply email and destroy the original message and any copies of 
the message as well as any attachments to the original message.___
Users mailing list: Users@clusterlabs.org
http://lists.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] How to Fence Virtualbox VM with Windows 10 as host.

2017-01-25 Thread durwin

Marek Grac  wrote on 01/25/2017 01:33:07 AM:

> From: Marek Grac 
> To: Cluster Labs - All topics related to open-source clustering 
> welcomed 
> Date: 01/25/2017 01:34 AM
> Subject: Re: [ClusterLabs] How to Fence Virtualbox VM with Windows 10 as 
host.
> 
> Hi,
> 
> On Tue, Jan 24, 2017 at 9:06 PM,  wrote:
> This is my first attempt at clustering, just so you know the level 
> required to convey ideas. 
> 
> I have Windows 10 running Virtualbox with 2 VMs running Fedora 25.  
> I have followed 'Pacemaker 1.1 Clusters from Scratch' 9th edition up
> through chapter 7.  It works.  I am uncertain as how to fence the 
> VMs with Windows 10 as host.  The output from 'pcs stonith describe 
> fence_vbox' is below. 
> 
> I have Cygwin installed with sshd configured and running.  I can 
> remotely ssh into the Windows 10 machine.  I can add the keys from 
> the machines into Windows authorized_keys so no user/password is 
> required.  I however do not know which of the options are 
> *required*.  Nor do I know what the options should be set to.  Some 
> of the options *are* obvious.  If I use *only* required ones, ipaddr
> is obvious, login is obvious, but not sure what port is.  Would it 
> be the name of the VM as Virtualbox knows it? 
> 
> ipaddr (required): IP address or hostname of fencing device 
> login (required): Login name 
> port (required): Physical plug number on device, UUID or 
> identification of machine 
> 
> Does the host require anything running on it to support the fence?  
> Do I require any other options in addition to 'required'?  How do I 
> test it from a nodes commandline? 
> 
> You can take  a look at manual page of fence_vbox (or run 
fence_vbox--help). 
> 
> In your case it should be enough to set:
> * ipaddr
> * login
> * port (= node to shutdown)

Thank you.  man page says.

   -n, --plug=[id]
  Physical plug number on device, UUID or identification of 
machine This parameter is always required.

How do I determine the 'plug' of the VM?  I the output of 'pcs stonith 
describe fence_vbox' refers to this as port (to my understanding, very 
misleading).

>From your reply, am I correct in assuming nothing to support Fencing is 
required to run on the Windows host?

Thank you,

Durwin

> * identity_file (= private key)
> 
> m,___
> Users mailing list: Users@clusterlabs.org
> http://lists.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



This email message and any attachments are for the sole use of the 
intended recipient(s) and may contain proprietary and/or confidential 
information which may be privileged or otherwise protected from 
disclosure. Any unauthorized review, use, disclosure or distribution is 
prohibited. If you are not the intended recipient(s), please contact the 
sender by reply email and destroy the original message and any copies of 
the message as well as any attachments to the original message.___
Users mailing list: Users@clusterlabs.org
http://lists.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] [Question] About log collection of crm_report.

2017-01-25 Thread renayama19661014

Hi Ken,

Thank you for comment.

For example, our user does not use pacemaker.log and corosync.log.

Via a syslog, the user makes setting to output all log to /var/log/ha-log.

-
(/etc/corosycn/corosync.conf)
logging {
        syslog_facility: local1
        debug: off
}

(/etc/sysconfig/pacemaker)
PCMK_logfile=none
PCMK_logfacility=local1
PCMK_logpriority=info
PCMK_fail_fast=yes

(/etc/rsyslog.conf)
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none;local1.none                
/var/log/messages
(snip)
# Save boot messages also to boot.log
local7.*                                                /var/log/boot.log
local1.info /var/log/ha-log
-

In present crm_report, in the case of the user who output log in a different 
file, the log is not collected in sosreport.

Is this not a problem?
Possibly is all /var/log going to collect it in future in sosreport?

Of course I know that "/var/log/ha-log" is collected definitely when I carry 
out crm_report alone.
I want to know why collection of log of this crm_report was stopped in 
sosreport.

For REDHAT, will it be to be enough for collection of sosreport contents?
If it is such a thing, we can understand.

- And I test crm_report at the present, but seem to have some problems.
- I intend to report the problem by Bugzilla again.

Best Regards,
Hideo Yamauchi.



- Original Message -
> From: Ken Gaillot 
> To: users@clusterlabs.org
> Cc: 
> Date: 2017/1/24, Tue 08:15
> Subject: Re: [ClusterLabs] [Question] About log collection of crm_report.
> 
> On 01/23/2017 04:17 PM, renayama19661...@ybb.ne.jp wrote:
>>  Hi All,
>> 
>>  When I carry out Pacemaker1.1.15 and Pacemaker1.1.16 in RHEL7.3, log in 
> conjunction with pacemaker is not collected in the file which I collected in 
> sosreport.
>>   
>> 
>>  This seems to be caused by the next correction and pacemaker.py script of 
> RHEL7.3.
>> 
>>   - 
> https://github.com/ClusterLabs/pacemaker/commit/1bcad6a1eced1a3b6c314b05ac1d353adda260f6
>>   - 
> https://github.com/ClusterLabs/pacemaker/commit/582e886dd8475f701746999c0093cd9735aca1ed#diff-284d516fab648676f5d93bc5ce8b0fbf
>> 
>> 
>>  ---
>>  (/usr/lib/python2.7/site-packages/sos/plugins/pacemaker.py)
>>  (snip)
>>          if not self.get_option("crm_scrub"):
>>              crm_scrub = ""
>>              self._log_warn("scrubbing of crm passwords has been 
> disabled:")
>>              self._log_warn("data collected by crm_report may 
> contain"
>>                             " sensitive values.")
>>          self.add_cmd_output('crm_report --sos-mode %s -S -d '
>>                              ' --dest %s --from "%s"' %
>>                              (crm_scrub, crm_dest, crm_from),
>>                              chroot=self.tmp_in_sysroot())
>>  (snip)
>>  ---
>> 
>> 
>>  When a user carries out crm_report in sosreport, what is the reason that 
> set search_logs to 0?
>> 
>>  We think that the one where search_logs works with 1 in sosreport is right.
>> 
>> 
>>  Best Regards,
>>  Hideo Yamauchi.
> 
> Hi Hideo,
> 
> The --sos-mode option is intended for RHEL integration, so it is only
> guaranteed to work with the combination of pacemaker and sosreport
> packages delivered with a particular version of RHEL (and its derivatives).
> 
> That allows us to make assumptions about what sosreport features are
> available. It might be better to detect those features, but we haven't
> seen enough usage of sosreport + pacemaker outside RHEL to make that
> worth the effort.
> 
> In this case, the version of sosreport that will be in RHEL 7.4 will
> collect pacemaker.log and corosync.log on its own, so the crm_report in
> pacemaker 1.1.16 doesn't need to collect the logs itself.
> 
> It might work if you build the latest sosreport:
> https://github.com/sosreport/sos
> 
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.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://lists.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] How to Fence Virtualbox VM with Windows 10 as host.

2017-01-25 Thread Marek Grac

Hi,

On Tue, Jan 24, 2017 at 9:06 PM,  wrote:

> This is my first attempt at clustering, just so you know the level
> required to convey ideas.
>
> I have Windows 10 running Virtualbox with 2 VMs running Fedora 25.  I have
> followed 'Pacemaker 1.1 Clusters from Scratch' 9th edition up through
> chapter 7.  It works.  I am uncertain as how to fence the VMs with Windows
> 10 as host.  The output from 'pcs stonith describe fence_vbox' is below.
>
> I have Cygwin installed with sshd configured and running.  I can remotely
> ssh into the Windows 10 machine.  I can add the keys from the machines into
> Windows authorized_keys so no user/password is required.  I however do not
> know which of the options are *required*.  Nor do I know what the options
> should be set to.  Some of the options *are* obvious.  If I use *only*
> required ones, ipaddr is obvious, login is obvious, but not sure what port
> is.  Would it be the name of the VM as Virtualbox knows it?
>
> ipaddr (required): IP address or hostname of fencing device
> login (required): Login name
> port (required): Physical plug number on device, UUID or
> identification of machine
>
> Does the host require anything running on it to support the fence?  Do I
> require any other options in addition to 'required'?  How do I test it from
> a nodes commandline?
>

You can take  a look at manual page of fence_vbox (or run fence_vbox
--help).

In your case it should be enough to set:
* ipaddr
* login
* port (= node to shutdown)
* identity_file (= private key)

m,
___
Users mailing list: Users@clusterlabs.org
http://lists.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] [Question] About log collection of crm_report.

Re: [ClusterLabs] How to Fence Virtualbox VM with Windows 10 as host.

Re: [ClusterLabs] How to Fence Virtualbox VM with Windows 10 as host.

Re: [ClusterLabs] [Question] About log collection of crm_report.

Re: [ClusterLabs] How to Fence Virtualbox VM with Windows 10 as host.

5 matches

Site Navigation

Mail list logo

Footer information