Beiträge von Aura

Aura · 1. Juli 2023

Zitat von Shadow™

Schau mal nach ob du genug Speicher hast mit df -h das hatte jemand mal den ich geholfen hatte bei ihn war kein Speicher zur Verfügung mehr.

Bitte melden Sie sich an, um diesen Anhang zu sehen.

Zitat von Aze

Diese Fehlermeldung zieht sich durch den Logfile:

Code

2023-07-01 02:02:10 80177f000 InnoDB: Error: table 'common/priv_settings'

InnoDB: in InnoDB data dictionary has tablespace id 7,

InnoDB: but a tablespace with that id does not exist. There is

InnoDB: a tablespace of name common/priv_settings and id 16, though. Have

InnoDB: you deleted or moved .ibd files?

InnoDB: Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html

InnoDB: for how to resolve the issue.

Hab die table jetzt gefixt. Neuer Log:

Spoiler anzeigen

Code

230701 17:50:02 mysqld_safe Logging to '/var/db/mysql/cloud619522.fastpipe.io.err'.
230701 17:50:02 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-07-01 17:50:02 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-07-01 17:50:02 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 2140 ...
2023-07-01 17:50:02 2140 [Note] Plugin 'FEDERATED' is disabled.
2023-07-01 17:50:02 2140 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-07-01 17:50:02 2140 [Note] InnoDB: The InnoDB memory heap is disabled
2023-07-01 17:50:02 2140 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-01 17:50:02 2140 [Note] InnoDB: Memory barrier is not used
2023-07-01 17:50:02 2140 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-01 17:50:02 2140 [Note] InnoDB: Not using CPU crc32 instructions
2023-07-01 17:50:02 2140 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-07-01 17:50:02 2140 [Note] InnoDB: Completed initialization of buffer pool
2023-07-01 17:50:02 2140 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2023-07-01 17:50:02 2140 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2023-07-01 17:50:02 2140 [Note] InnoDB: Database physically writes the file full: wait...
2023-07-01 17:50:02 2140 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2023-07-01 17:50:02 2140 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2023-07-01 17:50:03 2140 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2023-07-01 17:50:03 2140 [Warning] InnoDB: New log files created, LSN=45781
2023-07-01 17:50:03 2140 [Note] InnoDB: Doublewrite buffer not found: creating new
2023-07-01 17:50:03 2140 [Note] InnoDB: Doublewrite buffer created
2023-07-01 17:50:03 2140 [Note] InnoDB: 128 rollback segment(s) are active.
2023-07-01 17:50:03 2140 [Warning] InnoDB: Creating foreign key constraint system tables.
2023-07-01 17:50:03 2140 [Note] InnoDB: Foreign key constraint system tables created
2023-07-01 17:50:03 2140 [Note] InnoDB: Creating tablespace and datafile system tables.
2023-07-01 17:50:03 2140 [Note] InnoDB: Tablespace and datafile system tables created.
2023-07-01 17:50:03 2140 [Note] InnoDB: Waiting for purge to start
2023-07-01 17:50:03 2140 [Note] InnoDB: 5.6.51 started; log sequence number 0
/usr/local/libexec/mysqld: Error on delete of './auto.cnf' (Errcode: 2 - No such file or directory)
2023-07-01 17:50:03 2140 [Warning] World-writable config file './auto.cnf' has been removed.
2023-07-01 17:50:03 2140 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: f14ce3e1-1826-11ee-9b03-00091f6dd229.
2023-07-01 17:50:03 2140 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-07-01 17:50:03 2140 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-07-01 17:50:03 2140 [Note] Server hostname (bind-address): '*'; port: 3306
2023-07-01 17:50:03 2140 [Note] IPv6 is available.
2023-07-01 17:50:03 2140 [Note] - '::' resolves to '::';
2023-07-01 17:50:03 2140 [Note] Server socket created on IP: '::'.
2023-07-01 17:50:03 2140 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
2023-07-01 17:50:03 2140 [Note] Event Scheduler: Loaded 0 events
2023-07-01 17:50:03 2140 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51' socket: '/tmp/mysql.sock' port: 3306 Source distribution
230701 17:50:33 mysqld_safe mysqld restarted
230701 17:50:44 mysqld_safe mysqld from pid file /var/db/mysql/cloud619522.fastpipe.io.pid ended

Alles anzeigen

DB Syserr ist derselbe Fehler wie vorher. Leider keine .core Datei

Aura · 1. Juli 2023

Moin,

ich hab ein Problem mit meinem MySQL Server.

Ich hatte ein paar Wochen nichts am Server gemacht. ich hab ein Backup von meiner DB und allgemein den gamefiles. Habe einen neuen Server gemietet, FreeBSD normal geupdated etc.

MySQL startet, ich kann über Navicat drauf, Backup draufspielen etc. Keine Probleme. Bis ich den Server starte.

Nach ca. 20 Sekunden geht der MySQL Server down.

DB Syserr:

Spoiler anzeigen

Code

SYSERR: Jul 1 12:50:58 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Lost connection to MySQL server during query
query: SELECT MAX(id) FROM item WHERE id >= 10000001 and id <= 20000000
SYSERR: Jul 1 12:50:58 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 10000001 AND id <= 20000000
SYSERR: Jul 1 12:50:58 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 30000001 and id <= 40000000
SYSERR: Jul 1 12:50:58 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 30000001 AND id <= 40000000
SYSERR: Jul 1 12:51:12 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 210000001 and id <= 220000000
SYSERR: Jul 1 12:51:12 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 210000001 AND id <= 220000000
SYSERR: Jul 1 12:51:12 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 50000001 and id <= 60000000
SYSERR: Jul 1 12:51:12 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 50000001 AND id <= 60000000
SYSERR: Jul 1 12:51:22 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 230000001 and id <= 240000000
SYSERR: Jul 1 12:51:22 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 230000001 AND id <= 240000000
SYSERR: Jul 1 12:51:22 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 90000001 and id <= 100000000
SYSERR: Jul 1 12:51:22 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 90000001 AND id <= 100000000
SYSERR: Jul 1 12:51:22 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 70000001 and id <= 80000000
SYSERR: Jul 1 12:51:22 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 70000001 AND id <= 80000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 230000001 and id <= 240000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 230000001 AND id <= 240000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 70000001 and id <= 80000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 70000001 AND id <= 80000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 10000001 and id <= 20000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 10000001 AND id <= 20000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 30000001 and id <= 40000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 30000001 AND id <= 40000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 90000001 and id <= 100000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 90000001 AND id <= 100000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 210000001 and id <= 220000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 210000001 AND id <= 220000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT MAX(id) FROM item WHERE id >= 50000001 and id <= 60000000
SYSERR: Jul 1 17:14:48 :: DirectQuery: AsyncSQL::DirectQuery : mysql_query error: Can't connect to MySQL server on '127.0.0.1' (61)
query: SELECT COUNT(*) FROM item WHERE id >= 50000001 AND id <= 60000000

