Forum Activity for @soaringeagle

backup worker doesnt finish working

Installation and Configuration

where is their error logs i only thought aboyut ffmpeg cause both seem to work a certain amount of time.. then never actually finish the work

backup worker doesnt finish working

Installation and Configuration

nope even more limited then that only traces these events
jrCore_download_file - A user downloads a file
jrCore_stream_file - A user streams a file
jrEvent_attending - User clicks the attending button for an event
jrFoxyCart_vault_download - User downloads a Vault File
jrUser_login_success - User logs into the system
jrUser_signup_activated - A new user activates their account

does 'worker' have a process or anything that can be traced??
a script?
i totaly think i must be running into a timeout somewhere

backup worker doesnt finish working

Installation and Configuration

perfect! wait i dont think that is i think thats what i attemped to use to send an email when blogs are posted..which never worked

backup worker doesnt finish working

Installation and Configuration

this might be related to other or possibly all other issues ive been having
backup workers dont seem to finish working others often need resetting i still have no restores saved
i wonder if its related to the ffmpeg only "working so long then stopping
but the queue thing stays active
is there a way to add a trace of what the workers working on so you can see if its still working where it stops working (both time and function/data) to try to figure it out?
how common is it for workers to get stuck i mean you added a reset and delete for a reason would a trace help stop them from gertting stuck?

updated by @soaringeagle: 03/05/18 12:20:18PM

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

virginia worked

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

ill try virginia 1st, then tokeo
i was wondering the exact same thing!
since thats all i changed thats all it could be just cause i had a huge lot of data hoped to transport it closer

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

wait found this

i think it was a change on amazon then?

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

sent credentials
but heres something else
hourly backup of db is backing up only 145 megs about and i swear that db is over 2 gigs

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

ive generated key after key and created 3 buckets
i'll do it again and send it to ya but do you think the firewalling might be the issue? is that worth checking/ do you know the ip to whitelist?

db system backup error Invalid AWS setting - unable to store test file to S3

Using Jamroom

nope just did the whole process over new access key new bucket all defaults..nothing
hmm
do i need to whitelist amazons ip maybe?
if your certain nothing on their ends changed (and you can set it up on a new dev site with new access code and new bucket) then the only other thing i can imagine iis the servers firewall has to whitelist the ip