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
    wit ^Crudder debug: select(): -2
    wit rudder verbose: Closing listening socket
    wit rudder debug: Yielding lock 'lock.server_cfengine_bundle.server_cfengine.-bal-backup._var_rudder_cfengine_community_inputs_promises_cf_5056_MD5=ce9ed37b30768afd47469328cfbf1bdc'
    wit rudder debug: Entry not found in '/var/rudder/cfengine-community/state/cf_lock.lmdb': MDB_NOTFOUND: No matching key/data pair found
    Alexis Mousset
    @amousset
    Ok, might be normal actually. Could you run rudder agent update on a node using this server as policy server and see if it is visible in the logs?
    Rudder Chatbot
    @rudderbot
    wit this error is from the node
    wit rudder agent update on the node giver the "no suitable servers found error"
    wit the node is in the server but not updating since this update
    Alexis Mousset
    @amousset
    "no suitable server found" while the cf-serverd was running on the server and showing no log about the node?
    Rudder Chatbot
    @rudderbot
    wit cf-serverd doesn't start on this node
    wit maybe I just reinstall
    wit i have a more serious problem though since updating to v6
    Alexis Mousset
    @amousset
    you need to run cf-serverd on the server and the update on the node
    Rudder Chatbot
    @rudderbot
    wit zabbix_agentd: /opt/rudder/lib/libcurl.so.4: no version information available (required by /usr/sbin/zabbix_agentd)
    wit my zabbix agent is no longer starting seems to be due to rudder
    wit removing rudder from this node now allows zabbix to run
    Alexis Mousset
    @amousset
    Do you have a /etc/ld.so.conf.d/rudder.conf on the nodes having the problem?
    This should have been removed some time ago but if you upgraded from very old agent version we may be missing the cleanup script
    Rudder Chatbot
    @rudderbot
    wit I do yes
    Alexis Mousset
    @amousset
    From which version did you upgrade the agents?
    Rudder Chatbot
    @rudderbot
    wit i've never jump versions when upgrading.
    Alexis Mousset
    @amousset
    Ok, you can remove the file and run ldconfig, it should fix the zabbix agent
    Rudder Chatbot
    @rudderbot
    wit for my old oner. from 4 to 4.1 to 4.2 to 5 to 6
    Alexis Mousset
    @amousset
    I'll check when the migration script for this was removed
    Alexis Mousset
    @amousset
    I'm adding it back to 6.0 postinst too Normation/rudder-packages#2192
    maybe the 5.0 postinst script failed
    Matthew Frost
    @mattronix
    was SELinux in the end XD
    Alexis Mousset
    @amousset
    With Rudder 6.0?
    Matthew Frost
    @mattronix
    yep
    we have another issue howerver
    our agents show last status connected as never
    and we are not sure why
    debug, inventory, status, health, cfservered all looks good
    agents can access ports 443
    and the cfengine port
    no syslog anymore right?
    Alexis Mousset
    @amousset
    Is the compliance ok?
    where do you see the never connected status?
    Matthew Frost
    @mattronix
    portal
    nope
    grey
    Alexis Mousset
    @amousset
    Ok, then it's a reporting problem. What does systemctl status rudder-relayd give on the server?
    Matthew Frost
    @mattronix
    checking now
    looks good
    no issues from what i see
    Matthew Frost
    @mattronix
    found its a network issue
    sorry for wasting your time
    Matthew Frost
    @mattronix
    was UDP syslog actully tho
    Alexis Mousset
    @amousset
    Ok :)
    If you still have access to the server where the SELinux problem occurred, could you send the output of grep denial /var/log/audit/audit.log so that we can find the cause?