Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Rudder Chatbot
    @rudderbot
    mikes1988 cool, thanks so much :-) that seemed to run on the client alright
    mikes1988 do you know if the server will pick it up immediately, or does it need triggered there too?
    mikes1988 oh - spok etoo soon!
    mikes1988 that's the node updated on the server too
    fanf mikes1988: I don't know with your version, perhaps you will need to clear cache / start a generation by hand
    fanf gods, I don't even remember what 2.6 looks like (and I'm not sure I want to know, and I'm very happy it works for you)
    peck the inventory will need to way for at least one run on the server to be processed
    fanf I think 2.6 is older than most of my sons :)
    Rudder Chatbot
    @rudderbot
    mikes1988 thanks fanf & peck - that's it all sorted, I suppose I could have waited for the next automatic update, but it stopped a couple of rules applying which was annoying me a bit :-)
    peck is 1988 the date you installed rudder ?
    fanf peck: we are happy that users are fullfilled by their rudder installation :)
    mikes1988 peck: lol - it seems like it! On another note, we only decomissioned an old machine running hylafax a couple of years ago. By decomissioned I mean it blew up and we needed to replace it...
    mikes1988 was a pentium 3 machine
    mikes1988 solid as a rock
    Vincent Membré
    @VinceMacBuche
    an explosive rock then ;)
    Rudder Chatbot
    @rudderbot
    mikes1988 yeah just a bit :-)
    mikes1988 there's another one here running RHEL AS 3
    mikes1988 I get scared about reoboting them
    peck hehe
    peck any floppy disk based boot ?
    mikes1988 thank god no
    mikes1988 lol
    mikes1988 getting very nostalgic :-)
    Rudder Chatbot
    @rudderbot
    mikes1988 1988 is a reference to my year of manufacture - unfortunate choice of a username in the early 2000s, and I can't bring myself to change it
    Rudder Chatbot
    @rudderbot
    peck not easy to change a production year
    tpreti
    @tpreti
    hello
    Rudder Chatbot
    @rudderbot
    fanf hello
    tpreti
    @tpreti
    i'm trying to install a rudder-relay-server
    but i have this message : we could not generate policies for server '71636f02-b015-4466-98f5-76ab60375d3a', therefore making updates for nodes behind it unavailable. Maybe you are missing 'scale out' plugin?
    in the documentation, there is nothing about it
    can you help me ?
    this error is during the policy update
    the version of rudder is 5.0.13 on debian
    Francois Armand
    @fanf
    @tpreti you need the scale-out plugin, it is the one which provides the logic to handle policies for nodes behind relays => https://www.rudder.io/en/use/plugins/
    marson
    @ismenia_gitlab
    hello all
    Vincent Membré
    @VinceMacBuche
    Hello @ismenia_gitlab !
    marson
    @ismenia_gitlab
    I have a issue on rudder server, the status of the policies is going bad with many errors on /var/log/rudder/webapp/2019_10_03.stderrout.log
    the errors are:
    [2019-10-03 10:23:56] ERROR policy.generation - Policy update error for process '122311' at 2019-10-03 10:23:56: Cannot build target configuration node
    the health status is red
    Alexis Mousset
    @amousset
    Do you have more information when clicking on "Details" in the generation menu?
    marson
    @ismenia_gitlab
    I can't get the details now because the status still loading,
    Alexis Mousset
    @amousset
    Could you send us your full /var/log/rudder/webapp/2019_10_03.stderrout.log file? (in private or by email)
    marson
    @ismenia_gitlab
    Error
    Policy update process was stopped due to an error:
    ⇨ Policy update error for process '122314' at 2019-10-03 10:33:51
    ⇨ Cannot build target configuration node
    ⇨ Error while computing Node Configuration for nodes: Error with parameters expansion for node 'sst-p1305979fl.ads.local' (4ab56d2d-46a2-4505-96f6-0f630f64edef): Node sst-p1305979fl.ads.local '4ab56d2d-46a2-4505-96f6-0f630f64edef' get directives with incompatible different policy mode but technique 'servicesManagement/3.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 105a251a-bc4e-455c-878b-081b5c8ac4b0 ; 8693f7cc-0827-4851-9a43-a5d4fcc18e7c / 85ee09df-ba13-41b2-8453-0d510dddbb15; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'rmm-p1188644fl.ads.local' (ae1615c0-386b-422e-ab70-981cf2d542c4): Node rmm-p1188644fl.ads.local 'ae1615c0-386b-422e-ab70-981cf2d542c4' get directives with incompatible different policy mode but technique 'servicesManagement/3.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 105a251a-bc4e-455c-878b-081b5c8ac4b0 ; 8693f7cc-0827-4851-9a43-a5d4fcc18e7c / 85ee09df-ba13-41b2-8453-0d510dddbb15; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'sst-p1309380pl.ads.local' (07b67004-2c8d-413a-8b91-0a9157aefac8): Node sst-p1309380pl.ads.local '07b67004-2c8d-413a-8b91-0a9157aefac8' get directives with incompatible different policy mode but technique 'groupManagement/5.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 7e744382-28a0-4ff9-aecb-481e54f34754 ; 497f862b-f4fd-44f6-93c1-e1b1c5df60a6 / d57337b8-78cd-47bc-90b0-d95c62da61c6; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'sst-p1307285fl.ads.local' (331c0cce-b329-432b-a6aa-0893d8d444df): Node sst-p1307285fl.ads.local '331c0cce-b329-432b-a6aa-0893d8d444df' get directives with incompatible different policy mode but technique 'groupManagement/5.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 7e744382-28a0-4ff9-aecb-481e54f34754 ; 497f862b-f4fd-44f6-93c1-e1b1c5df60a6 / d57337b8-78cd-47bc-90b0-d95c62da61c6; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'rmm-p2000075fl.ads.local' (48c88552-406b-46c8-8c3c-a29a994776ef): Node rmm-p2000075fl.ads.local '48c88552-406b-46c8-8c3c-a29a994776ef' get directives with incompatible different policy mode but technique 'groupManagement/5.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 7e744382-28a0-4ff9-aecb-481e54f34754 ; 497f862b-f4fd-44f6-93c1-e1b1c5df60a6 / d57337b8-78cd-47bc-90b0-d95c62da61c6; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'shz-p0000316fl.ads.local' (c6a965ae-737d-4c8a-81fe-9e7bd1885a12): Node shz-p0000316fl.ads.local 'c6a965ae-737d-4c8a-81fe-9e7bd1885a12' get directives with incompatible different policy mode but technique 'groupManagement/5.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 7e744382-28a0-4ff9-aecb-481e54f34754 ; 497f862b-f4fd-44f6-93c1-e1b1c5df60a6 / d57337b8-78cd-47bc-90b0-d95c62da61c6; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'rmm-p2000143fl.ads.local' (588ee994-b993-4152-a38e-14231543f5a1): Node rmm-p2000143fl.ads.local '588ee994-b993-4152-a38e-14231543f5a1' get directives with incompatible different policy mode but technique 'servicesManagement/3.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 105a251a-bc4e-455c-878b-081b5c8ac4b0 ; 8693f7cc-0827-4851-9a43-a5d4fcc18e7c / 85ee09df-ba13-41b2-8453-0d510dddbb15; Inconsistant policy mode: both audit and enfor
    there is the contains of details
    Alexis Mousset
    @amousset
    The is the different policy modes applied on the same directive to the same node. Older techniques versions do not support this, and all directives from the same technique on a node need to use the same policy mode.
    you can upgrade your group management directives to 5.1 which supports mixed policy modes.
    Alexis Mousset
    @amousset
    the service management technique has no new versions supporting mixed modes, but you could use the new "services technique" which is simpler and supports mixed policy modes.
    marson
    @ismenia_gitlab
    Why before it'working?
    Alexis Mousset
    @amousset
    because you didn't have mixed policy modes on the same node and directive. You probably switched the policy mode of two directives based on these techniques.