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

    Issues with mail_reports.inc post upgrade to todays dev release

    Scheduled Pinned Locked Moved Plus 23.01 Development Snapshots (Retired)
    13 Posts 3 Posters 1.2k 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.
    • mtarboxM
      mtarbox @mtarbox
      last edited by

      @jimp
      Same results with tonight's release, 23.01.a.20221212.2233.
      Removed mail reports, rebooted, and reinstalled.

      Si vis pacem, para pactum.

      1 Reply Last reply Reply Quote 0
      • mtarboxM
        mtarbox
        last edited by

        Re: Issues with mail_reports.inc post upgrade to todays dev release

        And these are the emails it sends:

        X-Cron-Env: <SHELL=/bin/sh>
        X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin>
        X-Cron-Env: <LOGNAME=root>
        X-Cron-Env: <USER=root>

        Fatal error: Uncaught Error: Failed opening required 'mail_reports.inc' (include_path='.:/etc/inc:/usr/local/pfSense/include:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/') in /usr/local/bin/mail_reports_generate.php:24
        Stack trace:
        #0 {main}
        thrown in /usr/local/bin/mail_reports_generate.php on line 24

        And then about three hours later I receive this:

        X-Cron-Env: <SHELL=/bin/sh>
        X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin>
        X-Cron-Env: <LOGNAME=root>
        X-Cron-Env: <USER=root>

        eval: mail: not found
        cat: stdout: Broken pipe
        cat: stdout: Broken pipe
        cat: stdout: Broken pipe
        cat: stdout: Broken pipe
        cat: stdout: Broken pipe
        cat: stdout: Broken pipe
        cat: stdout: Broken pipe
        cat: stdout: Broken pipe
        cat: stdout: Broken pipe
        echo: write error on stdout
        echo: write error on stdout

        Si vis pacem, para pactum.

        mtarboxM 1 Reply Last reply Reply Quote 0
        • mtarboxM
          mtarbox @mtarbox
          last edited by mtarbox

          Now I know I'm effed!
          It still sends me emails, even with the package removed!
          It's borked. At least it is my home unit, and not my production unit.

          Si vis pacem, para pactum.

          1 Reply Last reply Reply Quote 0
          • Y
            yuryk
            last edited by

            I have exactly the same issue. It would help to know where this .inc should reside.

            mtarboxM 1 Reply Last reply Reply Quote 0
            • mtarboxM
              mtarbox @yuryk
              last edited by

              @yuryk because this is for a home lab, I’m just going to reformat and reinstall. I needed to update the bios on the fitlet2 anyway, so a perfect time. Flashing 2.6 now as I type this.

              Si vis pacem, para pactum.

              mtarboxM 1 Reply Last reply Reply Quote 0
              • mtarboxM
                mtarbox @mtarbox
                last edited by mtarbox

                @jimp
                And I just went through the process of re-installing 2.6, and the upgrade process to 22.01+ through to 23.01-BETA. Same issue.
                No packages other than mail reports installed. As vanilla as I can get.

                Crash report begins. Anonymous machine information:

                amd64
                14.0-CURRENT
                FreeBSD 14.0-CURRENT #0 plus-devel-main-n255994-d894b4aac11: Fri Dec 16 06:30:06 UTC 2022 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/obj/amd64/5QbEYaBj/var/jenkins/workspace/pfSense-Plus-snapshots-master-main/sources/FreeBS

                Crash report details:

                PHP Errors:
                [16-Dec-2022 14:05:59 America/New_York] PHP Fatal error: Uncaught Error: Failed opening required 'mail_reports.inc' (include_path='.:/etc/inc:/usr/local/pfSense/include:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/') in /usr/local/bin/mail_reports_generate.php:24
                Stack trace:
                #0 {main}
                thrown in /usr/local/bin/mail_reports_generate.php on line 24
                [16-Dec-2022 14:06:47 America/New_York] PHP Fatal error: Uncaught Error: Failed opening required 'mail_reports.inc' (include_path='.:/etc/inc:/usr/local/pfSense/include:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/') in /usr/local/bin/mail_reports_generate.php:24
                Stack trace:
                #0 {main}
                thrown in /usr/local/bin/mail_reports_generate.php on line 24
                [16-Dec-2022 14:07:19 America/New_York] PHP Fatal error: Uncaught Error: Failed opening required 'mail_reports.inc' (include_path='.:/etc/inc:/usr/local/pfSense/include:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/') in /usr/local/bin/mail_reports_generate.php:24
                Stack trace:
                #0 {main}
                thrown in /usr/local/bin/mail_reports_generate.php on line 24
                [16-Dec-2022 14:08:24 America/New_York] PHP Fatal error: Uncaught Error: Failed opening required 'mail_reports.inc' (include_path='.:/etc/inc:/usr/local/pfSense/include:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/') in /usr/local/bin/mail_reports_generate.php:24
                Stack trace:
                #0 {main}
                thrown in /usr/local/bin/mail_reports_generate.php on line 24

                No FreeBSD crash data found.

                Si vis pacem, para pactum.

                1 Reply Last reply Reply Quote 0
                • Y
                  yuryk
                  last edited by

                  So this is what I did:
                  Looks like the include file was not included in the build...

                  Download a copy of the missing mail_report.inc from github and copy it into /etc/inc of the pfsense. That should fix the issue....

                  1 Reply Last reply Reply Quote 0
                  • mtarboxM
                    mtarbox
                    last edited by mtarbox

                    @yuryk YOU FREAKING ROCKSTAR! That fixed the issue!
                    @jimp see the above for the fix.

                    Si vis pacem, para pactum.

                    1 Reply Last reply Reply Quote 0
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      Copying that file is the wrong fix. There is just one line that needs changed in one file to have it load the correct include path/name.

                      https://redmine.pfsense.org/issues/13773

                      https://github.com/pfsense/FreeBSD-ports/commit/9fe472d465f90fb272ae9b4edb3f1598a904c1f3

                      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                      Need help fast? Netgate Global Support!

                      Do not Chat/PM for help!

                      mtarboxM 1 Reply Last reply Reply Quote 1
                      • mtarboxM
                        mtarbox @jimp
                        last edited by

                        @jimp Thank you. I'll wait until tomorrow, tickle the system for an update and go from there.

                        Si vis pacem, para pactum.

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