Alles anzeigen

/var/db/mysql .err Datei:

Spoiler anzeigen

Code

2023-07-01 02:02:10 40939 [Note] Plugin 'FEDERATED' is disabled.
2023-07-01 02:02:10 40939 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-07-01 02:02:10 40939 [Note] InnoDB: The InnoDB memory heap is disabled
2023-07-01 02:02:10 40939 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-01 02:02:10 40939 [Note] InnoDB: Memory barrier is not used
2023-07-01 02:02:10 40939 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-01 02:02:10 40939 [Note] InnoDB: Not using CPU crc32 instructions
2023-07-01 02:02:10 40939 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-07-01 02:02:10 40939 [Note] InnoDB: Completed initialization of buffer pool
2023-07-01 02:02:10 40939 [Note] InnoDB: Highest supported file format is Barracuda.
2023-07-01 02:02:10 40939 [Note] InnoDB: The log sequence numbers 1806004 and 1806004 in ibdata files do not match the log sequence number 1806014 in the ib_logfiles!
2023-07-01 02:02:10 40939 [Note] InnoDB: Database was not shutdown normally!
2023-07-01 02:02:10 40939 [Note] InnoDB: Starting crash recovery.
2023-07-01 02:02:10 40939 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-07-01 02:02:10 40939 [Note] InnoDB: Restoring possible half-written data pages
2023-07-01 02:02:10 40939 [Note] InnoDB: from the doublewrite buffer...
2023-07-01 02:02:10 80177f000 InnoDB: Error: table 'common/priv_settings'
InnoDB: in InnoDB data dictionary has tablespace id 7,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name common/priv_settings and id 16, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2023-07-01 02:02:10 40939 [Note] InnoDB: 128 rollback segment(s) are active.
2023-07-01 02:02:10 40939 [Note] InnoDB: Waiting for purge to start
2023-07-01 02:02:10 40939 [Note] InnoDB: 5.6.51 started; log sequence number 1806014
2023-07-01 02:02:10 40939 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-07-01 02:02:10 40939 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-07-01 02:02:10 40939 [Note] Server hostname (bind-address): '*'; port: 3306
2023-07-01 02:02:10 40939 [Note] IPv6 is available.
2023-07-01 02:02:10 40939 [Note] - '::' resolves to '::';
2023-07-01 02:02:10 40939 [Note] Server socket created on IP: '::'.
2023-07-01 02:02:10 40939 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2023-07-01 02:02:46 40939 [Note] /usr/local/libexec/mysqld: Normal shutdown
2023-07-01 02:02:46 40939 [Note] Giving 0 client threads a chance to die gracefully
2023-07-01 02:02:46 40939 [Note] Shutting down slave threads
2023-07-01 02:02:46 40939 [Note] Forcefully disconnecting 0 remaining clients
2023-07-01 02:02:46 40939 [Note] Binlog end
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'partition'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_METRICS'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_CMPMEM'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_CMP'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_LOCKS'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'INNODB_TRX'
2023-07-01 02:02:46 40939 [Note] Shutting down plugin 'InnoDB'
2023-07-01 02:02:46 40939 [Note] InnoDB: FTS optimize thread exiting.
2023-07-01 02:02:46 40939 [Note] InnoDB: Starting shutdown...
2023-07-01 02:02:47 40939 [Note] InnoDB: Shutdown completed; log sequence number 1806024
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'BLACKHOLE'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'ARCHIVE'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'MRG_MYISAM'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'MyISAM'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'MEMORY'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'CSV'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'sha256_password'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'mysql_old_password'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'mysql_native_password'
2023-07-01 02:02:47 40939 [Note] Shutting down plugin 'binlog'
2023-07-01 02:02:47 40939 [Note] /usr/local/libexec/mysqld: Shutdown complete
230701 02:02:48 mysqld_safe Logging to '/var/db/mysql/cloud619522.fastpipe.io.err'.
230701 02:02:48 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-07-01 02:02:48 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-07-01 02:02:48 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 41130 ...
2023-07-01 02:02:48 41130 [Note] Plugin 'FEDERATED' is disabled.
2023-07-01 02:02:48 41130 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-07-01 02:02:48 41130 [Note] InnoDB: The InnoDB memory heap is disabled
2023-07-01 02:02:48 41130 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-01 02:02:48 41130 [Note] InnoDB: Memory barrier is not used
2023-07-01 02:02:48 41130 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-01 02:02:48 41130 [Note] InnoDB: Not using CPU crc32 instructions
2023-07-01 02:02:48 41130 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-07-01 02:02:48 41130 [Note] InnoDB: Completed initialization of buffer pool
2023-07-01 02:02:48 41130 [Note] InnoDB: Highest supported file format is Barracuda.
2023-07-01 02:02:48 41130 [Note] InnoDB: 128 rollback segment(s) are active.
2023-07-01 02:02:48 41130 [Note] InnoDB: Waiting for purge to start
2023-07-01 02:02:48 41130 [Note] InnoDB: 5.6.51 started; log sequence number 1806024
2023-07-01 02:02:48 41130 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-07-01 02:02:48 41130 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-07-01 02:02:48 41130 [Note] Server hostname (bind-address): '*'; port: 3306
2023-07-01 02:02:48 41130 [Note] IPv6 is available.
2023-07-01 02:02:48 41130 [Note] - '::' resolves to '::';
2023-07-01 02:02:48 41130 [Note] Server socket created on IP: '::'.
2023-07-01 02:02:48 41130 [Note] Event Scheduler: Loaded 0 events
2023-07-01 02:02:48 41130 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2023-07-01 02:11:33 41130 [Note] /usr/local/libexec/mysqld: Normal shutdown
2023-07-01 02:11:33 41130 [Note] Giving 5 client threads a chance to die gracefully
2023-07-01 02:11:33 41130 [Note] Event Scheduler: Purging the queue. 0 events
2023-07-01 02:11:33 41130 [Note] Shutting down slave threads
2023-07-01 02:11:35 41130 [Note] Forcefully disconnecting 5 remaining clients
2023-07-01 02:11:35 41130 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 4 user: 'root'
2023-07-01 02:11:35 41130 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 5 user: 'root'
2023-07-01 02:11:35 41130 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 10 user: 'root'
2023-07-01 02:11:35 41130 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 12 user: 'root'
2023-07-01 02:11:35 41130 [Warning] /usr/local/libexec/mysqld: Forcing close of thread 14 user: 'root'
2023-07-01 02:11:35 41130 [Note] Binlog end
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'partition'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_METRICS'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_CMPMEM'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_CMP'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_LOCKS'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'INNODB_TRX'
2023-07-01 02:11:35 41130 [Note] Shutting down plugin 'InnoDB'
2023-07-01 02:11:35 41130 [Note] InnoDB: FTS optimize thread exiting.
2023-07-01 02:11:35 41130 [Note] InnoDB: Starting shutdown...
2023-07-01 02:11:36 41130 [Note] InnoDB: Shutdown completed; log sequence number 1807845
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'BLACKHOLE'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'ARCHIVE'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'MRG_MYISAM'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'MyISAM'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'MEMORY'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'CSV'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'sha256_password'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'mysql_old_password'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'mysql_native_password'
2023-07-01 02:11:36 41130 [Note] Shutting down plugin 'binlog'
2023-07-01 02:11:36 41130 [Note] /usr/local/libexec/mysqld: Shutdown complete
230701 02:11:36 mysqld_safe mysqld from pid file /var/db/mysql/cloud619522.fastpipe.io.pid ended
230701 02:11:36 mysqld_safe Logging to '/var/db/mysql/cloud619522.fastpipe.io.err'.
230701 02:11:36 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-07-01 02:11:37 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-07-01 02:11:37 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 41327 ...
2023-07-01 02:11:37 41327 [Note] Plugin 'FEDERATED' is disabled.
2023-07-01 02:11:37 41327 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-07-01 02:11:37 41327 [Note] InnoDB: The InnoDB memory heap is disabled
2023-07-01 02:11:37 41327 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-01 02:11:37 41327 [Note] InnoDB: Memory barrier is not used
2023-07-01 02:11:37 41327 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-01 02:11:37 41327 [Note] InnoDB: Not using CPU crc32 instructions
2023-07-01 02:11:37 41327 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-07-01 02:11:37 41327 [Note] InnoDB: Completed initialization of buffer pool
2023-07-01 02:11:37 41327 [Note] InnoDB: Highest supported file format is Barracuda.
2023-07-01 02:11:37 41327 [Note] InnoDB: 128 rollback segment(s) are active.
2023-07-01 02:11:37 41327 [Note] InnoDB: Waiting for purge to start
2023-07-01 02:11:37 41327 [Note] InnoDB: 5.6.51 started; log sequence number 1807845
2023-07-01 02:11:37 41327 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-07-01 02:11:37 41327 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-07-01 02:11:37 41327 [Note] Server hostname (bind-address): '*'; port: 3306
2023-07-01 02:11:37 41327 [Note] IPv6 is available.
2023-07-01 02:11:37 41327 [Note] - '::' resolves to '::';
2023-07-01 02:11:37 41327 [Note] Server socket created on IP: '::'.
2023-07-01 02:11:37 41327 [Note] Event Scheduler: Loaded 0 events
2023-07-01 02:11:37 41327 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2023-07-01 02:34:30 41327 [Warning] IP address '34.77.127.183' has been resolved to the host name '183.127.77.34.bc.googleusercontent.com', which resembles IPv4-address itself.
2023-07-01 02:34:31 41327 [Warning] IP address '130.211.54.158' has been resolved to the host name '158.54.211.130.bc.googleusercontent.com', which resembles IPv4-address itself.
2023-07-01 02:47:54 41327 [Warning] Host name '190-78-206-161.lms-01-p69.cantv.net' could not be resolved: Name does not resolve
2023-07-01 03:09:04 41327 [Warning] Hostname 'a103-147-8-153.bdo.starnet.net.id' does not resolve to '103.147.8.153'.
2023-07-01 03:09:04 41327 [Note] Hostname 'a103-147-8-153.bdo.starnet.net.id' has the following IP addresses:
2023-07-01 03:09:04 41327 [Note] - 113.11.255.33
2023-07-01 03:09:04 41327 [Warning] Hostname 'a103-147-8-153.bdo.starnet.net.id' does not resolve to '103.147.8.153'.
2023-07-01 03:09:04 41327 [Note] Hostname 'a103-147-8-153.bdo.starnet.net.id' has the following IP addresses:
2023-07-01 03:09:04 41327 [Note] - 113.11.255.33
2023-07-01 04:16:27 41327 [Warning] IP address '117.194.192.245' could not be resolved: Name does not resolve
2023-07-01 04:16:28 41327 [Warning] IP address '117.194.192.245' could not be resolved: Name does not resolve
2023-07-01 04:32:41 41327 [Warning] IP address '181.233.12.126' could not be resolved: Name does not resolve
2023-07-01 04:58:01 41327 [Warning] IP address '2001:470:1:c84::211' could not be resolved: Name does not resolve
2023-07-01 06:15:32 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:32 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:33 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:33 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:34 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:34 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:35 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:35 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:36 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:36 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:37 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:37 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:38 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:38 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:39 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:39 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:40 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:40 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:41 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:41 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:42 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:42 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:43 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:43 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:44 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:44 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:44 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:45 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:45 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:46 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:46 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:47 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:47 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:48 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:48 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:49 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:49 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:50 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:50 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:51 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:51 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:51 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:52 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:52 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:53 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:53 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:54 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:54 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:55 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:15:55 41327 [Warning] IP address '103.206.107.118' has been resolved to the host name '107.206.103-118.in-addr.arpa', which resembles IPv4-address itself.
2023-07-01 06:37:45 41327 [Warning] IP address '202.142.125.244' could not be resolved: Name does not resolve
2023-07-01 06:37:45 41327 [Warning] IP address '202.142.125.244' could not be resolved: Name does not resolve
2023-07-01 06:40:53 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:53 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:53 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:53 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:54 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:54 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:55 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:55 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:56 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:56 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:57 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:57 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:57 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:58 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:58 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:59 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:40:59 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:00 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:00 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:00 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:01 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:01 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:02 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:02 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:03 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:03 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:04 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:04 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:04 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:05 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:05 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:06 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:06 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:07 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:07 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:07 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:08 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:08 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:09 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:09 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:10 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:10 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:10 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:11 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:11 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:12 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:12 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:13 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:13 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 06:41:14 41327 [Warning] IP address '49.204.92.246' has been resolved to the host name '49.204.92.246.actcorp.in', which resembles IPv4-address itself.
2023-07-01 07:02:11 41327 [Warning] Host name 'abts-kk-static-136.102.166.122.airtelbroadband.in' could not be resolved: Name does not resolve
2023-07-01 07:10:28 41327 [Warning] Host name 'host86.181-93-190.telecom.net.ar' could not be resolved: Name does not resolve
2023-07-01 07:10:28 41327 [Warning] Host name 'host86.181-93-190.telecom.net.ar' could not be resolved: Name does not resolve
2023-07-01 07:51:46 41327 [Warning] Host name 'm153.static.iplatense.com.ar' could not be resolved: Name does not resolve
2023-07-01 08:08:36 41327 [Warning] Hostname 'node-5rs.pool-113-53.dynamic.totinternet.net' does not resolve to '113.53.157.56'.
2023-07-01 08:08:36 41327 [Note] Hostname 'node-5rs.pool-113-53.dynamic.totinternet.net' has the following IP addresses:
2023-07-01 08:08:36 41327 [Note] - 113.53.29.56
2023-07-01 08:18:13 41327 [Warning] Host name 'abts-tn-static-59.2.185.136.airtelbroadband.in' could not be resolved: Name does not resolve
2023-07-01 08:18:44 41327 [Warning] IP address '223.226.221.190' could not be resolved: Name does not resolve
2023-07-01 08:29:10 41327 [Warning] IP address '103.230.102.209' could not be resolved: Name does not resolve
2023-07-01 08:29:10 41327 [Warning] IP address '103.230.102.125' could not be resolved: Name does not resolve
2023-07-01 08:29:11 41327 [Warning] IP address '103.230.102.173' could not be resolved: Name does not resolve
2023-07-01 08:29:11 41327 [Warning] IP address '103.230.102.116' could not be resolved: Name does not resolve
2023-07-01 08:29:12 41327 [Warning] IP address '103.230.102.234' could not be resolved: Name does not resolve
2023-07-01 08:29:13 41327 [Warning] IP address '103.230.102.28' could not be resolved: Name does not resolve
2023-07-01 08:29:13 41327 [Warning] IP address '103.230.102.10' could not be resolved: Name does not resolve
2023-07-01 08:29:14 41327 [Warning] IP address '103.230.102.203' could not be resolved: Name does not resolve
2023-07-01 08:29:14 41327 [Warning] IP address '103.230.102.178' could not be resolved: Name does not resolve
2023-07-01 08:29:15 41327 [Warning] IP address '103.230.102.197' could not be resolved: Name does not resolve
2023-07-01 08:29:16 41327 [Warning] IP address '103.230.102.24' could not be resolved: Name does not resolve
2023-07-01 08:29:18 41327 [Warning] IP address '103.230.102.108' could not be resolved: Name does not resolve
2023-07-01 08:29:22 41327 [Warning] IP address '103.230.102.66' could not be resolved: Name does not resolve
2023-07-01 08:29:24 41327 [Warning] IP address '103.230.102.152' could not be resolved: Name does not resolve
2023-07-01 08:29:24 41327 [Warning] IP address '103.230.102.171' could not be resolved: Name does not resolve
2023-07-01 08:29:25 41327 [Warning] IP address '103.230.102.40' could not be resolved: Name does not resolve
2023-07-01 08:29:26 41327 [Warning] IP address '103.230.102.7' could not be resolved: Name does not resolve
2023-07-01 08:29:26 41327 [Warning] IP address '103.230.102.170' could not be resolved: Name does not resolve
2023-07-01 08:29:28 41327 [Warning] IP address '103.230.102.43' could not be resolved: Name does not resolve
2023-07-01 08:29:29 41327 [Warning] IP address '103.230.102.47' could not be resolved: Name does not resolve
2023-07-01 08:29:30 41327 [Warning] IP address '103.230.102.22' could not be resolved: Name does not resolve
2023-07-01 08:29:30 41327 [Warning] IP address '103.230.102.89' could not be resolved: Name does not resolve
2023-07-01 08:29:32 41327 [Warning] IP address '103.230.102.205' could not be resolved: Name does not resolve
2023-07-01 08:29:32 41327 [Warning] IP address '103.230.102.221' could not be resolved: Name does not resolve
2023-07-01 08:29:33 41327 [Warning] IP address '103.230.102.9' could not be resolved: Name does not resolve
2023-07-01 08:29:33 41327 [Warning] IP address '103.230.102.29' could not be resolved: Name does not resolve
2023-07-01 08:29:37 41327 [Warning] IP address '103.230.102.30' could not be resolved: Name does not resolve
2023-07-01 08:29:38 41327 [Warning] IP address '103.230.102.2' could not be resolved: Name does not resolve
2023-07-01 08:29:38 41327 [Warning] IP address '103.230.102.105' could not be resolved: Name does not resolve
2023-07-01 08:29:39 41327 [Warning] IP address '103.230.102.101' could not be resolved: Name does not resolve
2023-07-01 08:29:42 41327 [Warning] IP address '103.230.102.222' could not be resolved: Name does not resolve
2023-07-01 08:29:43 41327 [Warning] IP address '103.230.102.238' could not be resolved: Name does not resolve
2023-07-01 08:29:44 41327 [Warning] IP address '103.230.102.20' could not be resolved: Name does not resolve
2023-07-01 08:29:44 41327 [Warning] IP address '103.230.102.129' could not be resolved: Name does not resolve
2023-07-01 08:29:46 41327 [Warning] IP address '103.230.102.194' could not be resolved: Name does not resolve
2023-07-01 08:29:46 41327 [Warning] IP address '103.230.102.127' could not be resolved: Name does not resolve
2023-07-01 08:29:47 41327 [Warning] IP address '103.230.102.65' could not be resolved: Name does not resolve
2023-07-01 08:40:45 41327 [Warning] IP address '103.212.213.138' could not be resolved: Name does not resolve
2023-07-01 08:47:18 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:18 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:18 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:19 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:19 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:20 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:21 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:21 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:22 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:25 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:26 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:27 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:27 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:28 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:28 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:29 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:30 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:30 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:31 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:31 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:32 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:33 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:33 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:34 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:34 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:35 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:36 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:36 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:37 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:37 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:38 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:39 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:39 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:40 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:40 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:41 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:45 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:45 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:46 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:46 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:47 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:48 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:51 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:52 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:53 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:53 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:54 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:54 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:55 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:47:56 41327 [Warning] IP address '190.74.180.46' has been resolved to the host name '190.74-180-46.dyn.dsl.cantv.net', which resembles IPv4-address itself.
2023-07-01 08:50:23 41327 [Warning] IP address '43.224.156.18' could not be resolved: Name does not resolve
2023-07-01 09:45:44 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:44 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:45 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:45 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:46 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:47 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:47 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:48 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:49 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:49 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:50 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:51 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:51 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:52 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:53 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:53 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:54 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:54 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:55 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:56 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:56 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:57 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:58 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:45:58 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:01 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:02 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:02 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:03 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:04 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:04 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:05 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:06 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:06 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:07 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:08 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:08 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:09 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:10 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:10 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:11 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:12 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:12 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:13 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:14 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:14 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:15 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:15 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:16 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:17 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 09:46:17 41327 [Warning] IP address '124.83.43.83' has been resolved to the host name '124.83.43.83.pldt.net', which resembles IPv4-address itself.
2023-07-01 10:05:33 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:33 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:34 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:34 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:34 41327 [Warning] IP address '112.196.62.6' could not be resolved: Name does not resolve
2023-07-01 10:05:35 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:35 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:35 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:36 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:37 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:38 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:38 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:39 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:39 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:40 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:40 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:40 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:41 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:41 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:43 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:43 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:44 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:45 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:45 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:46 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:46 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:46 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:47 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:47 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:47 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:48 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:48 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:48 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:49 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:49 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:50 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:50 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:50 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:52 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:52 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:53 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:53 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:53 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:54 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:54 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:54 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:55 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:55 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:56 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:56 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:05:56 41327 [Warning] IP address '202.71.157.26' has been resolved to the host name '202.71.157.26.static.teleglobal.in', which resembles IPv4-address itself.
2023-07-01 10:52:32 41327 [Warning] IP address '112.196.33.226' could not be resolved: Name does not resolve
2023-07-01 11:19:12 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:12 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:12 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:13 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:13 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:14 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:14 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:14 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:15 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:15 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:16 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:16 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:17 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:17 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:18 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:18 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:18 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:19 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:19 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:20 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:20 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:21 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:21 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:22 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:22 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:23 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:23 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:24 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:24 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:25 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:25 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:26 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:26 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:26 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:27 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:27 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:28 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:28 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:29 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:29 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:30 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:30 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:31 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:31 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:32 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:32 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:33 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:33 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:33 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 11:19:34 41327 [Warning] IP address '202.83.25.230' has been resolved to the host name '202.83.25.230.actcorp.in', which resembles IPv4-address itself.
2023-07-01 12:02:58 41327 [Warning] IP address '210.89.61.45' could not be resolved: Name does not resolve
2023-07-01 12:02:58 41327 [Warning] IP address '210.89.61.45' could not be resolved: Name does not resolve
230701 12:12:48 mysqld_safe Logging to '/var/db/mysql/cloud619522.fastpipe.io.err'.
230701 12:12:48 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-07-01 12:12:49 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-07-01 12:12:49 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 933 ...
2023-07-01 12:12:49 933 [Note] Plugin 'FEDERATED' is disabled.
2023-07-01 12:12:49 933 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-07-01 12:12:49 933 [Note] InnoDB: The InnoDB memory heap is disabled
2023-07-01 12:12:49 933 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-01 12:12:49 933 [Note] InnoDB: Memory barrier is not used
2023-07-01 12:12:49 933 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-01 12:12:49 933 [Note] InnoDB: Not using CPU crc32 instructions
2023-07-01 12:12:49 933 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-07-01 12:12:49 933 [Note] InnoDB: Completed initialization of buffer pool
2023-07-01 12:12:50 933 [Note] InnoDB: Highest supported file format is Barracuda.
2023-07-01 12:12:50 933 [Note] InnoDB: The log sequence numbers 1807845 and 1807845 in ibdata files do not match the log sequence number 1807855 in the ib_logfiles!
2023-07-01 12:12:50 933 [Note] InnoDB: Database was not shutdown normally!
2023-07-01 12:12:50 933 [Note] InnoDB: Starting crash recovery.
2023-07-01 12:12:50 933 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-07-01 12:12:50 933 [Note] InnoDB: Restoring possible half-written data pages
2023-07-01 12:12:50 933 [Note] InnoDB: from the doublewrite buffer...
2023-07-01 12:12:50 80177f000 InnoDB: Error: table 'common/priv_settings'
InnoDB: in InnoDB data dictionary has tablespace id 7,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name common/priv_settings and id 16, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2023-07-01 12:12:50 933 [Note] InnoDB: 128 rollback segment(s) are active.
2023-07-01 12:12:50 933 [Note] InnoDB: Waiting for purge to start
2023-07-01 12:12:50 933 [Note] InnoDB: 5.6.51 started; log sequence number 1807855
2023-07-01 12:12:50 933 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-07-01 12:12:50 933 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-07-01 12:12:50 933 [Note] Server hostname (bind-address): '*'; port: 3306
2023-07-01 12:12:50 933 [Note] IPv6 is available.
2023-07-01 12:12:50 933 [Note] - '::' resolves to '::';
2023-07-01 12:12:50 933 [Note] Server socket created on IP: '::'.
2023-07-01 12:12:50 933 [Note] Event Scheduler: Loaded 0 events
2023-07-01 12:12:50 933 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2023-07-01 12:47:11 933 [Warning] IP address '185.233.19.30' could not be resolved: Name does not resolve
2023-07-01 12:49:31 933 [Warning] IP address '1.22.172.22' could not be resolved: Name does not resolve
230701 12:51:00 mysqld_safe mysqld restarted
2023-07-01 12:51:23 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-07-01 12:51:23 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 12060 ...
2023-07-01 12:51:23 12060 [Note] Plugin 'FEDERATED' is disabled.
2023-07-01 12:51:23 12060 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-07-01 12:51:23 12060 [Note] InnoDB: The InnoDB memory heap is disabled
2023-07-01 12:51:23 12060 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-01 12:51:23 12060 [Note] InnoDB: Memory barrier is not used
2023-07-01 12:51:23 12060 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-01 12:51:23 12060 [Note] InnoDB: Not using CPU crc32 instructions
2023-07-01 12:51:23 12060 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-07-01 12:51:23 12060 [Note] InnoDB: Completed initialization of buffer pool
2023-07-01 12:51:23 12060 [Note] InnoDB: Highest supported file format is Barracuda.
2023-07-01 12:51:23 12060 [Note] InnoDB: The log sequence numbers 1807845 and 1807845 in ibdata files do not match the log sequence number 1807865 in the ib_logfiles!
2023-07-01 12:51:23 12060 [Note] InnoDB: Database was not shutdown normally!
2023-07-01 12:51:23 12060 [Note] InnoDB: Starting crash recovery.
2023-07-01 12:51:23 12060 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-07-01 12:51:23 12060 [Note] InnoDB: Restoring possible half-written data pages
2023-07-01 12:51:23 12060 [Note] InnoDB: from the doublewrite buffer...
2023-07-01 12:51:23 80177f000 InnoDB: Error: table 'common/priv_settings'
InnoDB: in InnoDB data dictionary has tablespace id 7,
InnoDB: but a tablespace with that id does not exist. There is
InnoDB: a tablespace of name common/priv_settings and id 16, though. Have
InnoDB: you deleted or moved .ibd files?
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
2023-07-01 12:51:23 12060 [Note] InnoDB: 128 rollback segment(s) are active.
2023-07-01 12:51:23 12060 [Note] InnoDB: Waiting for purge to start
2023-07-01 12:51:23 12060 [Note] InnoDB: 5.6.51 started; log sequence number 1807865
2023-07-01 12:51:23 12060 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-07-01 12:51:23 12060 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-07-01 12:51:23 12060 [Note] Server hostname (bind-address): '*'; port: 3306
2023-07-01 12:51:23 12060 [Note] IPv6 is available.
2023-07-01 12:51:23 12060 [Note] - '::' resolves to '::';
2023-07-01 12:51:23 12060 [Note] Server socket created on IP: '::'.
2023-07-01 12:51:23 12060 [Note] Event Scheduler: Loaded 0 events
2023-07-01 12:51:23 12060 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2023-07-01 13:16:08 12060 [Note] /usr/local/libexec/mysqld: Normal shutdown
2023-07-01 13:16:08 12060 [Note] Giving 0 client threads a chance to die gracefully
2023-07-01 13:16:08 12060 [Note] Event Scheduler: Purging the queue. 0 events
2023-07-01 13:16:08 12060 [Note] Shutting down slave threads
2023-07-01 13:16:08 12060 [Note] Forcefully disconnecting 0 remaining clients
2023-07-01 13:16:08 12060 [Note] Binlog end
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'partition'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_METRICS'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_CMPMEM'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_CMP'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_LOCKS'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'INNODB_TRX'
2023-07-01 13:16:08 12060 [Note] Shutting down plugin 'InnoDB'
2023-07-01 13:16:08 12060 [Note] InnoDB: FTS optimize thread exiting.
2023-07-01 13:16:08 12060 [Note] InnoDB: Starting shutdown...
2023-07-01 13:16:09 12060 [Note] InnoDB: Shutdown completed; log sequence number 1807891
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'BLACKHOLE'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'ARCHIVE'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'MRG_MYISAM'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'MyISAM'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'MEMORY'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'CSV'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'sha256_password'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'mysql_old_password'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'mysql_native_password'
2023-07-01 13:16:09 12060 [Note] Shutting down plugin 'binlog'
2023-07-01 13:16:09 12060 [Note] /usr/local/libexec/mysqld: Shutdown complete
230701 13:16:09 mysqld_safe mysqld from pid file /var/db/mysql/cloud619522.fastpipe.io.pid ended
230701 13:16:59 mysqld_safe Logging to '/var/db/mysql/cloud619522.fastpipe.io.err'.
230701 13:16:59 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2023-07-01 13:17:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-07-01 13:17:00 0 [Note] /usr/local/libexec/mysqld (mysqld 5.6.51) starting as process 911 ...
2023-07-01 13:17:00 911 [Note] Plugin 'FEDERATED' is disabled.
2023-07-01 13:17:00 911 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-07-01 13:17:00 911 [Note] InnoDB: The InnoDB memory heap is disabled
2023-07-01 13:17:00 911 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-07-01 13:17:00 911 [Note] InnoDB: Memory barrier is not used
2023-07-01 13:17:00 911 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-07-01 13:17:00 911 [Note] InnoDB: Not using CPU crc32 instructions
2023-07-01 13:17:00 911 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-07-01 13:17:00 911 [Note] InnoDB: Completed initialization of buffer pool
2023-07-01 13:17:00 911 [Note] InnoDB: Highest supported file format is Barracuda.
2023-07-01 13:17:00 911 [Note] InnoDB: 128 rollback segment(s) are active.
2023-07-01 13:17:00 911 [Note] InnoDB: Waiting for purge to start
2023-07-01 13:17:00 911 [Note] InnoDB: 5.6.51 started; log sequence number 1807891
Warning: World-writable config file './auto.cnf' is ignored
2023-07-01 13:17:00 911 [Warning] World-writable config file './auto.cnf' has been removed.
2023-07-01 13:17:00 911 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: ccc3d8c1-1800-11ee-9a0b-00091f6dd229.
2023-07-01 13:17:00 911 [Note] RSA private key file not found: /var/db/mysql//private_key.pem. Some authentication plugins will not work.
2023-07-01 13:17:00 911 [Note] RSA public key file not found: /var/db/mysql//public_key.pem. Some authentication plugins will not work.
2023-07-01 13:17:00 911 [Note] Server hostname (bind-address): '*'; port: 3306
2023-07-01 13:17:00 911 [Note] IPv6 is available.
2023-07-01 13:17:00 911 [Note] - '::' resolves to '::';
2023-07-01 13:17:00 911 [Note] Server socket created on IP: '::'.
2023-07-01 13:17:00 911 [Warning] Insecure configuration for --pid-file: Location '/var/db/mysql' in the path is accessible to all OS users. Consider choosing a different directory.
2023-07-01 13:17:01 911 [Note] Event Scheduler: Loaded 0 events
2023-07-01 13:17:01 911 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.6.51' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2023-07-01 13:23:09 911 [Warning] Host name '3-150-171-152.fibertel.com.ar' could not be resolved: Name does not resolve
2023-07-01 13:40:10 911 [Warning] Host name '201-210-242-34.genericrev.cantv.net' could not be resolved: Name does not resolve
2023-07-01 13:40:56 911 [Warning] IP address '103.110.169.66' could not be resolved: Name does not resolve
2023-07-01 14:50:43 911 [Warning] IP address '49.43.218.145' could not be resolved: Name does not resolve
2023-07-01 15:24:31 911 [Warning] Host name 'pppoe-static-252-82.online.com.kh' could not be resolved: Name does not resolve
2023-07-01 15:45:25 911 [Warning] IP address '45.234.63.14' could not be resolved: Name does not resolve
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:53 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:54 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:55 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:56 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:57 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:57 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:57 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:57 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:57 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:57 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:57 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 15:55:57 911 [Warning] IP address '88.201.229.172' has been resolved to the host name '88.201.229.172.pool.sknt.ru', which resembles IPv4-address itself.
2023-07-01 16:17:03 911 [Warning] IP address '186.167.203.245' could not be resolved: Name does not resolve
230701 17:14:36 mysqld_safe mysqld restarted
230701 17:14:48 mysqld_safe mysqld from pid file /var/db/mysql/cloud619522.fastpipe.io.pid ended

