14:01:52: load:C:\Users\Administrator\AppData\Roaming\rootjazz\Twitterdub1\database\dbaccount\0581e2a8-7cf1-468c-81cf-5ad6de27c7fa.bin
Exception: IOException
The process cannot access the file 'C:\Users\Administrator\AppData\Roaming\rootjazz\Twitterdub1\database\dbaccount\0581e2a8-7cf1-468c-81cf-5ad6de27c7fa.bin' because it is being used by another process.
14:11:13: load:C:\Users\Administrator\AppData\Roaming\rootjazz\Twitterdub1\database\dbaccount\d1797d49-7eb0-4bb3-bb3e-059e457a7d8d.bin
Exception: IOException
The process cannot access the file 'C:\Users\Administrator\AppData\Roaming\rootjazz\Twitterdub1\database\dbaccount\d1797d49-7eb0-4bb3-bb3e-059e457a7d8d.bin' because it is being used by another process.
14:11:57: load:C:\Users\Administrator\AppData\Roaming\rootjazz\Twitterdub1\database\dbaccount\e24bf0bd-5fa6-4d4e-b570-79f5ca27ffaa.bin
Exception: IOException
The process cannot access the file 'C:\Users\Administrator\AppData\Roaming\rootjazz\Twitterdub1\database\dbaccount\e24bf0bd-5fa6-4d4e-b570-79f5ca27ffaa.bin' because it is being used by another process.
You are having massive file locking issues, which should not be possible, unless something else on OS is locking.
IF you restart the machine, does the issue persist?
do you think does global process logs (adding) have something to do with it? I dont recall and not sure if this happened before i merge the logs
additional info
-if this error occurs, the bot wont run properly until I delete the logs.
-running TD on 2 machine. 1 on server and other is my own PC. both have high RAM and processor, both still have plenty of storage. BOTH HAVING THIS ISSUE
-running TD with 69 threads. CPU usage on spike is less than 50% but normally, most of the time its less than 5%
-i only run follow, unfollow and watch for new follower
-no antivirus/ firewall running
-dont have this issue before I merge the logs (not sure though)
Is there a way to undo the merge logs? it might fix it?
or how about I install the latest stable version? (does the Maxperaccount is working on the latest stable version?)
hope we can fix this issue asap. error occurs everyday and deleting the logs reduces my activity (following user already followed by others)
lavalamp wrote: ↑Thu Jan 12, 2023 3:11 pm
ok restarted it and error still there.
do you think does global process logs (adding) have something to do with it? I dont recall and not sure if this happened before i merge the logs
additional info
-if this error occurs, the bot wont run properly until I delete the logs.
-running TD on 2 machine. 1 on server and other is my own PC. both have high RAM and processor, both still have plenty of storage. BOTH HAVING THIS ISSUE
both machines running the same actions in the same way?
-running TD with 69 threads. CPU usage on spike is less than 50% but normally, most of the time its less than 5%
Is that within action threads, or processor action threads?
If you run a single action with in action ONE thread and in ONE thread on processing tab, does the issue still occur?
Is there a way to undo the merge logs? it might fix it?
IF you know the date of the merge, you can use the nearest backup files to there, but will result in some data loss (happened since backward date)
It might be the unfollow. Im still observing it
since I pause the unfollow, error didn't appear til now for 5 days
my settings for unfollow are
threads: 20 (action threads)
account inside the unfollow is 300+ (300+ account for 1 unfollow action with 20 threads) that might causing the problem.)
im still observing and will let you know if it still occur
lavalamp wrote: ↑Tue Jan 17, 2023 1:15 pm
It might be the unfollow. Im still observing it
since I pause the unfollow, error didn't appear til now for 5 days
my settings for unfollow are
threads: 20 (action threads)
account inside the unfollow is 300+ (300+ account for 1 unfollow action with 20 threads) that might causing the problem.)
im still observing and will let you know if it still occur
ok so the issue only appears to happen with a GROUP UNFOLLOW with 300 accounts and 20 threads within the group unfollow.
Let me check what happens in group actions with regards to this issue...