[CentOS 7/8 Repack] Full Cabal Server Installation + CentOS SQL (Database) [Updated 2023]

Joined
Aug 27, 2013
Messages
935
Reaction score
2,472
Location
RageZone
This tutorial will show you how to have a fully working Cabal Online Private Server on CentOS 7 VPS with a Database and overall - ready to launch officially* or not.
[This tutorial is written for CentOS 7 ONLY]​
*if you have a ready files though.
About repack: It's at stable stage, that has been planned for quite a while and it requires a bit more manual work than the usual one, but that I explain below, so hopefully, if you follow my tutorial, you will have no issues to have a server.

- Cleaned Libraries that stopped CentOS yum update and were not used at all.
- Overall clean-up of the whole repack and scripts.
- Infinite yum update [expected] without any issues (lol).

- If you will notice anything, please report here. REPACK RELATED ISSUES ONLY.
- As well as any feedback appreciated!
Links to one of the cheapest VPS's on the internet with a minimal anti-ddos:
-
-

- No more Windows R2
- No more Remote Desktops
- No more hassle

- No more 30-120 Euros a month for Dedicated Servers with additional charges for Windows Environment


IMPORTANT NOTE: If you will follow my full tutorial, you will have it a fully working server within 2 hours time. Repack has been tested and already used by couple servers and my test server.
This repack might not suite everyones taste, as it has a different cabal_status and overall OS environment is slightly different from CentOS 6.

Tutorial has sections, so make sure you follow them.

So, without further ado, lets begin:
To view the content, you need to sign In or register.


All credits belong to people who helped and supported the project not solely by feedback, but also financially.
Most credits: penetrator9000 (wished to remain in shadows) & Yamachi

References: DeXtR and Toast2250
Special thanks to @wantedxnn for CentOS 8 Stream

 

Attachments

Last edited:
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

€dit: Sorted out topic.
 
Last edited:
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

wow nice release

it was just what I was looking for
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Just a little note:

World_drop edits can be done without a server reboot here, just use cabal_reload (may cause a short lag-spike),
or to be channel-specific:
systemctl reload WorldSvr_XX_YY (X = Srv / Y = Channel number, depends on your settings).

Using wildcards obviously works too:
systemctl reload WorldSvr_01_*
or even
systemctl reload WorldSvr*

I guess there will be a few more servers in no time given the repack here.
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

anyone could do mini tutorial of how does the website leave on linux
anyone could do mini tutorial of how does the website leave on linux
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

is it possible to use virtual machine for test ? also how to edit database and add new things ?
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Have this mssql error what should i do ? and cabal server runs fine and how i should edit client to join my server ? and give us example about how to use mssql this is my first time use vm and centos7 and mssql
MrSensei - [CentOS 7/8 Repack] Full Cabal Server Installation + CentOS SQL (Database) [Updated 2023] - RaGEZONE Forums
 
Last edited:
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

İ cant install mssql what is this error ? he get error whilere reading files: Access denied
get this error.
Code:
This program has encountered a fatal error and cannot continue running.The following diagnostic information is available:


       Reason: 0x00000006
       Status: 0x40000015
      Message: Kernel bug check
      Address: 0x6a42b530
   Parameters: 0x6a62a250


               
               
               
               
               
   Stacktrace: 000000006a4e84f6 000000006a42b58b 000000006a41ed2d 
               000000006a42ae71 000000006a4e6a7d 000000006a4e5abc 
               000000006a4e5930 000000006a4e5865 


      Process: 1673 - sqlservr
       Thread: 1677 (application thread 0x1000)
  Instance Id: 2f2b1d0e-59e6-4fd5-984a-ed1b42b9fa4d
     Crash Id: 256ac502-e9c8-48cb-a3f4-80eb123991d1
  Build stamp: f7473acad6f0299cd161863aaa02e4284434ab6d915c7b467e2a14e907290249
 
Last edited:
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

SQL Server Agent (SQLEXPRESS) cannot be started because is a feature not supported on Express Edition, I had to switch to the version Developer Edition and now everything works fine.
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Well done :D Great release :congrats::eating:
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

SQL Server Agent (SQLEXPRESS) cannot be started because is a feature not supported on Express Edition, I had to switch to the version Developer Edition and now everything works fine.

This issue has nothing really to do with the release and shouldn't be mandatory, else - you'll just have to do what the error states:
Get a different version & stop using express.
You only need SQL Agent for cron jobs anyway, which you can set up using a variety of different options/alternatives.
Just google a little regarding it if you would like to keep things the way they are.
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Well detailed and very informative and very timely for me! Cheers for the update AzureSensei!
So i use my Windows Azure Centos 7.4 which is i hope good for this tuts release.

