Rootjazz

I see this often. It does seem that you can "warm" the accounts out of it with Twitterdub, but it takes some time and it doesn't seem to be a science. When I do moderate amounts of likes, tweets, follows etc the accounts often unlock within a few days, but some do not for several weeks. Yo...

One more update for now. To check if I had some kind of corrupted installation or data I tested this on another instance of TwitterDub I have that runs only about 70 accounts in a different niche. Exactly the same issue when I ran DM's across all accounts in parallel, existing global logs were shrun...

Tested overnight with just a single processor thread. Works absolutely fine, all global logs steadily increasing in size. However, it's far too slow to possibly send DM's across all accounts. @Martin, as far as I can tell some kind of lock occurs when multiple threads try to update the logs simultan...

Testing more, running smaller jobs again, 1 acct per job sending between 3 and 15 DM's. I queued up about 50 jobs, but only let the processor run 3 threads. Running 3 jobs in the processer logs seemed to be surviving. Soon after adding a 4th thread one of the large global logs was shrunk, 3.5mb down...

Tried again, restored my backups of the global logs, and created 4 jobs this time, each shared across approx 50 accounts. The same problem, within 5 minutes I noticed the global logs had been shrunk to a few KB. Tried running a single job across 810 accts overnight, just enough to send 1 DM from eac...

Resubmitted logs just after I found the above issue: 27187

Hi Martin,

Quick update, things were running fine until I tried to run 20 parallel threads (1 acct per thread sending DM's). Within a few minutes something happened and shrunk the newest log file down to 22.7 KB (from 3541 KB).

So possibly there is an issue with parallel threads clashing...

Hi Martin, I've done a ton of testing and recorded everything. Sorry for the massive reply, but hope the info is helpful: 1) Deleted existing raw logs 2) Confirmed there are two existing global DM logs, the original, and the one that got added when I ran "Convert Shared to Global" 3) Check...

Logs submitted: 41644

So set up a DM test using custom search to return 10 records max, and set the max actions for the job to 10 also. The thinking was, there SHOULD be some accounts that have already been processed, so I'd see less than 10/10 success in the completed jobs. Ran this job across many accounts and checked ...