Alles anzeigen

Jemand eine Ahnung woran das liegt? Hab alle Tipps ausm Internet durch (Rechte verteilen etc.)

EDIT:
Screen, dass der MySQL Server erst nachm Serverstart down geht:

Bitte melden Sie sich an, um diesen Anhang zu sehen.

Aura · 25. Juni 2023

Das hatten Sanii und Syreldar mal hier diskutiert:

Bitte melden Sie sich an, um diesen Link zu sehen.

Es soll wohl an der Methode liegen wie man items entfernt. Das mal angeschaut?

Aura · 24. Juni 2023

Nimm etwas Geld in die Hand und kauf das von Aslan, das ist im Gegensatz zu dem public Müll vernünftig

Aura · 18. Juni 2023

Zitat von California

Kann mir das System jemand erklären?

Es ist 2023 und dir muss jemand Battle Royale erklären?

Aura · 3. Juni 2023

Das hatte ich auch, der setzt die availIDt falsch, ich glaube 3 Stunden in die Zukunft. Müsste gucken wo ich das gefixt habe

EDIT: ich habs offenbar scheiße gelöst, aber "gelöst":

In /include/classes/user.php ist die Funktion "doLogin"
Ich habe da einfach

PHP

if(check_account_column('availDt') && check_availDt($userRow['id']))
return array(5, getLoginLastBanReason($userRow['id']), get_availDt($userRow['id']));

