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

    Mail Report not sending on schedule

    Scheduled Pinned Locked Moved pfSense Packages
    3 Posts 2 Posters 1.1k 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.
    • E
      eddi1984
      last edited by

      Hi all,

      I have configured mail report to send me daily emails. But it is not working.

      I have pfsense 2.2.4 on this machine. I also have 3 other routers running the same version and have almost similar report settings, and they work, just the one in question does not.

      I double checked the SMTP settings, and I can receive a test email. I am also able to send a test email from Mail Reports and receive it promptly.

      I also checked the crontab settings and there it is, it should work, as far as I can tell.

      CRONTAB:
      0	1	*	*	*	root	/usr/local/bin/mail_reports_generate.php 0 &
      0	1	*	*	*	root	/usr/local/bin/mail_reports_generate.php 1 &
      0	1	*	*	*	root	/usr/local/bin/mail_reports_generate.php 2 &
      

      When I checked the system logs, there is nothing in there, that suggests that mail reports tried to send and failed. Nothing, not a single line form mail reports.

      crontab also has an entry for dyndns and that is working properly, so cron is fine.

      Where else can I check, any ideas?

      See attached picture for mail reports settings that I use.

      Cheers.
      MailReportsProblem.png
      MailReportsProblem.png_thumb

      1 Reply Last reply Reply Quote 0
      • E
        eddi1984
        last edited by

        Does anybody have an idea? Any thoughts?

        Where else can I check "stuff"?

        Thanks.

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          So run the cron commands manually in console (without the trailing &) and see what happens?

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