Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Prob with built on Thu Oct 14 02:17:37 EDT 2010

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    4 Posts 4 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jimminy
      last edited by

      In System Logs under System, it just keeps repeating this (and so it continues..)
      Oct 15 20:40:01 last message repeated 2 times
      Oct 15 20:30:00 last message repeated 2 times
      Oct 15 20:20:00 last message repeated 2 times
      Oct 15 20:10:01 last message repeated 2 times
      Oct 15 20:00:00 last message repeated 2 times
      Oct 15 19:50:00 last message repeated 2 times
      Oct 15 19:40:00 check_reload_status: check_reload_status is starting.

      1 Reply Last reply Reply Quote 0
      • B
        BlueMatt
        last edited by

        The problem here is check_reload_status was rewritten to call a child process, thus meaning every time you call check_reload_status, you get two processes.  However, /usr/local/bin/checkreload.sh, was not rewritten.  Thus every five minutes when checkreload.sh gets run, it finds two processes and thinks this is in error, so kills them both and restarts check_reload_status.  Thus, the two 1s in the if statements in /usr/local/bin/checkreload.sh simply need changed to 2s.

        1 Reply Last reply Reply Quote 0
        • C
          clarknova
          last edited by

          Seeing the same thing here.

          2.0-BETA4  (i386)
          built on Thu Oct 14 01:16:12 EDT 2010
          FreeBSD 8.1-RELEASE-p1

          db

          1 Reply Last reply Reply Quote 0
          • E
            eri--
            last edited by

            Should be fixed on latest versions.
            Mostly disable the cronjob it is not needed anymore.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.