auskommentiert. Dadurch checkt der beim login nicht mehr ob du temporär gebannt bist, du kannst dich aber einloggen. Ich bin mir aber sicher dass er die availDt beim registrieren in die Zukunft setzt und beim login beim abfragen von der availDt (check_availDt Funktion in /include/functions/basic.php) denkt, dass du temporär gebannt bist weil die availDt > ist als die aktuelle Zeit. Muss man irgendwo vernünftig fixen können

Aura · 1. Juni 2023

Hallo,

ich habe den Itemshop von CYN3 verbaut. Soweit funktioniert auch alles, ich kann aber keine Kategorie anklicken.

Die erste, die automatisch ausgewählt ist, funktioniert. Die anderen sind nicht anklickbar. Syserr natürlich leer
Gif was das veranschaulicht:

Bitte melden Sie sich an, um diesen Anhang zu sehen.

Außerdem funktioniert das scrollen mit Mausrad nicht. Das geht in jedem anderen Window mit Scrollbar, nur im Itemshop nicht. Dafür auch jemand eine idee?

Aura · 18. April 2023

Nutze die:

Bitte melden Sie sich an, um diesen Anhang zu sehen.

Aura · 2. April 2023

Zitat von ToXiC

evt blockiert dein router neue ip vergabe oder sowas? haste mal deine ip tables gecleart? also da wo die ganzen geräte angezeigt werden kann sein

