Viewing 7 replies - 1 through 7 (of 7 total)
  • Can it that your hoster is Strato ?
    Strto only allows crating of files with 64MB. If the file goes over that size this message cames up. Ther is no workaround for that. Only one you can do is switsh the hoster.

    I get the same error message Signal “SIGXFSZ” was sent to script.
    Using a Strato Account, but I am not trying to store on the strato account, I tried to store at Dropbox. Is it the same reason that it does not work, as the file has to be generated first on the strato domain and after that would be transferred to Dropbox?

    Daniel Hüsken

    (@danielhuesken)

    The Backup Archive must be completly genereate on Strato bevor it can sent to Dropbox. And that is the bottelneck.

    Ganescha

    (@ganescha)

    Thanks Daniel,
    just good to know that it’s a problem with the Strato account and not a problem “between my ears” ??
    So I chose another workaround.. without a plugin. Just using ftp and the cpanel. Works fine too.
    Thanks again for your support!

    do you plan to implement the ability to chunk archive size like the updraft-guys do? and/or using a different zip-engine like they offer via wp-setup define?

    the other plugin has a couple of issues I don’t like, but at this point it’s the only way to create backups for one of my customers with such a crippled strato account.

    We will look in future what we can do.

    cheers!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘ERROR: Signal "SIGXFSZ" was sent to script’ is closed to new replies.