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

Error message when running backup: In Filesystem.php line 104:Failed to create "/tmp/backup/b6dc026e-7dfb-4667-bf24-7e72fc2856b3": mkdir(): No such file or directory.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not an issue
    • Affects Version/s: 15
    • Fix Version/s: None
    • Component/s: Backup & Restore
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      18.11.1
    • Distro:
      PBXinaflash

      Description

      When performing backup of installed PBX (Asterisk 18.11.1, FreePBX 15.0.22) an error message is presented: "There was an error during backup"

      and:

      In Filesystem.php line 104:

      Failed to create "/tmp/backup/7312ce51-db51-440f-991d-3be63a7a3113": mkdir(
      ): No such file or directory. 

      The inability to perform installed system backups makes maintaining backups impossible. The problem appeared after performing the FreePBX RCE Security Vulnerability fix as well as several module updates a few days ago. Prior to these updates and the fix, backup functioned properly.

       

      This issue occurs if the /tmp folder contents have been deleted - either in error or purposefully. (rm -rf /tmp/*). The files in the /tmp folder are "temporary" and anything used for processing data, i.e., data from the backup & restore module, should be created as needed.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                prasanthm Prasanth Mohan
                Reporter:
                geopeterwc geopeterwc
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

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