Unable to export

  • Resolved Anonymous User 15985895

    (@anonymized-15985895)


    6 years, 1 month ago

    Hello guys and gals,

    I have a customers site online and a lokal copy hosted in a laravel homestead virtual machine. As I usually do with several wp projects, I set them up locally first and then deploy iterations to the staging server. I use All-in-One WP Migration most of the time for that.

    Sometimes I do changes on the staging server together with the customer and migrate those changes back to local, too.

    As of late, I get the following error when trying to create a backup from the virtual machine:

    Unable to export

    Unable to open file for writing. File: /home/vagrant/code/premium-body-lounge/wp-content/plugins/all-in-one-wp-migration/storage/n6ee0807a42q/pbl.test-20181004-145358-109.wpress

    It still works the other way round (staging -> local).

    I checked for file and folder permissions, so that does not seem to be the issue. Any idea?

    Thank you for the nice plugin and your support.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Anonymous User 15985895

    (@anonymized-15985895)

    The error log states:

    Oct 04 2018 14:55:28
    {“Number”:2,”Message”:”fopen(\/home\/vagrant\/code\/premium-body-lounge\/wp-content\/plugins\/all-in-one-wp-migration\/storage\/n6ee0807a42q\/pbl.test-20181004-145358-109.wpress): failed to open stream: Text file busy”,”File”:”\/home\/vagrant\/code\/premium-body-lounge\/wp-content\/plugins\/all-in-one-wp-migration\/lib\/vendor\/servmask\/archiver\/class-ai1wm-archiver.php”,”Line”:84}

    Oct 04 2018 14:55:28
    {“Number”:2,”Message”:”unlink(\/home\/vagrant\/code\/premium-body-lounge\/wp-content\/plugins\/all-in-one-wp-migration\/storage\/n6ee0807a42q\/pbl.test-20181004-145358-109.wpress): Text file busy”,”File”:”\/home\/vagrant\/code\/premium-body-lounge\/wp-content\/plugins\/all-in-one-wp-migration\/lib\/vendor\/servmask\/filesystem\/class-ai1wm-directory.php”,”Line”:56}

    Oct 04 2018 14:55:28
    {“Number”:2,”Message”:”rmdir(\/home\/vagrant\/code\/premium-body-lounge\/wp-content\/plugins\/all-in-one-wp-migration\/storage\/n6ee0807a42q): Directory not empty”,”File”:”\/home\/vagrant\/code\/premium-body-lounge\/wp-content\/plugins\/all-in-one-wp-migration\/lib\/vendor\/servmask\/filesystem\/class-ai1wm-directory.php”,”Line”:60}

    Plugin Author Pim J. Iliev

    (@pimjitsawang)

    Hi nativebug,

    We are sorry to hear that you are having issues.
    The plugin needs to have space and access to be able to function on your site.
    Can you check that you have set permissions on your wp-content directory to 775 recursively and that you have enough disk space on the server to save the site 2.5 times?

    Best,

    Plugin Author Pim J. Iliev

    (@pimjitsawang)

    Please feel free to write to us at support at servmask.com for urgent assistance.

    Thread Starter Anonymous User 15985895

    (@anonymized-15985895)

    Hello @pimjitsawang and thanks for your reply.

    As stated in my initial comment, I had checked and set the file permissions. Additionally, there is still around 40 GB left of storage in the virtual machine.

    The error persists.

    Thanks for your support.

    Best

    Plugin Author Yani

    (@yaniiliev)

    @nativebug

    Try to uninstall the plugin and reinstall it.
    Repeat the export process.

    Thread Starter Anonymous User 15985895

    (@anonymized-15985895)

    Hello @yaniiliev,

    Thank you for chiming in. I did reinstall the plugin a couple of times before. Sadly to no avail.

    Greetings

    Plugin Author Yani

    (@yaniiliev)

    @nativebug

    The only other thing that I can think of is if the folder you are installing the plugin is on a mounted device/disk – if that is the case, the mounting could be the case as it changes its permissions depending on its mounting definition.

    Storage folder is created by the plugin itself so the plugin should be able to create files. Something happens when the plugin is installed and when you click on an export – it could be a server software that changes permission, security plugin, or something else.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Unable to export’ is closed to new replies.