Hab die ganze Table gecleart gehabt.

Hab jetzt meinen PC angeschlossen, mit LAN Kabel verbunden - selbe Ergebnis. Es muss also eine Einstellung im Router sein, aber welche?

EDIT:
Hab jetzt mal VMWare Player genommen anstatt VirtualBox. Damit geht es. Sehr weird. aber ich hinterfrage es nicht. Trotzdem danke für eure Lösungsansätze

Aura · 31. März 2023

Was tatsächlich Arbeit abnehmen würde, wäre wenn man VNUM Bereiche einfügen könnte.

z.B Neue Rüstung +0-9 und ich möchte bei jeder höheren Stufe +50 Def mehr und angeben können, wie hoch die Bonis steigen sollen

Dann zb eine Preview was er einfügen wird, nach eingegebenen Parametern und dann einfach auf einfügen gehen. Hoffe es ist verständlich was ich meine

Aura · 28. März 2023

FreeBSD updaten oder Bitte melden Sie sich an, um diesen Link zu sehen.

Aura · 28. März 2023

Füg mal in deinem root Ordner in der localeinfo.py das ein:

Spoiler anzeigen

Aura · 28. März 2023

Hallo,

ich suche jemanden, der mir 2 Runmaps macht.

Es soll 2x die exakt selbe Map sein, beide nur mit anderen Themen.

