Thread Starter
IvanRF
(@ivanrf)
Do you want to see the list of cron jobs? I have Wordfence installed and it has that functionality (to avoid installing a new plugin)
Hi,
I’m not familiar with Wordfence’s list of cron jobs, and if it has what is needed – but, there’s no harm in showing it, and then we can see.
David
Thread Starter
IvanRF
(@ivanrf)
I’ve already sent it to your email.
Thread Starter
IvanRF
(@ivanrf)
I had this values:
updraftplus_last_lock_time_ 2015-10-10 04:53:02 yes
updraftplus_last_lock_time_d 2015-10-28 04:25:26 yes
updraftplus_last_lock_time_f 2015-10-24 04:56:34 yes
updraftplus_last_lock_time_fd 2015-10-17 04:52:25 yes
updraftplus_locked_d 1 yes
updraftplus_locked_f 1 yes
updraftplus_semaphore_ 0 yes
updraftplus_semaphore_d 1 yes
updraftplus_semaphore_f 1 yes
updraftplus_semaphore_fd 0 yes
updraftplus_unlocked_ 1 yes
updraftplus_unlocked_fd 1 yes
I just delete them, let’s see what happens in the next backups.
Thread Starter
IvanRF
(@ivanrf)
David, for the last 4 days the DB backups were successful after removing semaphores data from the database. I’m marking this as resolved for now.
If you had similar issues in the past, maybe the “semaphores cleanup” should be implemented in the plugin.
Thread Starter
IvanRF
(@ivanrf)
Unfortunately, it started failing again. On November 4 and 6 (today), it couldn’t finish with the DB backups. Same message as before Failed to gain semaphore lock.
Any thoughts about a definitive solution? “semaphores cleanup” only worked for a week…
Hi Ivan,
The semaphore lock is time-based (https://en.wikipedia.org/wiki/Semaphore_%28programming%29), and can only lock for a maximum of 5 minutes, unless the time makes drastic changes (of hours, or days) on your server. If you, in MySQL, SELECT all those semaphore fields, what are their current values?
David
In your original report…
Another process starts (91s later)
Failed to gain semaphore lock
Another process starts (14s later)
Failed to gain semaphore lock
When you say “another process starts”, what does this refer to? Who starts the process – do you hit “Backup Now” again? If so, you just need to wait 5 minutes before doing so, for the lock to clear.
David
Thread Starter
IvanRF
(@ivanrf)
No, when I said “Another process starts” I was referring to a new log, the “seconds later” is the difference between the logs time in the first line.
Thread Starter
IvanRF
(@ivanrf)
Last night it worked. This are the current values:
updraftplus_last_lock_time_d 2015-11-07 04:32:24 yes
updraftplus_last_lock_time_f 2015-11-07 04:56:49 yes
updraftplus_locked_d 1 yes
updraftplus_locked_f 1 yes
updraftplus_semaphore_d 1 yes
updraftplus_semaphore_f 1 yes
Thread Starter
IvanRF
(@ivanrf)
I’m going to ask this again, since we are dealing with the wp_options table.
I had some unexpected behaviors with other plugins caused by W3 Total Cache with object and database cache enabled. Could that affect your db backup implementation?
I mean, could database cache be messing around with your semaphore values?
No, when I said “Another process starts” I was referring to a new log
So, how does this new process start? If it’s not you hitting “Backup Now”, then what is starting the new backup??
I mean, could database cache be messing around with your semaphore values?
I don’t have any knowledge about this – I’m not familiar with what WT3C’s database cacheing does, or how it works. All I can say is that we’ve not heard of a problem so far. Though, I’m still not clear on the parameters of your problem – the unclear thing currently is why there appear to be multiple backups starting shortly after eachother.
David
Thread Starter
IvanRF
(@ivanrf)
So, how does this new process start? If it’s not you hitting “Backup Now”, then what is starting the new backup??
I’m always talking about scheduled backups, I don’t have any issues with manual backups.
Thread Starter
IvanRF
(@ivanrf)
the unclear thing currently is why there appear to be multiple backups starting shortly after eachother
Days ago, I sent you the log files. You can check the times for each log there.
