Re: [Linux-ha-dev] crmsh issues FutureWarning of python
Hi Takatoshi-san, On Wed, Jun 26, 2013 at 11:48:00AM +0900, Takatoshi MATSUO wrote: Hi Dejan I received another FutureWarning of python. /usr/lib64/python2.6/site-packages/crmsh/completion.py:88: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead. if not doc Fixed now. Thanks! Dejan Regards, Takatoshi MATSUO 2013/6/21 Takatoshi MATSUO matsuo@gmail.com: Hi Dejan Thank you for your quick response. I can inhibit warnings. Regards, Takatoshi MATSUO 2013/6/21 Dejan Muhamedagic de...@suse.de: Hi Takatoshi-san, On Fri, Jun 21, 2013 at 04:41:39PM +0900, Takatoshi MATSUO wrote: Hi Dejan I use latest crmsh(ff28b19bdb1d) and it issues FutureWarning of python when using comment(#). config.crm file # Comment property \ no-quorum-policy=ignore \ stonith-enabled=false \ startup-fencing=false \ stonith-timeout=20s --- # crm configure load update config.crm /usr/lib64/python2.7/site-packages/crmsh/cibconfig.py:917: FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead. if comments and node: Fixed now. And some more. Hope there won't be any more in Future. Cheers, Dejan --- I use python 2.7.3 on Fedora 18. Python 2.6.6 issues same warning on RHEL6. Thanks, Takatoshi MATSUO ___ 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: 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/
Re: [Linux-ha-dev] crmsh issues FutureWarning of python
Hi Dejan
Thanks.
But previous commit c8e7cb61 or 7c9df6e81 (Jun 21) cause this error
when using comment between configuration.
config.crm
property \
no-quorum-policy=ignore \
stonith-enabled=false \
startup-fencing=false \
stonith-timeout=20s
# comment
primitive dummy ocf:heartbeat:Dummy
--
# crm configure load update config.crm
Traceback (most recent call last):
File /usr/sbin/crm, line 44, in module
main.run()
File /usr/lib64/python2.6/site-packages/crmsh/main.py, line 414, in run
do_work()
File /usr/lib64/python2.6/site-packages/crmsh/main.py, line 323, in do_work
if parse_line(levels, shlex.split(' '.join(l))):
File /usr/lib64/python2.6/site-packages/crmsh/main.py, line 149,
in parse_line
rv = d() # execute the command
File /usr/lib64/python2.6/site-packages/crmsh/main.py, line 148, in lambda
d = lambda: cmd[0](*args)
File /usr/lib64/python2.6/site-packages/crmsh/ui.py, line 1694, in load
return set_obj.import_file(method, url)
File /usr/lib64/python2.6/site-packages/crmsh/cibconfig.py, line
268, in import_file
return self.save(s, method == update)
File /usr/lib64/python2.6/site-packages/crmsh/cibconfig.py, line
455, in save
if self.process(cli_list, update) == False:
File /usr/lib64/python2.6/site-packages/crmsh/cibconfig.py, line
409, in process
obj = cib_factory.create_from_cli(cli_list)
File /usr/lib64/python2.6/site-packages/crmsh/cibconfig.py, line
2615, in create_from_cli
node = obj.cli2node(cli_list)
File /usr/lib64/python2.6/site-packages/crmsh/cibconfig.py, line
918, in cli2node
stuff_comments(node, comments)
File /usr/lib64/python2.6/site-packages/crmsh/xmlutil.py, line
506, in stuff_comments
add_comment(node, s)
File /usr/lib64/python2.6/site-packages/crmsh/xmlutil.py, line
503, in add_comment
e.insert(firstelem, comm_elem)
File lxml.etree.pyx, line 723, in lxml.etree._Element.insert
(src/lxml/lxml.etree.c:32132)
TypeError: 'NoneType' object cannot be interpreted as an index
Commit ff28b19b doesn't issue this error.
Regards,
Takatoshi MATSUO
2013/6/26 Dejan Muhamedagic de...@suse.de:
Hi Takatoshi-san,
On Wed, Jun 26, 2013 at 11:48:00AM +0900, Takatoshi MATSUO wrote:
Hi Dejan
I received another FutureWarning of python.
/usr/lib64/python2.6/site-packages/crmsh/completion.py:88:
FutureWarning: The behavior of this
method will change in future versions. Use specific 'len(elem)' or
'elem is not None' test instead.
if not doc
Fixed now. Thanks!
Dejan
Regards,
Takatoshi MATSUO
2013/6/21 Takatoshi MATSUO matsuo@gmail.com:
Hi Dejan
Thank you for your quick response.
I can inhibit warnings.
Regards,
Takatoshi MATSUO
2013/6/21 Dejan Muhamedagic de...@suse.de:
Hi Takatoshi-san,
On Fri, Jun 21, 2013 at 04:41:39PM +0900, Takatoshi MATSUO wrote:
Hi Dejan
I use latest crmsh(ff28b19bdb1d) and it issues FutureWarning of python
when using comment(#).
config.crm file
# Comment
property \
no-quorum-policy=ignore \
stonith-enabled=false \
startup-fencing=false \
stonith-timeout=20s
---
# crm configure load update config.crm
/usr/lib64/python2.7/site-packages/crmsh/cibconfig.py:917:
FutureWarning: The behavior of this method will change in future
versions. Use specific 'len(elem)' or 'elem is not None' test instead.
if comments and node:
Fixed now. And some more. Hope there won't be any more in Future.
Cheers,
Dejan
---
I use python 2.7.3 on Fedora 18.
Python 2.6.6 issues same warning on RHEL6.
Thanks,
Takatoshi MATSUO
___
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: 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: 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] LVS with IPv6
Hi, On 26 jun. 2013, at 02:49, Listas wrote: I'm trying to configure an IPv6 LVS. I need to run radvd on my router to work? I made this configuration: In my network gateway: ifconfig eth1 add 2001:db8:38a5::1/48 In realserver: ifconfig eth1 add 2001:db8:38a5:8::af5a/48 ifconfig lo add 2001:db8:38a5:8::2006/128 In virtualserver: ifconfig eth1 add 2001:db8:38a5::bc5f/48 ifconfig eth1 add 2001:db8:38a5:8::2006/128 ipvsadm -A -u [2001:db8:38a5:8:0:0:0:2006]:53 -s wlc ipvsadm -a -u [2001:db8:38a5:8:0:0:0:2006]:53 -r [2001:db8:38a5:8::af5a]:53 -w 888 Did the 2001:db8:38a5:8::2006 address actually get assigned to lo on the realserver? If not you have probably not yet disabled DAD (duplicate address detection) for lo on the realserver: echo 0 /proc/sys/net/ipv6/conf/lo/dad_transmits echo 0 /proc/sys/net/ipv6/conf/lo/accept_dad This should be done before configuring the IPv6 addresses, somewhat like the way you would change ARP configuration for IPv4. Also I would recommend using TCP to test the configuration as you might get more feedback on the client if something goes wrong. Kind regards, -- Sebastiaan Hoogeveen s.hoogev...@nederhost.nl NederHost is ingeschreven bij de Kamer van Koophandel onder dossier 34099781. ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
[Linux-HA] Resource Always Tries to Start on the Wrong Node
I don't understand why resources try to start on the wrong node (and of course fail). My nodes are ha05 and ha06. ha05 is master/primary and all resources are running on it. If I run... crm resource stop p_MySQL_185 ..the resource stops fine. Then if I run... crm resource start p_MySQL_185 ..the resource fails to start, and crm_mon shows that it tried to start on the wrong node (ha06). Then if I run... crm resource cleanup p_MySQL_185 ..the resource cleans up and starts on node ha05. Here is my crm config... node ha05.mycharts.md \ attributes standby=off node ha06.mycharts.md primitive p_ClusterIP ocf:heartbeat:IPaddr2 \ params ip=192.168.10.205 cidr_netmask=32 \ op monitor interval=15s \ meta target-role=Started primitive p_DRBD ocf:linbit:drbd \ params drbd_resource=ha_mysql \ op monitor interval=15s primitive p_FileSystem ocf:heartbeat:Filesystem \ params device=/dev/drbd0 directory=/ha_mysql fstype=ext3 options=noatime primitive p_MySQL_000 lsb:mysql_000 primitive p_MySQL_001 lsb:mysql_001 primitive p_MySQL_054 lsb:mysql_054 primitive p_MySQL_057 lsb:mysql_057 primitive p_MySQL_103 lsb:mysql_103 primitive p_MySQL_106 lsb:mysql_106 primitive p_MySQL_139 lsb:mysql_139 primitive p_MySQL_140 lsb:mysql_140 primitive p_MySQL_141 lsb:mysql_141 primitive p_MySQL_142 lsb:mysql_142 primitive p_MySQL_143 lsb:mysql_143 primitive p_MySQL_144 lsb:mysql_144 primitive p_MySQL_145 lsb:mysql_145 primitive p_MySQL_146 lsb:mysql_146 primitive p_MySQL_147 lsb:mysql_147 primitive p_MySQL_148 lsb:mysql_148 primitive p_MySQL_149 lsb:mysql_149 primitive p_MySQL_150 lsb:mysql_150 primitive p_MySQL_151 lsb:mysql_151 primitive p_MySQL_152 lsb:mysql_152 primitive p_MySQL_153 lsb:mysql_153 primitive p_MySQL_154 lsb:mysql_154 primitive p_MySQL_157 lsb:mysql_157 primitive p_MySQL_158 lsb:mysql_158 primitive p_MySQL_160 lsb:mysql_160 primitive p_MySQL_161 lsb:mysql_161 primitive p_MySQL_162 lsb:mysql_162 primitive p_MySQL_163 lsb:mysql_163 primitive p_MySQL_164 lsb:mysql_164 primitive p_MySQL_165 lsb:mysql_165 primitive p_MySQL_167 lsb:mysql_167 primitive p_MySQL_168 lsb:mysql_168 primitive p_MySQL_169 lsb:mysql_169 primitive p_MySQL_170 lsb:mysql_170 primitive p_MySQL_171 lsb:mysql_171 primitive p_MySQL_172 lsb:mysql_172 primitive p_MySQL_173 lsb:mysql_173 primitive p_MySQL_174 lsb:mysql_174 primitive p_MySQL_175 lsb:mysql_175 primitive p_MySQL_176 lsb:mysql_176 primitive p_MySQL_177 lsb:mysql_177 primitive p_MySQL_178 lsb:mysql_178 primitive p_MySQL_179 lsb:mysql_179 primitive p_MySQL_180 lsb:mysql_180 primitive p_MySQL_181 lsb:mysql_181 primitive p_MySQL_182 lsb:mysql_182 primitive p_MySQL_183 lsb:mysql_183 primitive p_MySQL_184 lsb:mysql_184 primitive p_MySQL_185 lsb:mysql_185 \ meta target-role=Started primitive p_MySQL_186 lsb:mysql_186 primitive p_MySQL_187 lsb:mysql_187 primitive p_MySQL_188 lsb:mysql_188 primitive p_MySQL_189 lsb:mysql_189 \ meta target-role=Started primitive p_MySQL_191 lsb:mysql_191 primitive p_MySQL_192 lsb:mysql_192 primitive p_MySQL_194 lsb:mysql_194 primitive p_MySQL_195 lsb:mysql_195 primitive p_MySQL_196 lsb:mysql_196 primitive p_MySQL_197 lsb:mysql_197 primitive p_MySQL_198 lsb:mysql_198 primitive p_MySQL_199 lsb:mysql_199 primitive p_MySQL_200 lsb:mysql_200 primitive p_MySQL_201 lsb:mysql_201 primitive p_MySQL_202 lsb:mysql_202 primitive p_MySQL_203 lsb:mysql_203 primitive p_MySQL_204 lsb:mysql_204 primitive p_MySQL_205 lsb:mysql_205 primitive p_MySQL_206 lsb:mysql_206 primitive p_MySQL_207 lsb:mysql_207 primitive p_MySQL_208 lsb:mysql_208 primitive p_MySQL_209 lsb:mysql_209 primitive p_MySQL_210 lsb:mysql_210 primitive p_MySQL_211 lsb:mysql_211 primitive p_MySQL_212 lsb:mysql_212 primitive p_MySQL_213 lsb:mysql_213 primitive p_MySQL_214 lsb:mysql_214 primitive p_MySQL_215 lsb:mysql_215 primitive p_MySQL_216 lsb:mysql_216 primitive p_MySQL_217 lsb:mysql_217 primitive p_MySQL_218 lsb:mysql_218 primitive p_MySQL_219 lsb:mysql_219 primitive p_MySQL_220 lsb:mysql_220 primitive p_MySQL_221 lsb:mysql_221 primitive p_MySQL_222 lsb:mysql_222 primitive p_MySQL_224 lsb:mysql_224 primitive p_MySQL_225 lsb:mysql_225 primitive p_MySQL_226 lsb:mysql_226 primitive p_MySQL_227 lsb:mysql_227 primitive p_MySQL_228 lsb:mysql_228 primitive p_MySQL_229 lsb:mysql_229 ms ms_DRBD p_DRBD \ meta master-max=1 master-node-max=1 clone-max=2 clone-node-max=1 notify=true colocation c_virtdb03 inf: ( p_MySQL_001 p_MySQL_139 p_MySQL_140 p_MySQL_141 p_MySQL_142 p_MySQL_143 p_MySQL_144 p_MySQL_145 p_MySQL_146 p_MySQL_147 p_MySQL_148 p_MySQL_149 p_MySQL_106 p_MySQL_103 p_MySQL_150 p_MySQL_057 p_MySQL_151 p_MySQL_152 p_MySQL_153 p_MySQL_154 p_MySQL_054 p_MySQL_157 p_MySQL_158 p_MySQL_160 p_MySQL_161 p_MySQL_162 p_MySQL_163 p_MySQL_164 p_MySQL_165 p_MySQL_167 p_MySQL_168 p_MySQL_169 p_MySQL_170 p_MySQL_171 p_MySQL_172 p_MySQL_173 p_MySQL_174 p_MySQL_175 p_MySQL_176 p_MySQL_177 p_MySQL_178 p_MySQL_179 p_MySQL_180 p_MySQL_181 p_MySQL_182
Re: [Linux-HA] disallowing concurrent configuration (CIB modifications)
On Thu, Jun 06, 2013 at 05:19:03PM +0200, Dejan Muhamedagic wrote: Hi, On Thu, Jun 06, 2013 at 03:11:16PM +0300, Vladislav Bogdanov wrote: 06.06.2013 08:43, Vladislav Bogdanov wrote: [...] I recall that LDAP has similar problem, which is easily worked around with specifying two values, one is original, second is new. That way you tell LDAP server: Replace value Y in attribute X to value Z. And if value is not Y at the moment of modification request, then command fails. cibadmin --patch works this way Who is baking new CIB in that case, cibadmin or cib? The patch is applied on the server - so cib Then that is safe way to go, assuming that cib daemon serializes modification requests. It would be great if crmsh use that trick. Hope to have something soon. Stay tuned. The patch for crmsh is attached and you'll need the very latest pacemaker (because cibadmin needed some fixing). Unfortunately, I cannot push this yet to the repository, as the current pacemaker 1.1.10-rc still identifies itself as 1.1.9. I'd appreciate if you could test it. Once again: Do not use this patch with anything before pacemaker commit 7cd53c! Cheers, Dejan Thanks, Dejan ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems # HG changeset patch # User Dejan Muhamedagic de...@hello-penguin.com # Date 1372250948 -7200 # Wed Jun 26 14:49:08 2013 +0200 # Node ID c60a0e24683631aa4f7ac5903b0bab51cff472e6 # Parent 186677999fcdc42dbaf97aa211c0d3b45870787b High: cibconfig: use cibadmin patch to update live CIB diff -r 186677999fcd -r c60a0e246836 modules/cibconfig.py --- a/modules/cibconfig.py Wed Jun 26 14:43:52 2013 +0200 +++ b/modules/cibconfig.py Wed Jun 26 14:49:08 2013 +0200 @@ -1928,7 +1928,6 @@ class CibFactory(Singleton): self._init_vars() self.regtest = options.regression_tests self.last_commit_time = 0 -self.all_committed = True # has commit produced error self._no_constraint_rm_msg = False # internal (just not to produce silly messages) self.supported_cib_re = ^pacemaker-1[.][012]$ def is_cib_sane(self): @@ -2052,18 +2051,15 @@ class CibFactory(Singleton): # create a doc from the list of objects # (used by CibObjectSetRaw) # -def _regtest_filter(self, cib): -for attr in (epoch, admin_epoch): -if cib.get(attr): -cib.set(attr, 0) -for attr in (cib-last-written,): -if cib.get(attr): -del cib.attrib[attr] +def bump_epoch(self): +try: +self.cib_attrs[epoch] = str(int(self.cib_attrs[epoch])+1) +except: +common_warn(could not bump epoch, setting it to 1) +self.cib_attrs[epoch] = 1 def _set_cib_attributes(self, cib): for attr in self.cib_attrs: cib.set(attr, self.cib_attrs[attr]) -if self.regtest: -self._regtest_filter(cib) def objlist2doc(self, obj_list, obj_filter=None): ''' Return document containing objects in obj_list. @@ -2096,8 +2092,6 @@ class CibFactory(Singleton): cib_attr = None return c.get(a) == cib_attr def is_current_cib_equal(self, silent=False): -if self.overwrite: -return True cib_elem = read_cib(cibdump2elem) if cib_elem is None: return False @@ -2122,9 +2116,10 @@ class CibFactory(Singleton): 'Commit the configuration to the CIB.' if not self.is_cib_sane(): return False -# all_committed is updated in the invoked object methods -self.all_committed = True -rc = self._commit_doc(force) +if cibadmin_can_patch(): +rc = self._patch_cib(force) +else: +rc = self._replace_cib(force) if rc: # reload the cib! common_debug(CIB commit successful) @@ -2132,8 +2127,8 @@ class CibFactory(Singleton): self.last_commit_time = time.time() self.reset() self.initialize() -return self.all_committed -def _commit_schema(self): +return rc +def _update_schema(self): ''' Set the validate-with, if the schema changed. ''' @@ -2144,13 +2139,13 @@ class CibFactory(Singleton): return False self.new_schema = False return True -def _commit_doc(self, force): +def _replace_cib(self, force): try: conf_el = self.cib_elem.findall(configuration)[0] except IndexErr: common_error(cannot find the configuration element) return False -if self.new_schema and not self._commit_schema(): +if self.new_schema and not self._update_schema():
Re: [Linux-HA] disallowing concurrent configuration (CIB modifications)
26.06.2013 15:57, Dejan Muhamedagic wrote: On Thu, Jun 06, 2013 at 05:19:03PM +0200, Dejan Muhamedagic wrote: Hi, On Thu, Jun 06, 2013 at 03:11:16PM +0300, Vladislav Bogdanov wrote: 06.06.2013 08:43, Vladislav Bogdanov wrote: [...] I recall that LDAP has similar problem, which is easily worked around with specifying two values, one is original, second is new. That way you tell LDAP server: Replace value Y in attribute X to value Z. And if value is not Y at the moment of modification request, then command fails. cibadmin --patch works this way Who is baking new CIB in that case, cibadmin or cib? The patch is applied on the server - so cib Then that is safe way to go, assuming that cib daemon serializes modification requests. It would be great if crmsh use that trick. Hope to have something soon. Stay tuned. The patch for crmsh is attached and you'll need the very latest pacemaker (because cibadmin needed some fixing). Unfortunately, I cannot push this yet to the repository, as the current pacemaker 1.1.10-rc still identifies itself as 1.1.9. I'd appreciate if you could test it. Seems to work during preliminary testing (stop clone with crm configure edit and then start it with crm resource start). cib process on the DC reports it received the diff and handles that perfectly. Thank you! I'll build updated package with this patch tomorrow and try to put that into real work. I mean to try concurrent updates. What would be the best way to achieve them? Is starting editing with crm configure edit with some concurrent command during that editing is enough (and save after command is run)? Vladislav ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] disallowing concurrent configuration (CIB modifications)
On Wed, Jun 26, 2013 at 06:13:33PM +0300, Vladislav Bogdanov wrote: 26.06.2013 15:57, Dejan Muhamedagic wrote: On Thu, Jun 06, 2013 at 05:19:03PM +0200, Dejan Muhamedagic wrote: Hi, On Thu, Jun 06, 2013 at 03:11:16PM +0300, Vladislav Bogdanov wrote: 06.06.2013 08:43, Vladislav Bogdanov wrote: [...] I recall that LDAP has similar problem, which is easily worked around with specifying two values, one is original, second is new. That way you tell LDAP server: Replace value Y in attribute X to value Z. And if value is not Y at the moment of modification request, then command fails. cibadmin --patch works this way Who is baking new CIB in that case, cibadmin or cib? The patch is applied on the server - so cib Then that is safe way to go, assuming that cib daemon serializes modification requests. It would be great if crmsh use that trick. Hope to have something soon. Stay tuned. The patch for crmsh is attached and you'll need the very latest pacemaker (because cibadmin needed some fixing). Unfortunately, I cannot push this yet to the repository, as the current pacemaker 1.1.10-rc still identifies itself as 1.1.9. I'd appreciate if you could test it. Seems to work during preliminary testing (stop clone with crm configure edit and then start it with crm resource start). cib process on the DC reports it received the diff and handles that perfectly. Thank you! I'll build updated package with this patch tomorrow and try to put that into real work. I mean to try concurrent updates. What would be the best way to achieve them? Is starting editing with crm configure edit with some concurrent command during that editing is enough (and save after command is run)? I didn't remove the check for the changes and anyway cib is going to refuse to apply the patch if the epoch is older. Of course, crmsh can set the epoch attribute to something greater than the current epoch. What would you suggest? Cheers, Dejan Vladislav ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
[Linux-HA] How/Where does ocf_log log?
Where exactly do calls using 'ocf_log' log the information? For instance with the call: ocf_log info Starting $InstanceName inside a start function, where (what file) should I be looking for this output? Does any configuration need to be done to have the logging enabled or should it work by default 'out of the box'? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] How/Where does ocf_log log?
On 2013-06-26T19:48:41, Tony Stocker tony.stoc...@nasa.gov wrote: Where exactly do calls using 'ocf_log' log the information? For instance with the call: ocf_log info Starting $InstanceName inside a start function, where (what file) should I be looking for this output? /var/log/messages. Though I'd be open to consider a separate log file per agent; the ocf-shellfunc file could make that configurable easily enough. Does any configuration need to be done to have the logging enabled or should it work by default 'out of the box'? It ought to work by default. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Experience is the name everyone gives to their mistakes. -- Oscar Wilde ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