Coden kann ich den selbst, brauche nur die Maps.

Gerne auf Discord anschreiben:

Aura#4903

Aura · 26. März 2023

Bitte melden Sie sich an, um diesen Anhang zu sehen.

Aura · 26. März 2023

Zitat von ToXiC

Zitat von xPain

Hat nichts damit zutun. Über Handyhotspot, auch WLAN, geht es. Es muss am Netzwerk liegen

das klingt richtig weird, ich hab auch ne fritzbox sämtliche ports immer freigegeben aber nicht für vm"s intern sondern halt nach außen, intern musste ich eig nie was freischalten egal ob im wlan oder nicht, müsste man sich mal bei dir direkt anglubschen.

porttriggering / portforwarding

Bitte melden Sie sich an, um diesen Anhang zu sehen.

ich hoste da kein m2 Stuff aber ich kann halt ganz normal auf meine vm"s zugreifen, ich nutz halt lan mit meinen 2 gigabit lan ports, die muss ich ab und anmal wechseln undso aber an sich gehts halt immer sofort, das was ich zensiert hab sind halt interne services undso aber haben halt nix mit m2 zutun

Alles anzeigen

Habs mit LAN getestet, genau dasselbe Ergebnis. Echt weird

Aura · 26. März 2023

Reup, falls jemand braucht:

