Patches

-nologs doesn't help im afraid :(

I am having these crashes also. At first I thought they were related to overlays or overclocking. I set my CPU and GPU back to default clocks, disabled steam overlay, disabled playsTV and AMD Gaming Evolved, disabled all mods, uninstalled and reinstalled 4 times, both on my SSD and HDD. The crashes are still happening. Sometimes its just a graphics crash, I can alt tab or task manager out and rerun it. Other times I get white artifact dots on screen before it finally blacks out, and I have to hard restart my entire PC. This has only started happening over the past 4 or so days. I thought this was an issue with my PC or me alone but seeing this post, it appears not.

SealTeamSloth, an Altis Life community that has been running more than 4 years now, is looking for capable and dedicated developers to help develop our mission file further with Altis, and in the near future, work with our Development Team on the upcoming new map, Tanoa! If you are interested or want any further information, you can contact me via PM here on the forums, or you can email me at carl.patchett@hotmail.co.uk Thanks everyone!

But If I just update it to version 70, without updating to SQL_RAW_2, there won't be any errors? I have absolutely no SQL experience, so i'm completely winging it here. All I know, is, for instance, our init.sqf is "extDB2" callExtension format["9:ADD_DATABASE_PROTOCOL:Database2:SQL_RAW:%1:ADD_QUOTES",_life_sql_id]; I have no idea what other files I would have to change serverside, or in the extDB2 ini itself to get SQL_RAW_2 working without errors. And I don't know if updating to that would incur errors within our current database, as it has been running SQL_RAW this entire time.

I have been applying these updates to our servers binaries in the hopes of extending crash times and such until a real fix is found. I was wondering however, in your dropbox there is a TBB4alloc folder with static malloc libraries in there. Should these be replaced also when updating the performance binaries? Or more to the point, is it required to update these? Regards, Carl.

I noticed you recently updated to Version 70 on the github, which while contains support (I assume) for SQL_CUSTOM_V2, still uses SQL_RAW. Would it be a huge time saver for me to update our exDB2 version from 62 to 70 without having to write out and change the SQL queries, considering its still using the old query calls? as our current server is still running the old version with SQL_RAW as the protocol. Or will I still be required to update our network backend to SQL_CUSTOM_V2 to update to extDB2 Ver 70? (Also the [Main] Version = 5 line at the top, is this just for revision checking? and if so is it changable to possibly [Main] Version 70 so we know which revision we are running on the server?) Regards, Carl.

This is most likely a simple problem, but any help you could provide would help me immensely. Due to the 1.54 ArmA update crashing some life servers often (including ours) we were advised by Dwarden to make sure our extDB2 dll files are up to date. After noticing ours was hanging back at ver 62, I downloaded the latest release, ver 69, and copied the appropriate DLL's over. The server boots up fine,but the DLL is having trouble with the changes from revision 62 to 69. I have seen the changelogs, deciding to use certain protocols instead of others, but I have never really had to tangle with these before. Using revision 69 generates the pretty straightforward error: [03:27:50:849096 --5:00] [Thread 10956] extDB2: Database Type: MySQL [03:27:50:851894 --5:00] [Thread 10956] extDB2: Database Session Pool Started [03:27:50:852121 --5:00] [Thread 10956] extDB2: Failed to Load Unknown Protocol: SQL_RAW [03:27:50:877368 --5:00] [Thread 10956] extDB2: Error Unknown Protocol: 516855 Input String: 2:516855:SELECT list FROM zones WHERE id = '1' [03:27:50:885143 --5:00] [Thread 10956] extDB2: Error: Syntax error: Not a valid integer: Error Unknown Protocol [03:27:50:885179 --5:00] [Thread 10956] extDB2: Error: Input String 4:Error Unknown Protocol [03:30:25:585025 --5:00] [Thread 10956] extDB2: Stopping ... So it seems the issue is our revision 62 copy of extDB2 is using SQL_RAW as the operating protocol. And the 69 revision no longer supports that. Any idea where I would start with getting it compatible again? My current thoughts on the matter were that it would take me going through all the SQL calls in our files and changing them from the SQL_RAW layout to the new few, SQL_CUSTOM_V2 and such. Like I said, any help would be appreciated, I wasn't the one who set this system up for our life server, so I'm just trying to get it put back together again. Cheers!