Announcement

Collapse
No announcement yet.

Report delivery time different after upgrade

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Report delivery time different after upgrade

    Hi,

    So I know that you cannot change the time that the daily reports are run. 2:00am local time is when they are supposed to run and that is what I am expecting.

    I was on 16.5 and it was working fine. 2am, all the time.

    I upgraded to 16.6.2 and reports changed to 6:00pm MST. I am in Denver, CO. My date / time is correct with NTP on server. What changed? I swear I have seen this in the past and there was some setting that needed to be changed and reports went back to 2am.

    Thank you,

    Jeff

  • #2
    You certainly can change the report time. There's no GUI support for it, but the time is based on jobs in the crontab . Look at /etc/cron.daily/reports_cron from the command line to see the reports commands, and /etc/crontab to see what time the daily cron is run, just like any linux system.

    Of course, you need to keep in mind any changes will likely be reverted at upgrade, and I'm not actually suggesting you edit this. What I am saying is you can look in the cron entries to see what's actually there, and based on that perhaps find a resolution.

    Interestingly, my main system shows this, which looks like 1:12 AM rather than 2:
    Code:
    12 1    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
    My home system looks like this, which is 1:05 AM:
    Code:
    5 1    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
    Last edited by jcoehoorn; 02-18-2023, 11:19 AM.
    Five time Microsoft ASP.Net MVP managing a Lenovo RD330 / E5-2420 / 16GB with Untangle 16.5.2 to protect a 1Gbps fiber link for ~450 residential college students and associated staff and faculty

    Comment


    • #3
      So this is interesting.

      17 1 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

      That means 1:17am. I had forced an NTP sync earlier today, even though I had current time. Guess I will see if I get reports in the 6pm hour again or 1am. Thanks for the info.

      Jeff

      Comment


      • #4
        I suspect this is a time zone issue, but one thing you certainly could do is add a simple file to /etc/cron.daily with a command to write a timestamp to a file
        Five time Microsoft ASP.Net MVP managing a Lenovo RD330 / E5-2420 / 16GB with Untangle 16.5.2 to protect a 1Gbps fiber link for ~450 residential college students and associated staff and faculty

        Comment


        • #5
          It's definitely a time zone issue. 6pm MST is 1am UTC and the cron shows 1:17 am. The reports are running at 2am UTC and not 2am local time. I received my reports at 6:31pm MST last night. I will play around with the cron job and see what I can come up with.

          Comment


          • #6
            PS:What is the output of date? It is 2:38:03 PM MST. FYI
            Code:
            # date
            Mon 20 Feb 2023 02:38:03 PM MST​
            PS: The forum thinks I posted this at Today, 03:39 PM. The time zone is set to MST. LOL
            Last edited by donhwyo; 02-20-2023, 01:43 PM.

            Comment


            • #7
              The system date / time is correct.

              [root @ untangle] ~ # date
              Tue 21 Feb 2023 06:31:13 AM MST
              [root @ untangle] ~ #

              ​It's 6:32am here. MST.

              Things are processing as UTC time. Last night I received a quarantine digest at 11:00pm MST. (6am UTC) It is set in the email settings to run at 6am MST.

              So something is not right with the timezone conversion after the upgrade.

              Comment

              Working...
              X
              😀
              🥰
              🤢
              😎
              😡
              👍
              👎