CentOS :
Still i got some road blocks and confusion in some parts of the tuts and apologies for that since im a complete beginner. So here's the pending questions for me to ask to finish the work.

Section 1 of the tuts.
First of many :)
FOR COMPLETE BEGINNERS:Strongly advised to use Fallen Cabal Files and Client, as you only need to put the files' Data and Common.ini and edit language.enc accordingly. As well as server files are the most stable and one of the most clean ones. Big thanks for @DeXtR for his amazing release.

For this one im confused on where should i put the downloaded files, i got the emerald client which is for the client to run the game and as far as i remember there should be some files that i should update with the client but i don't know which is that, and the Fallen Server files i mean where should I put them and do i need to update something? Apologies in advance. :(:

Section 2 of the tuts.
No issues were encountered except for the non existing command in my CentOS.
Code:
[COLOR=#666666]systemctrl restart firewalld[/COLOR]
I use the following instead. ( )
Code:
sudo firewall-cmd --reload



Section 3 of the tuts.
Third of many :)
Advisable: Get newest SSMS for yourself, in order to connect to your new database: DownloadFULL SETUP: Official Microsoft Link

The Official Microsoft Link is a dead link.
What is the purpose of the "Microsoft SQL Server Management Studio 17" is it to restore the dbase? also what are the credentials i should use.
SQL Server:

Also after copying the .bak files in /var/opt/mssql/backup, shouldn't i restore the the .bak files?

Section 4 of the tuts.
I'm Okay no issues :) but...
should i also open those endpoints in the ?


Section 5 of the tuts.
Here is one of my biggest confusion, what values should i put in the following parameters of the .
Enter MSSQL server IP: <<current centos server ip>>
Enter MSSQL server Port(default 1433):1433
Enter MSSQL server User: sa
Enter MSSQL server Password: <<secret password>> :ott1:
Enter IP for players to connect:<<current centos server ip>>


Is the information i supplied are correct ?


Section 6 of the tuts.
(*** SERVER SIDE ***)
I haven't done anything from this part, 1st i cant find where is my own .ini. I find this section somewhat unclear or unspecific (my own opinion don't flame me :*:) .

I think this i related to "Fallen" file downloaded from the Section 1 of the tuts, so should i just copy and paste or upload the "Data" and "Common" in Fallen files from my local to this location in the CentOS "
/etc/cabal".
I hope this section will be broaden if possible.

(
*** DATABASE SIDE ***​
)Likewise from the server side i haven't done anything from here...
Im not familiar on how i can check if my all dbase were restored which is similar to my question in the section 3.
I hope this section will be broaden if possible also.


Section 7 of the tuts.:mellow: (which is maybe for the client side)
After setting up the server and database side, shouldn't there be also a section for client, just a suggestion. Downloading the Emerald client will not be enough i think.


All in all thank you so much for this updated Cabal Setup tuts. Very highly appreciated. Looking forward for the answers :)
everything i said above were out of curiosity. thanks.
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Okay, so.. where we should start now.. hm..

First thing's first:

Your .ini file locations: /etc/cabal
Your Server configs: /etc/cabal/data

What you need to do is simply delete common.ini and data folder in the /etc/cabal and upload fallen's data and common.ini