Bitte melden Sie sich an, um diesen Anhang zu sehen.

Aura · 25. März 2023

Zitat von ToXiC

Zitat von xPain

Hey,

bin umgezogen, hab dadurch einen neuen DSL Vertrag mit neuem Router. Techniker war heute da und hat den Anschluss soweit freigeschaltet, funktioniert auch.
Wenn ich jetzt aber meine FreeBSD VM starten will, um auf meinem Source zu arbeiten, braucht WinSCP extrem lange zum verbinden
Bei Ordnerwechsel muss er jedes Mal neu zum "Server" verbinden, das dauert immer mindestens eine Minute
Netzwerkbrücke in den Einstellungen ist der WLAN Adapter von meinem Laptop. Ich habe nichts an den VM Einstellungen geändert, vor ein paar Tagen war ich noch mit meinem Handy Hotspot drinnen.
Muss ich irgendwas im Router einstellen, freischalten etc.? Es handelt sich um eine Fritzbox
Auf externe Server kann ich über WinSCP ohne Probleme zugreifen, es muss also an was anderem liegen

EDIT:
Kleiner Nachtrag:
Wenn ich von der VM aus google.com anpinge kommt folgendes:
Bitte melden Sie sich an, um diesen Anhang zu sehen.

Laut Google könnte es sein dass die VM nicht genug Ressourcen abbekommt um ein Netzwerk aufzubauen. Nachdem ich ein paar Einstellungen geändert habe keine Änderung. Neuer Ping:
Bitte melden Sie sich an, um diesen Anhang zu sehen.

Ums zu testen cleane FreeBSD VM aufgesetzt, genau dasselbe Ergebnis

EDIT:

Neuer Test. Hab wieder mit Handy Hotspot verbunden, damit geht das Netzwerk. Es muss also an dem WLAN liegen, bzw dann wohl dem Router. Jemand eine Idee?

Alles anzeigen
nutz halt Lan? Bei wlan ists klar das der lange braucht das ist Allgemein bekannt

Alles anzeigen

Hat nichts damit zutun. Über Handyhotspot, auch WLAN, geht es. Es muss am Netzwerk liegen

Aura · 24. März 2023

Hey,

bin umgezogen, hab dadurch einen neuen DSL Vertrag mit neuem Router. Techniker war heute da und hat den Anschluss soweit freigeschaltet, funktioniert auch.

Wenn ich jetzt aber meine FreeBSD VM starten will, um auf meinem Source zu arbeiten, braucht WinSCP extrem lange zum verbinden

Bei Ordnerwechsel muss er jedes Mal neu zum "Server" verbinden, das dauert immer mindestens eine Minute

Netzwerkbrücke in den Einstellungen ist der WLAN Adapter von meinem Laptop. Ich habe nichts an den VM Einstellungen geändert, vor ein paar Tagen war ich noch mit meinem Handy Hotspot drinnen.

Muss ich irgendwas im Router einstellen, freischalten etc.? Es handelt sich um eine Fritzbox

Auf externe Server kann ich über WinSCP ohne Probleme zugreifen, es muss also an was anderem liegen

EDIT:
Kleiner Nachtrag:
Wenn ich von der VM aus google.com anpinge kommt folgendes:

Bitte melden Sie sich an, um diesen Anhang zu sehen.

Laut Google könnte es sein dass die VM nicht genug Ressourcen abbekommt um ein Netzwerk aufzubauen. Nachdem ich ein paar Einstellungen geändert habe keine Änderung. Neuer Ping:

Bitte melden Sie sich an, um diesen Anhang zu sehen.

