1. 21 Jan, 2020 2 commits
  2. 17 Jan, 2020 2 commits
    • Maciej Lipinski's avatar
      [snmp] Bugfix: do not check startCnt when daemon is disabled. · 976c6328
      Maciej Lipinski authored
      SNMP checkes whether monitored daemons where restarted by looking
      at the respective /tmp/start_cnt_X file. Such file is not created
      if a daemon is disabled in configuration (dotconfig). Such
      disabling is a new feature. It turns out that not all of SNMP
      deamon was updated to accommodate it. The SNMP daemon was checking
      at start which daemons are disbled but later did not use this
      info in wrsStartCntGroup and the startCnt of the disabled deamons
      was attempted to be checked, resulting in an error. This has
      been fixed.
      976c6328
    • Jean-Claude BAU's avatar
  3. 14 Jan, 2020 1 commit
    • Jean-Claude BAU's avatar
      Bug fix: Monit errors appearing in syslog at startup · 65970bde
      Jean-Claude BAU authored
      As monit process is started after other processes, it does not take into
      account  the 'unmonitor' messages sent from start scripts (ldap.sh,
      ...). This generates error messages at startup.
      
      To avoid that, the configuration of monit is set now dynamically in the
      apply_dotconfig script. All disabled processes are then removed from the
      configuration to avoid errors due to process start order.
      Also the first monitoring cycle is postponed by 30s at startup.
      65970bde
  4. 13 Jan, 2020 2 commits
    • Jean-Claude BAU's avatar
      Bug fix: Cannot download dot-config (invalid hostname) · 734deab9
      Jean-Claude BAU authored
      If dot-config is read remotly using DHCP for the URL, the host name in
      the URL is not well substitute.
      The fix forces the update of "hostname" when the script
      dhcp_get_filename.sh is called.
      734deab9
    • Maciej Lipinski's avatar
      [issue #201] moved update of age-time within mutex · 85a7069b
      Maciej Lipinski authored
      The problem was as follows:
      - there were two nodes with the same MAC address, sending traffic
        at high frequency
      - the above triggers a lot of learning requests to rtud, as a result
      - rtu HASH table representation in SHMEM is constantly udpated
      - the aging process runs in background (separate process) and updates
        the time the entry was last used.
      
      The update process could not the time of last access in the HASH
      table in SHMEM because the learing process was constantly occupying
      the SHMEM. The age out process was never aging out entry (even if this
      one is within mutex) since the access time was never updated.
      
      Thus, now both, update of last access time and age-out process are
      both within mutex that allows the learning and aging-out processes
      to both access SHMEM and HW.
      85a7069b
  5. 10 Jan, 2020 6 commits
  6. 09 Jan, 2020 1 commit
  7. 08 Jan, 2020 26 commits