Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-9164

Freepbx.log huge and crashes system when drive full

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 12
    • Fix Version/s: 12, 13
    • Component/s: Asterisk Logfiles
    • Labels:
      None
    • ToDo:
    • Distro Version:
      6.12.65-26
    • Distro:
      FreePBX Distro

      Description

      A couple of times now in the last 3 months I have had the Freepbx.log file become huge 43G, which in turn fills the /dev/mapper/vg_ha-slash, and crashes Mysql making the system crippled. After deleting the file and rebooting the whole Server it works fine. The snipping of the log file i got was the below repeated. I am sorry i needed to get the system back up and running so I did not have time to investigate too much.

      [2015-Apr-27 10:56:01] [PHP-WARNING] (/var/www/html/admin/libraries/php-asmanager.php:266) - fgets(): 490 is not a valid stream resource
      [2015-Apr-27 10:56:01] [PHP-WARNING] (/var/www/html/admin/libraries/php-asmanager.php:262) - feof(): 490 is not a valid stream resource
      [2015-Apr-27 10:56:01] [PHP-WARNING] (/var/www/html/admin/libraries/php-asmanager.php:266) - fgets(): 490 is not a valid stream resource
      [2015-Apr-27 10:56:01] [PHP-WARNING] (/var/www/html/admin/libraries/php-asmanager.php:262) - feof(): 490 is not a valid stream resource

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                GameGamer43 Bryan Walters
                Reporter:
                cwoolverton thelkyone
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.