Jump to content
×
×
  • Create New...
  • 0

CH3 is closing itself? interesting syserr


lordzokarum

Question

hello,

after some time only ch3 is closing itself

i found this in syserr, 

 

SYSERR: Apr 15 17:48:27 :: pid_init: 
Start of pid: 6347

SYSERR: Apr 15 17:48:31 :: LoadMotion: cannot find accumulation data in file 'data/monster/horse_event1/03.msa'
SYSERR: Apr 15 17:48:31 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Apr 15 17:48:31 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Apr 15 17:48:31 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Apr 15 17:48:31 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Apr 15 17:48:31 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Apr 15 17:48:31 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Apr 15 17:48:31 :: LoadMotion: cannot find accumulation data in file 'data/monster/horse_event1/03.msa'

SYSERR: Apr 16 00:07:38 :: Analyze: Accept shutdown p2p command from 60.191.38.77.  <-- WHAT IS THIS - IS SOMEONE CLOSİNG THE CH FROM REMOTE HOW CAN I BLOCK

SYSERR: Apr 16 00:07:38 :: Process: UNKNOWN HEADER: 100, LAST HEADER: 5(1), REMAIN BYTES: 999, fd: 21

thanx

 

Link to comment
Share on other sites

6 answers to this question

Recommended Posts

  • 0
1 hour ago, Sirio said:

You can block the p2p ports from firewall

or

be sure that in your CONFIG files there is

ADMINPAGE_IP: localhost           (or simply your ip)

 

 

if have this lines in all my CONFIG's 

ADMINPAGE_ENABLE: 1
ADMINPAGE_NO_LOCALHOST: 0
adminpage_ip: xxx.xxx.xxx.xxx
BIND_IP: xxx.xxx.xxx.xxx
PUBLIC_IP: xxx.xxx.xxx.xxx
INTERNAL_IP: xxx.xxx.xxx.xxx

is there a link how i can block it from firewall

Link to comment
Share on other sites

  • 0
6 hours ago, Sirio said:

Change the ip of adminpage_ip in your IP, localhost or 127.0.0.1 (in all configs)

To setup the firewall you can see there: https://www.freebsd.org/doc/handbook/firewalls-ipfw.html

Or if your server provider allow you to setup a customized firewall then, block all the p2p_port from your config files

ich hab es mit 127.0.0.1 versucht, nun werde ich mal warten ob es wider OFF wird. Danke.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.


Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.