Server crash: The file 'archive:/CAB <...> is corrupted! Remove it and launch unity again!

[zootal]

I have returned to A19 after a prolonged absence. Clean install of the dedicated server on Linux, A19.5. Slackware 15, 5.10.32 kernel. 142GB storage available on SSD, server uses about 4GB out of 32 GB ram. The same box I've always run 7D and other servers on. Yes I verified/reinstalled the server. No mods. Vanilla world.

 

I am having a consistent server crashing problem. When any client joins and starts to run around, the server will crash within 5-10 minutes.  The error message is always the same. I'll gather logs and post them later, I still have a few tests to run before I give up. For now I'm asking if anyone else has seen this or has any input:

 

The file 'archive:/CAB-fedb5cd35fe052f26ff23b1c055cad80/CAB-fedb5cd35fe052f26ff23b1c055cad80' is corrupted! Remove it and launch unity again!
[Position out of bounds!]
 
(Filename: ./Runtime/Serialize/SerializationCaching/CachedReader.cpp Line: 220)

Obtained 24 stack frames.
#0  0x0055c65f072617 in (Unknown)
#1  0x0055c65e370903 in (Unknown)
#2  0x0055c65ea6995d in (Unknown)
#3  0x0055c65ea6a89d in (Unknown)
#4  0x0055c65f086320 in (Unknown)
#5  0x0055c65f08d80a in (Unknown)
#6  0x0055c65f08dc62 in (Unknown)
#7  0x0055c65f08df32 in (Unknown)
#8  0x0055c65f08e0e9 in (Unknown)
#9  0x0055c65f08e332 in (Unknown)
#10 0x0055c65f08e563 in (Unknown)
#11 0x0055c65ebb2c1e in (Unknown)
#12 0x0055c65ebab653 in (Unknown)
#13 0x0055c65ebad48a in (Unknown)
#14 0x0055c65ebad57e in (Unknown)
#15 0x0055c65e5bd348 in (Unknown)
#16 0x0055c65e5bd5ec in (Unknown)
#17 0x0055c65e5ad989 in (Unknown)
#18 0x0055c65e6b825a in (Unknown)
#19 0x00000040bb62a4 in (wrapper managed-to-native) UnityEngine.AssetBundle:LoadAsset_Internal (UnityEngine.AssetBundle,string,System.Type)
#20 0x00000040d0557c in LoadManager:LoadAssetFromBundle<T_REF> (string,string,System.Action`1<T_REF>,LoadManager/LoadGroup,bool,bool)
#21 0x00000040cfad28 in DataLoader:LoadAsset<T_REF> (DataLoader/DataPathIdentifier)
#22 0x00000040cfa660 in DataLoader:LoadAsset<T_REF> (string)
#23 0x0000004027fee0 in EntityFactory:LoadPrefabs (EntityClass,bool)

 

[SylenThunder]

Can't say I've ever run on Slackware, and you're on an unstable branch at that.

 

Have never seen that error either, but a full log might provide more insight. Would be helpful to know your installation steps as well since you're on a flavor of Linux that isn't technically supported.

[zootal]

I doubt the problem is Slackware, I've used it for many many years, and it's the only distro I've run my 7d servers on. Up until now they have been rock solid. I'll generate another new world and run until it crashes, and upload the full log. I've seen people complaining about this message related to unity, but not specifically for 7D2D. And I notice the last line is *always* "#23 0x0000004218cb60 in EntityFactory:LoadPrefabs (EntityClass,bool) ", indicating some relation to prefabs. I'm wondering if there is a bad prefab triggering this?

[Beelzybub]

43 minutes ago, zootal said:

I'm wondering if there is a bad prefab triggering this?

Maybe there's a lingering prefab or old data from a previous Alpha?

 

[zootal]

To make a long story short, I added these two lines to my startup script, and it hasn't crashed since:

 

ulimit -n 10240

TERM=xterm

 

I can give an argument for either of them causing the problem. I haven't yet had a chance to see which one might have fixed it. I know unity gets upset if the var TERM isn't to it's liking, and I've also seen weird things when file handles are exhausted, though that is quite rare. I'll run like this for a while to ensure it really is stable, and then take them away one at a time to see which was magic.

[SylenThunder]

59 minutes ago, zootal said:

To make a long story short, I added these two lines to my startup script, and it hasn't crashed since:

 

ulimit -n 10240

TERM=xterm

 

I can give an argument for either of them causing the problem. I haven't yet had a chance to see which one might have fixed it. I know unity gets upset if the var TERM isn't to it's liking, and I've also seen weird things when file handles are exhausted, though that is quite rare. I'll run like this for a while to ensure it really is stable, and then take them away one at a time to see which was magic.

ulimit is covered in the Pinned FAQ thread.  I didn't consider it being related to the cab error though. Usually when you hit the cap on ulimit you get the error about too many open files.