Rumor

ee /etc/ntpd.conf uncomment: restrict default ignore As far as I know this should do it. Could also try this next: service ntpd stop

I recommend you don't use NTP, block it or disable it if possible.. alot of ntp attacks going around lately.

problem fixed on teamviewer =>

the channel syserr the channel is having issues, so we want to see the channel syserr refresh WinSCP window

It's their core, if they don't want to do it they won't.. if you want it badly then pay someone to add it into the source or do it yourself I guess it depends on if someone would use it for bad things.. in my case it came with the 34083 core and I use it to scan for other server names then read the conversation to determine whether or not the player was intentionally trying to bring players to another server. I have alot of haters who like to come to my server and do this stuff..

yep it's running

Update your scripts with these: [Hidden Content] Just put all the folders in your game directory and let it replace channel1, channel2, etc.. it's only going to update the run.sh scripts.

Updated run.sh scripts in the download link

Remove the preloads from the run.sh scripts like this.. find this: ./vrunner --daemon --pid-path=pid.game --file=game --env="LD_32_LIBRARY_PATH=/usr/local/lib/metin2" --env="LD_32_PRELOAD=./libgame.so" >> autorun.log 2>&1 & remove this: --env="LD_32_LIBRARY_PATH=/usr/local/lib/metin2" --env="LD_32_PRELOAD=./libgame.so" End result should be like this: ./vrunner --daemon --pid-path=pid.game --file=game >> autorun.log 2>&1 & This was a mistake in the script and I'll update the package with the right scripts.

It could be depending on how many channels you have setup to start I guess. Or it could be some leftover pieces from a previous attempt to start the server. I suggest doing this: ps kill -s 9 pid pid pid pid where pid = the process id of each vrunner then use ps to confirm the processes are ended and start the server again using the start script. For a public server with active players, I don't recommend killing the cores this way. Normally once you've got the server stopping and starting correctly you should /shutdown ingame then use the shutdown script to end the core processes.

yeah just use NTP hahah

It's your project of course so I understand if you have your own policies but I want to put my opinion about the pm logging too.. I find it very useful for catching advertisers, and before having such an amazing anticheat I caught people who are cheating and teaching others how to cheat as well as discussing the frequent use of cheats. If something is so confidential people shouldn't/wouldn't be typing it in a pserver for an online game. If it's really that personal they would only be telling people in real life or somewhere they felt is a secure area. Nice on the adminpage setup. That reminds me, what about a feature where LOW_WIZARDs can have commands added? We can already restrict commands with the CMD file, but it would be nice to be able to customize exactly what commands each permission level has and whether or not they have a GM logo over their head and can be added to friends. The behavior would be similar to Metin2US, where they had MODs with abilities that LOW_WIZARD currently doesn't have but without the GM logo over their head or friend-adding restrictions. To keep the CONFIG clean, maybe set this up in jSON format(or something else simple like lua) or something in a file that can be put somewhere near the core and have a symlink in each channel folder for it.

usually by default all ports are unblocked. You can check by looking at your CONFIG files in the server files for the PORTs then setting those ports up in your serverinfo.py of your client. auth is used to login and it's usually in the 11000+ range. channels typically are set to 13000+ range. For your client, each channel should be connected to the port listed in the "first" folder of each channel (if you're using the files from this thread).

it doesn't really matter much.. make sure they aren't blocked or in use by something else and don't go higher than 65535 because that's the limitation on ports.

yeah doesn't sound like a ram issue

how much RAM do you have? It's pretty hard to get a dedicated server that doesn't have enough for a metin2 server. How many cores do you run too?

tits

nalgas

gushing

rape

Just you, something must be going wrong with your files or installation.

the reason why you can't connect and it says socket in use is the port is already in use. Your database port is 15000 and something is using it. You most likely have the metin2 files running but don't know it.

auth - stop them from logging in/not needed after /shutdown channels - allow them to close and finish writing to db db - allow db to be written to

The first link is an entire structure of server files based on the use of the 34083 core. The second link has a place to download the 40250 core, just replace the 34083 core with the 40250 one. Don't forget to also replace the db core.