[gnugo-devel] Cross-compile patch

[Tom Parker-Shemilt]

Hi folks. Wasn't sure how much dev was still being done on this, but
hopefully this is still of use to others. I wanted to get GNU Go
running on a Remarkable (and then eventually build a frontend), but
cross-compilation was hard, due to the fun of the programs in the
"patterns" folder being used at build time. I've seen earlier methods
described with multiple configure runs and deleting some files, but I
wanted something a little more reproducible. The attached patch
against the "ttn-maint" branch (which as best I could tell was the
most up-to-date branch so I didn't need half a dozen other fixes as
well) enables cross-compile in a single configure/make sequence. The
hard part was that the programs in "patterns" use libraries from other
folders that are also used by the host machine. To solve this, the
relevant folders now have a lib-host.a build as well as a
lib.a build. The latter is for the compile target, the former is
for the host target. This is done in a pretty crude way, but seems to
work so far. There's a little bit of hardcoding of the ranlib build
machine command name that I haven't fixed, as couldn't find an
equivalent of AX_PROG_CC_FOR_BUILD for ranlib.

https://github.com/palfrey/gnugo/pull/1 also has some other patches so
I could do a CI run using the Toltec (https://toltec-dev.org/) build
images for Remarkable but I'm assuming you've got no interest in
Github actions patches, and TBH once you've got cross-compile working
the Remarkable works just fine.

Enjoy!

Tom Parker-Shemilt
From ed1fa08c00d0571fc4416fb0649c64806854a8b0 Mon Sep 17 00:00:00 2001
From: Tom Parker-Shemilt 
Date: Wed, 4 Oct 2023 23:21:22 +0100
Subject: [PATCH] Working cross-compile build

This enables cross-compile in a single configure/make sequence. The hard part was that there's a variety of programs in patterns that get used at compile time, and so they need to be compiled for the build machine, but they use libraries from other folders that are also used by the host machine.

To solve this, the relevant folders have a lib-host.a build as well as a lib.a build. The latter is for the compile target, the former is for the host target. This is done in a pretty crude way, but seems to work so far.

Signed-off-by: Tom Parker-Shemilt 
---
 configure.ac   |   3 +
 engine/Makefile.am |  26 ++-
 m4/ax_prog_cc_for_build.m4 | 155 +
 patterns/Makefile.am   |  33 ++--
 sgf/Makefile.am|  18 -
 utils/Makefile.am  |  21 -
 6 files changed, 245 insertions(+), 11 deletions(-)
 create mode 100644 m4/ax_prog_cc_for_build.m4

diff --git a/configure.ac b/configure.ac
index 3ff08a7f..254e17bf 100644
--- a/configure.ac
+++ b/configure.ac
@@ -125,7 +125,10 @@ AC_ARG_ENABLE(socket-support,
  [  --disable-socket-support   don't compile GTP over TCP/IP support
   --enable-socket-supportcompile TCP/IP support (default)])
 
+AC_CONFIG_MACRO_DIR([m4])
+
 AC_PROG_CC
+AX_PROG_CC_FOR_BUILD
 
 dnl for automake 1.4.x
 AC_EXEEXT
diff --git a/engine/Makefile.am b/engine/Makefile.am
index d0203034..f4a37985 100644
--- a/engine/Makefile.am
+++ b/engine/Makefile.am
@@ -14,7 +14,7 @@ noinst_HEADERS = cache.h gnugo.h hash.h clock.h readconnect.h \
  influence.h liberty.h move_reasons.h board.h
 
 # preconfigured settings for various configurations
-noinst_LIBRARIES = libengine.a libboard.a
+noinst_LIBRARIES = libengine.a libengine-host.a libboard.a libboard-host.a
 
 libengine_a_SOURCES = \
   aftermath.c \
@@ -61,3 +61,27 @@ libboard_a_SOURCES = \
   boardlib.c \
   hash.c \
   printutils.c
+
+LINK_FOR_BUILD.c = $(CC_FOR_BUILD) $(CFLAGS_FOR_BUILD) $(LDFLAGS_FOR_BUILD)
+COMPILE_FOR_BUILD = $(CC_FOR_BUILD) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
+	$(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
+
+%-host.o : %.c	
+	$(AM_V_CC)$(COMPILE_FOR_BUILD) -MT $@ -MD -MP -MF $(DEPDIR)/$*.Tpo -c -o $@ $<
+	$(AM_V_at)$(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po
+
+libengine_host_a_SOURCES = 
+libengine_host_a_DEPENDENCIES = $(patsubst %.c,%-host.o,$(libengine_a_SOURCES))
+
+libengine-host.a: $(libengine_host_a_OBJECTS) $(libengine_host_a_DEPENDENCIES)
+	rm -f libengine-host.a
+	$(AM_V_AR)$(libengine_host_a_AR) libengine-host.a $(libengine_host_a_OBJECTS) $(libengine_host_a_DEPENDENCIES)
+	x86_64-linux-gnu-ranlib libengine-host.a
+
+libboard_host_a_SOURCES = 
+libboard_host_a_DEPENDENCIES = $(patsubst %.c,%-host.o,$(libboard_a_SOURCES))
+
+libboard-host.a: $(libboard_host_a_OBJECTS) $(libboard_host_a_DEPENDENCIES)
+	rm -f libboard-host.a
+	$(AM_V_AR)$(libboard_host_a_AR) libboard-host.a $(libboard_host_a_OBJECTS) $(libboard_host_a_DEPENDENCIES)
+	x86_64-linux-gnu-ranlib libboard-host.a
diff --git a/m4/ax_prog_cc_for_build.m4 b/m4/ax_prog_cc_for_build.m4
new file mode 100644
index ..1db8d73f
--- /dev/null
+++ b/m4/ax_pr

bug#60694: Issue building derivations in 1.4.0

[Tom Parker-Shemilt]

On Fri, 13 Jan 2023 at 03:35, Maxim Cournoyer  wrote:

> How much memory (RAM) do you have available on the machine?
>
> Guix pull consumes close to 2 GiB peak, if I recall correctly.

That was with 4GB. Tried upping to 8GB and now getting a different
error. My channels.scm is

(list (channel
(name 'guix)
(url "git://git.savannah.gnu.org/guix.git")
(commit "8e2f32cee982d42a79e53fc1e9aa7b8ff0514714"); tag v1.4.0
(introduction (make-channel-introduction
   "9edb3f66fd807b096b48283debdcddccfea34bad" ;2020-05-26
   (openpgp-fingerprint
"BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA")

==> virtualbox-iso: guix system: error: aborting reconfiguration
because commit 8e2f32cee982d42a79e53fc1e9aa7b8ff0514714 of channel
'guix' is not a descendant of 989a3916dc8967bcb7275f10452f89bc6c3389cc
==> virtualbox-iso: hint: Backtrace:
==> virtualbox-iso: In guix/ui.scm:
==> virtualbox-iso:2275:7 19 (run-guix . _)
==> virtualbox-iso:   2238:10 18 (run-guix-command _ . _)
==> virtualbox-iso: In ice-9/boot-9.scm:
==> virtualbox-iso:   1752:10 17 (with-exception-handler _ _ #:unwind? _ # _)
==> virtualbox-iso: In guix/status.scm:
==> virtualbox-iso: 835:3 16 (_)
==> virtualbox-iso: 815:4 15 (call-with-status-report _ _)
==> virtualbox-iso: In guix/scripts/system.scm:
==> virtualbox-iso:1281:4 14 (_)
==> virtualbox-iso: In ice-9/boot-9.scm:
==> virtualbox-iso:   1752:10 13 (with-exception-handler _ _ #:unwind? _ # _)
==> virtualbox-iso: In guix/store.scm:
==> virtualbox-iso:661:37 12 (thunk)
==> virtualbox-iso:1300:8 11 (call-with-build-handler # …)
==> virtualbox-iso:   2170:25 10 (run-with-store # …)
==> virtualbox-iso: In guix/scripts/system.scm:
==> virtualbox-iso:   1305:15  9 (_ _)
==> virtualbox-iso: 835:5  8 (perform-action reconfigure #<
name: #f format:…> …)
==> virtualbox-iso: In srfi/srfi-1.scm:
==> virtualbox-iso: 634:9  7 (for-each # …)
==> virtualbox-iso: In ice-9/boot-9.scm:
==> virtualbox-iso:   1685:16  6 (raise-exception _ #:continuable? _)
==> virtualbox-iso:   1685:16  5 (raise-exception _ #:continuable? _)
==> virtualbox-iso: In guix/ui.scm:
==> virtualbox-iso:802:16  4 (_ _)
==> virtualbox-iso:311:42  3 (display-hint "Use
@option{--allow-downgrades} to forc…" …)
==> virtualbox-iso: In ice-9/boot-9.scm:
==> virtualbox-iso:   1747:15  2 (with-exception-handler # …)
==> virtualbox-iso: In guix/build/syscalls.scm:
==> virtualbox-iso:   2299:35  1 (_)
==> virtualbox-iso:2288:8  0 (terminal-window-size _)

bug#60694: Acknowledgement (Issue building derivations in 1.4.0)

[Tom Parker-Shemilt]

I hit this while running in a low-CPU Virtualbox setup doing some
Packer work on https://github.com/palfrey/guix-vm. I upped the CPU
specs and got another error

==> virtualbox-iso: Backtrace:
==> virtualbox-iso: In ice-9/eval.scm:
==> virtualbox-iso: 155:9 19 (_ _)
==> virtualbox-iso: 159:9 18 (_
#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(# ?) ?) ?) ?) ?)
?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
==> virtualbox-iso: In ice-9/boot-9.scm:
==> virtualbox-iso: 152:2 17 (with-fluid* _ _ _)
==> virtualbox-iso: 152:2 16 (with-fluid* _ _ _)
==> virtualbox-iso: In ./guix/store.scm:
==> virtualbox-iso:   2170:24 15 (run-with-store # #
?)
==> virtualbox-iso:1998:8 14 (_ #)
==> virtualbox-iso: In ./guix/gexp.scm:
==> virtualbox-iso:299:22 13 (_ #)
==> virtualbox-iso:1180:2 12 (_ #)
==> virtualbox-iso:1046:2 11 (_ #)
==> virtualbox-iso: 892:4 10 (_ #)
==> virtualbox-iso: In ./guix/store.scm:
==> virtualbox-iso:   2055:12  9 (_ #)
==> virtualbox-iso:   1407:13  8 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  7 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  6 (map/accumulate-builds
# # ?)
==> virtualbox-iso:1403:5  5 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1419:15  4 (_ # ("/gnu/store/hvjrj0dmfjfh95wr5xn1hgwyw2nyaqlc-subversion?"
?) ?)
==> virtualbox-iso:   1419:15  3 (loop #f)
==> virtualbox-iso:713:11  2 (process-stderr # _)
==> virtualbox-iso: In ./guix/serialization.scm:
==> virtualbox-iso:102:11  1 (read-int #)
==> virtualbox-iso:  80:6  0 (get-bytevector-n* # 8)
==> virtualbox-iso:
==> virtualbox-iso: ./guix/serialization.scm:80:6: In procedure
get-bytevector-n*:
==> virtualbox-iso: ERROR:
==> virtualbox-iso:   1. :
==> virtualbox-iso:   file: #f
==> virtualbox-iso:   port: #
==> virtualbox-iso: guix pull: error: You found a bug: the program
'/gnu/store/lzinbzm0hxvnz11c4cin1ml9ybhrg7r5-compute-guix-derivation'
==> virtualbox-iso: failed to compute the derivation for Guix
(version: "8e2f32cee982d42a79e53fc1e9aa7b8ff0514714"; system:
"x86_64-linux";
==> virtualbox-iso: host version: "1.4.0"; pull-version: 1).
==> virtualbox-iso: Please report the COMPLETE output above by email
to .

On Mon, 9 Jan 2023 at 18:34, GNU bug Tracking System
 wrote:
>
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  bug-guix@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 60...@debbugs.gnu.org.
>
> Please do not send mail to help-debb...@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 60694: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60694
> GNU Bug Tracking System
> Contact help-debb...@gnu.org with problems

bug#60694: Issue building derivations in 1.4.0

[Tom Parker-Shemilt]

==> virtualbox-iso: Backtrace:
==> virtualbox-iso:   18 (primitive-load
"/gnu/store/lzinbzm0hxvnz11c4cin1ml9ybhrg7r5-compute-guix-derivation")
==> virtualbox-iso: In ice-9/eval.scm:
==> virtualbox-iso: 155:9 17 (_ _)
==> virtualbox-iso: 159:9 16 (_
#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(# ?) ?) ?) ?) ?)
?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
==> virtualbox-iso: In ice-9/boot-9.scm:
==> virtualbox-iso: 152:2 15 (with-fluid* _ _ _)
==> virtualbox-iso: 152:2 14 (with-fluid* _ _ _)
==> virtualbox-iso: In ./guix/store.scm:
==> virtualbox-iso:   2170:24 13 (run-with-store # #
?)
==> virtualbox-iso:1998:8 12 (_ #)
==> virtualbox-iso: In ./guix/gexp.scm:
==> virtualbox-iso:299:22 11 (_ #)
==> virtualbox-iso:1180:2 10 (_ #)
==> virtualbox-iso:1046:2  9 (_ #)
==> virtualbox-iso: 892:4  8 (_ #)
==> virtualbox-iso: In ./guix/store.scm:
==> virtualbox-iso:   2055:12  7 (_ #)
==> virtualbox-iso:   1407:13  6 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  5 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  4 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  3 (map/accumulate-builds
# # ?)
==> virtualbox-iso:1403:5  2 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1419:15  1 (_ # ("/gnu/store/p23y74y51gj4vml3mjlg9swx0gg4k22s-ruby-2.7.7.d?")
?)
==> virtualbox-iso:   1419:15  0 (loop #f)
==> virtualbox-iso:
==> virtualbox-iso: ./guix/store.scm:1419:15: In procedure loop:
==> virtualbox-iso: ERROR:
==> virtualbox-iso:   1. :
==> virtualbox-iso:   message: "some substitutes for the outputs
of derivation `/gnu/store/p23y74y51gj4vml3mjlg9swx0gg4k22s-ruby-2.7.7.drv'
failed (usually happens due to networking issues); try `--fallback' to
build derivation from source "
==> virtualbox-iso:   status: 1
==> virtualbox-iso: guix pull: error: You found a bug: the program
'/gnu/store/lzinbzm0hxvnz11c4cin1ml9ybhrg7r5-compute-guix-derivation'
==> virtualbox-iso: failed to compute the derivation for Guix
(version: "8e2f32cee982d42a79e53fc1e9aa7b8ff0514714"; system:
"x86_64-linux";
==> virtualbox-iso: host version: "1.4.0"; pull-version: 1).
==> virtualbox-iso: Please report the COMPLETE output above by email
to .

Jira (FACT-3080) facter.conf facts and fact-groups sections make facter very slow.

[Tom Parker (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3080  
 
 
  facter.conf facts and fact-groups sections make facter very slow.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 facter-no-facts-groups-section.conf, facter-no-facts-section.conf, facter-no-ttls.conf, full-facter.conf  
 
 
Created: 
 2021/10/06 9:36 AM  
 
 
Environment: 
 CentOS 7  Puppet-agent 7.11  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 Having a facter.conf file causes facter to slow down dramatically.  All files have been attached for reference. Time for puppet facts show (full-facter.conf) real    5m51.406s  user    5m42.813s  sys 0m4.949s Time for puppet facts show (facter-no-ttls.conf) real    5m54.552s  user    5m45.233s  sys 0m5.734s Time for puppet facts show (facter-no-facts-section.conf) real    2m30.101s  user    2m2.598s  sys 0m10.459s Time for puppet facts show (facter-no-fact-groups-section.conf) real    1m45.888s  user    1m33.713s  sys 0m9.433s Time for no facter.conf at all. real    1m41.443s  user    1m29.070s  sys 0m9.653s

Jira (FACT-3079) Caching not working for some custom facts

[Tom Parker (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-3079  
 
 
  Caching not working for some custom facts   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 facter.conf, yum, yum-facter-debug.log  
 
 
Created: 
 2021/10/06 7:31 AM  
 
 
Environment: 
 Puppet 7.11 on CentOS 7  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 I have configured facter to cache and block several core and custom facts (puppet 7.11) and I am finding that the behaviour is odd.   The example that I have attached here is from the puppetlabs-yum module that declares 3 custom facts: - yum_package_updates (This is the primary fact that does all the work) - yum_has_updates (returns the value of yum_package_updates.any?) 
 
yum_updates (returns the value of yum_package_updates.length) 
 My facter.conf file (attached) declares a yum group that contains these 3 facts but when I run puppet only the yum_package_updates fact is cached (cache file attached). This seems to cause the other two dependent facts (yum_has_updates and yum_updates) to force the resolution (not from cache) of the main yum_package_updates fact. I can also see in the debug logs that it seems to use the cache sometimes but then lose the cached value and resolve it again.  It also states that the cache file is expired, missing or corrupt but the file is fresh, created by facter itself and the ttl is 6 hours. If I specify all 3 facts in the cache individually (not in a group) the caching behaviour seems to work properly

Jira (PUP-7931) Support HTTPS Compression on report upload

[Tom Parker (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PUP-7931  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support HTTPS Compression on report upload   
 

  
 
 
 
 

 
 Hello,  has there been any progress on this ticket?  Would it be possible to also include the same for puppet facts upload?  It would also benefit from compression. Could it not just be a puppet.conf setting for compress_uploads = true (–compress_uploads) and let the administrator enable it once they are sure their server side can handle decompressing the payloads?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.210137.1505138923000.18814.1619474640036%40Atlassian.JIRA.

Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid

[Tom Parker (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2924  
 
 
  Facter fails "closed" if the facter.conf file is invalid   
 

  
 
 
 
 

 
Change By: 
         Tom Parker  
 
 
Attachment: 
 facter.conf  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383703.1611082995000.160985.1615311240032%40Atlassian.JIRA.

Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid

[Tom Parker (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  FACT-2924  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Facter fails "closed" if the facter.conf file is invalid   
 

  
 
 
 
 

 
 This is still not 100% fixed.  On puppet-agent.x86_64 0:7.4.1-1.el7 I can't even run a puppet agent --version without a crash. My badly formatted facter.conf (caused by erroneously converting to json unstead of hocon) is: {{{ }} {{  "facts": { }} {{    "blocklist": null, }} {{    "ttls": [ }} {{  { }} {{    "EC2": "1 day" }} {{  } }} {{    ] }} {{  } }} } [LIVE] gredb1 [k: gredb]:~ # puppet agent --version  Traceback (most recent call last):     21: from /opt/puppetlabs/puppet/bin/puppet:4:in `'     20: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'     19: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'     18: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `'     17: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'     16: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'     15: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:15:in `'     14: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'     13: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'     12: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:10:in `'     11: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:13:in `'     10: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options.rb:40:in `init'  9: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:12:in `init'  8: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:24:in `augment_all'  7: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:93:in `augment_facts'  6: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:93:in `new'  5: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:16:in `initialize'  4: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:83:in `load_facts_ttls'  3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:83:in `each'  2: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:84:in `block in load_facts_ttls'  1: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:106:in `ttls_to_seconds'  /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups

Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid

[Tom Parker (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2924  
 
 
  Facter fails "closed" if the facter.conf file is invalid   
 

  
 
 
 
 

 
Change By: 
         Tom Parker  
 

  
 
 
 
 

 
 With facter 4 shipped with puppet 7.1  is  if  the facter.conf file is invalid facter fails to load at all which prevents all subsequent puppet runs.     This means that instead of being able to fix the problem with a puppet run the administrator has to login to any affected server and fix the file by hand.  Would it be possible to fail "open" if the file is invalid?  Log an error and run with all defaults?  This would at least allow puppet to fix the problem on a subsequent run.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.

Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid

[Tom Parker (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2924  
 
 
  Facter fails "closed" if the facter.conf file is invalid   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/01/19 11:03 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
         Tom Parker  
 

  
 
 
 
 

 
 With facter 4 shipped with puppet 7.1 is the facter.conf file is invalid facter fails to load at all which prevents all subsequent puppet runs.  This means that instead of being able to fix the problem with a puppet run the administrator has to login to any affected server and fix the file by hand.   Would it be possible to fail "open" if the file is invalid?  Log an error and run with all defaults?  This would at least allow puppet to fix the problem on a subsequent run.  
 

  
 
 
 
 

 
 
 

 
 

Jira (FACT-2922) Add --timing to puppet facts show

[Tom Parker (Jira)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2922  
 
 
  Add --timing to puppet facts show   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2021/01/15 10:28 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 facter --timing is incredibly useful to find slow facts on my systems however with the removal of the --puppet flag it only shows the built in facts.   Would it be possible to have the --timing flag added to the puppet facts show command to show slow puppet fact resolutions as well?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935

Jira (PUP-9967) puppet plugin download doesn't respect the server variable in puppet.conf

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PUP-9967  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet plugin download doesn't respect the server variable in puppet.conf   
 

  
 
 
 
 

 
 Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321330.1565991716000.9875.1576267380219%40Atlassian.JIRA.

Jira (PUP-9967) puppet plugin download doesn't respect the server variable in puppet.conf

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PUP-9967  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet plugin download doesn't respect the server variable in puppet.conf   
 

  
 
 
 
 

 
 Is there a user section or a general section where server and proxy variables can be defined that would apply to all connections to the master?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321330.1565991716000.9737.1576265460068%40Atlassian.JIRA.

Jira (PUP-10106) Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PUP-10106  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb   
 

  
 
 
 
 

 
 Thanks Josh Cooper.    I will have to do some experiments to see how other applications on my system behave with .ls.cbn vs ls.cbn including python and older versions of ruby.   For everything so far with the exception of puppet/ruby the ls.cbn has always matched. I appreciate you keeping this ticket open.  The behaviour is indeed odd between ENV[no_proxy] and puppet.conf no_proxy although the .domain seems to be pretty consistent across the various environments and applications.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.330903.157151114.2734.1571844600615%40Atlassian.JIRA.

Jira (PUP-10106) Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PUP-10106  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb   
 

  
 
 
 
 

 
 Further testing shows that the issue is in the handling of no_proxy for a domain match.  NO_PROXY="ls.cbn, localhost, puppet, 127.0.0.1" fails. NO_PROXY="glycon.ls.cbn, ls.cbn, localhost, puppet, 127.0.0.1" works.   As far as I know this is incorrect behaviour as ls.cbn should match *.ls.cbn   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.330903.157151114.8509.1571517780048%40Atlassian.JIRA.

Jira (PUP-10106) Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10106  
 
 
  Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.17  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/10/19 11:52 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 Puppet Version: 5.5.17 Puppet Server Version: 5.3.10 OS Name/Version: CentOS 7 Since the update to puppet agent 5.5.17 the puppetdb forge module is using the configured proxy server and ignoring the no_proxy setting when trying to validate the connection to puppetdb.  This worked properly on 5.5.16.  My environment proxy settings are: *http_proxy=http://ottinstall.ls.cbn:3128* *ftp_proxy=http://ottinstall.ls.cbn:3128* *https_proxy=http://ottinstall.ls.cbn:3128* no_proxy=ls.cbn, localhost, puppet, 127.0.0.1 My puppetdb server is: *https://glycon.ls.cbn:8081* Desired Behavior:  Respect the no_proxy value ls.cbn and not proxy connections to https://glycon.ls.cbn:8018 Actual Behavior: opening connection to ottinstall.ls.cbn:3128... opened <- "CONNECT glycon.ls.cbn:8081 HTTP/1.1\r\nHost: glycon.ls.cbn:8081\r\n\r\n" -> "HTTP/1.1 403 Forbidden\r\n" -> "Server: squid/3.5.20\r\n" -> "Mime-Version: 1.0\r\n" -> "Date: Sat, 19 Oct 2019 18:46:40 GMT\r\n" -> "Content-Type: text/html;charset=utf-8\r\n" -> "Content-Length: 3448\r\n" -> "X-Squid-Error: ERR_ACCESS_DENIED 0\r\n" -> "Vary: Accept-Language\r\n" -> "Content-Language: en\r\n" -> "X-Cache: MISS from ottinstall.ls.cbn\r\n" -> "X-Cache-Lookup: NONE from ottinstall.ls.cbn:80\r\n" -> "Via: 1.1 ottinstall.ls.cbn (squid/3.5.20)\r\n" -> "Co

Jira (PUP-9967) puppet plugin download doesn't respect the server variable in puppet.conf

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9967  
 
 
  puppet plugin download doesn't respect the server variable in puppet.conf   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/16 2:41 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 Puppet Version: 5.5.14 Puppet Server Version: 5.5.14 OS Name/Version: Debian 9 Desired Behavior:  puppet plugin download should use the [agent] values in puppet.conf for making http connections to the puppet master. Actual Behavior:  if --server is not on the command line and 'puppet' doesn't resolve the action fails  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93

Re: [Freesurfer] Mass-Univariate LME - help please!

[tom parker]

External Email - Use Caution

Dear Kersten,

Thank you so much for the quick reply! It was really helpful!!
I still have a couple of doubts regarding the visualization of the results
if you don't mind.

After running the last command *fs_write_Y(sided_pval,mri,'**spval_lh.mgh')*,
I tried to visualize the results with *tksurfer fsaverage lh inflated
-overlay spval_lh.mgh -fthresh 1.3* (1.3 was the pth value that came out
from lme_mass_FDR2) but there were no clusters on the surface.

If I run mri_surfcluster with spval_lh.mgh as input it seems there are 15
clusters, here is a sample of the first clusters that come out:
# ClusterNo  Max   VtxMax   Size(mm^2)  TalX   TalY   TalZNVtxs
WghtVtx
   11.000   8  22284.41 -2.28.6   -3.3  48988
46268.86
   21.000  140211   1542.44 -8.2  -16.7   58.6   3024
2633.36
   31.000   44065   1510.18-16.3  -71.7   -4.6   2078
1810.43
  (...)

Am I doing something wrong?

I also tried the spatiotemporal mass-univariate approach that you suggested
but matlab gets stuck with this command:
[lhRgs,lhRgMeans] = lme_mass_RgGrow(lhsphere,lhRe,lhTh0,lhcortex,2,95);

In the terminal it says:
"Starting region growing algorithm
Computing seeds ..."

Do you have any suggestions on how to solve this?

Thanks again for the help!


Hi Tom,

basically most of it looks OK to me, just a few remarks:

I assume that you deliberately chose the plain mass-univariate approach
instead of the potentially more powerful spatiotemporal mass-univariate
approach.

For the interpretation of the intercepts, if desired, it may be
advantageous to code sex as 0 and 1, and de-mean age. But that's not
strictly necessary.

I suspect that it's just a typo, so just for the sake of completeness: for
contrast estimation, I don't think that using CM.C1, CM.C2, etc. would
work, as the program expects a 'C' substructure. So instead, one would use
CM1.C, CM2.C etc for the different contrasts, if I am not mistaken.

About the mri_surfcluster command: if you want to do the FDR2 inference as
suggested by the LME tutorial, just use the 'pth' value as returned by the
lme_mass_FDR2 script for thresholding. I believe that you are mixing
different kinds of inference (traditional FDR, clusterwise) otherwise.

Finally, if you want to make corrected inferences for the whole cortex,
it's probably better to compute one (FDR2) threshold for both hemispheres
at once (see the very last part of the tutorial) instead of treating them
separately.

And regarding your specific questions:

The order is fine.

You can visualize the 'spval_lh.mgh' by first loading e.g. the
'lh.inflated' surface of the fsaverage template, and then adding
'spval_lh.mgh' as an overlay. Same with e.g. 'rh.inflated' for the
'spval_rh.mgh' file.

About the Monte Carlo correction for this type of analysis others may know
better, sorry.

Best regards,

Kersten

Missatge de tom parker  del dia dg., 21 de jul.
2019 a les 20:50:

> Dear all,
>
> I am currently running a Mass-Univariate LME analysis in Freesurfer. I
> have some doubts about the last steps and I was wondering whether someone
> could help me figure them out and also check what I have done so far (sorry
> for the long email).
>
> My study has 2 time points (baseline, follow-up), 3 groups (controls,
> patients without cognitive problems, patients with cognitive problems) and
> 2 covariates of no interest (age, sex).
> I am interested in looking at the interactions between group and time
> (mainly whether the 2 patient groups show more cortical thinning over time
> compared to controls).
>
> These are the commands I have ran so far through terminal or in matlab:
>
> 1)
> mris_preproc --qdec-long long.qdec.table.dat --target fsaverage --hemi lh
> --meas thickness --out lh.thickness.mgh
> mris_preproc --qdec-long long.qdec.table.dat --target fsaverage --hemi rh
> --meas thickness --out rh.thickness.mgh
>
> 2)
> mri_surf2surf --hemi lh --s fsaverage --sval lh.thickness.mgh --tval
> lh.thickness_sm15.mgh --fwhm-trg 15 --cortex  --noreshape
> mri_surf2surf --hemi rh --s fsaverage --sval rh.thickness.mgh --tval
> rh.thickness_sm15.mgh --fwhm-trg 15 --cortex  --noreshape
>
> 3)
> [Y,mri] = fs_read_Y('lh.thickness_sm15.mgh');
> [Y,mri] = fs_read_Y('rh.thickness_sm15.mgh');
>
> 4)
> lhsphere = fs_read_surf('fsaverage/surf/lh.sphere')
> rhsphere = fs_read_surf('fsaverage/surf/rh.sphere')
> lhcortex = fs_read_label('fsaverage/label/lh.cortex.label')
> rhcortex = fs_read_label('fsaverage/label/rh.cortex.label')
>
> 5) Create X matrix in matlab, here is a sample:
> intercept time  group2 group2*time group3
> group3*time   age  sex
> 1 0   0  0  0
>   0 41   1
> 1 2.42  0  0

[Freesurfer] Mass-Univariate LME - help please!

[tom parker]

External Email - Use Caution

Dear all,

I am currently running a Mass-Univariate LME analysis in Freesurfer. I have
some doubts about the last steps and I was wondering whether someone could
help me figure them out and also check what I have done so far (sorry for
the long email).

My study has 2 time points (baseline, follow-up), 3 groups (controls,
patients without cognitive problems, patients with cognitive problems) and
2 covariates of no interest (age, sex).
I am interested in looking at the interactions between group and time
(mainly whether the 2 patient groups show more cortical thinning over time
compared to controls).

These are the commands I have ran so far through terminal or in matlab:

1)
mris_preproc --qdec-long long.qdec.table.dat --target fsaverage --hemi lh
--meas thickness --out lh.thickness.mgh
mris_preproc --qdec-long long.qdec.table.dat --target fsaverage --hemi rh
--meas thickness --out rh.thickness.mgh

2)
mri_surf2surf --hemi lh --s fsaverage --sval lh.thickness.mgh --tval
lh.thickness_sm15.mgh --fwhm-trg 15 --cortex  --noreshape
mri_surf2surf --hemi rh --s fsaverage --sval rh.thickness.mgh --tval
rh.thickness_sm15.mgh --fwhm-trg 15 --cortex  --noreshape

3)
[Y,mri] = fs_read_Y('lh.thickness_sm15.mgh');
[Y,mri] = fs_read_Y('rh.thickness_sm15.mgh');

4)
lhsphere = fs_read_surf('fsaverage/surf/lh.sphere')
rhsphere = fs_read_surf('fsaverage/surf/rh.sphere')
lhcortex = fs_read_label('fsaverage/label/lh.cortex.label')
rhcortex = fs_read_label('fsaverage/label/rh.cortex.label')

5) Create X matrix in matlab, here is a sample:
intercept time  group2 group2*time group3 group3*time
age  sex
1 0   0  0  0
  0 41   1
1 2.42  0  0  0
  0 41   1
1 0   1  0  0
  0 53   1
1 2.51  2.5   0
  0 53   1
1 0   0  0  0
0 54   2
1 5.25  0  0  0
  0 54   2

5)
lhstats = lme_mass_fit_vw(X, [1], Y, ni, lhcortex);
rhstats = lme_mass_fit_vw(X, [1], Y, ni, rhcortex);

6)
I entered 3 contrasts separately to check the interaction group*time.
CM.C1 = [0 0 0 1 0 0 0 0]; this contrast will show if group 1 and 2 show a
different cortical thinning pattern over time
CM.C2 = [0 0 0 0 0 1 0 0]; this contrast will show if group 1 and 3 show a
different cortical thinning pattern over time
CM.C3 = [0 0 0 -1 0 1 0 0]; this contrast will show if group 2 and 3 show a
different cortical thinning pattern over time

7)
For each of the previous contrasts, i did the following:

F_lhstats = lme_mass_F(lhstats, CM);
F_rhstats = lme_mass_F(rhstats, CM);
fs_write_fstats(F_lhstats, mri,' sigL.mgh', 'sig');
fs_write_fstats(F_rhstats, mri,' sigR.mgh', 'sig');

mri.volsz(4) = 1
[detvtx,sided_pval,pth] =
lme_mass_FDR2(F_lhstats.pval,F_lhstats.sgn,lhcortex,0.05,0);
[detvtx,sided_pval,pth] =
lme_mass_FDR2(F_rhstats.pval,F_rhstats.sgn,rhcortex,0.05,0);

8)
fs_write_Y(sided_pval,mri,'spval_lh.mgh');
fs_write_Y(sided_pval,mri,'spval_rh.mgh');

mri_surfcluster --subject fsaverage --hemi lh --in spval_lh.mgh
--cwpvalthresh 0.05 --fdr 0.05 --sign pos --o lh_time_cluster  --sum
lh_time_cluster_sum
mri_surfcluster --subject fsaverage --hemi rh --in spval_rh.mgh
--cwpvalthresh 0.05 --fdr 0.05 --sign pos --o rh_time_cluster  --sum
rh_time_cluster_sum


*My questions are:*
- Is the order of the steps (1-8) correct?
- How can I visualize the significant FDR-corrected results?
- Is there any way I can apply a Monte Carlo correction using the generated
files?

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer

[Freesurfer] LME - Monte Carlo

[tom parker]

External Email - Use Caution

Dear FreeSurfers,

I was reading the wiki documents about how to run LME analyses in
FreeSurfer.
I found that one of the disadvantages is that, at the moment, it only
allows FDR corrections to be applied for multiple comparisons.

I have 2 patient groups that show cortical thinning compared to controls at
baseline when I correct with Monte Carlo but nothing survives with FDR.
Now, I would like to see if these cortical thinning patterns change over
time so I thought I should keep things consistent and use Monte Carlo for
the longitudinal analysis as well.

Is there any way of using Monte Carlo for LME? I read some suggestions in
emails that were sent 2 years ago but I was wondering if there are any
updates or if there is a guide with recommended steps?

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer

Jira (PDB-4332) Unknown variable: 'postgresql::server::encoding' when puppetdb::manage_dbserver: false

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PDB-4332  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unknown variable: 'postgresql::server::encoding' when puppetdb::manage_dbserver: false   
 

  
 
 
 
 

 
 I figured out what I was doing wrong.  It's not a bug if you RTFM and include the correct submodules for the servers that will be puppetdb::servers.  I had the entire puppetdb class loaded with manage_dbserver: false which doesn't work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PDB-4332) Unknown variable: 'postgresql::server::encoding' when puppetdb::manage_dbserver: false

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4332  
 
 
  Unknown variable: 'postgresql::server::encoding' when puppetdb::manage_dbserver: false   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/05 5:32 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 If you set: puppetdb::manage_dbserver: false (for example when the puppetdb is on different server) the postgresql::server class never gets called so the postgresql::server:: variables are not set.  With strict_variables= true this causes a fatal error that currently can't be worked around without editing either the postgreql module code or the puppetdb module code.   Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Unknown variable: 'postgresql::server::encoding'. (file: /etc/puppetlabs/code/environments/testing/modules/postgresql/manifests/server/db.pp, line: 8, column: 17) (file: /etc/puppetlabs/code/environments/testing/modules/puppetdb/manifests/database/postgresql.pp, line: 34)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9553) Exported resources are deleted if a node runs in different environment

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PUP-9553  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Exported resources are deleted if a node runs in different environment   
 

  
 
 
 
 

 
 I have several things I can do as a workaround  but I still don't think there should be collisions between environments for facts, and exported resources (or really anything).  Should the environments not be kept isolated from each other completely?  Everything else is now separate (per-environment hiera, per-environment modules) but we don't have a separation in puppetdb    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

[python-win32] Python code to drop file onto GUI, using pywin32

[Tom Parker]

Here's my issue:

Given a filename and a GUI, I need some Python code (on Windows) to drop the 
file onto the GUI.


The GUI (third-party) already accepts files via drag and drop (using OLE, but 
not WM_DROPFILE).


I was thinking pywin32 might be the right tool to use, but I don't know where to 
get started.



Thanks for any pointers you can provide.

- Tom
___
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32

Jira (PUP-9553) Exported resources are deleted if a node runs in different environment

[Tom Parker (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9553  
 
 
  Exported resources are deleted if a node runs in different environment   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/03/08 3:36 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 I am using puppet environments to apply very different collections of modules on the same node.  I have an environment to download (but not install) packages overnight and one that just runs password changes all triggered from my puppet master using mcollective.   The problem that I run into is that if I run puppet agent --environment download all of the exported resources from environment production are removed from pupetdb.  Then, any nodes that are collecting those resources will delete the associated configuration if puppet is run on the collector before a production run happens again on the exporter. I know that since pdb 2.0 puppet db is environment aware and I'm wondering if there is any way to no clobber my exported resources across environment runs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Re: [EVDL] Nissan Leaf key: $300! Yikes

[Tom Parker via EV]

On 14/10/18 10:12, EVDL Administrator via EV wrote:


On 14 Oct 2018 at 7:57, Tom Parker via EV wrote:


My 2016 Leaf has remote charge port opening -- the key fob has a 3rd
button, if you hold it down for about 2 seconds, the door opens.

Darned if I can see the point of this.  How hard could it be to open the
charging port door with your left hand, when you're standing there with the
charging connector in your right hand?  (Or vice versa.)

Maybe I'm missing something, but it seems like I'd be more trouble to get
the keys out and find the right button.  And then you have to hold it down
for a while.  Nuisance.


Like the other Tom, I don't use it very often but it is useful if you 
forget to open the charge port before getting out of the car and the 
keys are handy. If the keys are buried in a bag I find it 's easier to 
bring the bag to the car and open the door and press the button to open 
the charge port rather than find the keys and press the button on the key.



OTOH, inside release fuel filler doors make sense.  They help prevent fuel
theft.  But with an EV, who's gonna steal your electrons?


Agreed, there isn't a major need to lock the charge port, except perhaps 
to reduce the vandalism attack surface. Other cars do it better than the 
Leaf, for example the i3 charge port opens when you push it, but it 
still locks with the car which may or may not be necessary.


___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

Re: [EVDL] Nissan Leaf key: $300! Yikes

[Tom Parker via EV]

On 14/10/18 07:46, Cor van de Water via EV wrote:


I meant on the key fob. For the 2011 and 2012 there is only a dash handle
to open the door latch.
The 2013+ has an electric latch opener, so theoretically it can be opened
remotely, but the functions on the wireless interface are severely limited.
Cor.


My 2016 Leaf has remote charge port opening -- the key fob has a 3rd 
button, if you hold it down for about 2 seconds, the door opens.


___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

[Freesurfer] FsPalm patch

[Tom Parker]

External Email - Use Caution

Dear Freesurfer developers,

I am attempting to download the FsPalm patch 
(https://surfer.nmr.mgh.harvard.edu/fswiki/FsPalm 
) using: the link described 
in the wiki - 
ftp://surfer.nmr.mgh.harvard.edu/pub/dist/freesurfer/6.0.0-patch/PALM 


However, there appears to be no directory at that location. 

Please can you inform me how to install the FsPalm patch?

Many thanks___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

[Openvas-discuss] OpenVas Command Line Scan Plugin Options

[Tom Parker]

Hi all,

is there a way from the command line to select a sub list of plugins to
scan a target with?

I know I can select from the GUI like shown here:
http://www.openvas.org/compendium/scan-options-plugins.html

But I don't know how to do it from the command line so I can try automate
it.

Is it possible?

I didn't see it from
http://www.openvas.org/src-doc/openvas-cli/index.html
or from
http://docs.greenbone.net/API/OMP/omp-7.0.html

I may be missing the obvious.

I don't want to fire the kitchen sink at the target. If it is a Windows box
then I don't want to fire Linux plugins at it. This will also help cut down
the scan time.

Any help to point me in the correct direction is welcome.
Thanks
Tom
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Soekris] [SPAM] Re: yet another dead 6501

[Tom Parker]

PC Engines apu2 is doing a nice job replacing soekris for us...

Tom


On 09/05/2017 02:19 PM, Michael Stone wrote:
> On Tue, Sep 05, 2017 at 06:02:29PM +, Wesley PA4WDH wrote:
>> Does anyone have an advice for an alternative ? I've seen some
>> alternatives on
>> the list but so far they didn't meet my requirements.
>> I'm using it as a home server so 2x sata, 3x GB ethernet ports are
>> minimum. The
>> Atom CPU is fine (faster is allowed of course :-) ), more than 2 GB
>> memory
>> would be nice since i'm hitting the limit there. Low power,
>> preferably fanless,
>> is important for me to keep it running 24x7.
>
> For that application, start with an apollo lake board, something like
> ASUS PRIME J3355I-C, add dual or quad port nic. It'll run absolute
> rings around a net6501.
> ___
> Soekris-tech mailing list
> Soekris-tech@lists.soekris.com
> http://lists.soekris.com/mailman/listinfo/soekris-tech

___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech

Re: [EVDL] Leaf battery pack overheating due to depth of discharge.

[Tom Parker via EV]

Lawrence, 

Is this a 30kWh leaf? 

We've seen that they will accept charge much faster than the 24kWh leaves, 
maintaining 50kW for most of the charge to 80%. This will put a lot more I^2R 
heating into the battery than charging slower. The 24kWh cars average under 
25kW for a charge to 80%.

How hot is 5 and 9 bars?

On Jun 22, 2017 9:45 AM, Lawrence Rhodes via EV wrote: > > After driving 135 
miles down to 13% charging back up to 85% caused the pack to go from 6 bars to 
9.  Today the plan is to try to stay above 50%.  So far so good.  The pack 
hasn't exceeded 6 bars. This is in hotter temperature than yesterday.  So 
ambient temperature doesn't seem a big factor. It is large depth of discharge 
then a fast charge.  Now in Santa Barbara.  Going to Rancho Jarupa near 
Riverside.  Lawrence Rhodes > > Sent from my MetroPCS 4G LTE Android device > 
On Jun 21, 2017 1:05 PM, via EV wrote: > > > > Send EV mailing list submissions 
to > > ev@lists.evdl.org > > > > To subscribe or unsubscribe via the World Wide 
Web, visit > > http://lists.evdl.org/listinfo.cgi/ev-evdl.org > > or, via 
email, send a message with subject or body 'help' to > > 
ev-requ...@lists.evdl.org > > > > You can reach the person managing the list at 
> > ev-ow...@lists.evdl.org > > > > When replying, please edit your Subject 
line so it is more specific > > than "Re: Contents of EV digest..." > > > > > > 
Also, please be careful not to append the entire digest to your reply. Many 
mail systems do this by default. Trim or delete the digest text from the bottom 
of your message, and quote only the parts to which you're replying. > > > > > > 
> > Today's Topics: > > > >    1. EVLN: EV-newswire posts for 20170621 
(brucedp5 via EV) > > > > > > 
-- > > > > 
Message: 1 > > Date: Wed, 21 Jun 2017 05:52:57 -0700 (PDT) > > From: brucedp5 
via EV > > To: ev@lists.evdl.org > > Subject: [EVDL] EVLN: EV-newswire posts 
for 20170621 > > Message-ID: <1498049577620-4687111.p...@n4.nabble.com> > > 
Content-Type: text/plain; charset=UTF-8 > > > > > > > > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVLN-How-Lotus-Evora-EV-performs-flat-out-on-the-track-r-125mi-ts-172mph-v-td4687110.html
 > > EVLN: How Lotus Evora EV performs flat-out on the track r:125mi ts:172mph 
> > (v) > > Watch a Lotus Evora With a Tesla's Electric Motor Set Silent Lap 
Times ... > > All of that power and instant electric torque make for a 
seriously quick > > track car, as the guys from Speed Academy find out ... > > 
> > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVLN-1-3k-Boosted-e-skateboards-sell-past-their-voluntary-pack-recall-r-7mi-ts-22mph-td4687109.html
 > > EVLN: $1.3k Boosted e-skateboards sell past their voluntary pack recall > 
> r:7mi ts:22mph > > Boosted electric skateboard maker seeks a reboot > > ... 
(redesigned packs keep water out and from short-circuiting their bms, > > 
preventing overheating) ... > > > > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVLN-Lyft-s-murky-plan-gt-an-auton-Bolt-EV-fleet-charged-w-renewable-electricity-td4687108.html
 > > EVLN: Lyft's murky plan> an auton (Bolt) EV fleet charged w/ renewable > > 
electricity > > Lyft just unveiled an aggressive plan to reduce its carbon 
emissions ... > > The ride-hailing service said all of its electric, autonomous 
vehicles will > > only use electricity generated by clean energy sources, 
starting ...  in > > Boston later this year ... > > > > + > > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/A-2nd-L2-WSU-Pullman-WA-gt-not-the-dual-L3-DC-EVSE-that-is-needed-td4687106.html
 > > A 2nd L2 @WSU Pullman-WA> (not the dual L3 DC EVSE that is needed) > > 
Electric car charging station to be installed in Pullman > > Palouse already 
has one electric car charging station but this fall a 2nd > > one is going in 
... 'We do know there are more EVs being purchased every > > day' ... > > > > 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVangel-Lough-is-holding-court-like-xXx-in-Issaquah-WA-td4687107.html
 > > EVangel Lough is holding court like xXx in Issaquah-WA > > Batteries 
included! Seattle Electric Vehicle Association leads the charge > > On a sunny 
day in May, Steven Lough is holding court among the gathered ? > > > > > > > > 
> > http://evdl.org/evln/ > > For all EVLN EV-newswire posts > > > > > > 
{brucedp.neocities.org} > > > > -- > > View this message in context: 
http://electric-vehicle-discussion-list.413529.n4.nabble.com/EVLN-EV-newswire-posts-for-20170621-tp4687111.html
 > > Sent from the Electric Vehicle Discussion List mailing list archive at 
Nabble.com. > > > > > > -- > > > > Subject: Digest 
Footer > > > > ___ > > 
EV@lists.evdl.org > > For general EVDL support, see http://evdl.org/help/ > > 
http://lists.evdl.org/listinfo.cgi/ev-evdl.org > > > > > > 

[Freesurfer] web image preprocessing

[tom parker]

Dear Freesurfer experts,

Does anyone know if there is a web portal where i can upload my T1 images
to preprocess them with freesurfer and download the preprocessed files?

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Re: [Soekris] They finally suspended operations

[Tom Parker]

Do you have a rack mount case that you like? 

I have been a Soekris customer for 12 years and am just now shopping for
a replacement for my rack mounted net6501s.  The APU2 looks great but I
will need to find a good 19" rack mount case for it as well.

Thanks for any info you have

Tom Parker


On 04/26/2017 06:48 PM, Dan Shechter wrote:
> I have replaced my failing 6501 with PC Engine APU2. Very happy.
>
> Funny how the rack mounting kits cost a lot, relative to the price of
> the APU its self.
>
> On Wed, Apr 26, 2017 at 12:58 PM, Nick Gyurov <ngyu...@gmail.com
> <mailto:ngyu...@gmail.com>> wrote:
>
> Bryan, I'm switching to PC Engines.
>
> On Thu, 27 Apr 2017 at 3:56 AM BKW Soekris
> <bkw+1481036...@netwtc.net <mailto:bkw%2b1481036...@netwtc.net>>
> wrote:
>
> On 2017-04-26 10:11, Scott Gustafson wrote:
> > From the home page announcement: http://soekris.com/
>
> Well, at least they've made it clear.  Now I can finally give
> up hope on
> a new product.  And I can also give up hope for some official
> contribution to the mailing list regarding the net6501
> problems.  And
> now I can officially start planning for the eventual
> replacement of my
> net6501, knowing that it will be REQUIRED to be a non-Soekris
> option.
> Now I need to find a rack mount server that can run completely
> fanless.
> Anybody have any suggestions?
>
> -Bryan
> ___
> Soekris-tech mailing list
> Soekris-tech@lists.soekris.com
> <mailto:Soekris-tech@lists.soekris.com>
> http://lists.soekris.com/mailman/listinfo/soekris-tech
> <http://lists.soekris.com/mailman/listinfo/soekris-tech>
>
> -- 
> Regards,
> Nick
>
> ___
> Soekris-tech mailing list
> Soekris-tech@lists.soekris.com <mailto:Soekris-tech@lists.soekris.com>
> http://lists.soekris.com/mailman/listinfo/soekris-tech
> <http://lists.soekris.com/mailman/listinfo/soekris-tech>
>
>
>
>
> ___
> Soekris-tech mailing list
> Soekris-tech@lists.soekris.com
> http://lists.soekris.com/mailman/listinfo/soekris-tech

___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech

Re: [Freesurfer] correlation coefficient R

[tom parker]

Thank you so much Doug!

It worked! I was just wondering which value I should report as the
correlation coefficient of my analysis.

This is the output I got:

# ColHeaders  Index SegId NVoxels Volume_mm3 StructName Mean StdDev Min Max
Range
  1  -4 2037320373.0  Seg-004-0.1596 0.0468-0.3134
-0.1017 0.2117

Should I report the mean (-0.1596) or the min (-0.3134)?

Thanks again

Try something like

mri_segstats --i pcc.mgh --seg cluster.ocn.mgh --excludeid 0 --sum
cluster.pcc.dat



2017-04-08 1:35 GMT+01:00 tom parker <tomparker...@gmail.com>:

> Hi Doug,
>
> Thank you for your answer!
>
> It would be great if you could send me some instructions.
>
> Thanks for the help!
>
> Douglas N Greve
> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+N+Greve%22>
>  Thu,
> 06 Apr 2017 13:32:07 -0700
> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170406>
>
> I guess you could average it over space (eg, over a cluster). Let me
> know if you want instructions. Otherwise, I'm not sure what to say.
>
>
>
> 2017-04-04 11:49 GMT+01:00 tom parker <tomparker...@gmail.com>:
>
>> Hi Doug,
>>
>> Thanks! I realize now I didn't explain myself properly.
>>
>> I need one single R value for the correlation analysis I made, similarly to 
>> when I correlate two variables with Pearson's R in a statistical package.
>>
>> I have a referee asking me to put it on a table with the freesurfer results. 
>> Is there a way to get a single average R value from the pcc.mgh file?
>>
>> Thank you so much!
>>
>>
>> Douglas Greve
>> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+Greve%22>
>>  Mon,
>> 03 Apr 2017 18:46:46 -0700
>> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170403>
>> Each vertex is a correlation value.
>>
>>
>>
>> 2017-04-04 1:09 GMT+01:00 tom parker <tomparker...@gmail.com>:
>>
>>> Thanks Doug!
>>>
>>> I have version 6 and got a pcc.mgh file.
>>>
>>> How can I get a correlation R value from this file?
>>>
>>> Thanks again
>>>
>>> Douglas N Greve
>>> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+N+Greve%22>
>>>  Mon,
>>> 03 Apr 2017 09:41:41 -0700
>>> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170403>
>>>
>>> if you are using version 6, then it should have produced a file called
>>> pcc.mgh. This the partial pearson correlation coef.
>>>
>>>
>>>
>>> 2017-04-03 15:40 GMT+01:00 tom parker <tomparker...@gmail.com>:
>>>
>>>> Dear Freesurfers,
>>>>
>>>> I made some correlations between cortical thickness and age in qdec.
>>>>
>>>> Is it possible to get the correlation coefficient value of this
>>>> analysis?
>>>>
>>>> I just need to put it in a table with the significant results.
>>>>
>>>> Thank you so much!
>>>>
>>>
>>>
>>
>
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Re: [Freesurfer] correlation coefficient R

[tom parker]

Hi Doug,

Thank you for your answer!

It would be great if you could send me some instructions.

Thanks for the help!

Douglas N Greve
<http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+N+Greve%22>
Thu,
06 Apr 2017 13:32:07 -0700
<http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170406>

I guess you could average it over space (eg, over a cluster). Let me
know if you want instructions. Otherwise, I'm not sure what to say.



2017-04-04 11:49 GMT+01:00 tom parker <tomparker...@gmail.com>:

> Hi Doug,
>
> Thanks! I realize now I didn't explain myself properly.
>
> I need one single R value for the correlation analysis I made, similarly to 
> when I correlate two variables with Pearson's R in a statistical package.
>
> I have a referee asking me to put it on a table with the freesurfer results. 
> Is there a way to get a single average R value from the pcc.mgh file?
>
> Thank you so much!
>
>
> Douglas Greve
> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+Greve%22>
>  Mon,
> 03 Apr 2017 18:46:46 -0700
> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170403>
> Each vertex is a correlation value.
>
>
>
> 2017-04-04 1:09 GMT+01:00 tom parker <tomparker...@gmail.com>:
>
>> Thanks Doug!
>>
>> I have version 6 and got a pcc.mgh file.
>>
>> How can I get a correlation R value from this file?
>>
>> Thanks again
>>
>> Douglas N Greve
>> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+N+Greve%22>
>>  Mon,
>> 03 Apr 2017 09:41:41 -0700
>> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170403>
>>
>> if you are using version 6, then it should have produced a file called
>> pcc.mgh. This the partial pearson correlation coef.
>>
>>
>>
>> 2017-04-03 15:40 GMT+01:00 tom parker <tomparker...@gmail.com>:
>>
>>> Dear Freesurfers,
>>>
>>> I made some correlations between cortical thickness and age in qdec.
>>>
>>> Is it possible to get the correlation coefficient value of this analysis?
>>>
>>> I just need to put it in a table with the significant results.
>>>
>>> Thank you so much!
>>>
>>
>>
>
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Re: [Freesurfer] correlation coefficient R

[tom parker]

Hi Doug,

Thanks! I realize now I didn't explain myself properly.

I need one single R value for the correlation analysis I made,
similarly to when I correlate two variables with Pearson's R in a
statistical package.

I have a referee asking me to put it on a table with the freesurfer
results. Is there a way to get a single average R value from the
pcc.mgh file?

Thank you so much!


Douglas Greve
<http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+Greve%22>
Mon,
03 Apr 2017 18:46:46 -0700
<http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170403>
Each vertex is a correlation value.



2017-04-04 1:09 GMT+01:00 tom parker <tomparker...@gmail.com>:

> Thanks Doug!
>
> I have version 6 and got a pcc.mgh file.
>
> How can I get a correlation R value from this file?
>
> Thanks again
>
> Douglas N Greve
> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+N+Greve%22>
>  Mon,
> 03 Apr 2017 09:41:41 -0700
> <http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170403>
>
> if you are using version 6, then it should have produced a file called
> pcc.mgh. This the partial pearson correlation coef.
>
>
>
> 2017-04-03 15:40 GMT+01:00 tom parker <tomparker...@gmail.com>:
>
>> Dear Freesurfers,
>>
>> I made some correlations between cortical thickness and age in qdec.
>>
>> Is it possible to get the correlation coefficient value of this analysis?
>>
>> I just need to put it in a table with the significant results.
>>
>> Thank you so much!
>>
>
>
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Re: [Freesurfer] correlation coefficient R

[tom parker]

Thanks Doug!

I have version 6 and got a pcc.mgh file.

How can I get a correlation R value from this file?

Thanks again

Douglas N Greve
<http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=from:%22Douglas+N+Greve%22>
Mon,
03 Apr 2017 09:41:41 -0700
<http://www.mail-archive.com/search?l=freesurfer@nmr.mgh.harvard.edu=date:20170403>

if you are using version 6, then it should have produced a file called
pcc.mgh. This the partial pearson correlation coef.



2017-04-03 15:40 GMT+01:00 tom parker <tomparker...@gmail.com>:

> Dear Freesurfers,
>
> I made some correlations between cortical thickness and age in qdec.
>
> Is it possible to get the correlation coefficient value of this analysis?
>
> I just need to put it in a table with the significant results.
>
> Thank you so much!
>
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

[Freesurfer] correlation coefficient R

[tom parker]

Dear Freesurfers,

I made some correlations between cortical thickness and age in qdec.

Is it possible to get the correlation coefficient value of this analysis?

I just need to put it in a table with the significant results.

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Re: [EVDL] Nissan Leaf CAN Bus Man in the Middle

[Tom Parker via EV]

On 14/03/17 07:07, Bill Dube via EV wrote:


Outstanding work Tom.
Not many folks have the ability (or patience) to tackle this job, but 
a lot of us will use this. Makes the Leaf battery module so much more 
useful as a functional unit.


To be clear my contribution so far is only

* writing a simple tool to explore how the system behaves when messages 
are modified
* writing a configuration file for kayak and a wireshark dissector to 
decode some of the can bus messages
* finding the car mostly works when the battery can send messages to it 
and it cannot send messages to the battery
* discovering which signals the leaf instrument cluster is using for the 
capacity, temperature and state of charge displays


The work to decipher enough of the Leaf BMS to use it outside the car 
was done by others.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

Re: [EVDL] Nissan Leaf CAN Bus Man in the Middle

[Tom Parker via EV]

On 13/03/17 04:39, Jay Summet via EV wrote:
The next time I use a Leaf pack on an EV I want to be able to just 
plug it in "unmodified" and make use of the existing BMS and CAN 
interface, it's good to know that people are making good progress on 
the "auto" side of this.


The BMS is already understood mostly enough to use in a conversion. 
While it evidently logs an error when the car is missing, it's quite 
happy to tell you the battery current, voltage, remaining capacity and 
cell voltage levels. There are some more signals that would be a good 
idea to follow but I don't know if anyone has identified them:


* High voltage discharge permit signal
* System main relay ON permit signal
* Insulation resistance signal
* Li-ion battery dischargeable power signal

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

[EVDL] Nissan Leaf CAN Bus Man in the Middle

[Tom Parker via EV]

I wrote a man in the middle for the leaf battery communication. It uses 
can4python and Kayak's kcd format to describe the signals. It probably 
only works on Linux. Source code is here 
https://carrott.org/git/leaf-can-utils.git


It decodes all the messages received on one interface (from the battery) 
into signals, lets me change their values, and then re-encodes them back 
into the can bus format, recalculates the new checksum when necessary 
and sends them out the other interface (to the car).


Yesterday I spent some time testing it on a Gen 1 leaf at 
https://bluecars.nz


We cut the can bus wires inside the battery box, just after they go 
through the water proof connector to the outside and connected about 1 
metre of thin figure 8 wire to each side of the cut. This let us access 
the bus on the car and the bus on the battery while the battery was 
plugged in under the car. It's possible to get enough slack in the 
internal battery loom to feed the connector all the way through the 
machined hole and make room for some extra wires to pass through.


With the two pairs connected together, the car behaved normally, going 
into ready and spinning the wheels.


The BMS module terminates the bus so we connected a termination resistor 
to the car side of the cut and used termination on the CAN interface 
talking to the battery. We plugged the other end of the man in the 
middle to the OBD2 port and didn't use termination.


The MitM just worked.

The car is very tolerant of errors on the CAN bus. You can stop the 
battery messages and it goes into turtle mode and all the battery info 
disappears off the instrument cluster. When you re-start the battery 
messages it goes back to normal mode and the battery info reappears. 
Start-up is quite critical, if you don't let the battery send it's start 
up messages the car doesn't go into ready mode. The car never shut down 
or went into a permanent turtle mode while I was messing with data on 
the bus -- it always went back to normal mode if I restored the 
unmodified messages flow from the BMS. I modified the data in nearly 
every field to see what would happen.


The car will go into ready and turn the wheels even when it cannot send 
messages to the battery. This means the startup sequence doesn't involve 
a car to battery handshake, even if the car is expecting some startup 
messages from the battery within a time window. The "check engine" light 
comes on and it does record some DTCs:
* P3180 (EVC-249) VCM detects an error signal that is received from LBC 
via CAN communication for 0.02 seconds or more.
* P3183 (EVC-250) After a lapse of 0.3 seconds from M/C RELAY ON, the 
following state remains for 2.8 seconds or more: LBC's calculation 
result to the VCM-set example question is incorrect.


My MitM only works in one direction (from the battery to the car) and it 
turns out my CAN bus setup wouldn't let two programs play together, so 
when I started a CAN repeater (candump -b) to copy data from the car to 
the battery I got corrupted frames and no buffer space errors. I'm going 
to make the MitM work in both directions to resolve this.


If you play a different car's battery messages into this car, it does 
not go into ready. I didn't spend much time on this and I didn't write 
code to start the BMS messages at the right time, I just started playing 
the recording of a running BMS and switched the car on. One experiment 
that I should have tried was to start the car with it's real battery and 
then switch to messages recorded from a different car. There are some 
new DTCs when you try to start a the car while playing messages recorded 
from another car including


* P3102 Li-ion Battery ID Registration must be performed if the Li-ion 
battery controller or VCM is replaced.


The next experiment is to swap in a BMS module from another car.

I figured out some more of the BMS protocol by messing with the data and 
seeing how the car reacted.


The Fuel Gauge display on the instrument cluster is powered by the GIDs 
signal (the first 10 bits of 0x5BC), not the state of charge signal 
(first 10 bits of 0x55B). I guess it knows how many GIDS is "full" 
because the battery will have fewer gids and still read full as it ages.


0x5BC bits 36-39 (ie the high nibble of the 5th byte) somehow effects 
the Fuel Gauge, lower numbers mean more bars, all other things being the 
same. Maybe this is used to calculate how many GIDs each bar is worth? I 
haven't explored this.


The battery capacity gauge (the bars outside the fuel gauge) is 
controlled by a muxed field, when 0x5BC bits 32-35 (ie the low nibble of 
the 5th byte) is 0x3, 0x5BC bits 16-19 (ie the low nibble of the 3rd 
byte) contains the capacity bars. I haven't yet used the mux field 
support in the kcd format to express this -- can4python doesn't support 
it so I had to hand code it. The cluster does not remember the capacity 
-- changing this value directly manipulates the number of bars 
displayed, the 

Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

[Tom Parker via EV]

On 27/01/17 13:36, Collin Kidder via EV wrote:


Any logs anyone could send me from a Leaf would be great. But, I might
be on to something. Byte 4 (the fifth byte if you start counting at 0)
is always a constant value for a given car. It stays the same across
all 0x5C0 frames, it stays the same whether driving or charging. Every
vehicle I've got a capture from has a unique byte here that never
changes with any captures from that car no matter what else the car is
doing. Pretty much all of the rest of the bytes change as you charge
or discharge. I think what might be happening is that this byte is a
sort of identifier that the rest of the system uses to see whether the
pack is the same one it last knew. 256 unique values might not seem
like a lot but that means that your odds of getting a pack with the
same byte as your old pack is 1/256 or less than 0.5% - not so likely.
One way to test this would be to set up a man in the middle
configuration and then change that byte and see if it makes the car
puke. Or, take a car with a replaced pack and try to change the
reported byte from the new LBC to the reported byte from the old LBC
and see if the car then wants to work better.


I don't see a constant here. With the exception of one capture, each 
capture from my car has a single value in byte 4 but it is decreasing 
(except once when it went down and up) slowly over the last year or so 
for which I have data:


Each line represents one capture and has the following format
byte_number value_in_hex:count_in_decimal

4 84:7
4 84:12
4 84:14
4 84:80
4 84:252
4 84:128
4 84:10
4 84:14
4 82:1607
4 82:40
4 82:22
4 82:91
4 80:40
4 80:4332
4 7e:14
4 7e:53
4 7c:531 fe:1
4 7c:36
4 7c:19
4 7c:6
4 7a:72
4 7c:8
4 7c:22
4 7c:8
4 7c:28
4 7c:30
4 7c:1
4 7a:40
4 7a:165
4 7a:38
4 7a:54

The exception was captured during remote climate control, and I have 531 
frames with 7c with one frame containing fe about 2/3 of the way through 
the capture:


1572272017-01-07 08:38:05.031301LBC 0x5c016STD: 
0x05c0   c0 72 74 00 7c d4 00 00
1575332017-01-07 08:38:05.531215LBC 0x5c016STD: 
0x05c0   00 fe fe 00 fe fc 00 00
1572272017-01-07 08:38:05.031301LBC 0x5c016STD: 
0x05c0   c0 72 74 00 7c d4 00 00

I have 2 short captures made on the same day from a Gen 2 and there it 
alternates between two values:


4 ba:5 c0:2
4 ba:8 c0:4
___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

[Tom Parker via EV]

On 27/01/17 07:29, Cor van de Water via EV wrote:

Also, the LBC validation happens without disconnecting the aux battery.
I know for sure as I never disconnect the 12V battery and when I swapped
my pack for a complete replacement pack from Washington State, the
yellow light on the dash came on and my Leaf was in Limp mode while I
only disconnected the (non-energized, due to the contactors in the pack)
HV lines and the control bus.
Just wheeling the original pack back under my Leaf and swapping the
connectors removed the Limp mode, so I know for a fact that the Leaf
validates the battery upon pressing the power button while the aux
battery is connected continuously, so it seems that you were looking at
the wrong thing.
Probably a trace of the EV bus as soon as the power button is depressed
(when a *lot* of communication is happening) will tell the story.
You may start the trace as soon as the brake is pressed.


Thank you for this information Cor!

I have many captures of my car's startup on the EV Bus and unless my 
hardware misses the important frames, I don't see anything special at 
startup. 0x603 is sent once, is the first frame sent and always with 
payload 00. A number of frames are sent with lots of bits set which 
later contain valid data - for example the first couple of frames from 
the LBC:


1 2017-01-26 21:47:24.907267CAN16STD: 
0x0603   00
8 2017-01-26 21:47:24.993307VCM Info   16STD: 
0x01f2   08 64 00 00 00 01 01 06
652017-01-26 21:47:25.139218LBC Battery V/A16STD: 
0x01db   7f e0 ff c6 00 00 00 de
662017-01-26 21:47:25.140191LBC 0x1dc  16STD: 
0x01dc   ff ff ff ff 1f ff fc 6b

And I can see the VCM go through it's startup sequence (in 0x1f2 byte 
5). However all the frames other than 0x603 are sent more than once per 
second.


I'll capture startup from some more cars, identify which bytes are 
different and use a man in the middle to selectively tamper with those 
bytes and see what causes the car to reject the battery. Hopefully there 
aren't too many differences! Carl at https://bluecars.nz/ has a leaf 
system on the bench, so establishing the man in the middle won't be too 
hard.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

[Tom Parker via EV]

On 27/01/17 07:06, Cor van de Water via EV wrote:

Did you grab communication from *both* CAN buses?
The Leaf's Battery Controller (LBC) communicates via the VCM which is
connected to both the EV CAN bus and the normal CAN bus, to the
Combination Meter, which is supposed to hold the key that is paired to
the LBC. So some communication spills over from one CAN bus to the
other. Both are available on the OBD (Data Link) connector. Without a
dump from both, it is hard to tell what would disable/enable the Leaf
since only half the communication can be seen.
I'm only capturing the EV CAN bus -- I'm interested in how the BMS is 
authenticated by the rest of the car, so that transaction must pass 
through the EV bus to get to the BMS. Unless it isn't done on the CAN 
bus at all, but that seems unlikely?

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

[Tom Parker via EV]

On 24/01/17 23:25, Tom Parker via EV wrote:

On my car, there is only one frame that isn't repeated continuously 
after startup (0x603 is sent once, with a single byte payload which is 
00 in my captures).


I'll try disconnecting the 12v battery tomorrow and see if anything 
different happens at when it's connected, or during the first startup.


I removed the 12V battery and there was no activity on the EV CAN bus 
when it was reconnected. There were also no new messages when I turned 
the car on, and other than 0x603, they all streamed continuously. I 
waited quite a long time (10 minutes maybe) before reconnecting the battery.


I guess this means the BMS authentication is in the repeating messages, 
or it is triggered by some other event than disconnecting the 12V 
battery, or you can have the 12V battery disconnected for a very long 
time without breaking the BMS authentication.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

[Tom Parker via EV]

On 24/01/17 04:07, Ed Blackmond via EV wrote:


I am interested in learning how to reset the capacity gauge. Cor replaced the 
battery cells in my 2011 Leaf about 2000 miles ago. LeafSpy now reports about 
62.5AH, but the capacity gauge on the dash hasn't budged. I get over 265 GIDs 
on a full charge and the car has range equal to what it was when new.  The 
state of charge gauge works fine and the distance to empty number is as 
inaccurate as ever.




When you say the capacity gauge, do you mean the outer column of battery 
bars? IE you car still has the number of bars remaining that your old 
battery had before it was replaced?


You kept the original BMS, right? Do you know if the BMS is reporting 
healthy data and the instrument cluster is ignoring it, or if the BMS is 
reporting the old data? Obviously the BMS is reporting Ah & GIDs values 
that match the battery, but perhaps those values don't drive the 
instrument display? What about the SOH?

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

Re: [EVDL] Anyone interested in 2015 Leaf drivetrain or interior/exterior/suspension parts?

[Tom Parker via EV]

On 23/01/17 10:52, Cor van de Water via EV wrote:

I sent you a separate email with an idea to avoid a fake Leaf pack and still 
keep the BMS happy and report SoC.


Is anyone trying to reverse engineer the handshake between the Leaf BMS 
and the rest of the car?


As I understand it, the Leaf BMS is quite happy to work on it's own but 
some other part car authenticates the BMS and is not happy if the BMS is 
swapped. A friend tried swapping the whole battery including the BMS he 
says the car was not happy, it worked but only in Turtle mode, 
regardless of state of charge.


Has anyone identified the CAN bus messages that contain the 
authentication handshake? I've been collecting information at 
https://carrott.org/emini/Nissan_Leaf_OVMS#Leaf_Can_Bus but I haven't 
seen information about the BMS authentication.


Could you put a man in the middle between the BMS and the rest of the 
car which allows the original BMS board to authenticate, but replaces 
all the battery status messages with "everything is fine"? Obviously the 
man in the middle would need to talk to the BMS on the new battery 
(either another Nissan or a whole new BMS or whatever) and tell the car 
everything is not fine if the new battery is in trouble.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

Re: [EVDL] Recent Model EV Conversion - CAN and accesories to work..

[Tom Parker via EV]

On 04/01/17 04:50, Collin Kidder via EV wrote:


I don't think that generic sales pitches are acceptable on this list
but since it is topically relevant I'd like to quickly mention that I
am involved in the creation of many pieces of hardware and software to
aid in these things.

CANDue: http://store.evtv.me/proddetail.php?prod=EVTVDue2=23
SavvyCAN: http://www.savvycan.com


Along these lines, the audio from 
https://xi.hope.net/schedule.html#-2016-car-hacking-tools- is worth a 
listen and gives links to http://opengarages.org/index.php/Tools (which 
includes Colin's SavvyCAN) and other resources.


More advanced, https://media.ccc.de/v/33c3-8131-dieselgate_a_year_later 
shows how to glitch a VW ECU to bypass the flash read-protect and 
retrieve a firmware image (also the technical Dieselgate information is 
interesting but off topic). Going from a firmware image to an emulated 
ECU is probably the hard way to make a modern car work without it's ICE.


___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

[Pkg-javascript-devel] Bug#850082: Fix recursive dependency on node-yamlish/marked

[Tom Parker]

Package: nodejs
Version: 6.9.2~dfsg-1

At the moment, there's a recursive dependency between nodejs and
node-yamlish/marked, which means that various architectures that don't have
a current nodejs aren't able to make a new one (causing BD-Uninstallable as
per https://buildd.debian.org/status/package.php?p=nodejs). Luckily
apparently there's a way around this sort of thing using build profiles (
https://wiki.debian.org/BuildProfileSpec), and I've attached a patch
(against the master-6.x branch in the source repo, but might well build
against lower versioned ones with small changes).

Thanks,

Tom Parker


nodejs-build-profiles.patch
Description: Binary data
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Bug#850082: Fix recursive dependency on node-yamlish/marked

[Tom Parker]

Package: nodejs
Version: 6.9.2~dfsg-1

At the moment, there's a recursive dependency between nodejs and
node-yamlish/marked, which means that various architectures that don't have
a current nodejs aren't able to make a new one (causing BD-Uninstallable as
per https://buildd.debian.org/status/package.php?p=nodejs). Luckily
apparently there's a way around this sort of thing using build profiles (
https://wiki.debian.org/BuildProfileSpec), and I've attached a patch
(against the master-6.x branch in the source repo, but might well build
against lower versioned ones with small changes).

Thanks,

Tom Parker


nodejs-build-profiles.patch
Description: Binary data

[Freesurfer] question white matter analysis

[tom parker]

Dear FreeSurfers,

Thanks for the previous reply on what the white.K and white.H are.
I would like to make an analysis in Qdec using one of these measures.
However, I didn't find much information online so I would like to ask you 3
final things:

1. Which of the two measures (mean, gaussian) is more suitable for an
analysis of white matter volume/curvature?

2. How can I apply some smoothing to the white.K and white.H files to be
able to make an analysis in Qdec?

3. Should I include ITV as a covariate in these analyses?

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

[Freesurfer] question white matter

[tom parker]

Dear Freesurfers,

Could anyone tell me what the white.H and white.K measures in Qdec are?

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Re: [Soekris] mSATA SSDs for a net 6501

[Tom Parker]

I'm using Adata 64GB cards with no problems at all running CentOS
(http://www.adata.com/en/ssd/specification/181)

Tom


On 11/25/2016 07:24 PM, Jeff Simmons wrote:
> I've got a couple of net6501's running OpenBSD 6.0, and I'd like to
> replace the mSATA SSDs with something larger. The SSDs I have were
> purchased directly from Soekris, and looking around the market there's
> a lot of mSATA stuff that I'm not sure would work. Any limits as to
> size, SATA version, etc. that I should watch out for? Any specific
> recommendations? If I could get 60G I'd be a very happy camper.
>
> Any assistance greatly appreciated.
>

___
Soekris-tech mailing list
Soekris-tech@lists.soekris.com
http://lists.soekris.com/mailman/listinfo/soekris-tech

[Freesurfer] Error long_mris_slopes

[tom parker]

Dear FreeSurfers,

I've been trying to run a longitudinal cortical thickness analysis in
FreeSurfer but unfortunately, so far, it has not worked.

After preprocessing the data following the instructions from the tutorial,
I tried running:
*long_mris_slopes --qdec /Volumes/WD/Long/qdec/long.qdec.table.dat --meas
thickness --hemi lh --do-avg --do-rate --do-pc1 --do-spc --do-stack
--do-label --time years --qcache fsaverage --sd /Volumes/WD/Long/*

And the following error came out:

*Parsing the qdec table: /Volumes/WD/Long/qdec/long.qdec.table.datERROR:
qdec table /Volumes/WD/Long/qdec/long.qdec.table.dat not found or empty?*

The path is correct and there are no empty lines in the file.

When I ran:
*mris_preproc --debug --qdec-long qdec/long.qdec.table.dat*

This comes out:




























*set echo = 1 ;set debug = 1 ;set debug = 1breakswbreakswendendwhile (
$#argv != 0 )while ( 2 != 0 )set flag = $argv[1] ; shift ;set flag =
--qdec-longshiftswitch ( $flag )switch ( --qdec-long )if ( $#argv == 0 )
goto arg1err ;if ( 1 == 0 ) goto arg1errset fsgdf = $argv[1] ; shift ;set
fsgdf = qdec/long.qdec.table.datshiftif ( ! -e $fsgdf ) thenif ( ! -e
qdec/long.qdec.table.dat ) thenecho "ERROR: cannot find $fsgdf" ;echo
ERROR: cannot find qdec/long.qdec.table.datERROR: cannot find
qdec/long.qdec.table.datexit 1 ;exit 1*

Do you have any idea why this is happening?

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

[Freesurfer] mri_surfcluster

[tom parker]

Dear Freesurfers,

I ran a comparison between different groups using mri_glmfit.
Now I would like to correct the results in sig.mgh by multiple comparisons
using FDR. I tried using tksurfer but it doesn't work so well on my
computer and I read that freeview does not allow to do that yet.

I'm now trying to use mri_surfcluster to do it. Is this correct?
mri_surfcluster --in sig.mgh --subject fsaverage --surf inflated --hemi lh
--fdr 0.05 --sign pos

After I run it some thresholds appear in the terminal.
Should I use these thresholds to create a FDR corrected sig.mgh map or is
there a direct way of getting this using mri_surfcluster or other command?

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

[Bug 1592435] [NEW] chef-client depnds on ruby1.9.1

[Tom Parker]

Public bug reported:

If you try and run chef-client, you get "/usr/bin/env: ‘ruby1.9.1’: No
such file or directory" and ruby1.9.1 isn't present in Ubuntu Xenial.

chef package version: 12.3.0-3ubuntu1

** Affects: chef (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592435

Title:
  chef-client depnds on ruby1.9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chef/+bug/1592435/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Jira (PUP-6386) Error: Failed to apply catalog: Validation of File[xxxxxxx] failed: You cannot specify a remote recursion without a source

[Tom Parker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom Parker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6386 
 
 
 
  Error: Failed to apply catalog: Validation of File[xxx] failed: You cannot specify a remote recursion without a source  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.5.0 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client, Server 
 
 
 

Created:
 

 2016/06/03 11:32 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Tom Parker 
 
 
 
 
 
 
 
 
 
 
This file resource fails when catalog_terminus = static_compiler 
 file  {'/etc/ppp/peers': ensure => directory, source => "puppet:///modules/ppp/peers", recurse => remote, sourceselect => all, require => Package[$packages], } 
The error generated is: Error: Failed to apply catalog: Validation of File[/etc/ppp/peers] failed: You cannot specify a remote recursion without a source at /etc/puppetlabs/code/modules/ppp/manifests/init.pp:9 
I am running puppetserver 2.4.0-1puppetlabs1 on Debian and 

Re: [EVDL] Japanese leaf charging cable

[Tom Parker via EV]

On 05/03/2016 08:28 AM, George Tyler via EV wrote:

Hi, here in NZ many people are importing used Nissan Leaf's from Japan.
Japan has different voltage and frequency to the supply here, leaf charging
cable: 200V 60hz, NZ voltage 230V 50Hz. There is a small transformer in the
cable that has to be changed, but opening the cable means that it has to be
re-certified. Does anyone know what the charging cable electronics does?
The cable has an EVSE embedded in it. This basically tells the car how 
much current is available and only turns on the power if a car is 
actually present. In the EVSE supplied with the Gen 1 cars the power 
supply for the circuit inside the EVSE has a mains step down transformer 
not for more than 200v. This transformer will saturate on 240V and get 
very hot. The dealer forgot to do the replacement on our car and it 
failed after about 6 weeks being plugged in continuously. They replaced 
it with one that had been modified. I think you may also have to replace 
some over-voltage protection too.


What is the certification you're worried by? I'm not aware of needing a 
certification to plug something in in New Zealand.


The EVSE supplied with the Gen 2 cars is smaller, I don't know if that 
one needs modification or not.


If you don't want to modify the Nissan EVSE you might look at 
https://bluecars.nz/bc-shop/ in Auckland. Carl has an 8-10-16A 
selectable EVSE with a 16A caravan plug & a caravan to "normal" 10A 3 
pin plug adapter (with 10A circuit breaker and RCD). He also has a fixed 
8A EVSE.

___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
Read EVAngel's EV News at http://evdl.org/evln/
Please discuss EV drag racing at NEDRA (http://groups.yahoo.com/group/NEDRA)

[Freesurfer] Qdec DOSS

[tom parker]

Hi Freesurfers,

I posted this question a few days ago but didn't get any replies.
Would you mind answering this for me?

I compared 2 groups, while controlling for 1 covariate in qdec using
freesurfer 5.1.

There were no significant interactions with the covariate so I need to use
DOSS.

I read on several post that DOSS has some bugs related to the generation of
contrasts in qdec and that mri_glmfit should be used to run a DOSS analysis.

However, when I ran my analysis with DOSS in qdec I saw that the C.mat file
looked like this: 1 -1 0, which seems correct to me.

My question is can I use DOSS in qdec in this case? Or are there other bugs
related to using it in qdec?

Thank you so much!
___
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

kdb5_ldap_util: Unable to find requested database type while setting up lib handle

[Tom Parker]

Good evening. 

I am trying to set up a new kerberos realm using the ldap plugin and I
am getting the following error when I try to run:

/usr/sbin/kdb5_ldap_util stashsrvpw -f
/var/kerberos/krb5kdc/ldap_service_password cn=admin,dc=ls,dc=cbn

kdb5_ldap_util: Unable to find requested database type while setting up
lib handle

As far as I know I have everything installed correctly. 

I am using CentOS 7 and have the following rpms installed. 

krb5-server-1.13.2-10.el7.x86_64
krb5-libs-1.13.2-10.el7.x86_64
krb5-server-ldap-1.13.2-10.el7.x86_64

The kldap plugin is located as below:

/usr/lib64/libkdb_ldap.so
/usr/lib64/libkdb_ldap.so.1
/usr/lib64/libkdb_ldap.so.1.0
/usr/lib64/krb5/plugins/kdb
/usr/lib64/krb5/plugins/kdb/db2.so
/usr/lib64/krb5/plugins/kdb/kldap.so

Any help getting this to work would be appreciated.

Kerberos mailing list   Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

[issue26183] 2.7.11 won't clean install on Windows 10 x64

[Tom Parker]

Tom Parker added the comment:

FYI, I ran into this same issue, I believe this was caused by my selecting 
Python tools when installing Visual Studio 2015 Community edition. But I 
removed it and the issued didn't go away.

Then I deleted some empty python registry keys and voila the installer worked.

--
nosy: +tomparker

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26183>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue26183] 2.7.11 won't clean install on Windows 10 x64

[Tom Parker]

Tom Parker added the comment:

Ah OK :) I had done a W10 reset to wipe my PC before reinstalling VS so I 
could't imagine where else the python registry keys could have come from.

My install sequence was:

SQL Server 2012 Developer
Visual Studio 2015 Community Edition
Office 365
Inkscape - maybe??
Then Python 2.7.11

--

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26183>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Jira (FACT-823) Facter truncates interface names and then cannot load their data

[Tom Parker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom Parker created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-823 
 
 
 
  Facter truncates interface names and then cannot load their data  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 2.0.2 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 Community 
 
 
 

Created:
 

 2015/02/12 3:19 PM 
 
 
 

Environment:
 
 
SuSE Linux Enterprize 11 SP3 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Tom Parker 
 
 
 
 
 
 
 
 
 
 
I have several devices managed with puppet that use GRE tunnels with long interface names. Facter truncates the names of the devices when enumerating them and then cannot load the data.  
Device Names: tun_dnl_sps_0: tun_dnl_sps_2: tun_dnl_sps_4: tun_dnl_tgu_0: tun_dnl_tgu_2: tun_dnl_tgu_4: 
Puppet output:  Info: Loading facts Device tun_dnl_t does not exist. Device tun_dnl_t does not exist. Device tun_dnl_t does not exist. Device tun_dnl_t does not exist. Device tun_dnl_s does not exist. Device tun_dnl_s does not exist. Device tun_dnl_s does not exist. Device tun_dnl_s does not exist. Device tun_dnl_t does not exist. Device tun_dnl_t does

Re: [Openvpn-users] compat-names and spaces in Common Names

[Tom Parker]

Hi Gert.

I think the solution to my problem is for me to use a client-connect
script to handle the quirks of my particular use case without requiring
anything from the openvpn code.   I can get the Common Name in the
script and then search for the file with my naming convention as needed
or return an error if none is found.  This way I can keep the
functionality of ccd-exclusive and compat-names while not requiring any
name munging within openvpn itself.

I agree that maintaining code paths for all the possible scenarios is
not desirable and you already provide a great way for me to extend your
code with the script hooks that have been in place for years.

Thanks for your quick response and for making a great piece of software!

Tom



On 23/10/14 03:10 PM, Gert Doering wrote:
 Hi,

 On Thu, Oct 23, 2014 at 11:06:27AM -0400, Tom Parker wrote:
 We have recently upgrades to openvpn 2.3 and this name remapping has
 been removed.  I appreciate that for lots of things not changing the
 Common Name at all is the correct behaviour but i'm wondering if there
 is a flag that can be set to retain the behaviour for ccd files. 

 With the current version compat-names still works but it has been
 deprecated and will be removed according to the docs in the source code.

 I would rather not have spaces in my file names as that makes all kinds
 of other scripts more difficult to manage.  Sadly, regenerating all the
 certificate common names will not be a trivial task either. 

 Is there a plan to maintain backwards compatability with ccd files that
 have spaces mapped to underscores?
 Well, such questions really should be discussed on the openvpn-devel
 mailing list (as not all developers read here, and if we try to search
 something in the archives, we won't do it on the -user list...).

 We always strive to get rid of code that is no longer needed or
 should not be needed, and this is one of these code paths, which is
 why we planned to remove it (and, well, compat-names really breaks
 things for users with non-ASCII user names, because all of a sudden,
 all users are named ___...)

 I see your point about the ccd file names, but I worry that if we
 change that *again* (= always change spaces to underscores, but do
 no other name remapping) we might break people's configs *again* for
 those who have converted to User Name format already...

 Anyway.  I think we'd discuss a patch very thoroughly that would do
 this, and not reject it right away :-) (but over there in the -devel 
 list).

 gert



--
___
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Re: [Linux-HA] Hertbeat fail-over Email Alert

[Tom Parker]

Hi Lars

Can you provide more details about this resource agent.  The
documentation is a little sparse.  What events will cause an e-mail to
be sent?

Thanks!

Tom

On 24/09/14 06:53 PM, Lars Ellenberg wrote:
 On Tue, Sep 23, 2014 at 04:55:20PM +0530, Atul Yadav wrote:
 Dear Team ,

 In our environment for storage HA, we are using heartbeat method.

 Our Storage HA is working fine with Heartbeat management.

 Now we need your guidance to setup the EMAIL alert at the time of fail-over
  happen and fail over completed.

 We already setup smtp in both the servers.
 And we are able to send mail from terminal window.
 Storage1
 Storage2

 Please guide us.
 What's wrong with the MailTo resource agent?


___
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

[Nut-upsuser] sysOID for SMART-UPS 2200 RM XL

[Tom Parker]

Hello.   Just wanted to report this sysOID to you.  The UPSC output is
below.

Network UPS Tools - Generic SNMP UPS driver 0.70 (2.7.1)
kill: No such process
No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.11'!
Please report it to NUT developers, with an 'upsc' output for your device.
Going back to the classic MIB detection method.
Detected SMART-UPS 2200 RM XL on host guyups2.gy.ls.cbn (mib: apcc 1.2)
[guyups2] Warning: excessive poll failures, limiting error reporting
[guyups2] Warning: excessive poll failures, limiting error reporting

[LIVE] guybackup:~ # upsc guyups2
ambient.1.humidity.alarm.high: 60.00
ambient.1.humidity.alarm.low: 30.00
ambient.1.temperature.alarm.high: 40.00
ambient.1.temperature.alarm.low: 10.00
ambient.humidity: 0.00
ambient.temperature: 25.0
battery.charge: 100.00
battery.charge.restart: 0
battery.current: 0.00
battery.current.total: 0.00
battery.date: 10/11/11
battery.packs: 0.00
battery.runtime: 1080.00
battery.runtime.low: 300
battery.voltage: 55.00
device.mfr: APC
device.model: SMART-UPS 2200 RM XL
device.serial: QS0411211473
device.type: ups
driver.name: snmp-ups
driver.parameter.mibs: auto
driver.parameter.pollfreq: 15
driver.parameter.pollinterval: 2
driver.parameter.port: guyups2.gy.ls.cbn
driver.parameter.snmp_version: v1
driver.version: 2.7.1
driver.version.data: apcc MIB 1.2
driver.version.internal: 0.70
input.frequency: 60.50
input.sensitivity: high
input.transfer.high: 132
input.transfer.low: 103
input.transfer.reason: noTransfer
input.voltage: 112.40
input.voltage.maximum: 113.70
input.voltage.minimum: 11.20
output.frequency: 60.50
output.voltage: 112.40
output.voltage.nominal: 115
ups.delay.shutdown: 180
ups.delay.start: 180
ups.firmware: 83.14.D
ups.id: guyups2
ups.load: 34.80
ups.mfr: APC
ups.mfr.date: 03/11/04
ups.model: SMART-UPS 2200 RM XL
ups.serial: QS0411211473
ups.status: OL
ups.temperature: 30.60
ups.test.date: 07/03/2014
ups.test.result: Ok

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Linux-HA] SBD flipping between Pacemaker: UNHEALTHY and OK

[Tom Parker]

ok.  I have fixed that to be no_path_retry fail but I don't think this
has anything to do with the errors I am seeing. 

They seem to be related to sbd's link with my cluster, not with disk I/O

Tom

On 23/04/14 03:11 AM, emmanuel segura wrote:
 the first thing, you are using no_path_retry in wrong way in your
 multipath, try to read this
 http://www.novell.com/documentation/oes2/clus_admin_lx/data/bl9ykz6.html


 2014-04-22 20:41 GMT+02:00 Tom Parker tpar...@cbnco.com:

 I have attached the config files to this e-mail.  The sbd dump is below

 [LIVE] qaxen1:~ # sbd -d /dev/mapper/qa-xen-sbd dump
 ==Dumping header on disk /dev/mapper/qa-xen-sbd
 Header version : 2.1
 UUID   : ae835596-3d26-4681-ba40-206b4d51149b
 Number of slots: 255
 Sector size: 512
 Timeout (watchdog) : 45
 Timeout (allocate) : 2
 Timeout (loop) : 1
 Timeout (msgwait)  : 90
 ==Header on disk /dev/mapper/qa-xen-sbd is dumped

 On 22/04/14 02:30 PM, emmanuel segura wrote:
 you are missingo cluster configuration and sbd configuration and
 multipath
 config


 2014-04-22 20:21 GMT+02:00 Tom Parker tpar...@cbnco.com:

 Has anyone seen this?  Do you know what might be causing the flapping?

 Apr 21 22:03:03 qaxen6 sbd: [12962]: info: Watchdog enabled.
 Apr 21 22:03:03 qaxen6 sbd: [12973]: info: Servant starting for device
 /dev/mapper/qa-xen-sbd
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Monitoring Pacemaker health
 Apr 21 22:03:03 qaxen6 sbd: [12973]: info: Device /dev/mapper/qa-xen-sbd
 uuid: ae835596-3d26-4681-ba40-206b4d51149b
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Legacy plug-in detected, AIS
 quorum check enabled
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Waiting to sign in with
 cluster ...
 Apr 21 22:03:04 qaxen6 sbd: [12971]: notice: Using watchdog device:
 /dev/watchdog
 Apr 21 22:03:04 qaxen6 sbd: [12971]: info: Set watchdog timeout to 45
 seconds.
 Apr 21 22:03:04 qaxen6 sbd: [12974]: info: Waiting to sign in with
 cluster ...
 Apr 21 22:03:06 qaxen6 sbd: [12974]: info: We don't have a DC right now.
 Apr 21 22:03:08 qaxen6 sbd: [12974]: WARN: Node state: UNKNOWN
 Apr 21 22:03:09 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:03:09 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:03:10 qaxen6 sbd: [12974]: WARN: Node state: pending
 Apr 21 22:03:11 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:15:01 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:15:01 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:16:37 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:16:37 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:25:08 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:25:08 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:26:44 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:26:44 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:39:24 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:39:24 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:42:44 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:42:44 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 01:36:24 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 01:36:24 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 01:36:34 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 01:36:34 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 06:53:15 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 06:53:15 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 06:54:03 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 06:54:03 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 09:57:21 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 09:57:21 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 09:58:12 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 09:58:12 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 10:59:49 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 10:59:49 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 11:00:41 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 11:00:41 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 11:50:55 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 11:50:55 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 11:51:06 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 11:51:06 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 13:09:12 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 13:09:12 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 13:09:35 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 13:09:35 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 13:31:35 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 13:31:35 qaxen6 sbd: [12971]: WARN

Re: [Linux-HA] SBD flipping between Pacemaker: UNHEALTHY and OK

[Tom Parker]

SDB has a connection to pacemaker to establish overall cluster health
(the -P flag).  This seems to be where the problem is.  I just don't
know what the problem might be.

On 23/04/14 11:32 AM, emmanuel segura wrote:
 what do you mean with link?


 2014-04-23 15:23 GMT+02:00 Tom Parker tpar...@cbnco.com:

 ok.  I have fixed that to be no_path_retry fail but I don't think this
 has anything to do with the errors I am seeing.

 They seem to be related to sbd's link with my cluster, not with disk I/O

 Tom

 On 23/04/14 03:11 AM, emmanuel segura wrote:
 the first thing, you are using no_path_retry in wrong way in your
 multipath, try to read this
 http://www.novell.com/documentation/oes2/clus_admin_lx/data/bl9ykz6.html


 2014-04-22 20:41 GMT+02:00 Tom Parker tpar...@cbnco.com:

 I have attached the config files to this e-mail.  The sbd dump is below

 [LIVE] qaxen1:~ # sbd -d /dev/mapper/qa-xen-sbd dump
 ==Dumping header on disk /dev/mapper/qa-xen-sbd
 Header version : 2.1
 UUID   : ae835596-3d26-4681-ba40-206b4d51149b
 Number of slots: 255
 Sector size: 512
 Timeout (watchdog) : 45
 Timeout (allocate) : 2
 Timeout (loop) : 1
 Timeout (msgwait)  : 90
 ==Header on disk /dev/mapper/qa-xen-sbd is dumped

 On 22/04/14 02:30 PM, emmanuel segura wrote:
 you are missingo cluster configuration and sbd configuration and
 multipath
 config


 2014-04-22 20:21 GMT+02:00 Tom Parker tpar...@cbnco.com:

 Has anyone seen this?  Do you know what might be causing the flapping?

 Apr 21 22:03:03 qaxen6 sbd: [12962]: info: Watchdog enabled.
 Apr 21 22:03:03 qaxen6 sbd: [12973]: info: Servant starting for device
 /dev/mapper/qa-xen-sbd
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Monitoring Pacemaker health
 Apr 21 22:03:03 qaxen6 sbd: [12973]: info: Device
 /dev/mapper/qa-xen-sbd
 uuid: ae835596-3d26-4681-ba40-206b4d51149b
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Legacy plug-in detected,
 AIS
 quorum check enabled
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Waiting to sign in with
 cluster ...
 Apr 21 22:03:04 qaxen6 sbd: [12971]: notice: Using watchdog device:
 /dev/watchdog
 Apr 21 22:03:04 qaxen6 sbd: [12971]: info: Set watchdog timeout to 45
 seconds.
 Apr 21 22:03:04 qaxen6 sbd: [12974]: info: Waiting to sign in with
 cluster ...
 Apr 21 22:03:06 qaxen6 sbd: [12974]: info: We don't have a DC right
 now.
 Apr 21 22:03:08 qaxen6 sbd: [12974]: WARN: Node state: UNKNOWN
 Apr 21 22:03:09 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:03:09 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:03:10 qaxen6 sbd: [12974]: WARN: Node state: pending
 Apr 21 22:03:11 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:15:01 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:15:01 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:16:37 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:16:37 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:25:08 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:25:08 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:26:44 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:26:44 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:39:24 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:39:24 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:42:44 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:42:44 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 01:36:24 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 01:36:24 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 01:36:34 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 01:36:34 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 06:53:15 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 06:53:15 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 06:54:03 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 06:54:03 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 09:57:21 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 09:57:21 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 09:58:12 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 09:58:12 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 10:59:49 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 10:59:49 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 11:00:41 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 11:00:41 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 11:50:55 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 11:50:55 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 11:51:06 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 11:51:06 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 13:09:12 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 13

[Linux-HA] Resource blocked

[Tom Parker]

Good morning

I am trying to restart resources on one of my clusters and I am getting
the message

pengine[13397]:   notice: LogActions: Start   domtcot1-qa(qaxen1
- blocked)

How can I find out why this resource is blocked.

Thanks
___
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] SBD flipping between Pacemaker: UNHEALTHY and OK

[Tom Parker]

I have attached the config files to this e-mail.  The sbd dump is below

[LIVE] qaxen1:~ # sbd -d /dev/mapper/qa-xen-sbd dump
==Dumping header on disk /dev/mapper/qa-xen-sbd
Header version : 2.1
UUID   : ae835596-3d26-4681-ba40-206b4d51149b
Number of slots: 255
Sector size: 512
Timeout (watchdog) : 45
Timeout (allocate) : 2
Timeout (loop) : 1
Timeout (msgwait)  : 90
==Header on disk /dev/mapper/qa-xen-sbd is dumped

On 22/04/14 02:30 PM, emmanuel segura wrote:
 you are missingo cluster configuration and sbd configuration and multipath
 config


 2014-04-22 20:21 GMT+02:00 Tom Parker tpar...@cbnco.com:

 Has anyone seen this?  Do you know what might be causing the flapping?

 Apr 21 22:03:03 qaxen6 sbd: [12962]: info: Watchdog enabled.
 Apr 21 22:03:03 qaxen6 sbd: [12973]: info: Servant starting for device
 /dev/mapper/qa-xen-sbd
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Monitoring Pacemaker health
 Apr 21 22:03:03 qaxen6 sbd: [12973]: info: Device /dev/mapper/qa-xen-sbd
 uuid: ae835596-3d26-4681-ba40-206b4d51149b
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Legacy plug-in detected, AIS
 quorum check enabled
 Apr 21 22:03:03 qaxen6 sbd: [12974]: info: Waiting to sign in with
 cluster ...
 Apr 21 22:03:04 qaxen6 sbd: [12971]: notice: Using watchdog device:
 /dev/watchdog
 Apr 21 22:03:04 qaxen6 sbd: [12971]: info: Set watchdog timeout to 45
 seconds.
 Apr 21 22:03:04 qaxen6 sbd: [12974]: info: Waiting to sign in with
 cluster ...
 Apr 21 22:03:06 qaxen6 sbd: [12974]: info: We don't have a DC right now.
 Apr 21 22:03:08 qaxen6 sbd: [12974]: WARN: Node state: UNKNOWN
 Apr 21 22:03:09 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:03:09 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:03:10 qaxen6 sbd: [12974]: WARN: Node state: pending
 Apr 21 22:03:11 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:15:01 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:15:01 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:16:37 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:16:37 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:25:08 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:25:08 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:26:44 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:26:44 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 21 22:39:24 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 21 22:39:24 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 21 22:42:44 qaxen6 sbd: [12974]: info: Node state: online
 Apr 21 22:42:44 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 01:36:24 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 01:36:24 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 01:36:34 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 01:36:34 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 06:53:15 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 06:53:15 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 06:54:03 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 06:54:03 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 09:57:21 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 09:57:21 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 09:58:12 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 09:58:12 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 10:59:49 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 10:59:49 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 11:00:41 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 11:00:41 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 11:50:55 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 11:50:55 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 11:51:06 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 11:51:06 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 13:09:12 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 13:09:12 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 13:09:35 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 13:09:35 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 13:31:35 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 13:31:35 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 13:31:44 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 13:31:44 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 13:32:52 qaxen6 sbd: [12974]: WARN: AIS: Quorum outdated!
 Apr 22 13:32:52 qaxen6 sbd: [12971]: WARN: Pacemaker health check:
 UNHEALTHY
 Apr 22 13:33:01 qaxen6 sbd: [12974]: info: Node state: online
 Apr 22 13:33:01 qaxen6 sbd: [12971]: info: Pacemaker health check: OK
 Apr 22 13:44:39 qaxen6 sbd: [12974]: WARN

[Nut-upsuser] User defined variables in upsstats.html

[Tom Parker]

Hello

Is there any way to set and consume user defined variables in upsstats.html

I would like to set lower thresholds for temperature than are set in the
UPSes for my web page but I cannot figure out how to pass a value that
is not a variable into IFBETWEEN.

Is there a way to say:

@IFBETWEEN 15 25 ambient.temperature@
td BGCOLOR=#00FF00
@ELSE@
td BGCOLOR=#FF
@ENDIF@

Thank you

Tom

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Linux-HA] /usr/sbin/lrmadmin missing from cluster-glue

[Tom Parker]

Thanks Kristoffer.

How is tuning done for lrm now?

Tom

On 01/24/2014 01:41 AM, Kristoffer Grönlund wrote:
 On Sat, 28 Dec 2013 11:18:44 -0500
 Tom Parker tpar...@cbnco.com wrote:

 Hello

 /usr/sbin/lrmadmin is missing from the latest version of cluster-glue
 in SLES SP3.  Has the program been deprecated or is this an issue in
 the packaging of the RPM?

 Hi,

 I know this is a bit late, but I just discovered this email. Yes,
 lrmadmin has been deprecated since it is incompatible with recent
 versions of pacemaker.

 Thanks

 Tom
 ___
 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] /usr/sbin/lrmadmin missing from cluster-glue

[Tom Parker]

Hello

/usr/sbin/lrmadmin is missing from the latest version of cluster-glue in
SLES SP3.  Has the program been deprecated or is this an issue in the
packaging of the RPM?

Thanks

Tom
___
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: [Sugar-devel] XO-system 1a builds

[Tom Parker]

On 28/10/13 22:12, James Cameron wrote:

On Mon, Oct 28, 2013 at 09:01:02PM +1300, Tom Parker wrote:
zdextract in the bios-crypto package will unpack it, giving you a disk
image, which you can then loopback mount as a filesystem and compare
with another filesystem.

http://wiki.laptop.org/go/User:Quozl/Remastering is an example use of
zdextract for adding files to a build without having to re-run the
builder.  hasn't been tested since 2012, but it should help you
understand zdextract.


Thank you!

I modified your remastering script to leave the filesystems mounted. 
Then I used diff to compare them manually. My script is attached, along 
with another script to unmount and release the loopbacks.


The difference between 32049oe4.zd and 32050oe4.zd appears to be a 
changed flashplayer. 50 and 51 have a bunch of activity and translation 
changes.


mount-zd.sh
Description: application/shellscript


umount-zd.sh
Description: application/shellscript
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Using a new keyboard layout for XO4

[Tom Parker]

On 21/11/13 23:27, Basanta Shrestha wrote:

Dear all,
We are planing on using a different keyboard layout for XO4. The new
layout we think is phonetically based and easier for children. I simply
switched the /usr/share/X11/symbols/np file with a new one but did not
work. I guess there are some other works that needs to be done before we
can use this file. Can you suggest what needs to be done?

The layout I want to use is http://nepalinux.org/input/ne


We did this for Maori. We used James's Tiny Core Linux based 
customization stick.


See http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/scripts/asroot 
for the script that is run _before the first boot of the laptop_ to 
insert the Maori keyboard, change the keyboard configuration and update 
the Maori translations. The Maori keyboard is called mi. You may also be 
interested in 
http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/scripts/asolpc 
which changes the user's locale preferences.


See http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/mknzusb for 
the script which makes the customization flash drive. Be sure to read 
and understand it before running as it will wipe your disk and you will 
be sad if it wipes the wrong one!


Clone the whole repo if you like, but my server's bandwidth is not great 
and there is about 50MB in there, so be patient. I should probably 
refactor it to use a submodule to get tinycorexo.

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Using a new keyboard layout for XO4

[Tom Parker]

On 21/11/13 23:27, Basanta Shrestha wrote:

Dear all,
We are planing on using a different keyboard layout for XO4. The new
layout we think is phonetically based and easier for children. I simply
switched the /usr/share/X11/symbols/np file with a new one but did not
work. I guess there are some other works that needs to be done before we
can use this file. Can you suggest what needs to be done?

The layout I want to use is http://nepalinux.org/input/ne


We did this for Maori. We used James's Tiny Core Linux based 
customization stick.


See http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/scripts/asroot 
for the script that is run _before the first boot of the laptop_ to 
insert the Maori keyboard, change the keyboard configuration and update 
the Maori translations. The Maori keyboard is called mi. You may also be 
interested in 
http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/scripts/asolpc 
which changes the user's locale preferences.


See http://carrott.org/git/mktinycorexo_nz.git/blob/HEAD:/mknzusb for 
the script which makes the customization flash drive. Be sure to read 
and understand it before running as it will wipe your disk and you will 
be sad if it wipes the wrong one!


Clone the whole repo if you like, but my server's bandwidth is not great 
and there is about 50MB in there, so be patient. I should probably 
refactor it to use a submodule to get tinycorexo.

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: [Linux-HA] Antw: Xen XL Resource Agent

[Tom Parker]

My thoughts were to create a new RA and let admins choose. If you would prefer 
to auto-detect that is an option as well.

Tom

From: Lars Marowsky-Bree
Sent: Monday, November 18, 2013 8:27 AM
To: General Linux-HA mailing list
Reply To: General Linux-HA mailing list
Subject: Re: [Linux-HA] Antw: Xen XL Resource Agent


On 2013-11-15T09:05:53, Tom Parker tpar...@cbnco.com wrote:

 The XL tools are much faster and lighter weight.   I am not sure if they
 report proper codes (I will have to test) but the XM stack has been
 deprecated so at some point I assume it will go away completely.

The Xen RA already supports xen-list and xen-destroy in addition to
the xm tools. Patches to additionally support xl are welcome.

(Auto-detect what is available, and then choose xl - xen-* - xm.)

We can't yet drop xm, since not all environments have xl yet.


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
___
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] Antw: Xen XL Resource Agent

[Tom Parker]

The XL tools are much faster and lighter weight.   I am not sure if they
report proper codes (I will have to test) but the XM stack has been
deprecated so at some point I assume it will go away completely.

[LIVE] qaxen1:~ # time xl list
NameID   Mem VCPUs  State  
Time(s)
Domain-0 0 2534712 r- 
146383.6

Domain list removed

real0m0.053s
user0m0.000s
sys 0m0.008s


[LIVE] qaxen1:~ # time xm
list

  

NameID   Mem VCPUs  State  
Time(s) 


Domain-0 0 2534712 r-
146381.1
  


Domain list removed

real0m0.352s
user0m0.236s
sys 0m0.036s

On 11/15/2013 02:04 AM, Ulrich Windl wrote:
 Tom Parker tpar...@cbnco.com schrieb am 14.11.2013 um 19:23 in Nachricht
 5285150b.9050...@cbnco.com:
 Hello.

 Now that XM has been deprecated is anyone working on a Xen RA that uses
 the xl tool stack? 
 I woonder whether xl will (opposed to xm) report proper exit codes if 
 operations fail. Otherwise I don't see the reason to change tools. MHO...

 I am willing to do the work but I don't want to duplicate the effort if
 someone else is doing/has already done it.

 Tom
 ___
 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 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] Xen XL Resource Agent

[Tom Parker]

Hello.

Now that XM has been deprecated is anyone working on a Xen RA that uses
the xl tool stack? 

I am willing to do the work but I don't want to duplicate the effort if
someone else is doing/has already done it.

Tom
___
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 many primitives, groups can I have

[Tom Parker]

You will also have to be careful of the shared memory size between the nodes. I 
had issues with massive cibs. Setting some environment variables fixed the 
issue but the defaults are too small.

From: Digimer
Sent: Monday, November 11, 2013 10:24 AM
To: General Linux-HA mailing list
Reply To: General Linux-HA mailing list
Subject: Re: [Linux-HA] How many primitives, groups can I have


On 11/11/13 07:57, Michael Brookhuis wrote:
 Hi,

 Is there a limit in the number of proimitives, etc you can have?
 What maximum number is recommended based on best-practices?

 Are 1500 to many?

 Thanks
 Mima

The cib will be very large, so pushing changes to other nodes will take
time (specially if you have many nodes). I suspect you will run into
corosync timeouts before you hit any coded upper limits. You will likely
have to play with corosync timing values to get that high, assuming your
network is fast enough at all.

But in the end, as I understand it, there is no coded upper limit.

--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
___
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

Re: [Linux-HA] How many primitives, groups can I have

[Tom Parker]

I have found my settings.

I needed to set the following in /etc/sysconfig/pacemaker

# Force use of a particular class of IPC connection

# PCMK_ipc_type=shared-mem|socket|posix|sysv

export PCMK_ipc_type=shared-mem

# Specify an IPC buffer size in bytes

# Useful when connecting to really big clusters that exceed the default 20k 
buffer

# PCMK_ipc_buffer=20480

export PCMK_ipc_buffer=2048


and in my bashrc file (for the crm tools to work proplery) I have

[LIVE] qaxen1:~ # cat .bashrc 

# Load Pacemaker IPC settings for crm

PACEMAKER_SYSCONFIG=/etc/sysconfig/pacemaker

if [ -f $PACEMAKER_SYSCONFIG ]; then

. $PACEMAKER_SYSCONFIG

fi


Hope this helps.

On 11/11/2013 03:35 PM, Tom Parker wrote:
 You will also have to be careful of the shared memory size between the nodes. 
 I had issues with massive cibs. Setting some environment variables fixed the 
 issue but the defaults are too small.

 From: Digimer
 Sent: Monday, November 11, 2013 10:24 AM
 To: General Linux-HA mailing list
 Reply To: General Linux-HA mailing list
 Subject: Re: [Linux-HA] How many primitives, groups can I have


 On 11/11/13 07:57, Michael Brookhuis wrote:
 Hi,

 Is there a limit in the number of proimitives, etc you can have?
 What maximum number is recommended based on best-practices?

 Are 1500 to many?

 Thanks
 Mima
 The cib will be very large, so pushing changes to other nodes will take
 time (specially if you have many nodes). I suspect you will run into
 corosync timeouts before you hit any coded upper limits. You will likely
 have to play with corosync timing values to get that high, assuming your
 network is fast enough at all.

 But in the end, as I understand it, there is no coded upper limit.

 --
 Digimer
 Papers and Projects: https://alteeve.ca/w/
 What if the cure for cancer is trapped in the mind of a person without
 access to education?
 ___
 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 mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

[Sugar-devel] XO-system 1a builds

[Tom Parker]

Hi,

I'm not entirely sure if this is the right mailing list, if there is a 
more appropriate one, please let me know.


I'm looking for the URL to download XO-system 1a for XO-4 (build 49). 
It seems that it is no longer available. 
http://download.laptop.org.au/XO/F18/13.2.0/XO-system-1a/ has what is 
likely to be build 50 and http://build.laptop.org.au/xo/os/build-51/ has 
build 51.


I do have a copy of build 49 (which is a good thing, we have a small 
deployment with that build) but would like a stable URL to refer people to.


Does anyone know where the change log for these builds is kept? I'd like 
to know if there are any important bug fixes we're missing out on.


Thanks.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Linux-HA] Antw: Re: Xen RA and rebooting

[Tom Parker]

Thanks for the feedback.  Dejan, I have some SLES nodes that are running
around 30 pretty heavy VMs and I found that while I never go to 5s that
the time it would take to reboot was not a constant.   I have a feeling
that this bug in xen-list may take a while to be fixed upstream and
trickle down into the released xen packages so we may be using this fix
for a while.

The full longdesc now reads:

longdesc lang=en
When the guest is rebooting, there is a short interval where the guest
completely disappears from xm list, which, in turn, will cause the monitor
operation to return a not running status.

If a monitor status returns not running, then test status
again for wait_for_reboot seconds (perhaps it'll show up).

NOTE: This timer increases the amount of time the cluster will
wait before declaring a VM dead and recovering it.
/longdesc

Tom

On 10/21/2013 03:28 AM, Ulrich Windl wrote:
 When the guest is rebooting, there is a short interval where the guest
 completely disappears from xm list, which, in turn, will cause the monitor
 operation to return a not running status. If the guest cannot be found , 
 this
 value will cause some extra delay in the monitor operation to work around the
 problem.

___
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] Antw: Re: Xen RA and rebooting

[Tom Parker]

Hi Dejan.

How can I revert my commits so that they are not include multiple
things? I will submit one patch with the logging cleanup and then if
needed another with my changes to the meta-data.

Tom

On 10/21/2013 09:39 AM, Dejan Muhamedagic wrote:
 Hi Ulrich!

 On Mon, Oct 21, 2013 at 09:28:50AM +0200, Ulrich Windl wrote:
 Hi!

 Basically I think there should be no hard-coded constants whose value depends
 on some performance measurements, like 5s for rebooting a VM.
 It's actually not 5s, but the status is run 5 times. If the load
 is high, my guess is that the Xen tools used by the RA would
 suffer proportionally.

 So I support
 Tom's changes.

 However I noticed:

 +running; apparently, this period lasts only for a second or
 +two

 (missing full stop at end of sentence)
 That's at the end of the comment and, typically, comments end
 with a carriage return (as is here the case).

 Actually I'd rephrase the description:

 When the guest is rebooting, there is a short interval where the guest
 completely disappears from xm list, which, in turn, will cause the monitor
 operation to return a not running status. If the guest cannot be found , 
 this
 value will cause some extra delay in the monitor operation to work around the
 problem.

 (I.e. try to describe the effect, not the implementation)
 That's the code, so the implementation is described. The very
 top of the comment says:

   # If the guest is rebooting, it may completely disappear from the
   # list of defined guests

 I was hoping that that was enough of an explanation. Look for
 a more thorough description of the cause in the changelog. BTW,
 note that this is a _workaround_ and that the thing should
 eventually be fixed in Xen.

 And yes, I appreciate consistent log formats also ;-)
 That's always welcome, of course. It should also go in a
 separate commit.

 Thanks,

 Dejan

 Regards,
 Ulrich

 Tom Parker tpar...@cbnco.com schrieb am 18.10.2013 um 19:30 in
 Nachricht
 5261703a.5070...@cbnco.com:
 Hi Dejan.  Sorry to be slow to respond to this.  I have done some
 testing and everything looks good. 

 I spent some time tweaking the RA and I added a parameter called
 wait_for_reboot (default 5s) to allow us to override the reboot sleep
 times (in case it's more than 5 seconds on really loaded hypervisors). 
 I also cleaned up a few log entries to make them consistent in the RA
 and edited your entries for xen status to be a little bit more clear as
 to why we think we should be waiting. 

 I have attached a patch here because I have NO idea how to create a
 branch and pull request.  If there are links to a good place to start I
 may be able to contribute occasionally to some other RAs that I use.

 Please let me know what you think.

 Thanks for your help

 Tom


 On 10/17/2013 06:10 AM, Dejan Muhamedagic wrote:
 On Thu, Oct 17, 2013 at 11:45:17AM +0200, Dejan Muhamedagic wrote:
 Hi Tom,

 On Wed, Oct 16, 2013 at 05:28:28PM -0400, Tom Parker wrote:
 Some more reading of the source code makes me think the  || [
 $__OCF_ACTION != stop ]; is not needed. 
 Yes, you're right. I'll drop that part of the if statement. Many
 thanks for testing.
 Fixed now. The if statement, which was obviously hard to follow,
 got relegated to the monitor function.  Which makes the
 Xen_Status_with_Retry really stand for what's happening in there ;-)

 Tom, hope you can test again.

 Cheers,

 Dejan

 Cheers,

 Dejan

 Xen_Status_with_Retry() is only called from Stop and Monitor so we only
 need to check if it's a probe.  Everything else should be handled in the
 case statement in the loop.

 Tom

 On 10/16/2013 05:16 PM, Tom Parker wrote:
 Hi.  I think there is an issue with the Updated Xen RA.

 I think there is an issue with the if statement here but I am not sure.
 I may be confused about how bash || works but I don't see my servers
 ever entering the loop on a vm disappearing.

 if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
 return $rc
 fi

 Does this not mean that if we run a monitor operation that is not a
 probe we will have:

 (ocf_is_probe) return false
 (stop != monitor) return true
 (false || true) return true

 which will cause the if statement to return $rc and never enter the
 loop? 
 Xen_Status_with_Retry() {
   local rc cnt=5

   Xen_Status $1
   rc=$?
   if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
 return $rc
   fi
   while [ $rc -eq $OCF_NOT_RUNNING -a $cnt -gt 0 ]; do
 case $__OCF_ACTION in
 stop)
   ocf_log debug domain $1 reported as not running, waiting
 $cnt
 seconds ...
   ;;
 monitor)
   ocf_log warn domain $1 reported as not running, but it is
 expected to be running! Retrying for $cnt seconds ...
   ;;
 *) : not reachable
 ;;
 esac
 sleep 1
 Xen_Status $1
 rc=$?
 let cnt=$((cnt-1))
   done
   return $rc
 }



 On 10/16/2013 12:12 PM, Dejan Muhamedagic wrote:
 Hi Tom,

 On Tue, Oct 15

Re: [Linux-HA] Antw: Re: Xen RA and rebooting

[Tom Parker]

Hi Dejan.  Sorry to be slow to respond to this.  I have done some
testing and everything looks good. 

I spent some time tweaking the RA and I added a parameter called
wait_for_reboot (default 5s) to allow us to override the reboot sleep
times (in case it's more than 5 seconds on really loaded hypervisors). 
I also cleaned up a few log entries to make them consistent in the RA
and edited your entries for xen status to be a little bit more clear as
to why we think we should be waiting. 

I have attached a patch here because I have NO idea how to create a
branch and pull request.  If there are links to a good place to start I
may be able to contribute occasionally to some other RAs that I use.

Please let me know what you think.

Thanks for your help

Tom


On 10/17/2013 06:10 AM, Dejan Muhamedagic wrote:
 On Thu, Oct 17, 2013 at 11:45:17AM +0200, Dejan Muhamedagic wrote:
 Hi Tom,

 On Wed, Oct 16, 2013 at 05:28:28PM -0400, Tom Parker wrote:
 Some more reading of the source code makes me think the  || [
 $__OCF_ACTION != stop ]; is not needed. 
 Yes, you're right. I'll drop that part of the if statement. Many
 thanks for testing.
 Fixed now. The if statement, which was obviously hard to follow,
 got relegated to the monitor function.  Which makes the
 Xen_Status_with_Retry really stand for what's happening in there ;-)

 Tom, hope you can test again.

 Cheers,

 Dejan

 Cheers,

 Dejan

 Xen_Status_with_Retry() is only called from Stop and Monitor so we only
 need to check if it's a probe.  Everything else should be handled in the
 case statement in the loop.

 Tom

 On 10/16/2013 05:16 PM, Tom Parker wrote:
 Hi.  I think there is an issue with the Updated Xen RA.

 I think there is an issue with the if statement here but I am not sure. 
 I may be confused about how bash || works but I don't see my servers
 ever entering the loop on a vm disappearing.

 if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
 return $rc
 fi

 Does this not mean that if we run a monitor operation that is not a
 probe we will have:

 (ocf_is_probe) return false
 (stop != monitor) return true
 (false || true) return true

 which will cause the if statement to return $rc and never enter the loop? 

 Xen_Status_with_Retry() {
   local rc cnt=5

   Xen_Status $1
   rc=$?
   if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
 return $rc
   fi
   while [ $rc -eq $OCF_NOT_RUNNING -a $cnt -gt 0 ]; do
 case $__OCF_ACTION in
 stop)
   ocf_log debug domain $1 reported as not running, waiting $cnt
 seconds ...
   ;;
 monitor)
   ocf_log warn domain $1 reported as not running, but it is
 expected to be running! Retrying for $cnt seconds ...
   ;;
 *) : not reachable
 ;;
 esac
 sleep 1
 Xen_Status $1
 rc=$?
 let cnt=$((cnt-1))
   done
   return $rc
 }



 On 10/16/2013 12:12 PM, Dejan Muhamedagic wrote:
 Hi Tom,

 On Tue, Oct 15, 2013 at 07:55:11PM -0400, Tom Parker wrote:
 Hi Dejan

 Just a quick question.  I cannot see your new log messages being logged
 to syslog

 ocf_log warn domain $1 reported as not running, but it is expected to
 be running! Retrying for $cnt seconds ...

 Do you know where I can set my logging to see warn level messages?  I
 expected to see them in my testing by default but that does not seem to
 be true.
 You should see them by default. But note that these warnings may
 not happen, depending on the circumstances on your host. In my
 experiments they were logged only while the guest was rebooting
 and then just once or maybe twice. If you have recent
 resource-agents and crmsh, you can enable operation tracing (with
 crm resource trace rsc monitor interval).

 Thanks,

 Dejan

 Thanks

 Tom


 On 10/08/2013 05:04 PM, Dejan Muhamedagic wrote:
 Hi,

 On Tue, Oct 08, 2013 at 01:52:56PM +0200, Ulrich Windl wrote:
 Hi!

 I thought, I'll never be bitten by this bug, but I actually was! Now 
 I'm
 wondering whether the Xen RA sees the guest if you use pygrub, and 
 pygrub is
 still counting down for actual boot...

 But the reason why I'm writing is that I think I've discovered another 
 bug in
 the RA:

 CRM decided to recover the guest VM v02:
 [...]
 lrmd: [14903]: info: operation monitor[28] on prm_xen_v02 for client 
 14906:
 pid 19516 exited with return code 7
 [...]
  pengine: [14905]: notice: LogActions: Recover prm_xen_v02 (Started 
 h05)
 [...]
  crmd: [14906]: info: te_rsc_command: Initiating action 5: stop
 prm_xen_v02_stop_0 on h05 (local)
 [...]
 Xen(prm_xen_v02)[19552]: INFO: Xen domain v02 already stopped.
 [...]
 lrmd: [14903]: info: operation stop[31] on prm_xen_v02 for client 
 14906: pid
 19552 exited with return code 0
 [...]
 crmd: [14906]: info: te_rsc_command: Initiating action 78: start
 prm_xen_v02_start_0 on h05 (local)
 lrmd: [14903]: info: rsc:prm_xen_v02 start[32] (pid 19686)
 [...]
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stderr) Error: 
 Domain 'v02

Re: [Linux-HA] Antw: Re: Xen RA and rebooting

[Tom Parker]

I may have actually created the pull request properly... 

Please let me know and again thanks for your help.

Tom

On 10/18/2013 01:30 PM, Tom Parker wrote:
 Hi Dejan.  Sorry to be slow to respond to this.  I have done some
 testing and everything looks good. 

 I spent some time tweaking the RA and I added a parameter called
 wait_for_reboot (default 5s) to allow us to override the reboot sleep
 times (in case it's more than 5 seconds on really loaded hypervisors). 
 I also cleaned up a few log entries to make them consistent in the RA
 and edited your entries for xen status to be a little bit more clear as
 to why we think we should be waiting. 

 I have attached a patch here because I have NO idea how to create a
 branch and pull request.  If there are links to a good place to start I
 may be able to contribute occasionally to some other RAs that I use.

 Please let me know what you think.

 Thanks for your help

 Tom


 On 10/17/2013 06:10 AM, Dejan Muhamedagic wrote:
 On Thu, Oct 17, 2013 at 11:45:17AM +0200, Dejan Muhamedagic wrote:
 Hi Tom,

 On Wed, Oct 16, 2013 at 05:28:28PM -0400, Tom Parker wrote:
 Some more reading of the source code makes me think the  || [
 $__OCF_ACTION != stop ]; is not needed. 
 Yes, you're right. I'll drop that part of the if statement. Many
 thanks for testing.
 Fixed now. The if statement, which was obviously hard to follow,
 got relegated to the monitor function.  Which makes the
 Xen_Status_with_Retry really stand for what's happening in there ;-)

 Tom, hope you can test again.

 Cheers,

 Dejan

 Cheers,

 Dejan

 Xen_Status_with_Retry() is only called from Stop and Monitor so we only
 need to check if it's a probe.  Everything else should be handled in the
 case statement in the loop.

 Tom

 On 10/16/2013 05:16 PM, Tom Parker wrote:
 Hi.  I think there is an issue with the Updated Xen RA.

 I think there is an issue with the if statement here but I am not sure. 
 I may be confused about how bash || works but I don't see my servers
 ever entering the loop on a vm disappearing.

 if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
 return $rc
 fi

 Does this not mean that if we run a monitor operation that is not a
 probe we will have:

 (ocf_is_probe) return false
 (stop != monitor) return true
 (false || true) return true

 which will cause the if statement to return $rc and never enter the loop? 

 Xen_Status_with_Retry() {
   local rc cnt=5

   Xen_Status $1
   rc=$?
   if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
 return $rc
   fi
   while [ $rc -eq $OCF_NOT_RUNNING -a $cnt -gt 0 ]; do
 case $__OCF_ACTION in
 stop)
   ocf_log debug domain $1 reported as not running, waiting $cnt
 seconds ...
   ;;
 monitor)
   ocf_log warn domain $1 reported as not running, but it is
 expected to be running! Retrying for $cnt seconds ...
   ;;
 *) : not reachable
 ;;
 esac
 sleep 1
 Xen_Status $1
 rc=$?
 let cnt=$((cnt-1))
   done
   return $rc
 }



 On 10/16/2013 12:12 PM, Dejan Muhamedagic wrote:
 Hi Tom,

 On Tue, Oct 15, 2013 at 07:55:11PM -0400, Tom Parker wrote:
 Hi Dejan

 Just a quick question.  I cannot see your new log messages being logged
 to syslog

 ocf_log warn domain $1 reported as not running, but it is expected to
 be running! Retrying for $cnt seconds ...

 Do you know where I can set my logging to see warn level messages?  I
 expected to see them in my testing by default but that does not seem to
 be true.
 You should see them by default. But note that these warnings may
 not happen, depending on the circumstances on your host. In my
 experiments they were logged only while the guest was rebooting
 and then just once or maybe twice. If you have recent
 resource-agents and crmsh, you can enable operation tracing (with
 crm resource trace rsc monitor interval).

 Thanks,

 Dejan

 Thanks

 Tom


 On 10/08/2013 05:04 PM, Dejan Muhamedagic wrote:
 Hi,

 On Tue, Oct 08, 2013 at 01:52:56PM +0200, Ulrich Windl wrote:
 Hi!

 I thought, I'll never be bitten by this bug, but I actually was! Now 
 I'm
 wondering whether the Xen RA sees the guest if you use pygrub, and 
 pygrub is
 still counting down for actual boot...

 But the reason why I'm writing is that I think I've discovered 
 another bug in
 the RA:

 CRM decided to recover the guest VM v02:
 [...]
 lrmd: [14903]: info: operation monitor[28] on prm_xen_v02 for client 
 14906:
 pid 19516 exited with return code 7
 [...]
  pengine: [14905]: notice: LogActions: Recover prm_xen_v02 (Started 
 h05)
 [...]
  crmd: [14906]: info: te_rsc_command: Initiating action 5: stop
 prm_xen_v02_stop_0 on h05 (local)
 [...]
 Xen(prm_xen_v02)[19552]: INFO: Xen domain v02 already stopped.
 [...]
 lrmd: [14903]: info: operation stop[31] on prm_xen_v02 for client 
 14906: pid
 19552 exited with return code 0
 [...]
 crmd: [14906]: info: te_rsc_command: Initiating action 78: start

Re: [EVDL] Morris Minor Conversion

[Tom Parker]

On 17/10/13 19:02, David Chapman wrote:

Yes, check the archives. I seem to recall someone converting a Mini many years 
ago. I assume you are talking about one of the first gen? Dach.


I'm (still!) converting a classic Mini. While most of the Minors have 
the same engine as the Mini, converting to electric will be quite 
different because the Minor is rear wheel drive while the Mini is front 
wheel drive. This means the gearbox, clutch and engine crankshaft are 
completely different.


I don't know much about Minors, but I'm sure a conversion is possible.
___
UNSUBSCRIBE: http://www.evdl.org/help/index.html#usub
http://lists.evdl.org/listinfo.cgi/ev-evdl.org
For EV drag racing discussion, please use NEDRA 
(http://groups.yahoo.com/group/NEDRA)

Re: [Linux-HA] Antw: Re: Xen RA and rebooting

[Tom Parker]

Hi.  I think there is an issue with the Updated Xen RA.

I think there is an issue with the if statement here but I am not sure. 
I may be confused about how bash || works but I don't see my servers
ever entering the loop on a vm disappearing.

if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
return $rc
fi

Does this not mean that if we run a monitor operation that is not a
probe we will have:

(ocf_is_probe) return false
(stop != monitor) return true
(false || true) return true

which will cause the if statement to return $rc and never enter the loop? 

Xen_Status_with_Retry() {
  local rc cnt=5

  Xen_Status $1
  rc=$?
  if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
return $rc
  fi
  while [ $rc -eq $OCF_NOT_RUNNING -a $cnt -gt 0 ]; do
case $__OCF_ACTION in
stop)
  ocf_log debug domain $1 reported as not running, waiting $cnt
seconds ...
  ;;
monitor)
  ocf_log warn domain $1 reported as not running, but it is
expected to be running! Retrying for $cnt seconds ...
  ;;
*) : not reachable
;;
esac
sleep 1
Xen_Status $1
rc=$?
let cnt=$((cnt-1))
  done
  return $rc
}



On 10/16/2013 12:12 PM, Dejan Muhamedagic wrote:
 Hi Tom,

 On Tue, Oct 15, 2013 at 07:55:11PM -0400, Tom Parker wrote:
 Hi Dejan

 Just a quick question.  I cannot see your new log messages being logged
 to syslog

 ocf_log warn domain $1 reported as not running, but it is expected to
 be running! Retrying for $cnt seconds ...

 Do you know where I can set my logging to see warn level messages?  I
 expected to see them in my testing by default but that does not seem to
 be true.
 You should see them by default. But note that these warnings may
 not happen, depending on the circumstances on your host. In my
 experiments they were logged only while the guest was rebooting
 and then just once or maybe twice. If you have recent
 resource-agents and crmsh, you can enable operation tracing (with
 crm resource trace rsc monitor interval).

 Thanks,

 Dejan

 Thanks

 Tom


 On 10/08/2013 05:04 PM, Dejan Muhamedagic wrote:
 Hi,

 On Tue, Oct 08, 2013 at 01:52:56PM +0200, Ulrich Windl wrote:
 Hi!

 I thought, I'll never be bitten by this bug, but I actually was! Now I'm
 wondering whether the Xen RA sees the guest if you use pygrub, and pygrub 
 is
 still counting down for actual boot...

 But the reason why I'm writing is that I think I've discovered another bug 
 in
 the RA:

 CRM decided to recover the guest VM v02:
 [...]
 lrmd: [14903]: info: operation monitor[28] on prm_xen_v02 for client 14906:
 pid 19516 exited with return code 7
 [...]
  pengine: [14905]: notice: LogActions: Recover prm_xen_v02 (Started h05)
 [...]
  crmd: [14906]: info: te_rsc_command: Initiating action 5: stop
 prm_xen_v02_stop_0 on h05 (local)
 [...]
 Xen(prm_xen_v02)[19552]: INFO: Xen domain v02 already stopped.
 [...]
 lrmd: [14903]: info: operation stop[31] on prm_xen_v02 for client 14906: 
 pid
 19552 exited with return code 0
 [...]
 crmd: [14906]: info: te_rsc_command: Initiating action 78: start
 prm_xen_v02_start_0 on h05 (local)
 lrmd: [14903]: info: rsc:prm_xen_v02 start[32] (pid 19686)
 [...]
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stderr) Error: Domain 
 'v02'
 already exists with ID '3'
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stdout) Using config 
 file
 /etc/xen/vm/v02.
 [...]
 lrmd: [14903]: info: operation start[32] on prm_xen_v02 for client 14906: 
 pid
 19686 exited with return code 1
 [...]
 crmd: [14906]: info: process_lrm_event: LRM operation prm_xen_v02_start_0
 (call=32, rc=1, cib-update=5271, confirmed=true) unknown error
 crmd: [14906]: WARN: status_from_rc: Action 78 (prm_xen_v02_start_0) on h05
 failed (target: 0 vs. rc: 1): Error
 [...]

 As you can clearly see start failed, because the guest was found up 
 already!
 IMHO this is a bug in the RA (SLES11 SP2: resource-agents-3.9.4-0.26.84).
 Yes, I've seen that. It's basically the same issue, i.e. the
 domain being gone for a while and then reappearing.

 I guess the following test is problematic:
 ---
   xm create ${OCF_RESKEY_xmfile} name=$DOMAIN_NAME
   rc=$?
   if [ $rc -ne 0 ]; then
 return $OCF_ERR_GENERIC
 ---
 Here xm create probably fails if the guest is already created...
 It should fail too. Note that this is a race, but the race is
 anyway caused by the strange behaviour of xen. With the recent
 fix (or workaround) in the RA, this shouldn't be happening.

 Thanks,

 Dejan

 Regards,
 Ulrich


 Dejan Muhamedagic deja...@fastmail.fm schrieb am 01.10.2013 um 12:24 
 in
 Nachricht 20131001102430.GA4687@walrus.homenet:
 Hi,

 On Tue, Oct 01, 2013 at 12:13:02PM +0200, Lars Marowsky-Bree wrote:
 On 2013-10-01T00:53:15, Tom Parker tpar...@cbnco.com wrote:

 Thanks for paying attention to this issue (not really a bug) as I am
 sure I am not the only one with this issue.  For now I have set all my
 VMs to destroy so

Re: [Linux-HA] Antw: Re: Xen RA and rebooting

[Tom Parker]

Some more reading of the source code makes me think the  || [
$__OCF_ACTION != stop ]; is not needed. 

Xen_Status_with_Retry() is only called from Stop and Monitor so we only
need to check if it's a probe.  Everything else should be handled in the
case statement in the loop.

Tom

On 10/16/2013 05:16 PM, Tom Parker wrote:
 Hi.  I think there is an issue with the Updated Xen RA.

 I think there is an issue with the if statement here but I am not sure. 
 I may be confused about how bash || works but I don't see my servers
 ever entering the loop on a vm disappearing.

 if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
 return $rc
 fi

 Does this not mean that if we run a monitor operation that is not a
 probe we will have:

 (ocf_is_probe) return false
 (stop != monitor) return true
 (false || true) return true

 which will cause the if statement to return $rc and never enter the loop? 

 Xen_Status_with_Retry() {
   local rc cnt=5

   Xen_Status $1
   rc=$?
   if ocf_is_probe || [ $__OCF_ACTION != stop ]; then
 return $rc
   fi
   while [ $rc -eq $OCF_NOT_RUNNING -a $cnt -gt 0 ]; do
 case $__OCF_ACTION in
 stop)
   ocf_log debug domain $1 reported as not running, waiting $cnt
 seconds ...
   ;;
 monitor)
   ocf_log warn domain $1 reported as not running, but it is
 expected to be running! Retrying for $cnt seconds ...
   ;;
 *) : not reachable
 ;;
 esac
 sleep 1
 Xen_Status $1
 rc=$?
 let cnt=$((cnt-1))
   done
   return $rc
 }



 On 10/16/2013 12:12 PM, Dejan Muhamedagic wrote:
 Hi Tom,

 On Tue, Oct 15, 2013 at 07:55:11PM -0400, Tom Parker wrote:
 Hi Dejan

 Just a quick question.  I cannot see your new log messages being logged
 to syslog

 ocf_log warn domain $1 reported as not running, but it is expected to
 be running! Retrying for $cnt seconds ...

 Do you know where I can set my logging to see warn level messages?  I
 expected to see them in my testing by default but that does not seem to
 be true.
 You should see them by default. But note that these warnings may
 not happen, depending on the circumstances on your host. In my
 experiments they were logged only while the guest was rebooting
 and then just once or maybe twice. If you have recent
 resource-agents and crmsh, you can enable operation tracing (with
 crm resource trace rsc monitor interval).

 Thanks,

 Dejan

 Thanks

 Tom


 On 10/08/2013 05:04 PM, Dejan Muhamedagic wrote:
 Hi,

 On Tue, Oct 08, 2013 at 01:52:56PM +0200, Ulrich Windl wrote:
 Hi!

 I thought, I'll never be bitten by this bug, but I actually was! Now I'm
 wondering whether the Xen RA sees the guest if you use pygrub, and pygrub 
 is
 still counting down for actual boot...

 But the reason why I'm writing is that I think I've discovered another 
 bug in
 the RA:

 CRM decided to recover the guest VM v02:
 [...]
 lrmd: [14903]: info: operation monitor[28] on prm_xen_v02 for client 
 14906:
 pid 19516 exited with return code 7
 [...]
  pengine: [14905]: notice: LogActions: Recover prm_xen_v02 (Started h05)
 [...]
  crmd: [14906]: info: te_rsc_command: Initiating action 5: stop
 prm_xen_v02_stop_0 on h05 (local)
 [...]
 Xen(prm_xen_v02)[19552]: INFO: Xen domain v02 already stopped.
 [...]
 lrmd: [14903]: info: operation stop[31] on prm_xen_v02 for client 14906: 
 pid
 19552 exited with return code 0
 [...]
 crmd: [14906]: info: te_rsc_command: Initiating action 78: start
 prm_xen_v02_start_0 on h05 (local)
 lrmd: [14903]: info: rsc:prm_xen_v02 start[32] (pid 19686)
 [...]
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stderr) Error: Domain 
 'v02'
 already exists with ID '3'
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stdout) Using config 
 file
 /etc/xen/vm/v02.
 [...]
 lrmd: [14903]: info: operation start[32] on prm_xen_v02 for client 14906: 
 pid
 19686 exited with return code 1
 [...]
 crmd: [14906]: info: process_lrm_event: LRM operation prm_xen_v02_start_0
 (call=32, rc=1, cib-update=5271, confirmed=true) unknown error
 crmd: [14906]: WARN: status_from_rc: Action 78 (prm_xen_v02_start_0) on 
 h05
 failed (target: 0 vs. rc: 1): Error
 [...]

 As you can clearly see start failed, because the guest was found up 
 already!
 IMHO this is a bug in the RA (SLES11 SP2: resource-agents-3.9.4-0.26.84).
 Yes, I've seen that. It's basically the same issue, i.e. the
 domain being gone for a while and then reappearing.

 I guess the following test is problematic:
 ---
   xm create ${OCF_RESKEY_xmfile} name=$DOMAIN_NAME
   rc=$?
   if [ $rc -ne 0 ]; then
 return $OCF_ERR_GENERIC
 ---
 Here xm create probably fails if the guest is already created...
 It should fail too. Note that this is a race, but the race is
 anyway caused by the strange behaviour of xen. With the recent
 fix (or workaround) in the RA, this shouldn't be happening.

 Thanks,

 Dejan

 Regards,
 Ulrich


 Dejan Muhamedagic deja...@fastmail.fm schrieb am 01.10.2013

Re: [Linux-HA] Antw: Re: Xen RA and rebooting

[Tom Parker]

Hi Dejan

Just a quick question.  I cannot see your new log messages being logged
to syslog

ocf_log warn domain $1 reported as not running, but it is expected to
be running! Retrying for $cnt seconds ...

Do you know where I can set my logging to see warn level messages?  I
expected to see them in my testing by default but that does not seem to
be true.

Thanks

Tom


On 10/08/2013 05:04 PM, Dejan Muhamedagic wrote:
 Hi,

 On Tue, Oct 08, 2013 at 01:52:56PM +0200, Ulrich Windl wrote:
 Hi!

 I thought, I'll never be bitten by this bug, but I actually was! Now I'm
 wondering whether the Xen RA sees the guest if you use pygrub, and pygrub is
 still counting down for actual boot...

 But the reason why I'm writing is that I think I've discovered another bug in
 the RA:

 CRM decided to recover the guest VM v02:
 [...]
 lrmd: [14903]: info: operation monitor[28] on prm_xen_v02 for client 14906:
 pid 19516 exited with return code 7
 [...]
  pengine: [14905]: notice: LogActions: Recover prm_xen_v02 (Started h05)
 [...]
  crmd: [14906]: info: te_rsc_command: Initiating action 5: stop
 prm_xen_v02_stop_0 on h05 (local)
 [...]
 Xen(prm_xen_v02)[19552]: INFO: Xen domain v02 already stopped.
 [...]
 lrmd: [14903]: info: operation stop[31] on prm_xen_v02 for client 14906: pid
 19552 exited with return code 0
 [...]
 crmd: [14906]: info: te_rsc_command: Initiating action 78: start
 prm_xen_v02_start_0 on h05 (local)
 lrmd: [14903]: info: rsc:prm_xen_v02 start[32] (pid 19686)
 [...]
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stderr) Error: Domain 
 'v02'
 already exists with ID '3'
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stdout) Using config file
 /etc/xen/vm/v02.
 [...]
 lrmd: [14903]: info: operation start[32] on prm_xen_v02 for client 14906: pid
 19686 exited with return code 1
 [...]
 crmd: [14906]: info: process_lrm_event: LRM operation prm_xen_v02_start_0
 (call=32, rc=1, cib-update=5271, confirmed=true) unknown error
 crmd: [14906]: WARN: status_from_rc: Action 78 (prm_xen_v02_start_0) on h05
 failed (target: 0 vs. rc: 1): Error
 [...]

 As you can clearly see start failed, because the guest was found up 
 already!
 IMHO this is a bug in the RA (SLES11 SP2: resource-agents-3.9.4-0.26.84).
 Yes, I've seen that. It's basically the same issue, i.e. the
 domain being gone for a while and then reappearing.

 I guess the following test is problematic:
 ---
   xm create ${OCF_RESKEY_xmfile} name=$DOMAIN_NAME
   rc=$?
   if [ $rc -ne 0 ]; then
 return $OCF_ERR_GENERIC
 ---
 Here xm create probably fails if the guest is already created...
 It should fail too. Note that this is a race, but the race is
 anyway caused by the strange behaviour of xen. With the recent
 fix (or workaround) in the RA, this shouldn't be happening.

 Thanks,

 Dejan

 Regards,
 Ulrich


 Dejan Muhamedagic deja...@fastmail.fm schrieb am 01.10.2013 um 12:24 in
 Nachricht 20131001102430.GA4687@walrus.homenet:
 Hi,

 On Tue, Oct 01, 2013 at 12:13:02PM +0200, Lars Marowsky-Bree wrote:
 On 2013-10-01T00:53:15, Tom Parker tpar...@cbnco.com wrote:

 Thanks for paying attention to this issue (not really a bug) as I am
 sure I am not the only one with this issue.  For now I have set all my
 VMs to destroy so that the cluster is the only thing managing them but
 this is not super clean as I get failures in my logs that are not really
 failures.
 It is very much a severe bug.

 The Xen RA has gained a workaround for this now, but we're also pushing
 Take a look here:

 https://github.com/ClusterLabs/resource-agents/pull/314 

 Thanks,

 Dejan

 the Xen team (where the real problem is) to investigate and fix.


 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 
 ___
 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 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

Re: [Linux-HA] Antw: Re: Xen RA and rebooting

[Tom Parker]

This scares me too.  If the start operation finds a running vm and
fails, my cluster config will automatically try to start the same VM on
the next node it has available.  This scenario almost guarantees
duplicate VMs even if I  have the on_reboot=destroy. 

Dejan,  I am not sure but I don't think your patch will take care of
this.  In my opinion a start that finds a running version should return
success (vm should be started and it is.)

Tom

On 10/08/2013 07:52 AM, Ulrich Windl wrote:
 Hi!

 I thought, I'll never be bitten by this bug, but I actually was! Now I'm
 wondering whether the Xen RA sees the guest if you use pygrub, and pygrub is
 still counting down for actual boot...

 But the reason why I'm writing is that I think I've discovered another bug in
 the RA:

 CRM decided to recover the guest VM v02:
 [...]
 lrmd: [14903]: info: operation monitor[28] on prm_xen_v02 for client 14906:
 pid 19516 exited with return code 7
 [...]
  pengine: [14905]: notice: LogActions: Recover prm_xen_v02 (Started h05)
 [...]
  crmd: [14906]: info: te_rsc_command: Initiating action 5: stop
 prm_xen_v02_stop_0 on h05 (local)
 [...]
 Xen(prm_xen_v02)[19552]: INFO: Xen domain v02 already stopped.
 [...]
 lrmd: [14903]: info: operation stop[31] on prm_xen_v02 for client 14906: pid
 19552 exited with return code 0
 [...]
 crmd: [14906]: info: te_rsc_command: Initiating action 78: start
 prm_xen_v02_start_0 on h05 (local)
 lrmd: [14903]: info: rsc:prm_xen_v02 start[32] (pid 19686)
 [...]
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stderr) Error: Domain 'v02'
 already exists with ID '3'
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stdout) Using config file
 /etc/xen/vm/v02.
 [...]
 lrmd: [14903]: info: operation start[32] on prm_xen_v02 for client 14906: pid
 19686 exited with return code 1
 [...]
 crmd: [14906]: info: process_lrm_event: LRM operation prm_xen_v02_start_0
 (call=32, rc=1, cib-update=5271, confirmed=true) unknown error
 crmd: [14906]: WARN: status_from_rc: Action 78 (prm_xen_v02_start_0) on h05
 failed (target: 0 vs. rc: 1): Error
 [...]

 As you can clearly see start failed, because the guest was found up already!
 IMHO this is a bug in the RA (SLES11 SP2: resource-agents-3.9.4-0.26.84).

 I guess the following test is problematic:
 ---
   xm create ${OCF_RESKEY_xmfile} name=$DOMAIN_NAME
   rc=$?
   if [ $rc -ne 0 ]; then
 return $OCF_ERR_GENERIC
 ---
 Here xm create probably fails if the guest is already created...

 Regards,
 Ulrich


 Dejan Muhamedagic deja...@fastmail.fm schrieb am 01.10.2013 um 12:24 in
 Nachricht 20131001102430.GA4687@walrus.homenet:
 Hi,

 On Tue, Oct 01, 2013 at 12:13:02PM +0200, Lars Marowsky-Bree wrote:
 On 2013-10-01T00:53:15, Tom Parker tpar...@cbnco.com wrote:

 Thanks for paying attention to this issue (not really a bug) as I am
 sure I am not the only one with this issue.  For now I have set all my
 VMs to destroy so that the cluster is the only thing managing them but
 this is not super clean as I get failures in my logs that are not really
 failures.
 It is very much a severe bug.

 The Xen RA has gained a workaround for this now, but we're also pushing
 Take a look here:

 https://github.com/ClusterLabs/resource-agents/pull/314 

 Thanks,

 Dejan

 the Xen team (where the real problem is) to investigate and fix.


 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 
 ___
 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 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] Antw: Re: Xen RA and rebooting

[Tom Parker]

I want to test the updated RA.  Does anyone know how I can increase the
loglevel to warn or debug without restarting my cluster?  I am not
seeing any of the new messages in my logs.

Tom

On 10/08/2013 07:52 AM, Ulrich Windl wrote:
 Hi!

 I thought, I'll never be bitten by this bug, but I actually was! Now I'm
 wondering whether the Xen RA sees the guest if you use pygrub, and pygrub is
 still counting down for actual boot...

 But the reason why I'm writing is that I think I've discovered another bug in
 the RA:

 CRM decided to recover the guest VM v02:
 [...]
 lrmd: [14903]: info: operation monitor[28] on prm_xen_v02 for client 14906:
 pid 19516 exited with return code 7
 [...]
  pengine: [14905]: notice: LogActions: Recover prm_xen_v02 (Started h05)
 [...]
  crmd: [14906]: info: te_rsc_command: Initiating action 5: stop
 prm_xen_v02_stop_0 on h05 (local)
 [...]
 Xen(prm_xen_v02)[19552]: INFO: Xen domain v02 already stopped.
 [...]
 lrmd: [14903]: info: operation stop[31] on prm_xen_v02 for client 14906: pid
 19552 exited with return code 0
 [...]
 crmd: [14906]: info: te_rsc_command: Initiating action 78: start
 prm_xen_v02_start_0 on h05 (local)
 lrmd: [14903]: info: rsc:prm_xen_v02 start[32] (pid 19686)
 [...]
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stderr) Error: Domain 'v02'
 already exists with ID '3'
 lrmd: [14903]: info: RA output: (prm_xen_v02:start:stdout) Using config file
 /etc/xen/vm/v02.
 [...]
 lrmd: [14903]: info: operation start[32] on prm_xen_v02 for client 14906: pid
 19686 exited with return code 1
 [...]
 crmd: [14906]: info: process_lrm_event: LRM operation prm_xen_v02_start_0
 (call=32, rc=1, cib-update=5271, confirmed=true) unknown error
 crmd: [14906]: WARN: status_from_rc: Action 78 (prm_xen_v02_start_0) on h05
 failed (target: 0 vs. rc: 1): Error
 [...]

 As you can clearly see start failed, because the guest was found up already!
 IMHO this is a bug in the RA (SLES11 SP2: resource-agents-3.9.4-0.26.84).

 I guess the following test is problematic:
 ---
   xm create ${OCF_RESKEY_xmfile} name=$DOMAIN_NAME
   rc=$?
   if [ $rc -ne 0 ]; then
 return $OCF_ERR_GENERIC
 ---
 Here xm create probably fails if the guest is already created...

 Regards,
 Ulrich


 Dejan Muhamedagic deja...@fastmail.fm schrieb am 01.10.2013 um 12:24 in
 Nachricht 20131001102430.GA4687@walrus.homenet:
 Hi,

 On Tue, Oct 01, 2013 at 12:13:02PM +0200, Lars Marowsky-Bree wrote:
 On 2013-10-01T00:53:15, Tom Parker tpar...@cbnco.com wrote:

 Thanks for paying attention to this issue (not really a bug) as I am
 sure I am not the only one with this issue.  For now I have set all my
 VMs to destroy so that the cluster is the only thing managing them but
 this is not super clean as I get failures in my logs that are not really
 failures.
 It is very much a severe bug.

 The Xen RA has gained a workaround for this now, but we're also pushing
 Take a look here:

 https://github.com/ClusterLabs/resource-agents/pull/314 

 Thanks,

 Dejan

 the Xen team (where the real problem is) to investigate and fix.


 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 
 ___
 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 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] Antw: Re: Xen RA and rebooting

[Tom Parker]

Thanks to everyone who helped on this one.  I really appreciate the
speed that this has been looked at and resolved.  I am kind of surprised
that no one has reported it before.

Lars.  Do you know the bug report number with the Xen guys?  I would
like to watch that as it progresses as well.

Thanks again!

Tom

On 10/01/2013 06:24 AM, Dejan Muhamedagic wrote:
 Hi,

 On Tue, Oct 01, 2013 at 12:13:02PM +0200, Lars Marowsky-Bree wrote:
 On 2013-10-01T00:53:15, Tom Parker tpar...@cbnco.com wrote:

 Thanks for paying attention to this issue (not really a bug) as I am
 sure I am not the only one with this issue.  For now I have set all my
 VMs to destroy so that the cluster is the only thing managing them but
 this is not super clean as I get failures in my logs that are not really
 failures.
 It is very much a severe bug.

 The Xen RA has gained a workaround for this now, but we're also pushing
 Take a look here:

 https://github.com/ClusterLabs/resource-agents/pull/314

 Thanks,

 Dejan

 the Xen team (where the real problem is) to investigate and fix.


 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
 ___
 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

Re: [Linux-HA] Antw: Re: Xen RA and rebooting

[Tom Parker]

Hi Ulrich.  You have summed it up exactly and the chances seem small but
in the real world (Murphy's Law I guess) I have hit this many times. 
Twice to the point where I have mangled a Production VM to the point of
garbage.  The larger the available free memory on the cluster as a whole
seems to make a big difference because there seems to be a much greater
chance of the cluster deciding to move a dead vm while it is rebooting. 

Thanks for paying attention to this issue (not really a bug) as I am
sure I am not the only one with this issue.  For now I have set all my
VMs to destroy so that the cluster is the only thing managing them but
this is not super clean as I get failures in my logs that are not really
failures.

Tom


On 09/30/2013 07:56 AM, Ulrich Windl wrote:
 Hi!

 With Xen paravirtualization, when a VM (guest) is rebootet (e.g. via guest's 
 reboot), the actual VM (which doesn't really exist as a concept in 
 paravirtualization) is destroyed for a moment and then is recreated (AFAIK). 
 That's why xm console does not survive a guest reboot, and that's why a RA 
 may see the guest is gone for a moment before it's recreated.

 A clean fix would be in Xen to keep the guest in xm list during reboot.

 The chances to be hit by the problem are small, but when hit, the 
 consequences are bad.

 Regards,
 Ulrich

 Ferenc Wagner wf...@niif.hu schrieb am 17.09.2013 um 11:38 in Nachricht
 87six37pph@lant.ki.iif.hu:
 Lars Marowsky-Bree l...@suse.com writes:

 The RA thinks the guest is gone, the cluster reacts and schedules it
 to be started (perhaps elsewhere); and then the hypervisor starts it
 locally again *too*.

 I think changing those libvirt settings to destroy could work - the
 cluster will then restart the guest appropriately, not the hypervisor.
 Maybe the RA is just too picky about the reported VM state.  This is one
 of the reasons* I'm using my own RA for managing libvirt virtual
 domains: mine does not care about the fine points, if the domain is
 active in any state, it's running, as far as the RA is concerned, so a
 domain reset is not a cluster event in any case.

 On the other hand, doesn't the recover action after a monitor failure
 consist of a stop action on the original host before the new start, just
 to make sure?  Or maybe I'm confusing things...

 Regards,
 Feri.

 * Another is that mine gets the VM definition as a parameter, not via
   some shared filesystem.
 ___
 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 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] Xen RA and rebooting

[Tom Parker]

On 09/17/2013 01:13 AM, Vladislav Bogdanov wrote:
 14.09.2013 07:28, Tom Parker wrote:
 Hello All

 Does anyone know of a good way to prevent pacemaker from declaring a vm
 dead if it's rebooted from inside the vm.  It seems to be detecting the
 vm as stopped for the brief moment between shutting down and starting
 up.  Often this causes the cluster to have two copies of the same vm if
 the locks are not set properly (which I have found to be unreliable) one
 that is managed and one that is abandonded.

 If anyone has any suggestions or parameters that I should be tweaking
 that would be appreciated.
 I use following in libvirt VM definitions to prevent this:
   on_poweroffdestroy/on_poweroff
   on_rebootdestroy/on_reboot
   on_crashdestroy/on_crash

 Vladislav
Does this not show as a lot of failed operations?  I guess they will
clean themselves up after the failure expires.

 ___
 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

Re: [Linux-HA] Xen RA and rebooting

[Tom Parker]

On 09/17/2013 04:18 AM, Lars Marowsky-Bree wrote:
 On 2013-09-16T16:36:38, Tom Parker tpar...@cbnco.com wrote:

 Can you kindly file a bug report here so it doesn't get lost
 https://github.com/ClusterLabs/resource-agents/issues ?
 Submitted (Issue *#308)*
 Thanks.

 It definitely leads to data corruption and I think has to do with the
 way that the locking is not working properly on my lvm partitions. 
 Well, not really an LVM issue. The RA thinks the guest is gone, the
 cluster reacts and schedules it to be started (perhaps elsewhere); and
 then the hypervisor starts it locally again *too*.
I mean the locking of the LVs.  I should not be able to mount the same
LV in two places.  I know I can lock each LV exclusive to a node but I
am not sure how to tell the RA to do that for me.  At the moment I am
activating a VG with the LVM RA and that is shared across all my
physical machines.  If I do exclusive activation I think that locks the
vg to a particular node instead of the LVs.

 I think changing those libvirt settings to destroy could work - the
 cluster will then restart the guest appropriately, not the hypervisor.


 Regards,
 Lars


___
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] Clone colocation missing?

[Tom Parker]

Now that I have started using resource templates for my VMs (Thanks for
this suggestion Lars!) I have added one simple colocation rule to my cluster

My VMs all use the @CBNXen resource template and I have:

order virtual-machines-after-storage inf: storage-clone CBNXen
colocation virtual-machines-with-storage inf: CBNXen storage-clone

This should take care of all the ordering and colocation needs for my VMs

Tom


On 09/14/2013 07:14 AM, Lars Marowsky-Bree wrote:
 On 2013-09-13T17:48:40, Tom Parker tpar...@cbnco.com wrote:

 Hi Feri

 I agree that it should be necessary but for some reason it works well 
 the way it is and everything starts in the correct order.  Maybe 
 someone on the dev list can explain a little bit better why this is 
 working.  It may have something to do with the fact that it's a clone 
 instead of a primitive.
 And luck. Your behaviour is undefined, and will work for most of the
 common cases.

 : versus inf: on the order means that, during a healthy start-up,
 A will be scheduled to start before B. It does not mean that B will need
 to be stopped before A. Or that B shouldn't start if A can't. Typically,
 both are required.

 Since you've got ordering, *normally*, B will start on a node where A is
 running. However, if A can't run on a node for any given reason, B will
 still try to start there without collocation. Typically, you'd want to
 avoid that.

 The issues with the start sequence tend to be mostly harmless - you'll
 just get additional errors for failure cases that might distract you
 from the real cause.

 The stop issue can be more difficult, because it might imply that A
 fails to stop because B is still active, and you'll get stop escalation
 (fencing). However, it might also mean that A enters an escalated stop
 procedure itself (like Filesystem, which will kill -9 processes that are
 still active), and thus implicitly stop B by force. That'll probably
 work, you'll see everything stopping, but it might require additional
 time from B on next start-up to recover from the aborted state.

 e.g., you can be lucky, but you also might turn out not to be. In my
 experience, this means it'll all work just fine during controlled
 testing, and then fail spectacularly under a production load.

 Hence the recommendation to fix the constraints ;-)


 (And, yes, this *does* suggest that we made a mistake in making this so
 easy to misconfigure. But, hey, ordering and colocation are independent
 concepts! The design and abstraction is pure! And I admit that I guess
 I'm to blame for that to a large degree ... If the most common case is
 A, then B + B where A, why isn't there a recommended constraint that
 just does both with no way of misconfiguring that? It's pretty high on
 my list of things to have fixed.)


 Regards,
 Lars


___
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] Xen RA and rebooting

[Tom Parker]

On 09/14/2013 07:18 AM, Lars Marowsky-Bree wrote:
 On 2013-09-14T00:28:30, Tom Parker tpar...@cbnco.com wrote:

 Does anyone know of a good way to prevent pacemaker from declaring a vm
 dead if it's rebooted from inside the vm.  It seems to be detecting the
 vm as stopped for the brief moment between shutting down and starting
 up. 
 Hrm. Good question. Because to the monitor, it really looks as if the VM
 is temporarily gone, and it doesn't know ... Perhaps we need to keep
 looking for it for a few seconds.

 Can you kindly file a bug report here so it doesn't get lost
 https://github.com/ClusterLabs/resource-agents/issues ?
Submitted (Issue *#308)*
 Often this causes the cluster to have two copies of the same vm if the
 locks are not set properly (which I have found to be unreliable) one
 that is managed and one that is abandonded.
 *This* however is really, really worrisome and sounds like data
 corruption. How is this happening?
It definitely leads to data corruption and I think has to do with the
way that the locking is not working properly on my lvm partitions.   It
seems to mostly happen on clusters where I am using lvm slices on an MSA
as shared storage (they don't seem to lock at the lv level) and the
placement-strategy is utilization.  If Xen reboots and the cluster
declares the vm as dead it seems to try to start it on another node that
has more resources instead of the node where it was running.  It doesn't
happen consistently enough for me to detect a pattern and seems to never
happen on my QA system where I can actually cause corruption without
anyone getting mad.  If I can isolate how it happens I will file a bug.


 The work-around right now is to put the VM resource into maintenance
 mode for the reboot, or to reboot it via stop/start of the cluster
 manager.


 Regards,
 Lars


___
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] Clone colocation missing? (was: Pacemaker 1.19 cannot manage more than 127 resources)

[Tom Parker]

Hi Feri

I agree that it should be necessary but for some reason it works well 
the way it is and everything starts in the correct order.  Maybe 
someone on the dev list can explain a little bit better why this is 
working.  It may have something to do with the fact that it's a clone 
instead of a primitive.

Tom

On Thu 05 Sep 2013 04:48:40 AM EDT, Ferenc Wagner wrote:
 Tom Parker tpar...@cbnco.com writes:

 I have attached my original crm config with 201 primitives to this e-mail.

 Hi,

 Sorry to sidetrack this thread, but I really wonder why you only have
 order constraints for your Xen resources, without any colocation
 constraints.  After all, they can only start after the *local* storage
 clone has started...  For example, you have this:

 primitive abrazotedb ocf:heartbeat:Xen [...]
 order abrazotedb-after-storage-clone : storage-clone abrazotedb

 and I miss (besides the already mentioned inf above) something like:

 colocation abrazotedb-with-storage-clone inf: abratozedb storage-clone

 Or is this really unnecessary for some reason?  Please enlighten me.
___
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