Hey there. I created my own post so we can monitor and fix this error once and for all.
"ERROR: CRITICAL_93785439537530: Previous processed logs failed to load - please contact support and submit logs for review:"
This happen when i run the unfollow. when this error occurs, follow and unfollow wont work anymore.
This issue is in my main computer and in 1 of my server
-OS is windows 10 pro (home pc and windows 2012 (dedicated server)
-TD is using 64bit version
-specs are high, rarely reach 10% of usage
-storage have large space left
-Version: 3.3.9.764
sent the logs with ID: logs_37938
hope it can be fix asap.
Thanks
Critical error
- martin@rootjazz
- Site Admin
- Posts: 34634
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Critical error
there is a problem with your global_all file. I've seen this before, for some reason the file doesn't load, the program makes a backup and removes it, so the program should then create a new version of the file, but that also doesn't load - although when testing the file, it works perfectly for me...
Haven't solved this bug yet, but send me your database and I can try again:
Can you submit your database please
TOOLS > CREATE DB BACKUP AND SEND TO SUPPORT
then send your DB ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)
Regards,
Martin
Haven't solved this bug yet, but send me your database and I can try again:
Can you submit your database please
TOOLS > CREATE DB BACKUP AND SEND TO SUPPORT
then send your DB ID - the first 4 numbers is sufficient (displayed after successful uploading of logs)
Regards,
Martin
Re: Critical error
there i sent it.
database_backup_3.3.9.764_2023-05-28.78514128_xxxxxxxxxxx.zip
i think it has something to do with global logs. my "watchfornewfollower" instance doesn't have this error coz i dont use global logs with it. but not sure, just my observation. anyway i leave it with your expertise. hope to get a reply soon with a good news
thanks
database_backup_3.3.9.764_2023-05-28.78514128_xxxxxxxxxxx.zip
i think it has something to do with global logs. my "watchfornewfollower" instance doesn't have this error coz i dont use global logs with it. but not sure, just my observation. anyway i leave it with your expertise. hope to get a reply soon with a good news
thanks
Re: Critical error
I also notice a huge CPU usage when i run unfollow. from 1-4% to 30% and up, and that was only 1 unfollow action added
Re: Critical error
any update regarding the issue?
- martin@rootjazz
- Site Admin
- Posts: 34634
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Critical error
sorry, I downloaded your logs, they were large so took a while then I forgot. I will look today
Re: Critical error
thank you..
hope you find what causing it so we can work on update
hope you find what causing it so we can work on update
- martin@rootjazz
- Site Admin
- Posts: 34634
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Critical error
now, I'm looking now
- martin@rootjazz
- Site Admin
- Posts: 34634
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Critical error
ok so you're original global_all file failed to load as it was corrupted. The program then failed to read the new file created a few times. However, the most recent version of the file seems ok.
Let me see if the backup version of this file will be read and used when rebuilding globals
Let me see if the backup version of this file will be read and used when rebuilding globals
Re: Critical error
Ok thanks. pls let me know the result. and also if you need more logs/ files to send