Re: [Linux-ha-dev] crm_resource in 2.1.1 prints info messages
On 7/19/07, Serge Dubrouski <[EMAIL PROTECTED]> wrote: It's good to have them in the logs and I have no objections there, but why on the screen? Because in order to see the regular messages we have already enabled logging to stderr. So anything that goes to the logs also goes to stderr - which i agree is annoying. If i get a chance, I'll try and do something about it today And may be it's a good idea to make that configurable through ha.cf. Currently there is no way (as far as I know) to disable info messages form going to the logs. And because of that log files can become really big (for example httpd ocf RA generates an info message for each monitoring event). There is a debug level parameter in ha.cf but it doesn't help to eliminate those info messages. I haven't tried logfacility feature yet, may be that will help. the best way is to send everything to syslog-ng and filter it there. ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] crm_resource in 2.1.1 prints info messages
On 7/20/07, Keisuke MORI <[EMAIL PROTECTED]> wrote: Lars Marowsky-Bree <[EMAIL PROTECTED]> writes: > On 2007-07-19T13:42:53, Serge Dubrouski <[EMAIL PROTECTED]> wrote: > >> In the latest 2.1.1 crm_resource prints info messages with every invocation: >> >> crm_resource -W -r PTEGroup >> crm_resource[9813]: 2007/07/19_13:39:05 info: Invoked: crm_resource -W >> -r PTEGroup >> resource PTEGroup is running on: goodman >> >> crm_resource -U -r PTEGroup >> crm_resource[10223]: 2007/07/19_13:41:48 info: Invoked: crm_resource >> -U -r PTEGroup >> >> And so on. Not a big deal, just annoying. It wasn't like this in >> previous releases. > > That is quite intentional. It shouldn't necessarily print it, but you > wouldn't believe how helpful it is to be able to see the actual user > commands executed in the logs ;-) > > "Honest I didn't do anything!" > > If you have specific suggestions about commands which needn't be logged, > lets discuss that. I also feel annoyance with that log. We are using attrd_updater command in the monitor operation of a RA to control resources by our own attribute values and rules. In that case the messages is logged every 10 seconds for example :-( We might also use crm_resource to run periodically for monitoring from another system administration tool. How about changing the log level for this message down to debug level? At this time, no. As lars said, its important information to us and presumably the reason you want it at debug is so that its not printed - which pretty much defeats the point. ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] HA_SBIN_DIR is not set on ocf scripts
On 2007-07-19T20:40:12, Alan Robertson <[EMAIL PROTECTED]> wrote: > I'm in "let's try and do this right mode". You act like that's a bad thing. I don't. Sigh. I take no issue with your release procedures about discussing patches before merging them. I'm just pointing out that all Andrew suggested (on this list, as per the procedures) basically amounts to the fact that the patches he pushes to dev are considered to be good for the release by him - so then it's your call whether you want to merge them or not. > So, which "Lars" should I listen to? > The Lars that said the procedures are fine, and agreed to them? > or the Lars that now says I should pay no attention to our agreements? I tire of this. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] Downloading Heartbeat STABLE 2.1 from CVS gives me 2.0.9 - wrong tag ?
On 7/20/07, Alan Robertson <[EMAIL PROTECTED]> wrote: Andrew Beekhof wrote: > On 7/18/07, Maxim Veksler <[EMAIL PROTECTED]> wrote: >> Hello people, >> >> I'm looking for building Heartbeat 2.1.0 on redhat. >> I've downloaded from http://hg.linux-ha.org/lha-2.1/archive/tip.tar.gz >> >> The content of this archive: >> >> > tar xzpf tip.tar.gz >> > ls >> > Heartbeat-STABLE-2-1-0ad5421d5664 tip.tar.gz >> > cd Heartbeat-STABLE-2-1-0ad5421d5664/ >> > grep -E 'HAPKGVERSION="[0-9.]+"' configure.in >>HAPKGVERSION="2.0.9" >> >> What gives ? > > At the time it was clearly not 2.0.8 anymore but that revision didn't > become 2.1.0 until afterwards (for various reasons). Hence the > numbering confusion, which isn't helped by Alan subsequently > disavowing it and wanting to start with 2.1.1 I never disavowed 2.1.0. Yes. You did. In this thread. "There is no 2.1.0" ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] crm_resource in 2.1.1 prints info messages
On 7/20/07, Andrew Beekhof <[EMAIL PROTECTED]> wrote: On 7/19/07, Serge Dubrouski <[EMAIL PROTECTED]> wrote: > It's good to have them in the logs and I have no objections there, but > why on the screen? If i get a chance, I'll try and do something about it today Done: http://hg.beekhof.net/lha/crm-dev/rev/0fe6b70ed457 ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] Using of LOCAL7 log facility
the crm does inherit the log settings from ha.cf, however for a number of reasons we default to LOCAL7 if no other value is set. to disable syslog logging completely, put this in ha.cf: logfacility none On 7/20/07, Serge Dubrouski <[EMAIL PROTECTED]> wrote: Just found that Heartbeat code explicitly uses LOCAL7 logfacility for system logging: cl_log_set_entity(entity); cl_log_set_facility(LOG_LOCAL7); and so on. On standard Linux distribution ( RedHat at least) LOCAL7 is dedicated for boot processes and is directed to go to boot.log. What was the reason in ignoring the logfacility value from ha.cf and explicitly using LOCAL7? -- Serge Dubrouski. ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/ ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
[Linux-ha-dev] Bug 1655 crmd stucks in S_TERMINATE when pengine was killed
Hi, I filed a bug on the subject and cc-ing to the ML and Alan just in case if this might affect to the upcoming release. http://old.linux-foundation.org/developer_bugzilla/show_bug.cgi?id=1655 As I wroted on the bugzilla, we found this during our regression test. We suffered this problem on 2.0.8 first and then it seemed to be solved with the dev version, so we really have been longing and waiting for the fix is in the official release. Is there any chance to fix this bug very soon? Regards, Keisuke MORI NTT DATA Intellilink Corporation ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] Bug 1655 crmd stucks in S_TERMINATE when pengine was killed
On 7/20/07, Keisuke MORI <[EMAIL PROTECTED]> wrote: Hi, I filed a bug on the subject and cc-ing to the ML and Alan just in case if this might affect to the upcoming release. http://old.linux-foundation.org/developer_bugzilla/show_bug.cgi?id=1655 As I wroted on the bugzilla, we found this during our regression test. We suffered this problem on 2.0.8 first and then it seemed to be solved with the dev version, so we really have been longing and waiting for the fix is in the official release. Is there any chance to fix this bug very soon? Unlikely to be fixed before I return from vacation in a week ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
Re: [Linux-ha-dev] Using of LOCAL7 log facility
On 7/20/07, Andrew Beekhof <[EMAIL PROTECTED]> wrote: the crm does inherit the log settings from ha.cf, however for a number of reasons we default to LOCAL7 if no other value is set. to disable syslog logging completely, put this in ha.cf: logfacility none Unfortunately this isn't a true statement. I tried to set logfacility to local6 and then to none. Still messages in boot.log. And setting lofgacility to none doesn't completely disable syslog logging. On 7/20/07, Serge Dubrouski <[EMAIL PROTECTED]> wrote: > Just found that Heartbeat code explicitly uses LOCAL7 logfacility for > system logging: > > cl_log_set_entity(entity); > cl_log_set_facility(LOG_LOCAL7); > > and so on. > > On standard Linux distribution ( RedHat at least) LOCAL7 is dedicated > for boot processes and is directed to go to boot.log. What was the > reason in ignoring the logfacility value from ha.cf and explicitly > using LOCAL7? > > -- > Serge Dubrouski. > ___ > Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev > Home Page: http://linux-ha.org/ > ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/ -- Serge Dubrouski. ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
[Linux-ha-dev] Bugs in the last Apache RA
apache RA in the last version of Heartbeat was updated with ability to scan HTTP config files to look up required httpd config parameters (status URL and so). Unfortunately it was done little bit incorrectly. My httpd.conf file has following records: Include conf/balancer-prod.conf Include conf/extra/httpd-default.conf and so on. All these cause following error messages for apache RA: ls: conf/extra/httpd-mpm.conf: No such file or directory ls: conf/extra/httpd-default.conf: No such file or directory ls: conf/balancer-pte.conf: No such file or directory Than happens because awk code in apachecat function doesn't use ServerRoor parameter when it processes Include records. Again it's not a big deal because it doesn't break main functionality. But it is really annoying because it creates those error messages with every invocation of apache RA. -- Serge Dubrouski. ___ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
