Skip to content
This repository has been archived by the owner on May 14, 2024. It is now read-only.

[Install Bug]: <ark_survival_ascended> #2547

Closed
KazadorFR opened this issue Nov 8, 2023 · 10 comments
Closed

[Install Bug]: <ark_survival_ascended> #2547

KazadorFR opened this issue Nov 8, 2023 · 10 comments
Labels
install bug Egg Install Fails not confirmed bug has not been reproduced or confirmed

Comments

@KazadorFR
Copy link

KazadorFR commented Nov 8, 2023

Panel Version

1.11.5

Wings Version

1.11.8

Service

ark_survival_ascended

Modified

no

Expected Behavior

install the egg, start the server

Actual Behavior

egg installation, server startup, then zombie server with 0.5% CPU usage, and 150 MB of ram.

server constantly marking on startup even after 10 hours

several pterodactyl installations, all other eggs work without problem. 20 GB of RAM available, CPU widely available also. a 20 groin of tentavite with different configuration like, change of port, server name, space or not, well almost everything that is possible to modify, the behavior is always exactly the same.

Steps To Reproduce

each installation reproduces the same error

Install logs

https://pteropaste.com/0mdvjhvjbttm/

@KazadorFR KazadorFR added install bug Egg Install Fails not confirmed bug has not been reproduced or confirmed labels Nov 8, 2023
@KazadorFR KazadorFR changed the title [Install Bug]: <Egg Name> [Install Bug]: <ark_survival_ascended> Nov 8, 2023
@gOOvER
Copy link
Contributor

gOOvER commented Nov 8, 2023

crashlog dont care here; thats more something for the devs

@dagbs
Copy link
Contributor

dagbs commented Nov 8, 2023

The only thing I noticed that isn't documented anywhere with no proper crash-log errors is when users who use Proxmox don't have their VM's processor type set to Host... and I have no idea why this is needed but if everything else is default then it's probably a processor bridge issue.

@gOOvER
Copy link
Contributor

gOOvER commented Nov 8, 2023

The only thing I noticed that isn't documented anywhere with no proper crash-log errors is when users who use Proxmox don't have their VM's processor type set to Host... and I have no idea why this is needed but if everything else is default then it's probably a processor bridge issue.

This should be default, because kvm64 is not really an option. With Host you have a real Core, not a VCore.

CPU type kvm64 presents a limited set of instructions to the VM's OS, which will limit how the OS can run code. For example MMX, AVX or AES instructions are not in a kvm64 CPU. using CPU type "host" will increase the performance of your VMS

@KazadorFR
Copy link
Author

I would never have thought of that for myself, I'm going to look at it and give you updates on the progress.

@dagbs
Copy link
Contributor

dagbs commented Nov 8, 2023

image
image

@KazadorFR
Copy link
Author

Well it works! thank you very much, I would never have found it without your help! I hope others will be helped by this post.

@dagbs
Copy link
Contributor

dagbs commented Nov 8, 2023

np

Just want to point out this is not a bug with the egg or pterodactyl, it's an issue with A:SA

@gOOvER
Copy link
Contributor

gOOvER commented Nov 8, 2023

With Host modus in proxmox should be a part of pterodactyl docu, but i will not push anything there.

Its also not a problem of the game; more the problem of the host configuration

@KazadorFR
Copy link
Author

I spent several days researching, and I never saw any documentation of this problem, and I realize that I already had other minor problems with other eggs and I think that all my problem comes only from this configuration problem with proxmox

@QuintenQVD0
Copy link
Collaborator

It looks to me like this is resolved so I am closing this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
install bug Egg Install Fails not confirmed bug has not been reproduced or confirmed
Projects
None yet
Development

No branches or pull requests

4 participants