Ums zu testen cleane FreeBSD VM aufgesetzt, genau dasselbe Ergebnis

EDIT:

Neuer Test. Hab wieder mit Handy Hotspot verbunden, damit geht das Netzwerk. Es muss also an dem WLAN liegen, bzw dann wohl dem Router. Jemand eine Idee?

Aura · 5. März 2023

Moin,

wollte den IS auf den [40250] Reference Serverfiles einbauen.

Game klappt, bei DB kommt erst folgendes:

Spoiler anzeigen

Wenn ich die makefile anpasse, dass er nach boost sucht, kommt folgendes:

Spoiler anzeigen

C

In file included from ClientManagerBoot.cpp:13:
In file included from /usr/local/include/boost/uuid/detail/md5.hpp:29:
In file included from /usr/local/include/boost/cast.hpp:18:
In file included from /usr/local/include/boost/numeric/conversion/cast.hpp:33:
In file included from /usr/local/include/boost/numeric/conversion/converter.hpp:13:
In file included from /usr/local/include/boost/numeric/conversion/conversion_traits.hpp:13:
In file included from /usr/local/include/boost/numeric/conversion/detail/conversion_traits.hpp:18:
In file included from /usr/local/include/boost/numeric/conversion/detail/int_float_mixture.hpp:19:
In file included from /usr/local/include/boost/mpl/integral_c.hpp:32:
/usr/local/include/boost/mpl/aux_/integral_wrapper.hpp:73:31: error: integer value -1 is outside the valid range of values [0, 3] for this enumeration type [-Wenum-constexpr-conversion]
typedef AUX_WRAPPER_INST( BOOST_MPL_AUX_STATIC_CAST(AUX_WRAPPER_VALUE_TYPE, (value - 1)) ) prior;
^
/usr/local/include/boost/mpl/aux_/static_cast.hpp:24:47: note: expanded from macro 'BOOST_MPL_AUX_STATIC_CAST'
# define BOOST_MPL_AUX_STATIC_CAST(T, expr) static_cast<T>(expr)
^
In file included from ClientManagerBoot.cpp:13:
In file included from /usr/local/include/boost/uuid/detail/md5.hpp:29:
In file included from /usr/local/include/boost/cast.hpp:18:
In file included from /usr/local/include/boost/numeric/conversion/cast.hpp:33:
In file included from /usr/local/include/boost/numeric/conversion/converter.hpp:13:
In file included from /usr/local/include/boost/numeric/conversion/conversion_traits.hpp:13:
In file included from /usr/local/include/boost/numeric/conversion/detail/conversion_traits.hpp:18:
In file included from /usr/local/include/boost/numeric/conversion/detail/int_float_mixture.hpp:19:
In file included from /usr/local/include/boost/mpl/integral_c.hpp:32:
/usr/local/include/boost/mpl/aux_/integral_wrapper.hpp:73:31: error: integer value -1 is outside the valid range of values [0, 3] for this enumeration type [-Wenum-constexpr-conversion]
/usr/local/include/boost/mpl/aux_/static_cast.hpp:24:47: note: expanded from macro 'BOOST_MPL_AUX_STATIC_CAST'
# define BOOST_MPL_AUX_STATIC_CAST(T, expr) static_cast<T>(expr)
^
In file included from ClientManagerBoot.cpp:13:
In file included from /usr/local/include/boost/uuid/detail/md5.hpp:29:
In file included from /usr/local/include/boost/cast.hpp:18:
In file included from /usr/local/include/boost/numeric/conversion/cast.hpp:33:
In file included from /usr/local/include/boost/numeric/conversion/converter.hpp:13:
In file included from /usr/local/include/boost/numeric/conversion/conversion_traits.hpp:13:
In file included from /usr/local/include/boost/numeric/conversion/detail/conversion_traits.hpp:18:
In file included from /usr/local/include/boost/numeric/conversion/detail/int_float_mixture.hpp:19:
In file included from /usr/local/include/boost/mpl/integral_c.hpp:32:
/usr/local/include/boost/mpl/aux_/integral_wrapper.hpp:73:31: error: integer value -1 is outside the valid range of values [0, 3] for this enumeration type [-Wenum-constexpr-conversion]
/usr/local/include/boost/mpl/aux_/static_cast.hpp:24:47: note: expanded from macro 'BOOST_MPL_AUX_STATIC_CAST'
# define BOOST_MPL_AUX_STATIC_CAST(T, expr) static_cast<T>(expr)
^
In file included from ClientManagerBoot.cpp:13:
In file included from /usr/local/include/boost/uuid/detail/md5.hpp:29:
In file included from /usr/local/include/boost/cast.hpp:18:
In file included from /usr/local/include/boost/numeric/conversion/cast.hpp:33:
In file included from /usr/local/include/boost/numeric/conversion/converter.hpp:13:
In file included from /usr/local/include/boost/numeric/conversion/conversion_traits.hpp:13:
In file included from /usr/local/include/boost/numeric/conversion/detail/conversion_traits.hpp:18:
In file included from /usr/local/include/boost/numeric/conversion/detail/int_float_mixture.hpp:19:
In file included from /usr/local/include/boost/mpl/integral_c.hpp:32:
/usr/local/include/boost/mpl/aux_/integral_wrapper.hpp:72:31: error: integer value 4 is outside the valid range of values [0, 3] for this enumeration type [-Wenum-constexpr-conversion]
typedef AUX_WRAPPER_INST( BOOST_MPL_AUX_STATIC_CAST(AUX_WRAPPER_VALUE_TYPE, (value + 1)) ) next;
^
/usr/local/include/boost/mpl/aux_/static_cast.hpp:24:47: note: expanded from macro 'BOOST_MPL_AUX_STATIC_CAST'
# define BOOST_MPL_AUX_STATIC_CAST(T, expr) static_cast<T>(expr)
^
4 errors generated.
gmake: *** [Makefile:66: .obj/ClientManagerBoot.o] Error 1
gmake: *** Waiting for unfinished jobs....

Alles anzeigen

Jemand eine Idee?

Aura · 25. Januar 2023

Wish:
Like already suggested, diffrent currencies, like Items

Beiträge von Aura

MySQL Server verliert connection

MySQL Server verliert connection

real_time items verschwinden (manchmal) im nemeres Turm

Battlepass 1970-01-01 01:00:00 Unix Time

Official Battle Royale[REVERSED]

Das Konto ist vorübergehend gesperrt. () - Metin2CMS

Itemshop CYN3 Button Probleme

Suche Ingame Namens Änderung

Zugriff auf lokale VM sehr langsam

[Preview] Proto-Tool by Zynko

FreeBSD keine installation möglich (MySQL, Python etc.)

Save Login Interface syserr fehler

2x Runmap

Suche Schlaf Texturen

Zugriff auf lokale VM sehr langsam

EterNexus ohne Werbung

Zugriff auf lokale VM sehr langsam

Zugriff auf lokale VM sehr langsam

[Free] Itemshop by sura_head

[Question] Offlineshop