Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Matthew Frost
    @mattronix
    !
    Francois Armand
    @fanf
    but I understand it doesn't help present use case
    I can't make it a 404 for next 6.1 patch release though
    (and in the middle time, I fear you will have to regex match on the horrible, non-sensible message about node not found in removed nodes)
    Francois Armand
    @fanf
    Matthew Frost
    @mattronix
    np
    Matthew Frost
    @mattronix
    my api problem is indeed the full data
    very slow when getting full
    but i want the system inventory and extended node properties
    things like PID i dont really care about
    anyway to go that route?
    i see i am blind
    default may do the job
    Francois Armand
    @fanf
    @mattronix : nodes?include=minimal,properties,cpu etc
    Suvi
    @Suvi8

    Hello guys,
    A question about the conditions in technique editor:

    How can i make a condition for example NOT_Success or NOT_Repaired?

    How to use AND / OR / NOR / NOT

    Alexis Mousset
    @amousset
    . for and, | for or, ( ) for grouping
    Suvi
    @Suvi8
    Thanks Alexis, but if i want a condition for example: NOT_Successfull
    Alexis Mousset
    @amousset
    ! for not, forgot this one!
    Suvi
    @Suvi8

    Hi, i have a problem with aws.py Script,

    On certain Amazon EC2 Instances, the script gives an error:

    Traceback (most recent call last):
    File "aws.py", line 68, in <module>
    if is_ec2():
    File "aws.py", line 18, in is_ec2
    with open("/sys/hypervisor/uuid") as f:
    FileNotFoundError: [Errno 2] No such file or directory: '/sys/hypervisor/uuid'

    Francois Armand
    @fanf
    @Suvi8 it seems to be linked to the way the underlying host or VM is configured, I found: https://ask.openstack.org/en/question/21171/launch-xenserver-vm-errno-2-no-such-file-or-directory-syshypervisoruuid/
    Alexis Mousset
    @amousset
    @Suvi8 Is it a specific instance typeor OS that fails with this error?
    Bert Driehuis
    @driehuis_gitlab
    For the life of me, I can't figure out where the contents of /etc/cron.d/rudder-agent is coming from. I want to reduce the number of cron calls, but rudder seems to be overwriting my changes.
    Alexis Mousset
    @amousset
    It's part of the system policies of the agent, so it's enforced at each agent run
    Bert Driehuis
    @driehuis_gitlab
    Ah, found the template! /var/rudder/configuration-repository/techniques/system/common/1.0/rudder-agent-community-cron. The docs warn against editing files in this directory, but I think for such templates it should be okay to edit and commit them, I reckon. Or will this complicate upgrading rudder later?
    Alexis Mousset
    @amousset
    It should not be a problem, but you may have to do it after each upgrade
    Bert Driehuis
    @driehuis_gitlab
    I should be able to manage that, thanks!
    skygeneve
    @skygeneve
    hello, is there a hostname character limit ?
    Alexis Mousset
    @amousset
    I don't think so, do you have problems with long hostnames?
    skygeneve
    @skygeneve
    I have a vm with 34 character and it dosent show on the accept nodes on rudder
    I got this error : error: Finished command related to promiser '/opt/rudder/bin/run-inventory --local=/var/rudder/tmp/inventory/euw2-vvis-mis-dev-lx-ldnlngpy1-ec2-c4c3a82e-32d9-4751-aef8-0530120491d3.ocs' -- an error occurred, returned 2
    Alexis Mousset
    @amousset
    if you run the inventory with -i do you have more info about the error?
    Suvi
    @Suvi8

    @Suvi8 Is it a specific instance typeor OS that fails with this error?

    no its not specific on OS Type, it worked once for all, but after Rudder Upgrade it stopped...i guess

    skygeneve
    @skygeneve
    @amousset nope same info
    @Suvi8 is a EC2 vm amazone
    Nicolas Charles
    @ncharles
    you can run the command /opt/rudder/bin/run-inventory --debug --local=/var/rudder/tmp/inventory/euw2-vvis-mis-dev-lx-ldnlngpy1-ec2-c4c3a82e-32d9-4751-aef8-0530120491d3.ocs
    @skygeneve it would add more details on why it fails
    skygeneve
    @skygeneve
    ok thank you
    seems that there is and RO file
    /opt/rudder/bin/run-inventory: 37: /etc/profile: TMOUT: is read only
    skygeneve
    @skygeneve
    all good thanks for your help
    Haneef haroon
    @haneef_haroon_twitter
    I am trying rudder-server on centos 7 but jetty service is not starting after the installation. error: Finished command related to promiser '/bin/systemctl --no-ask-password start rudder-jetty.service' -- an error occurred, returned 1
    error: Method 'ncf_services' failed in some repairs
    error: Method 'service_action' failed in some repairs
    error: Method 'service_start' failed in some repairs
    error: Method 'service_started' failed in some repairs
    E| error server-roles Check jetty process jetty service running could not be repaired
    E| compliant server-roles Check jetty boot script jetty service enabled was correct
    error: Method 'rudder_generic_service' failed in some repairs
    Francois Armand
    @fanf
    hello @haneef_haroon_twitter . What version of rudder did you tried? Is there anything relevant on /var/log/rudder/webapp/2020_11_30_stderrout.log (look for ERROR)? If no, or if the log file is missing, perhaps in /var/log/rudder/webapp/java.log or /var/log/rudder/install/rudder-server-root-*.log ?
    Haneef haroon
    @haneef_haroon_twitter
    I tried with 6.1 and 6.2 as well. I ran into the same issue. java.log is empty. I dont see any errors in the other log files mentioned
    Francois Armand
    @fanf
    @haneef_haroon_twitter can you try a direct systemctl start rudder-jetty and send me /var/log/rudder/webapp/2020_11_30_stderrout.log (or post it somewhere, in private message for ex)
    1 reply
    AlexanderT
    @ati_ito_twitter
    Heyyo, I made a fresh installation of Ubuntu 20.04 on my laptop and now I am not receiving any policy from Rudder Server. I was able to accept my node, but after that there is no communication. Network is okay and checked by our admin. Any ideas?
    Francois Armand
    @fanf
    @ati_ito_twitter perhaps check allowed networks in rudder > settings. With a laptop, it's possible that your IP range is dynamic (depending on your current location), and that the current one is not allowed.
    that being said, I'm not sur I understood: did you install a rudder agent on the laptop, or is it that you have on your laptop a whole env for testing (vm for rudder root server, vm for node with agent, etc) ?
    AlexanderT
    @ati_ito_twitter

    Hi @fanf, thanks for your answer. On our server is any network allowed. My problem is, that the laptop is not receiving any policy from the server, which is not on the same device. I tried "rudder agent factory-reset" and also another hostname, nothing helps:

    root@ubuntu6:~# rudder agent run -ui
    Rudder agent 6.1.6-ubuntu20.04
    Node uuid: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    R: *

    • rudder-agent could not get an updated configuration from the policy server. *
    • This can be caused by: *
      • an agent key that has been changed *
      • if this node is not accepted or deleted node on the Rudder root server *
      • if this node has changed policy server without sending a new inventory *
    • Any existing configuration policy will continue to be applied without change. *

    error: Rudder agent policies could not be updated.
    Start execution with config [0]

    rudder info: Automatically promoting context scope for 'heartbeat_sent' to namespace visibility, due to persistence
    R: [INFO] Starting CFEngine 3.15.1 on host ubuntu6 (ubuntu_20 x86_64)
    M| State Technique Component Key Message
    E| compliant Common ncf Initialization Configuration library initialization was correct
    E| error Common Update Cannot update configuration policy
    R: *

    • rudder-agent could not get an updated configuration from the policy server. *
    • This can be caused by a network issue, an unavailable server, or if this *
    • node was deleted from the Rudder root server. *
    • Any existing configuration policy will continue to be applied without change. *

    E| compliant Common Security parameters The internal environment security is acceptable
    E| compliant Common CRON Daemon Cron daemon status was correct
    E| compliant Common Compute inventory splay rudder_run_invent| Scheduling rudder_run_inventory was correct
    info Inventory inventory An inventory was already sent less than 8 hours ago
    E| compliant Inventory inventory Next inventory scheduled between 00:00 and 06:00

    Summary

    6 components verified in 4 directives
    => 6 components in Enforce mode
    -> 5 compliant
    -> 1 error

    Vincent Membré
    @VinceMacBuche
    if you do a factory-reset you have to accept the node again, (factory reset makes this nodes a new node, with a new id and a new key, you have to run a new inventory from the node with rudder agent inventory then accept it again in the web interface (and you may also delete the old node )
    Did you set the allowed networks to 0.0.0.0/0 ?