Support » Plugin: All-in-One WP Migration » There is not enough disk space – Amazon RDS Import

  • Resolved Ben

    (@cyberliciousben)


    Hi,

    We’re trying to utilize the plugin for third-party migrations. We’re using Amazon RDS in AWS instead of MySQL for additional security and performance goodness. We received this message:

    There is not enough space available on the disk.
    Free up 678.94 MB of disk space.

    The file itself is 189.47 MB creating this 868.41 MB space that we have no idea where it’s even coming from as we currently have 6.1 GB available. What else is it looking for, and will it work with Amazon RDS? The DB credentials for RDS are still handled through wp-config.php so I’m not sure where to even begin looking.

    Thanks in advance for your help,
    Ben

    The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Yani Iliev

    (@yaniiliev)

    Yes, the plugin will work with RDS.
    The message indicates that there is not enough disk space for the plugin to import/restore the backup file. This is not related to RDS but to the instance where WordPress is running.

    Ben

    (@cyberliciousben)

    Hi Yani,

    Thanks for the quick response. It’s great that it’ll work with RDS as I thought it would. We click the “I have space” button, and it just shows the bar stuck at 0%. We’re on a m4.large with a 8GiB EBS with 6.1GiB avail. Is there anything else we should be looking at? We also have CloudFront running off the ELB, but plan to move it to read from an S3 bucket.

    Plugin Author Yani Iliev

    (@yaniiliev)

    Do you have permission setup correctly?
    Maybe turn off SeLinux?
    Something is telling PHP that it cannot write data to the filesystem.

    Ben

    (@cyberliciousben)

    Will double check but we should have 2775 on the directories and granted all permissions on the DB.

    Ben

    (@cyberliciousben)

    ^granted all privileges…

    Plugin Author Yani Iliev

    (@yaniiliev)

    The plugin is calling disk_free_space with wp-content/plugins/all-in-one-wp-migration/storage as argument. The function returns size that is less than the size of the file that you are importing.

    
    $path = 'wp-content/plugins/all-in-one-wp-migration/storage';
    $disk_free_space = disk_free_space($path);
    if ($disk_free_space < $upload_file_size * 2) {
        // display a message that there is not enough disk space
    }
    

    You need to figure out why disk_free_space reports that there is not enough available space. I mentioned SeLinux and permissions, it might also be where WordPress install is being mounted. I am out of ideas. This is quite specific to the environment that PHP/WordPress is running on.

    Ben

    (@cyberliciousben)

    What about Amazon EFS? The EFS is essentially mirroring websites in two separate availability zones just in case Godzilla crushes one.

    Plugin Author Yani Iliev

    (@yaniiliev)

    I am not familiar with Amazon EFS and what implications it will have on PHP and WordPress.
    You should consider hiring someone so that you can give them direct access to the site for a far more efficient fix than we can provide here.

    Please try https://jobs.wordpress.net/ and do not accept any hire offers posted to these forums.

    Ben

    (@cyberliciousben)

    We have about 8 AWS certified cloud engineers currently working on it. We paid for this plugin, and it’s S3 extension for backups. So are you telling me you haven’t tested this with Amazon’s Elastic File System? It’s right here in their beautiful documentation. Looking forward to your response, and how you’ve tested it or plan to for the sake of your users and sales.

    Ben

    (@cyberliciousben)

    The EFS is for 99.9999% uptime.

    Plugin Author Yani Iliev

    (@yaniiliev)

    You should have started with this.

    We paid for this plugin, and it’s S3 extension for backups

    For premium products please reach over to our support team.
    Premium products are not supported on these forums.

    Ben

    (@cyberliciousben)

    Ok great! Yeah, WordPress codex isn’t that complicated but I do appreciate you judging my expertise. /s

    Ben

    (@cyberliciousben)

    RESOLVED! The plugin had issues reading the file space on the EFS using the ‘File’ import. We had to drop the file in from the bastion server into the web server’s /wp-content/ai1wm-backups/ directory then use the ‘Restore’ from the Backup option.

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.