Section 3 bits for newest SSMS is for backup restoration and database management. Better to have newest ones than some sort of 2008 (It's 2018, so I believe everyone should update at least a bit :D ) Although there is another reason - some errors can be shown on some old versions of SSMS that doesn't appear on newest ones due to unsupported features and no one will be able to help anyone if that's the case.

Section 4 bit depends on you, if you will be able to connect to the server, then no need, if not - you will have to open them. I have not used Microsoft Azure, so I cannot give you any more information about it.

Section 5 is correct.

Section 6 server and database... Well, that needs a brand new tutorials if you struggle with these bits, but to put in short:

Database: Create new databases (empty ones) and restore .bak files accordingly.
Server side: LoginSvr_01.ini and WorldSvr_01_0X.ini are located in /etc/cabal


As for client, you should look into tutorials section how to find out client's magickey and cabalmain's version (it might even be needed to get a non-packed cabalmain for your client, don't remember if Emerald is packed or not) and you will have to set Magickey and Version in the database and loginsvr based on client, or you can make up your owns and then change them everywhere.

as for most vital part in the client: your cabal folder/data/language/english/language.enc <<< decompress this using HellSpider's ENC tool and change info inside (it will need ip and loginsvr + chatnode ports) and then compress it.
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

I advise everyone who's new to the server bits to look up the crash fixes for chatnode/worldsvr etc (bin fixes for /usr/bin/worldsvr etc).
Else you won't get anywhere for too long.
Nothing rly topic/release related but something you should be aware of in general.
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Nice TUT

I got 1 problem
 
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Bischke go tools>options>designers>table and database designers> off the tick on "prevent saving changes that require......."

if your server will run please help me too
 
Last edited:
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Bischke go tools>options>designers>table and database designers> off the tick on "prevent saving changes that require......."

if your server will run please help me too

Ty for help

Server start, but no good cabal client :-(

● GlobalDBAgent.service - CABAL GlobalDBAgent server daemon
Loaded: loaded (/etc/systemd/system/GlobalDBAgent.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:21 CET; 3min 9s ago
Process: 7071 ExecStart=/usr/bin/GlobalDBAgent (code=exited, status=0/SUCCESS)
Main PID: 7096 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/GlobalDBAgent.service
jan 30 19:32:21 localhost.localdomain systemd[1]: Starting CABAL GlobalDBAgent server daemon...
jan 30 19:32:21 localhost.localdomain systemd[1]: Started CABAL GlobalDBAgent server daemon.
● AuthDBAgent.service - CABAL AuthDBAgent server daemon
Loaded: loaded (/etc/systemd/system/AuthDBAgent.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:22 CET; 3min 8s ago
Process: 7116 ExecStart=/usr/bin/AuthDBAgent (code=exited, status=0/SUCCESS)
Main PID: 7141 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/AuthDBAgent.service
jan 30 19:32:22 localhost.localdomain systemd[1]: Starting CABAL AuthDBAgent server daemon...
jan 30 19:32:22 localhost.localdomain systemd[1]: Started CABAL AuthDBAgent server daemon.
● CashDBAgent.service - CABAL CashDBAgent server daemon
Loaded: loaded (/etc/systemd/system/CashDBAgent.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:23 CET; 3min 7s ago
Process: 7171 ExecStart=/usr/bin/CashDBAgent (code=exited, status=0/SUCCESS)
Main PID: 7196 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/CashDBAgent.service
jan 30 19:32:23 localhost.localdomain systemd[1]: Starting CABAL CashDBAgent server daemon...
jan 30 19:32:23 localhost.localdomain systemd[1]: Started CABAL CashDBAgent server daemon.
● EventDBAgent.service - CABAL EventDBAgent server daemon
Loaded: loaded (/etc/systemd/system/EventDBAgent.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:24 CET; 3min 6s ago
Process: 7216 ExecStart=/usr/bin/EventDBAgent (code=exited, status=0/SUCCESS)
Main PID: 7241 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/EventDBAgent.service
jan 30 19:32:24 localhost.localdomain systemd[1]: Starting CABAL EventDBAgent server daemon...
jan 30 19:32:24 localhost.localdomain systemd[1]: Started CABAL EventDBAgent server daemon.
● PCBangDBAgent.service - CABAL PCBangDBAgent server daemon
Loaded: loaded (/etc/systemd/system/PCBangDBAgent.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:25 CET; 3min 5s ago
Process: 7261 ExecStart=/usr/bin/PCBangDBAgent (code=exited, status=0/SUCCESS)
Main PID: 7286 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/PCBangDBAgent.service
jan 30 19:32:25 localhost.localdomain systemd[1]: Starting CABAL PCBangDBAgent server daemon...
jan 30 19:32:25 localhost.localdomain systemd[1]: Started CABAL PCBangDBAgent server daemon.
● DBAgent_01.service - CABAL DBAgent server daemon
Loaded: loaded (/etc/systemd/system/DBAgent_01.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:26 CET; 3min 4s ago
Process: 7305 ExecStart=/usr/bin/DBAgent_01 (code=exited, status=0/SUCCESS)
Main PID: 7330 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/DBAgent_01.service
jan 30 19:32:26 localhost.localdomain systemd[1]: Starting CABAL DBAgent server daemon...
jan 30 19:32:26 localhost.localdomain systemd[1]: Started CABAL DBAgent server daemon.
● RockAndRollITS.service - CABAL RockAndRollITS server daemon
Loaded: loaded (/etc/systemd/system/RockAndRollITS.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:27 CET; 3min 3s ago
Process: 7360 ExecStart=/usr/bin/RockAndRollITS (code=exited, status=0/SUCCESS)
Main PID: 7385 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/RockAndRollITS.service
jan 30 19:32:27 localhost.localdomain systemd[1]: Starting CABAL RockAndRollITS server daemon...
jan 30 19:32:27 localhost.localdomain systemd[1]: Started CABAL RockAndRollITS server daemon.
● GlobalMgrSvr.service - CABAL GlobalMgrSvr server daemon
Loaded: loaded (/etc/systemd/system/GlobalMgrSvr.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:29 CET; 3min 2s ago
Process: 7395 ExecStart=/usr/bin/GlobalMgrSvr (code=exited, status=0/SUCCESS)
Main PID: 7420 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/GlobalMgrSvr.service
jan 30 19:32:29 localhost.localdomain systemd[1]: Starting CABAL GlobalMgrSvr server daemon...
jan 30 19:32:29 localhost.localdomain systemd[1]: Started CABAL GlobalMgrSvr server daemon.
● PartySvr_01.service - CABAL PartySvr server daemon
Loaded: loaded (/etc/systemd/system/PartySvr_01.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:42 CET; 2min 49s ago
Process: 7445 ExecStart=/usr/bin/PartySvr_01 (code=exited, status=0/SUCCESS)
Main PID: 7470 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/PartySvr_01.service
└─7471 /usr/bin/PartySvr_01
jan 30 19:32:42 localhost.localdomain systemd[1]: Starting CABAL PartySvr server daemon...
jan 30 19:32:42 localhost.localdomain systemd[1]: Started CABAL PartySvr server daemon.
● ChatNode_01.service - CABAL ChatNode server daemon
Loaded: loaded (/etc/systemd/system/ChatNode_01.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:43 CET; 2min 48s ago
Process: 7480 ExecStart=/usr/bin/ChatNode_01 (code=exited, status=0/SUCCESS)
Main PID: 7505 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/ChatNode_01.service
jan 30 19:32:43 localhost.localdomain systemd[1]: Starting CABAL ChatNode server daemon...
jan 30 19:32:43 localhost.localdomain systemd[1]: Started CABAL ChatNode server daemon.
● EventMgrSvr.service - CABAL EventMgrSvr server daemon
Loaded: loaded (/etc/systemd/system/EventMgrSvr.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:44 CET; 2min 47s ago
Process: 7523 ExecStart=/usr/bin/EventMgrSvr (code=exited, status=0/SUCCESS)
Main PID: 7548 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/EventMgrSvr.service
jan 30 19:32:44 localhost.localdomain systemd[1]: Starting CABAL EventMgrSvr server daemon...
jan 30 19:32:44 localhost.localdomain systemd[1]: Started CABAL EventMgrSvr server daemon.
● LoginSvr_01.service - CABAL LoginSvr server daemon
Loaded: loaded (/etc/systemd/system/LoginSvr_01.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:45 CET; 2min 45s ago
Process: 7559 ExecStart=/usr/bin/LoginSvr_01 (code=exited, status=0/SUCCESS)
Main PID: 7584 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/LoginSvr_01.service
jan 30 19:32:45 localhost.localdomain systemd[1]: Starting CABAL LoginSvr server daemon...
jan 30 19:32:45 localhost.localdomain systemd[1]: Started CABAL LoginSvr server daemon.
● AgentShop_01.service - CABAL AgentShop server daemon
Loaded: loaded (/etc/systemd/system/AgentShop_01.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:46 CET; 2min 44s ago
Process: 7594 ExecStart=/usr/bin/AgentShop_01 (code=exited, status=0/SUCCESS)
Main PID: 7619 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/AgentShop_01.service
jan 30 19:32:46 localhost.localdomain systemd[1]: Starting CABAL AgentShop server daemon...
jan 30 19:32:46 localhost.localdomain systemd[1]: Started CABAL AgentShop server daemon.
● WorldSvr_01_01.service - CABAL WorldSvr server daemon
Loaded: loaded (/etc/systemd/system/WorldSvr_01_01.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:47 CET; 2min 43s ago
Process: 7631 ExecStart=/usr/bin/WorldSvr_01_01 (code=exited, status=0/SUCCESS)
Main PID: 7656 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/WorldSvr_01_01.service
jan 30 19:32:47 localhost.localdomain systemd[1]: Starting CABAL WorldSvr server daemon...
jan 30 19:32:47 localhost.localdomain systemd[1]: Started CABAL WorldSvr server daemon.
● WorldSvr_01_02.service - CABAL WorldSvr server daemon
Loaded: loaded (/etc/systemd/system/WorldSvr_01_02.service; enabled; vendor preset: disabled)
Active: active (exited) since di 2018-01-30 19:32:48 CET; 2min 42s ago
Process: 7667 ExecStart=/usr/bin/WorldSvr_01_02 (code=exited, status=0/SUCCESS)
Main PID: 7694 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/WorldSvr_01_02.service
jan 30 19:32:48 localhost.localdomain systemd[1]: Starting CABAL WorldSvr server daemon...
jan 30 19:32:48 localhost.localdomain systemd[1]: Started CABAL WorldSvr server daemon.
 
Back