#mcollective

hey: any guys out there using mco on AIX (7100/6100)?

not directly, but better just to ask your question as it may not be AIX specific

hehe ..true ...some nodes just throwing core dumps (ruby)

and we are unable to debug

when do they do this?

and what version of MCollective is this with?

brb ...have to check :)

puppet is running rock stable (ruby 2.0)

mco is on level 2.41

if the segfault is a startup, you may be hitting this: https://tickets.puppetlabs.com/browse/MCO-580

like 10% of our node are crashing

timing information is important

not on startup ...but maybe after a puppetrun

then please work to capture console output and a core file so we can attempt to investigate further

w00t that would be really great! i mean i had to completly disable mco

on all nodes ..b/c we are monitoring errpt & core dumps

i will try to deliver the core dumps ...

_rc ...ruby 2.0 is not supposed to be the reason?

if you're running a recent enough mcollective, 2.0 should be ok

I'd have to check release notes to say which version

thx a lot

i really want to use all the great features we are using on linux also on AIX

you should be running 2.6.0 or newer for ruby 2.0 compatibility: https://tickets.puppetlabs.com/browse/MCO-421

otherwise the signal handers are unsafe

thx _rc ...i will check this out & give you feedback

[marionette-collective] kylog pushed 4 new commits to 2.8.x: http://git.io/xbAf

marionette-collective/2.8.x 6e88ad9 Richard Clamp: MCO-617 Assign version in-tree...

marionette-collective/2.8.x 3e07927 Richard Clamp: MCO-617 disable check for @DEVELOPMENT_VERSION@ in ddls...

marionette-collective/2.8.x 781aebe Richard Clamp: MCO-617 don't expand version in packaging tasks