Failed to delete oplog on the ZenServer with Win+Linux Build

Development Pipeline & Plugins
, ,
1

Hi,

we have a shared ZenServer running on one of our Build Machines. This causes the local ZenServer to fail to start and crash the editor on startup.

We’ve worked around that issue by setting UE-ZenSharedDataCacheHost as environment variable. This causes the same error spam but prevents the crash on that machine.

We’ve intermittently encountered the “Failed to delete oplog on the ZenServer” Error and after some investigation decided to update the shared ZenServer version to 5.7.20.

After the update the error is now consistently appearing when cooking the server for win+linux. But only on the machine that is hosting the shared ZenServer.

LogZenStore: Display: Establishing oplog ‘TheBus.aadad99b/LinuxServer’

LogZenStore: Display: Zen project ‘TheBus.aadad99b’ creation FAILED

LogZenStore: Display: Establishing oplog ‘TheBus.aadad99b/WindowsServer’

LogZenStore: Display: Zen project ‘TheBus.aadad99b’ creation FAILED

Is there a recommended approach for running the Shared ZenServer on a Build Machine?

What can we do to prevent the crash from happening?

Regards,

Max

[Attachment Removed]

2

Hi Max,

I’d like more information to be able to provide guidance here. Specifically if you could provide the commandline and environment (with redactions for your own privacy) that was used when UE was invoked to understand the specifics here.

Fundamentally what I’m trying to establish is:

  1. What zenserver (a locally autolaunched instance or shared one) was being used in the role of Local DDC
  2. What zenserver (a locally autolaunched instance or shared one) was being used in the role of Shared DDC
  3. What zenserver (a locally autolaunched instance or shared one) was being used in the role of Cooked Output Storage

If things are configured the way I would consider correct, I expect:

  1. Either a locally autolaunched zenserver instance being used as Local DDC or no Local DDC if your build machines don’t keep local cache
  2. Either a shared zenserver instance being used as Shared DDC or no Shared DDC if your build machines haven’t been configured to have a shared cache
  3. A locally autolaunched zenserver instance being used as Cooked Output Storage

The “oplogs” are part of cooked output storage (item 3), and if things are configured correctly should not be influenced at all by the Shared DDC configuration, but it’s possible you’re trying to do cooked output storage on a shared host, and that’s not a desirable configuration. But that’s what I’m trying to figure out.

[Attachment Removed]