Welcome!

Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!

Join Today!

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

Joined
Aug 27, 2013
Messages
778
Reaction score
1,824
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:
Section 1 [Minimal to Average Requirements]:
Minimal Requirements of User:
1. Read in english.
2. Follow tutorial accurately.
3. NO RUSHING. Patience is a virtue.
4. Double-check every step done and verify it.
5. Assure that everything has been done correctly and as tutorial says.

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.

Minimal Requirements of System:
1. CentOS 7 [Not Debian, not Ubuntu, not Fedora or any of that sort]
2. 6 GB Ram [CentOS SQL requires minimum of 4 GB RAM]
3. 100 GB of space [can be either SSD or HDD]
4. 100mbps Bandwith [This is only if you won't make it public or will not go international, for public release strongly advised to have 1 GBPS]

Section 2 [System Preparation]:

Assumingly you've got your CentOS 7 running, you have to do couple of things:

1. Check if you have a running Firewalld. Command to check it:
Code:
systemctl status firewalld
- If it is shown as: Active: active (running) then go to Step 2.
- If it is show as: Inactive then go to Step 1.1.

1.1. Command to restart Firewalld:
Code:
systemctl enable firewalld
1.2. Command to start Firewalld:
Code:
systemctl start firewalld
*
* Repeat Step 1 to check if it is Running now.
1.3. If you would like to restart your firewall, then use:
Code:
systemctl restart firewalld

2. Run Yum Update to update your system:
Code:
yum update

Section 3 [Ports & Firewalld]:

Advice: Highly suggested to use custom ports for open ports like Chatnode, LoginSvr, WorldSvr* and AgentShop*.

1. Allow ports in the Firewalld:
sudo firewall-cmd --zone=public --add-port=YOUR_PORT_HERE/tcp --permanent
Code:
sudo firewall-cmd --zone=public --add-port=1433/tcp --permanent

Required Ports [Default ones, change accordingly to your custom ones if you decide to change]:
- 80 - HTTP
- 443 - HTTPS
- 1433 - Database
- 38101 - LoginSvr
- 38121 - Chatnode
- 38151 - AgentShop
- 38111 - 38116 - Channels*
- 38126 - War [170-190]*
You can open a full port range by typing:
Code:
sudo firewall-cmd --zone=public --add-port=38111-38126/tcp --permanent
* DO NOT OPEN GLOBALMGRSVR PORT.
** The ports provided are fully sufficient for full server use.

2. After you have added all of the ports, restart firewalld:
Code:
sudo firewall-cmd --reload

3. Check if you have added all of the ports you require:
Code:
firewall-cmd --list-all

4. OPTIONAL - You can also create a new zone in firewalld, if you decide not to use public zone, as well as add blocks / drop specific connections and such:

5. To remove ports from your firewall:
Code:
sudo firewall-cmd --zone=public --remove-port=38111-38126/tcp --permanent

Useful guide for a bit more indepth firewalld commands:

Section 4 [Database Installation & Restoration]:
Database Installation

Advisable: Get newest SSMS for yourself, in order to connect to your new database:

FULL SETUP:

Minimal Setup:

1. Download the Microsoft SQL Server [2019] Red Hat repository configuration file:
Code:
sudo curl -o /etc/yum.repos.d/mssql-server.repo https://packages.microsoft.com/config/rhel/7/mssql-server-2019.repo

2. Run the following commands to install SQL Server:
Code:
sudo yum install -y mssql-server

3. Run mssql-conf setup and follow the prompts to set the SA password and choose express edition [Number 3] <- because it is a Free Edition of newest SQL:
Code:
sudo /opt/mssql/bin/mssql-conf setup

4. Check if SQL is running:
Code:
systemctl status mssql-server

5. Make backup directory to restore your backups from:
Code:
mkdir -p /var/opt/mssql/backup

6. Upload your database backups [.bak files] into: /var/opt/mssql/backup
CLEAN EP8 Database Backups [Toast's]:
Contains:
Code:
* Account
* Authentication
* CabalCash
* CabalGuild
* EventData
* Netcafebilling
* Server01
cabalmanager is NOT NEEDED. It does not have any function in EP8.


Database Restoration

1. Login to your installed database, right click on Database and select "New Query", then copy this:
Code:
CREATE DATABASE Account;
CREATE DATABASE Authentication;
CREATE DATABASE CabalCash;
CREATE DATABASE CabalGuild;
CREATE DATABASE EventData;
CREATE DATABASE NetcafeBilling;
CREATE DATABASE Server01;
and click "Run". It will create all databases you will require.

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


2. Once databases are created, and backups are uploaded to /var/opt/mssql/backup, right-click on database and follow these steps:
Step 1: "Account" database -> "Tasks" -> "Restore" -> "Database..."
jRJmxcH - [CentOS 7/8 Repack] Full Cabal Server Installation + CentOS SQL (Database) [Updated 2023] - RaGEZONE Forums


Step 2: Select "Device" -> Click on 3 dots (in image marked as 2) -> Select "Add" -> Once window opens, click on "backup" and select Account.bak file -> Click "Ok"
[outcome will be like picture]


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


Step 3: Select "Options" (1) -> Tick "Overwrite the existing database (WITH REPLACE) (2). If you have "Take tail-log backup before restore" -> DESELECT IT. It has to be as show in the image below -> Click "Ok" and wait till database restores.

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


Now repeat the STEPS ABOVE for all databases until they are fully restored.

Old method for 2017 MSSQL - reported problems - NOT ADVISED TO USE IT:
Once you have done all points in Database Installation part, follow these simple to restore your database using PuTTy Terminal, which is simple copy-paste + enter.

1. Download required repository for SQLCMD:
Code:
curl https://packages.microsoft.com/config/rhel/7/prod.repo > /etc/yum.repos.d/msprod.repo
2. Run the following command to install it:
Code:
sudo yum install mssql-tools unixODBC-devel
3. Create a symlink using this command:
Code:
sudo ln -s /opt/mssql-tools/bin/* /usr/local/bin/
4. Using the following line in PuTTy terminal, you will create a database and restore it at the same time, without the need to login to SSMS Management and create everything there, as show in this sample:
Code:
sqlcmd -S localhost -U SA -Q "RESTORE DATABASE [[COLOR=#ff0000][B]Account[/B][/COLOR]] FROM DISK = N'/var/opt/mssql/backup/[COLOR=#ff0000][B]Account.bak[/B][/COLOR]' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5"

Copy paste the following lines in the spoiler below to restore full database.
*Important: after each line, you will be prompted to input database password.

Code:
sqlcmd -S localhost -U SA -Q "RESTORE DATABASE [Account] FROM DISK = N'/var/opt/mssql/backup/Account.bak' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5"
Click Enter -> Input your database password -> Click Enter -> Done!
Code:
sqlcmd -S localhost -U SA -Q "RESTORE DATABASE [Authentication] FROM DISK = N'/var/opt/mssql/backup/Authentication.bak' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5"
Click Enter -> Input your database password -> Click Enter -> Done!
Code:
sqlcmd -S localhost -U SA -Q "RESTORE DATABASE [CabalCash] FROM DISK = N'/var/opt/mssql/backup/CabalCash.bak' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5"
Click Enter -> Input your database password -> Click Enter -> Done!
Code:
sqlcmd -S localhost -U SA -Q "RESTORE DATABASE [CabalGuild] FROM DISK = N'/var/opt/mssql/backup/CabalGuild.bak' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5"
Click Enter -> Input your database password -> Click Enter -> Done!
Code:
sqlcmd -S localhost -U SA -Q "RESTORE DATABASE [EventData] FROM DISK = N'/var/opt/mssql/backup/EventData.bak' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5"
Click Enter -> Input your database password -> Click Enter -> Done!
Code:
sqlcmd -S localhost -U SA -Q "RESTORE DATABASE [NetCafeBilling] FROM DISK = N'/var/opt/mssql/backup/NetCafeBilling.bak' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5"
Click Enter -> Input your database password -> Click Enter -> Done!
Code:
sqlcmd -S localhost -U SA -Q "RESTORE DATABASE [Server01] FROM DISK = N'/var/opt/mssql/backup/Server01.bak' WITH FILE = 1, NOUNLOAD, REPLACE, STATS = 5"
Click Enter -> Input your database password -> Click Enter -> Done!

Database Location and Commands:

Location: /var/opt/mssql
Backups: /var/opt/mssql/backup
Command to restart database:
Code:
systemctl restart mssql-server

P.S. SQL has its own cmd, but it is not adviseable for novice user to use it, as SSMS does everything you need.

# Useful Tips #

- How to change default database username to my own?
Answer: Login to your Database -> Select "Security" (below "Databases") -> right-click user "sa" -> click "Rename" -> change it to whatever you like and hit "Enter" on your keyboard -> Done!
xJP69ZN - [CentOS 7/8 Repack] Full Cabal Server Installation + CentOS SQL (Database) [Updated 2023] - RaGEZONE Forums


- How to change MSSQL default port (1433) into my custom one?
Answer:
- Firstly, add it into your firewall zone. If you will not add it before hand, you will block yourself out of the database.
- Then, run the following command in SSH terminal:
Code:
/opt/mssql/bin/mssql-conf set network.tcpport YOUR_PORT_HERE
- After that you will be prompted to restart MSSQL Server, so use the following:
Code:
systemctl restart mssql-server.service



Section 5 [Repack Installation]:

REPACK DOWNLOAD LINK:
1. cabal_ep8_repack.tar.gz into /root directory.

2. Run command:
Code:
tar xzvf cabal*

3. Run command:
Code:
chmod +x install.sh

4. Start instalation:
Code:
./install.sh

Installation is pretty straight forward, just let it install everything and update system and additional libraries.

5. When installation is finished, type:
Code:
cabal_config
and input required information.

6. After that is completed, type:
Code:
mkdir -p /var/log/cabal

REPACK COMMANDS:

Creation / Config:
Code:
cabal_create -s - creates Servers [World] (SAMPLE: cabal_create -s 1 [will create 1 server])
cabal_create -c - creates Channels (SAMPLE: cabal_create -c 2 1 [will create 2 channels in the 1st server])cabal_config = Server ips, database port and credentials
Management:
Code:
cabal_start - starts services
cabal_stop - stops services
cabal_status - checks services

cabal_reload - reloads services [B]on live server[/B]
cabal_restart - restarts services
cabal_restart -d - restarts services and deletes all logs*
[Please download a fixed version of cabal_restart -d from here: and replace it with the existing one in: /etc/cabal/Template/sh]
Section 6 [Server Setup a.k.a. Finishing Touches]:


*** SERVER SIDE ***

VERY VERY BIG ADVISE: DO NOT paste your .ini files of any config, apart of common.ini ; just recreate it on the new ones. [Advising as some people had experienced some sort of a issues in regards to changing .ini files that were not common.ini and I had no time to look into it, but anyone with knowledge and kind enough could post anything about it and I will update this tutorial]

1. Go to WorldSvr_0X_0X and change ports accordingly, as repack will recreate all channels [WorldSvr_0X_0X on port: 38111 ; so you won't see any other channels apart of Channel 1]

For beginners:
Lets say you created 5 channels, you will see only channel 1 because all of them has port 38111 set on it, so what you need to do is this:
Go to WorldSvr_01_02 and change it's port to 38112
Go to WorldSvr_01_03 and change it's port to 38113
Go to WorldSvr_01_04 and change it's port to 38114
Go to WorldSvr_01_05 and change it's port to 38115

2. Check GlobalMgrSvr_0X.ini file to setup your channels accordingly.

3. Update LoginSvr_0X.ini and Account Database-> dbo.cabal_client_version table with your client's Magic Key and Client Version.

4. Refer to Toast repack's War Channels and Saint Vikalitan event, it doesn't have an automatically added ones yet.

5. Another Advise: Replace ONLY Data folder and Common.ini [Don't forget to link each of them to your Channels if you have more than one] if you start a fresh server.

5.1. CHMOD your new Data folder and Common.ini files with right permissions, using these commands:
Code:
sudo chmod -R 777 /etc/cabal/Data
*This will set all permissions to new Data folder and it's subfolders.
Code:
sudo chmod 777 /etc/cabal/Common.ini
*Change accordingly to your common.ini name.

6. Channel & Server types: Toast's Tutorial

*** DATABASE SIDE ***


Noticed some issues connecting to bega or some websites, so do the following to avoid them:

1. Assumingly you restored all database, go to:
Code:
Account -> Tables -> dbo.cabal_auth_table -> right-click it and select "Design" -> go to password section and change it from: var(50) to var(256) -> click "Save" in the tools meniu line.

2. Go to Account -> Programabillity -> Stored Procedures -> dbo.cabal_tool_registerAccount and change all password var(XX) to var(256) -> click run and then close it.

3. Go to Account -> Programabillity -> Stored Procedures -> dbo.cabal_tool_registerAccount_web and change all password var(XX) to var(256) -> click run and then close it.

4. [B]REMINDER:[/B] go to Account -> dbo.cabal_client_version_table and update Magic Key and Version in order to connect properly into your server.
[/SPOILER]

[CENTER][COLOR=#000080][SIZE=4][B][URL="https://www.youtube.com/watch?v=1Bix44C1EzY"]Congratulations![/URL]

Now you can type: cabal_restart -d
and join your server!

[/B][/SIZE][/COLOR]
[SIZE=5][COLOR=#0000ff][B]Useful Tips & Tricks:

[/B][/COLOR][/SIZE][/CENTER]
[Spoiler]
1. [B]Lock Channel on your IP[/B]
[I]Mini tutorial:[/I]
Simply add a rule to your existing Firewalld zone, using this command:
[CODE]firewall-cmd --permanent --zone=public --add-rich-rule='
  rule family="ipv4"
  source address="[B][COLOR=#ff0000]YOUR_IP[/COLOR][/B]/32"
  port protocol="tcp" port="[COLOR=#ff0000][B]YOUR_PORT/s[/B][/COLOR]" accept'
* In "your port" part, add channel port you want to lock on your IP, which will lead for channel to be visible for everyone, but if someone else will try to click on it, it will not allow to connect. Only user/s who's IP/s are added to this rule, can connect to the channel.
You can also insert a port range, just like in Firewalld section of this tutorial.


Once you paste it, you have to reload your Firewalld:
Code:
sudo firewall-cmd --reload

To remove your "lock" and allow everyone to connect to the channel, copy-paste this, with the details changed accordingly:
Code:
firewall-cmd --permanent --zone=public --remove-rich-rule='
  rule family="ipv4"
  source address="[B][COLOR=#ff0000]YOUR_IP[/COLOR][/B]/32"
  port protocol="tcp" port="[B][COLOR=#ff0000]YOUR_PORT/s[/COLOR][/B]" accept'
Once you paste it, you have to reload your Firewalld:
Code:
sudo firewall-cmd --reload
CentOS 8 Stream Installation
Changelog:
-replaced 'yum' with 'dnf' command
-replaced 'openssl-devel' with 'openssl-compat-1.0.2o' and also changed the symlink with new version
-added 'MSSQL SERVER 2022' during the instalation also will launch it's configuration
-added a fix for CentOS Stream 8 (durring the boot: 'A start job is running for Flush Journal to Persistent Storage (XXs / 1min 30s)')

And the rest of the steps are same as above (Refer to CentOS 7).

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

You must be registered for see attachments list
Last edited:
Junior Spellweaver
Joined
Dec 19, 2013
Messages
183
Reaction score
37
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

€dit: Sorted out topic.
 
Last edited:
Experienced Elementalist
Joined
Feb 17, 2015
Messages
259
Reaction score
111
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

wow nice release

it was just what I was looking for
 
Junior Spellweaver
Joined
Dec 19, 2013
Messages
183
Reaction score
37
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.
 
Initiate Mage
Joined
Jan 25, 2013
Messages
67
Reaction score
1
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
 
Initiate Mage
Joined
Apr 4, 2017
Messages
18
Reaction score
1
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 ?
 
Initiate Mage
Joined
Apr 4, 2017
Messages
18
Reaction score
1
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:
Initiate Mage
Joined
Apr 4, 2017
Messages
18
Reaction score
1
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:
Experienced Elementalist
Joined
Feb 17, 2015
Messages
259
Reaction score
111
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.
 
Initiate Mage
Joined
Oct 17, 2016
Messages
12
Reaction score
1
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Well done :D Great release :congrats::eating:
 
Junior Spellweaver
Joined
Dec 19, 2013
Messages
183
Reaction score
37
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.
 
Initiate Mage
Joined
May 24, 2014
Messages
12
Reaction score
1
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>> :eek:tt1:
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.
 
Joined
Aug 27, 2013
Messages
778
Reaction score
1,824
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.
 
Junior Spellweaver
Joined
Dec 19, 2013
Messages
183
Reaction score
37
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.
 
Joined
Feb 22, 2013
Messages
19
Reaction score
2
Re: [CentOS 7 Repack] Full Cabal Server Installation + CentOS SQL (Database)

Nice TUT

I got 1 problem
 
Initiate Mage
Joined
Apr 4, 2017
Messages
18
Reaction score
1
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:
Joined
Feb 22, 2013
Messages
19
Reaction score
2
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
Top