Dedicated LiF:YO Server on Ubuntu 20.04 LTS

1
Hello everybody,

I am new to the forums. I am having issues with setting up the Server on Ubuntu 20.04. LTS. Although I know that its not explicitely supported as I followed all the steps twice on the guide for Ubuntu here: https://kb.feudal.tools/knowledge-base/ ... ntu-linux/ I am hoping to get some help.

Now back to topic. I am having issues that the initialization of the server es extremly slow. I mean the following part:

https://kb.feudal.tools/knowledge-base/ ... Gameserver

It is stating that it take a couple of minutes. My first attempt ran the whole night with still some activity on the logs files(Round about 10 hours). Opening the Database manually with the corresponding and dedicated database user and selecting some tables has a result. So the process of initially setting up the server is doing something.

The log files show something like this:
WARN 2021-01-05 12:40:59.934 {} <<Thread>> [] DB::noRS(0 ms) UPDATE guild_actions_queue set OwnerConnectionID = CONNECTION_ID(), OwnedTimestamp = CURRENT_TIMESTAMP() where OwnerConnectionID = 0 limit 10; [T:DBIGuildsProcess:50]
WARN 2021-01-05 12:40:59.936 {} <<Thread>> [] DB::RS(1 ms) SELECT `ID`, `TicketID`, `ActionType`, `ProducerCharID`, `GuildID`, `CharID`, `GuildName`, `GuildTag`, `GuildCharter`, `GuildTypeID`, `CharIsKicked`, `CharGuildRoleID`, `OtherGuildID`, `StandingTypeID`, `UnmovableObjectID`, `ClaimID`, `HeraldryID`, `CanEnter`, `CanBuild`, `CanClaim`, `CanUse`, `CanDestroy` FROM `guild_actions_queue` where OwnerConnectionID = CONNECTION_ID() ORDER BY `ID` [T:DBIGuildsProcess:50]
So what did I do? I followed all the instructions from the above mentioned guide. I never had any other output than stated in the pictures provided and landed at this slow database input with the following console output then initiating this here:
<myserverinfo>:~/yoserver$ nohup xvfb-run wine ddctd_cm_yo_server.exe -worldid 1 &
[2] 2892
<myserverinfo>:~/yoserver$ nohup: ignoring input and appending output to 'nohup.out'
The specs of my system are as followed:
i7 3770
32gb 1600mhz RAM
Mass storage is on an SSD

<myselrverinfo>:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and- ... acy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
If anyone has encountered the same problem and has an advice for me. Please help me out. If you need any further information for help just tell me. I will provide what is needed. The Ubuntu 20.04 LTS is freshly installed.

Best regards,

Mox

Re: Dedicated LiF:YO Server on Ubuntu 20.04 LTS

2
hey,
I think there's nothing wrong with your setup. Running the nohup [...] command is not supposed to give any output.
The log files show something like this:
WARN 2021-01-05 12:40:59.934 {} <<Thread>> [] DB::noRS(0 ms) UPDATE guild_actions_queue set OwnerConnectionID = CONNECTION_ID(), OwnedTimestamp = CURRENT_TIMESTAMP() where OwnerConnectionID = 0 limit 10; [T:DBIGuildsProcess:50]
WARN 2021-01-05 12:40:59.936 {} <<Thread>> [] DB::RS(1 ms) SELECT `ID`, `TicketID`, `ActionType`, `ProducerCharID`, `GuildID`, `CharID`, `GuildName`, `GuildTag`, `GuildCharter`, `GuildTypeID`, `CharIsKicked`, `CharGuildRoleID`, `OtherGuildID`, `StandingTypeID`, `UnmovableObjectID`, `ClaimID`, `HeraldryID`, `CanEnter`, `CanBuild`, `CanClaim`, `CanUse`, `CanDestroy` FROM `guild_actions_queue` where OwnerConnectionID = CONNECTION_ID() ORDER BY `ID` [T:DBIGuildsProcess:50]
These are logs from normal server operation. It's the guild system working and checking for new guild actions every 5 seconds. So if you see that in your log, the server is up and running. Have you tried to connect? If it's not working, maybe some firewall rule is blocking clients.

Re: Dedicated LiF:YO Server on Ubuntu 20.04 LTS

4
moxon1982 wrote: 06 Jan 2021, 11:38 That would be an aweful mistake of myself.

I recently discovered that the ufw service wasnt running so the system only allowed known services.

I will allow port 28000-28003 now and see if it is working.
Okay... this can be considered as solved. I open the wrong ports at the firewall. Thanks for the help with the Guild Actions Log... Everything is working fine now.
cron