Closed rleite01 closed 6 years ago
Is that IP address yours?
If yes, how do you start the Ranksystem?
Which system do you have? Please share us your ranksystem.log.
Hello Newcomer,
That's right this is my IP Numeral "Home" http://prntscr.com/ixp27z Linux,cwp control,
Application Version Apache: Apache/2.4.29 PHP: 5.6.30 MySQL: 10.1.32-MariaDB DNCentOS release 6.9
It looks like the CentOS Web Panel overwrite the $_SERVER['HTTP_HOST'] and/or $_SERVER['REMOTE_ADDR'])
You will find the considered code in line 58 inside the jobs/bot.php
if(isset($_SERVER['HTTP_HOST']) || isset($_SERVER['REMOTE_ADDR'])) {
Try to replace it with this one:
if(isset($_SERVER['HTTP_HOST'])) {
If that doesn't help too, remove the lines 58 - 60:
if(isset($_SERVER['HTTP_HOST']) || isset($_SERVER['REMOTE_ADDR'])) {
shutdown($mysqlcon, $logpath, $timezone, 1, "Request to start the Ranksystem from ".$_SERVER['REMOTE_ADDR'].". It seems the request came not from the command line!", 1);
}
Please give us a short feedback.
Hi, my friend, I've made the changes and it's still going on.
I'm testing on other platforms like Cpanel as well. http://prntscr.com/iyo9al
I removed the line: 58 to 60
new error http://prntscr.com/iyoaso
The error message says all, you need to know.
You modified the file jobs/bot.php.. It seems to be the file permissions gone lost. Correct the permissions and it should be working.
When you fixed the permissions problem, I would like to test something with you.. Sure, only if you agree.
Please contact us for this on our public TS3 server (ts-n.net). Perhaps we can solve the problem together.
All settled my friend!
Just remove line 58 to 60
It is not just as easy.. That lines have a reason ;-)
Seems to be you (rleite01) are not willing to help us.. it's a pity
really had not been solved, now the bot is opening several other bots, because when I disconnect the server shows, several stop
2018-07-14 00:42:14.229678 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:14.160416 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:14.079104 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:13.298681 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:13.065289 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:12.726861 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:12.367770 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:12.269146 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:11.873094 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:09.674934 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:09.655225 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:02.666234 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:02.276404 INFO Received signal to stop! Shutting down! 2018-07-14 00:42:00.455418 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:58.161713 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:52.475352 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:48.066415 INFO Conceder o grupo do servidor Soldado 2ª Classe ao usuário 2638 (ID-Ùnica: 'Bruno1v9'; Cliente-database-ID vJ/xBl5OVaKha/XQq0/qgUZcmf8=). 2018-07-14 00:41:42.991927 INFO Grupo do servidor removido Soldado 1ª Classe do usuário 2639 (ID-Ùnica: 'Bruno1v9'; Cliente-database-ID vJ/xBl5OVaKha/XQq0/qgUZcmf8=). 2018-07-14 00:41:34.170954 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:27.090124 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:22.544927 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:19.030188 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:16.969799 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:16.534944 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:15.862103 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:15.303778 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:12.321156 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:11.416758 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:11.251646 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:11.235653 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:07.181984 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:07.010971 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:06.909617 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:01.490238 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:01.487550 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:01.239032 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:01.235247 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:01.194282 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:01.174999 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:00.691900 INFO Received signal to stop! Shutting down! 2018-07-14 00:41:00.129627 INFO Received signal to stop! Shutting down! 2018-07-14 00:40:59.975190 INFO Received signal to stop! Shutting down! 2018-07-14 00:40:59.968429 INFO Received signal to stop! Shutting down! 2018-07-14 00:40:55.203777 INFO Received signal to stop! Shutting down! 2018-07-14 00:40:55.157778 INFO Received signal to stop! Shutting down!
doesn't belong to this issue and its also closed, make a new issue pls as you will get no help here - (locked)
really had not been solved,
It is months ago you opened this topic. That problem appears now or directly after the made changes (described above).
because when I disconnect the server shows, several stop
When you disconnect with your client, the Ranksystem Bot will stops, I understood that right?
2018-03-28 20:59:22.170066 CRITICAL Request to start the Ranksystem from 189.110.84.161. It seems the request came not from the command line! Shutting down!
Friends, you can help me. I'm trying to solve this problem but unfortunately I can not.