#[LB-Phone] RAGE ERROR: Unknown

1 messages · Page 1 of 1 (latest)

wispy breach
#

Hello!
This has taken about 3 weeks of testing but we finally narrowed down our RAGE ERROR: Unknowns.

It seems something POST Phone update 2.2.0.
We updated to latest (2.3.6) a few days ago (we typically wait a week before pushing a release), and still were experience the crash. We thought it was a map conflict, car conflict, and other scripts... we changed phone spawning to client sided instead of server, changed it from the custom prop to base game prop, etc etc.

It wasnt until we disabled simply the phone, when it all stopped.
We get about 140 players a night, so lots of people to test this and after weeks of rage errors being in the 100s every night per TX-Admin... we had 0 last night with the phone being off.

My theory is 2 things maybe, that might help narrow... our SQL being to large and its overloading data for players (we havnt wiped phone tables in a LONG time) - or something shortly after 2.2.0 causing it. We noticed in the update logs after 2.2.0, it introduced cell towers... maybe thats a hint to the issue? im not sure. But we do know for fact, no Rage with the phone turned fully off.

I hope we can work together and solve this, because this particular phone is the ONLY phone thats unique to players and I love that feature, and this wasnt an issue back in 2.2.0 (i currently rolled us back to that version and using it as its not causing the RAGE).

wispy breach
#

Just wanted to provide an update on this. We went back to latest release, and started getting mass RAGE errors again... so we went the nuclear approach and for testing sake - we completely dumped our old DB of data (almost a years worth of phone data.)

Havnt raged since...

So current theory, The phone bogs if the DB is to larger, causing graphical render errors - when trying to open the phone - hience the rage type crash?

distant sinew
wispy breach
#

yup, i took a backup right before wipe (incase i majorly screwed up).

Dedicated OVH Server.

CPU
AMD Ryzen 9 5900X - 12c/24t - 3.7 GHz/4.8 GHz
RAM
128 GB ECC 2666 MHz

Data disks
3×960 GB SSD NVMe
Soft RAID

Operating system (OS)
Ubuntu Server 22.04 LTS "Jammy Jellyfish"

Public bandwidth
3 Gbps outgoing
3 Gbps incoming

Private bandwidth
6 Gbps outgoing
6 Gbps incoming

distant sinew
#

And was the error happening to people pretty indiscriminately? Like ppl with top end PCs getting the error as well?

wispy breach
#

So, thats something we tried to track...
I had a test channel for the crashing, where people were posting their pc specs, location in world irl, Driver versions, vpn if on one, etc etc... and it was VERY random.

I for example, have not gotten the crash, but im on higher end equipment.

I was just tagged in 2 separate discords (assuming someone else is watching this bug report?) as a reference to their servers getting Rage Crashing as well.

Ill check with them and see if they follow my above steps if it helps their server too... then that would atleast get us multipe sources (servers) of data to try and match up.

wispy breach
#

^^ update - so in both cases the other servers are also using LB phone.
For testing, i informed them of what i did regarding a data wipe and told them to maybe try that if they are willing (also to make a backup).

obsidian dawn
#

I’m also experiencing this issue

wispy breach
#

^^ ours was roughly the same at 70-80%. after wiping the tables.... im at:

#

Much better the having 100s a night - and overall a ton of my other crashes have come drastically down as well, like client timeouts.

wondering if theres just excess data thats slagging the threads and causing it. The rage being coorelated to bulk data as its rendering the phone UIs maybe

wispy breach
#

@distant sinew - any ideas? clearing the table weekly is going to drastically upset my playerbase.

obsidian dawn
#

Could you kindly share if there are any updates?