Automatic update not updating...

Zero

New Member
Log:

TitleAutomatic update notification!
Message[2020-05-13 00:00:02] - Acquiring the mutex lock...
[2020-05-13 00:00:02] - Checking the system for all functions and binaries...
[2020-05-13 00:00:02] - All functions and binaries are in place, we can continue...
[2020-05-13 00:00:02] - Fetching latest version number...
[2020-05-13 00:00:02] - Trying to backup the app before the upgrade...
[2020-05-13 00:00:02] - The backup manager extension is missing or is disabled, no backup can be made!
[2020-05-13 00:00:02] - Fetching the file signature...
[2020-05-13 00:00:02] - The file signature is 4ba361f89ececa3f48ee8a999c1886f49846ce1d
[2020-05-13 00:00:02] - Downloading the update file, this might take a while...
[2020-05-13 00:00:04] - Download complete, checking the signature...
[2020-05-13 00:00:04] - Server response is correct, unzipping the file...
[2020-05-13 00:00:09] - Waiting for running campaigns to finish...
[2020-05-13 00:00:09] - Done waiting for campaigns to finish, it took 0 seconds!
[2020-05-13 00:00:09] - The archive has been unzipped successfully, trying to copy the files over...
[2020-05-13 00:00:10] - Unable to copy the files in the right location!
Date added5/12/20, 8:00 PM
 
This happens when your existing files are owned by a linux user, say root and your are running the cron jobs as another user, a web user for example, and the second user does not have enough permissions to overwrite existing files, since they aren't owned by it.
I would check and make sure all your mailwizz files are owned by the same user under which you have added the cron jobs.
 
Back
Top