Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error affecting FXServer artifacts 12078 and onward: "Failed to open packfile: ReadBulk of header failed:" #3011

Closed
RageOps opened this issue Dec 17, 2024 · 1 comment
Labels

Comments

@RageOps
Copy link

RageOps commented Dec 17, 2024

What happened?

After noticing an uptick in user complaints about a specific issue: "Failed to open packfile: ReadBulk of header failed:" when attempting to connect to servers, I investigated whether the issue was related to a certain version of artifacts. On a fresh FXServer creation, Linux (Ubuntu) environment, I was able to reproduce the error on both artifacts 12083 and 12078. When using artifacts 12031, the issue was not present.

I tested both Release and Canary client versions. The connection error was present for both Release and Canary on 12078, and was not present on Release or Canary on 12031.

The only resources installed on the server were the default cfx-server-data resources.

Error screenshot:
image

This image shows chat as the resource that couldn't be loaded, but I have also seen sessionmanager and resource monitor as resources that are indicated in the error message. Leading me to believe that the issue does not depend on the resource that is failing to load.

Client log:
CitizenFX_log_2024-12-17T052541.log

Server log: (I don't have a brain and couldn't figure out how to network my txAdmin port on my host)
image

Expected result

Players are able to connect to servers regardless of artifacts version

Reproduction steps

Server:

  1. Create new Linux FXServer with artifact version 12083 or 12078. In my case I used 12078
  2. Install the cfx-server-data resources.
  3. Run the server

Client

  1. Attempt to connect to the server
  2. Be met with the above error message.

Importancy

There's a workaround

Area(s)

FiveM, FXServer

Specific version(s)

Server 12078/12083 linux

Additional information

This was not tested on a localhost environment.

@RageOps RageOps added bug triage Needs a preliminary assessment to determine the urgency and required action labels Dec 17, 2024
@FabianTerhorst
Copy link
Contributor

Thanks for the report, this issue has been resolved inside the latest artifacts 12092+.

@github-actions github-actions bot removed the triage Needs a preliminary assessment to determine the urgency and required action label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants