szogun

Sama VestaCP raczej nie wywala mysql, ponieważ przed wrzuceniem skryptu działała stabilnie przez prawie pół roku. Co do skryptu,który uruchamia on zapisuje i odczytuje dane z mysql niestety dużo o nim nie mogę powiedzieć ponieważ sam kod jest zakodowany aby nie łamać jego licencji niestety chwilowo kontakt z autorem jest utrudniony z racji urlopu. Co do samego skryptu nie mogę znaleźć nic godnego aby zrobić kontrolowany crash mysql czy miał byś może jakiś link? Może przydadzą się log MySQLa 2019-07-31T04:52:21.167720Z 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 5000) 2019-07-31T04:52:21.381943Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2019-07-31T04:52:21.384449Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-0ubuntu0.16.04.1) starting as process 8542 ... 2019-07-31T04:52:21.391678Z 0 [Note] InnoDB: PUNCH HOLE support available 2019-07-31T04:52:21.391722Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-07-31T04:52:21.391728Z 0 [Note] InnoDB: Uses event mutexes 2019-07-31T04:52:21.391733Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2019-07-31T04:52:21.391741Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8 2019-07-31T04:52:21.391747Z 0 [Note] InnoDB: Using Linux native AIO 2019-07-31T04:52:21.392181Z 0 [Note] InnoDB: Number of pools: 1 2019-07-31T04:52:21.392337Z 0 [Note] InnoDB: Using CPU crc32 instructions 2019-07-31T04:52:21.394586Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2019-07-31T04:52:21.409390Z 0 [Note] InnoDB: Completed initialization of buffer pool 2019-07-31T04:52:21.412852Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2019-07-31T04:52:21.429271Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2019-07-31T04:52:21.470833Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2019-07-31T04:52:21.470950Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2019-07-31T04:52:21.656559Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2019-07-31T04:52:21.658568Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2019-07-31T04:52:21.658603Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2019-07-31T04:52:21.659053Z 0 [Note] InnoDB: Waiting for purge to start 2019-07-31T04:52:21.709353Z 0 [Note] InnoDB: 5.7.27 started; log sequence number 780369815 2019-07-31T04:52:21.709866Z 0 [Note] Plugin 'FEDERATED' is disabled. 2019-07-31T04:52:21.718690Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2019-07-31T04:52:21.728801Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190731 6:52:21 2019-07-31T04:52:21.732432Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key 2019-07-31T04:52:21.732462Z 0 [Note] Server hostname (bind-address): '*'; port: 3306 2019-07-31T04:52:21.732528Z 0 [Note] IPv6 is available. 2019-07-31T04:52:21.732541Z 0 [Note] - '::' resolves to '::'; 2019-07-31T04:52:21.732582Z 0 [Note] Server socket created on IP: '::'. 2019-07-31T04:52:21.743417Z 0 [Note] Event Scheduler: Loaded 0 events 2019-07-31T04:52:21.743592Z 0 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.7.27-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 2019-07-31T04:52:22.189532Z 2 [Note] Access denied for user 'root'@'localhost' (using password: NO) 2019-07-31T04:52:22.210926Z 3 [Note] Access denied for user 'debian-sys-maint'@'localhost' (using password: YES) 2019-07-31T04:52:22.385031Z 0 [Note] Giving 0 client threads a chance to die gracefully 2019-07-31T04:52:22.385067Z 0 [Note] Shutting down slave threads 2019-07-31T04:52:22.385071Z 0 [Note] Forcefully disconnecting 0 remaining clients 2019-07-31T04:52:22.385079Z 0 [Note] Event Scheduler: Purging the queue. 0 events 2019-07-31T04:52:22.385116Z 0 [Note] Binlog end 2019-07-31T04:52:22.385481Z 0 [Note] Shutting down plugin 'ngram' 2019-07-31T04:52:22.385491Z 0 [Note] Shutting down plugin 'partition' 2019-07-31T04:52:22.385495Z 0 [Note] Shutting down plugin 'BLACKHOLE' 2019-07-31T04:52:22.385499Z 0 [Note] Shutting down plugin 'ARCHIVE' 2019-07-31T04:52:22.385501Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL' 2019-07-31T04:52:22.385505Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2019-07-31T04:52:22.385517Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2019-07-31T04:52:22.385520Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2019-07-31T04:52:22.385523Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2019-07-31T04:52:22.385525Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2019-07-31T04:52:22.385528Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2019-07-31T04:52:22.385531Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2019-07-31T04:52:22.385533Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2019-07-31T04:52:22.385536Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2019-07-31T04:52:22.385538Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2019-07-31T04:52:22.385541Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2019-07-31T04:52:22.385543Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2019-07-31T04:52:22.385546Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2019-07-31T04:52:22.385549Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2019-07-31T04:52:22.385551Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2019-07-31T04:52:22.385554Z 0 [Note] Shutting down plugin 'INNODB_METRICS' 2019-07-31T04:52:22.385556Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO' 2019-07-31T04:52:22.385559Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2019-07-31T04:52:22.385561Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2019-07-31T04:52:22.385564Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2019-07-31T04:52:22.385566Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 2019-07-31T04:52:22.385569Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 2019-07-31T04:52:22.385572Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 2019-07-31T04:52:22.385574Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM' 2019-07-31T04:52:22.385577Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET' 2019-07-31T04:52:22.385579Z 0 [Note] Shutting down plugin 'INNODB_CMP' 2019-07-31T04:52:22.385582Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 2019-07-31T04:52:22.385584Z 0 [Note] Shutting down plugin 'INNODB_LOCKS' 2019-07-31T04:52:22.385587Z 0 [Note] Shutting down plugin 'INNODB_TRX' 2019-07-31T04:52:22.385589Z 0 [Note] Shutting down plugin 'InnoDB' 2019-07-31T04:52:22.385651Z 0 [Note] InnoDB: FTS optimize thread exiting. 2019-07-31T04:52:22.386213Z 0 [Note] InnoDB: Starting shutdown... 2019-07-31T04:52:22.486617Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool 2019-07-31T04:52:22.486847Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 190731 6:52:22 2019-07-31T04:52:23.305093Z 0 [Note] InnoDB: Shutdown completed; log sequence number 780369834 2019-07-31T04:52:23.311101Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2019-07-31T04:52:23.311146Z 0 [Note] Shutting down plugin 'MRG_MYISAM' 2019-07-31T04:52:23.311156Z 0 [Note] Shutting down plugin 'MEMORY' 2019-07-31T04:52:23.311163Z 0 [Note] Shutting down plugin 'CSV' 2019-07-31T04:52:23.311171Z 0 [Note] Shutting down plugin 'MyISAM' 2019-07-31T04:52:23.311184Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2019-07-31T04:52:23.311234Z 0 [Note] Shutting down plugin 'sha256_password' 2019-07-31T04:52:23.311239Z 0 [Note] Shutting down plugin 'mysql_native_password' 2019-07-31T04:52:23.311567Z 0 [Note] Shutting down plugin 'binlog' 2019-07-31T04:52:23.312262Z 0 [Note] /usr/sbin/mysqld: Shutdown complete 2019-07-31T04:52:23.571321Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2019-07-31T04:52:23.575054Z 0 [Note] mysqld (mysqld 5.7.27-0ubuntu0.16.04.1) starting as process 8627 ... 2019-07-31T04:52:23.583080Z 0 [Note] InnoDB: PUNCH HOLE support available 2019-07-31T04:52:23.583118Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-07-31T04:52:23.583127Z 0 [Note] InnoDB: Uses event mutexes 2019-07-31T04:52:23.583132Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2019-07-31T04:52:23.583146Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8 2019-07-31T04:52:23.583151Z 0 [Note] InnoDB: Using Linux native AIO 2019-07-31T04:52:23.583446Z 0 [Note] InnoDB: Number of pools: 1 2019-07-31T04:52:23.583599Z 0 [Note] InnoDB: Using CPU crc32 instructions 2019-07-31T04:52:23.586850Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2019-07-31T04:52:23.598598Z 0 [Note] InnoDB: Completed initialization of buffer pool 2019-07-31T04:52:23.601777Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2019-07-31T04:52:23.614942Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2019-07-31T04:52:23.636255Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2019-07-31T04:52:23.636348Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2019-07-31T04:52:23.786357Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2019-07-31T04:52:23.788487Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2019-07-31T04:52:23.788553Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2019-07-31T04:52:23.789076Z 0 [Note] InnoDB: Waiting for purge to start 2019-07-31T04:52:23.839348Z 0 [Note] InnoDB: 5.7.27 started; log sequence number 780369834 2019-07-31T04:52:23.839754Z 0 [Note] Plugin 'FEDERATED' is disabled. 2019-07-31T04:52:23.847885Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2019-07-31T04:52:23.850493Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190731 6:52:23 2019-07-31T04:52:23.857546Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key 2019-07-31T04:52:23.857577Z 0 [Note] Server hostname (bind-address): '*'; port: 3306 2019-07-31T04:52:23.857619Z 0 [Note] IPv6 is available. 2019-07-31T04:52:23.857624Z 0 [Note] - '::' resolves to '::'; 2019-07-31T04:52:23.857655Z 0 [Note] Server socket created on IP: '::'. 2019-07-31T04:52:23.861105Z 0 [Warning] Insecure configuration for --pid-file: Location '/tmp' in the path is accessible to all OS users. Consider choosing a different directory. 2019-07-31T04:52:23.871760Z 0 [Note] Event Scheduler: Loaded 0 events 2019-07-31T04:52:23.872051Z 0 [Note] Execution of init_file '/var/lib/mysql-files/tmp.cU2bIwrmWZ' started. 2019-07-31T04:52:23.875274Z 0 [Note] Execution of init_file '/var/lib/mysql-files/tmp.cU2bIwrmWZ' ended. 2019-07-31T04:52:23.875359Z 0 [Note] mysqld: ready for connections. Version: '5.7.27-0ubuntu0.16.04.1' socket: '/tmp/tmp.ranaPHcsgM/mysqld.sock' port: 3306 (Ubuntu) 2019-07-31T04:52:23.875583Z 0 [Note] Giving 0 client threads a chance to die gracefully 2019-07-31T04:52:23.875596Z 0 [Note] Shutting down slave threads 2019-07-31T04:52:23.875601Z 0 [Note] Forcefully disconnecting 0 remaining clients 2019-07-31T04:52:23.875607Z 0 [Note] Event Scheduler: Purging the queue. 0 events 2019-07-31T04:52:23.875641Z 0 [Note] Binlog end 2019-07-31T04:52:23.876081Z 0 [Note] Shutting down plugin 'ngram' 2019-07-31T04:52:23.876092Z 0 [Note] Shutting down plugin 'partition' 2019-07-31T04:52:23.876096Z 0 [Note] Shutting down plugin 'BLACKHOLE' 2019-07-31T04:52:23.876101Z 0 [Note] Shutting down plugin 'ARCHIVE' 2019-07-31T04:52:23.876104Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL' 2019-07-31T04:52:23.876108Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2019-07-31T04:52:23.876110Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2019-07-31T04:52:23.876113Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2019-07-31T04:52:23.876116Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2019-07-31T04:52:23.876119Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2019-07-31T04:52:23.876122Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2019-07-31T04:52:23.876125Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2019-07-31T04:52:23.876137Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2019-07-31T04:52:23.876140Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2019-07-31T04:52:23.876143Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2019-07-31T04:52:23.876146Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2019-07-31T04:52:23.876148Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2019-07-31T04:52:23.876151Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2019-07-31T04:52:23.876153Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2019-07-31T04:52:23.876156Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2019-07-31T04:52:23.876159Z 0 [Note] Shutting down plugin 'INNODB_METRICS' 2019-07-31T04:52:23.876162Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO' 2019-07-31T04:52:23.876164Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2019-07-31T04:52:23.876167Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2019-07-31T04:52:23.876169Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2019-07-31T04:52:23.876172Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 2019-07-31T04:52:23.876174Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 2019-07-31T04:52:23.876177Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 2019-07-31T04:52:23.876180Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM' 2019-07-31T04:52:23.876183Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET' 2019-07-31T04:52:23.876185Z 0 [Note] Shutting down plugin 'INNODB_CMP' 2019-07-31T04:52:23.876188Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 2019-07-31T04:52:23.876190Z 0 [Note] Shutting down plugin 'INNODB_LOCKS' 2019-07-31T04:52:23.876193Z 0 [Note] Shutting down plugin 'INNODB_TRX' 2019-07-31T04:52:23.876195Z 0 [Note] Shutting down plugin 'InnoDB' 2019-07-31T04:52:23.876252Z 0 [Note] InnoDB: FTS optimize thread exiting. 2019-07-31T04:52:23.876353Z 0 [Note] InnoDB: Starting shutdown... 2019-07-31T04:52:23.976740Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool 2019-07-31T04:52:23.976970Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 190731 6:52:23 2019-07-31T04:52:25.489235Z 0 [Note] InnoDB: Shutdown completed; log sequence number 780369853 2019-07-31T04:52:25.491904Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2019-07-31T04:52:25.491944Z 0 [Note] Shutting down plugin 'MRG_MYISAM' 2019-07-31T04:52:25.491954Z 0 [Note] Shutting down plugin 'MEMORY' 2019-07-31T04:52:25.491960Z 0 [Note] Shutting down plugin 'CSV' 2019-07-31T04:52:25.491968Z 0 [Note] Shutting down plugin 'MyISAM' 2019-07-31T04:52:25.491981Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2019-07-31T04:52:25.492140Z 0 [Note] Shutting down plugin 'sha256_password' 2019-07-31T04:52:25.492151Z 0 [Note] Shutting down plugin 'mysql_native_password' 2019-07-31T04:52:25.492352Z 0 [Note] Shutting down plugin 'binlog' 2019-07-31T04:52:25.493812Z 0 [Note] mysqld: Shutdown complete 2019-07-31T04:52:25.813556Z 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 5000) 2019-07-31T04:52:26.024547Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2019-07-31T04:52:26.028588Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-0ubuntu0.16.04.1) starting as process 8713 ... 2019-07-31T04:52:26.034710Z 0 [Note] InnoDB: PUNCH HOLE support available 2019-07-31T04:52:26.034755Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2019-07-31T04:52:26.034764Z 0 [Note] InnoDB: Uses event mutexes 2019-07-31T04:52:26.034772Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2019-07-31T04:52:26.034781Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8 2019-07-31T04:52:26.034788Z 0 [Note] InnoDB: Using Linux native AIO 2019-07-31T04:52:26.035217Z 0 [Note] InnoDB: Number of pools: 1 2019-07-31T04:52:26.035370Z 0 [Note] InnoDB: Using CPU crc32 instructions 2019-07-31T04:52:26.038744Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2019-07-31T04:52:26.051154Z 0 [Note] InnoDB: Completed initialization of buffer pool 2019-07-31T04:52:26.055691Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2019-07-31T04:52:26.068542Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 2019-07-31T04:52:26.108129Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2019-07-31T04:52:26.108234Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2019-07-31T04:52:26.278765Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2019-07-31T04:52:26.282183Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2019-07-31T04:52:26.282283Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2019-07-31T04:52:26.285420Z 0 [Note] InnoDB: Waiting for purge to start 2019-07-31T04:52:26.335863Z 0 [Note] InnoDB: 5.7.27 started; log sequence number 780369853 2019-07-31T04:52:26.336329Z 0 [Note] Plugin 'FEDERATED' is disabled. 2019-07-31T04:52:26.340264Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2019-07-31T04:52:26.343238Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190731 6:52:26 2019-07-31T04:52:26.350890Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key 2019-07-31T04:52:26.350915Z 0 [Note] Server hostname (bind-address): '*'; port: 3306 2019-07-31T04:52:26.350962Z 0 [Note] IPv6 is available. 2019-07-31T04:52:26.350967Z 0 [Note] - '::' resolves to '::'; 2019-07-31T04:52:26.350997Z 0 [Note] Server socket created on IP: '::'. 2019-07-31T04:52:26.359932Z 0 [Note] Event Scheduler: Loaded 0 events 2019-07-31T04:52:26.360132Z 0 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.7.27-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) 2019-07-31T04:52:26.838141Z 2 [Note] Access denied for user 'root'@'localhost' (using password: NO) 2019-07-31T04:52:27.067398Z 3 [Note] Access denied for user 'debian-sys-maint'@'localhost' (using password: YES) 2019-07-31T04:57:59.473427Z 6 [Warning] Host name 'hostby.fcloud.biz' could not be resolved: Name or service not known 2019-07-31T04:57:59.520326Z 6 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T05:19:42.011617Z 15 [Warning] IP address '217.182.74.157' has been resolved to the host name '157.ip-217-182-74.eu', which resembles IPv4-address itself. 2019-07-31T05:19:42.012190Z 15 [Note] Access denied for user 'admin_onesms'@'217.182.74.157' (using password: YES) 2019-07-31T05:52:21.419286Z 31 [Note] Access denied for user 'admin_onesms'@'217.182.74.157' (using password: YES) 2019-07-31T05:54:13.903085Z 32 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T06:50:58.573090Z 57 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T07:47:19.057958Z 80 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T07:51:50.146835Z 83 [Note] Aborted connection 83 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T07:54:26.656988Z 84 [Note] Aborted connection 84 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T08:43:31.331281Z 105 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T09:29:09.244634Z 124 [Note] Aborted connection 124 to db: 'admin_onerankme' user: 'admin_stats' host: 'o22.1sk.pl' (Got timeout reading communication packets) 2019-07-31T09:39:03.904706Z 140 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T09:41:01.000030Z 135 [Note] Aborted connection 135 to db: 'admin_onerankme' user: 'admin_stats' host: 'o22.1sk.pl' (Got timeout reading communication packets) 2019-07-31T10:26:22.478051Z 159 [Note] Aborted connection 159 to db: 'admin_onerankme' user: 'admin_stats' host: 'o22.1sk.pl' (Got timeout reading communication packets) 2019-07-31T10:35:11.242758Z 172 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T10:49:17.251925Z 177 [Note] Aborted connection 177 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T10:51:25.377333Z 178 [Note] Aborted connection 178 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T11:02:36.595963Z 185 [Note] Aborted connection 185 to db: 'admin_onerankme' user: 'admin_stats' host: 'o22.1sk.pl' (Got timeout reading communication packets) 2019-07-31T11:06:07.110811Z 192 [Note] Aborted connection 192 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T11:08:01.193101Z 195 [Note] Aborted connection 195 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T11:30:46.819226Z 206 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T11:42:31.417079Z 211 [Warning] IP address '218.60.67.89' could not be resolved: Name or service not known 2019-07-31T11:58:56.148512Z 236 [Note] Aborted connection 236 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T12:03:58.355154Z 239 [Note] Aborted connection 239 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T12:09:27.692826Z 242 [Note] Aborted connection 242 to db: 'admin_onerankme' user: 'admin_stats' host: 'o22.1sk.pl' (Got timeout reading communication packets) 2019-07-31T12:12:03.327934Z 247 [Note] Aborted connection 247 to db: 'admin_onerankme' user: 'admin_stats' host: 'o14.1sk.pl' (Got timeout reading communication packets) 2019-07-31T12:26:06.379434Z 256 [Note] Access denied for user 'root'@'88.214.26.17' (using password: YES) 2019-07-31T12:41:04.169274Z 262 [Note] Aborted connection 262 to db: 'admin_robot' user: 'admin_teamspeak' host: 'localhost' (Got timeout reading communication packets) 2019-07-31T12:41:13.309357Z 265 [Note] Aborted connection 265 to db: 'admin_robot' user: 'admin_teamspeak' host: 'localhost' (Got timeout reading communication packets) 2019-07-31T12:41:16.373380Z 266 [Note] Aborted connection 266 to db: 'admin_robot' user: 'admin_teamspeak' host: 'localhost' (Got timeout reading communication packets)

Tak resetowałem MySQLa. To już za dużo jak dla mnie więc sobie odpuszczę

Tak jest dostępna, nie ma nałożonych limitów. Teraz zauważyłem że w momencie gdy skrypt przestanie działać, wykonuję się zadanie z crontaba dodatkowo dziwnym trafem przed ostatnie dwa tygodnie gdy wykonywane było owe zadanie skrypt działał poprawnie gdzies wskazuje na to brak logów i zapisanych danych z mysql sudo /usr/local/vesta/bin/v-update-sys-vesta-all I teraz moje pytanie jak to pogodzić?

15:16:15 [Database] - Error, błędne zapytanie: `INSERT INTO server_info VALUES(:key, :value)` (Exception: `PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away Problem polega w tym że zapytanie jest dobre bo w momencie pojawienia się błędu gdy odpale ponownie skrypt wszytkie dane ponownie sie zapisują w dalszych logach wynalazłem dodatkow 2019-07-29T13:06:07.633431Z 4 [Note] Aborted connection 4 to db: 'xxx' user: 'xxx' host: 'localhost' (Got timeout reading communication packets) 2019-07-29T13:06:16.939920Z 7 [Note] Aborted connection 7 to db: 'xxx' user: 'xxx' host: 'localhost' (Got timeout reading communication packets) Obecnie ciężko stwierdzić ponieważ cały skrypt zapisuje logi przy każdej czynności te same lecz stawiam że jest to funkcja która zapisuje dane z serwera do mysql

Zmagam się z małym problemem na własnym vpsie z bazą danych PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server podczas gdy pierwszy raz błąd wystąpił, zmieniłem lekko konfigurację poszczególnych ustawień w bazie typu wait_timeout, innodb_log_file_size, max_allowed_packet lecz błąd po jakiś czasie powrócił i teraz pytanie jakie zalecacie ustawienie mysql aby błąd przestał się powtarzać [mysqld_safe] socket=/var/run/mysqld/mysqld.sock [mysqld] user=mysql pid-file=/var/run/mysqld/mysqld.pid socket=/var/run/mysqld/mysqld.sock port=3306 basedir=/usr datadir=/var/lib/mysql tmpdir=/tmp lc-messages-dir=/usr/share/mysql log_error=/var/log/mysql/error.log symbolic-links=0 skip-external-locking key_buffer_size = 16M max_allowed_packet = 1024M table_open_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M #innodb_use_native_aio = 0 innodb_file_per_table innodb_log_file_size = 1024MB max_connections=70 max_user_connections=30 wait_timeout=90 interactive_timeout=90 long_query_time=5 open_files_limit=5000 !includedir /etc/mysql/conf.d/

Mam takie pytanie czy jest realne zrobienie integracji bota z discorda do sterowania np. vpsem przez ssh oraz czy może jest już jakieś gotowe rozwiązanie?

Przeniesienie od nich domeny to jedne wielkie jaja, zgłaszając w panelu chęć uzyskania kodu authinfo na początku przebiegł w miarę sprawnie, na początku dostałem od nich email pod którym miałem wyrazić zgodę aby kod authinfo uzyskali w moim imieniu u pośrednika gdzie trzymają domeny po przesłaniu tego co kazali temat pozyskania kodu został zamieciony pod dywan do czasu gdy pewna Pani do mnie zadzwoniła że firma Hekko złożyła w moim imieniu pozyskanie kodu authinfo lecz przy tym nie dokonała wszystkich formalności przez co zamiast 7 dni czas pozyskania całego kodu wydłużył się na grubo ponad miesiąc czasu.

W sumie tak lecz sam autory skryptu już też pomógł wystarczyło w pliku Utils.php zmienić REMOTE_ADDR na HTTP_X_REAL_IP a samemu szukając własnie nie mogłem nigdzie tego znaleźć dla potom,nych plik znajduje się w private/php/Utils

Nginax działa jako proxy Pod tym wykrywa ip maszyny - echo $_SERVER['REMOTE_ADDR']; Jak dodałem sobie echo $_SERVER['HTTP_X_REAL_IP']; to już wykrywa moje ip

Witam Niestety moja wiedza już tak daleko nie sięga, posiadam na serwerze vps konfiguracje nginax z apache2 i po zainstalowaniu skryptu GitHub - Wruczek/ts-website: A website for your TeamSpeak 3 server zamiast wykrywać ip użytkownika wykrywa ip maszyny i problem leży w tym że nie potrafię samodzielnie tego ogarnąć

@OVH czy jest możliwość pozyskania większej pamięci ram dla vps ssd nie przechodząc na kolejny pakiet np. dajmy pakiet pierwszy który daję 20gb i 2 gb ramu aby pozyskać dla niego 4gb

No dobrze a jakiś pomysł jak uruchomić to na vpsie u nich ?

Witam Posiadam mały problem z uruchomieniem sekcji "monitoring" na ovh dla vpsa, na ich stronie można znaleźć instrukcję jak to aktywować https://docs.ovh.com/pl/dedicated/instalacja-rtm/ lecz po użyciu ich zalecanej komendy wyskakuje No such directory ‘made-in-ovh/rtm’.

Korzystam z sqlite, w tym problem że przeglądając bazę jest wpis "client_created" już robiłem porównywałem dwie bazy i nadal to samo

Hej mały problem z serwerem, który nie wiem jak za bardzo rozwiązać w logach mam 2019-03-25 21:15:32.946755|CRITICAL|DatabaseQuery | |unknown table field requested: client_created 2019-03-25 21:15:32.999343|WARNING |Query | |query connection closed unexpected: collate_byname<char>::collate_byname failed to construct for 2019-03-26 16:36:10.499394|CRITICAL|DatabaseQuery | |unknown table field requested: client_created 2019-03-26 16:36:10.569347|WARNING |Query | |query connection closed unexpected: collate_byname<char>::collate_byname failed to construct for 2019-03-26 16:37:53.397094|CRITICAL|DatabaseQuery | |unknown table field requested: client_created 2019-03-26 16:37:53.439212|WARNING |Query | |query connection closed unexpected: collate_byname<char>::collate_byname failed to construct for 2019-03-26 16:43:06.276373|CRITICAL|DatabaseQuery | |unknown table field requested: client_created 2019-03-26 16:43:06.324273|WARNING |Query | |query connection closed unexpected: collate_byname<char>::collate_byname failed to construct for 2019-03-26 16:44:18.219929|CRITICAL|DatabaseQuery | |unknown table field requested: client_created 2019-03-26 16:44:18.255212|WARNING |Query | |query connection closed unexpected: collate_byname<char>::collate_byname failed to construct for 2019-03-26 16:46:38.426858|CRITICAL|DatabaseQuery | |unknown table field requested: client_created 2019-03-26 16:46:38.473734|WARNING |Query | |query connection closed unexpected: collate_byname<char>::collate_byname failed to construct for 2019-03-26 16:55:17.645506|CRITICAL|DatabaseQuery | |unknown table field requested: client_created 2019-03-26 16:55:17.700141|WARNING |Query | |query connection closed unexpected: collate_byname<char>::collate_byname failed to construct for 2019-03-26 19:20:33.700636|CRITICAL|DatabaseQuery | |unknown table field requested: client_created

Mam mały problem z konfiguracją reguł w firewall na vpsie który opiera się o vesta panel, próbuje dodać Monitoring SLA z ovh aby poprawnie działa, na necie wyczytałem że muszę te zmiany wprowadzić ręcznie z racji że panel nie przyjmuje takiej formy ip Adresy ip jakie muszę dodać 92.222.184.0/24 92.222.185.0/24 92.222.186.0/24 167.114.37.0/24 217.182.72.4/32 Reguły jakie wprowadziłem w pliku RULE='19' ACTION='ACCEPT' PROTOCOL='ICMP' IP='92.222.184.0/24' COMMENT='IP Monitoring SLA' SUSPENDED='no' TIME='00:59:00' DATE='2019-01-30' RULE='20' ACTION='ACCEPT' PROTOCOL='ICMP' IP='92.222.185.0/24' COMMENT='IP Monitoring SLA' SUSPENDED='no' TIME='00:59:01' DATE='2019-01-30' RULE='21' ACTION='ACCEPT' PROTOCOL='ICMP' IP='92.222.186.0/24' COMMENT='IP Monitoring SLA' SUSPENDED='no' TIME='00:59:02' DATE='2019-01-30' RULE='22' ACTION='ACCEPT' PROTOCOL='ICMP' IP='167.114.37.0/24' COMMENT='IP Monitoring SLA' SUSPENDED='no' TIME='00:59:03' DATE='2019-01-30' RULE='22' ACTION='ACCEPT' PROTOCOL='ICMP' IP='217.182.72.4/32' COMMENT='IP Monitoring SLA' SUSPENDED='no' TIME='00:59:04' DATE='2019-01-30' I teraz po przejściu do zakładki firewall, automatycznie dodało wszystkim ip port 9987

Mój błąd, udało się, dziękuje za pomoc

Niby działa ale panel pokazuje że nadal serwery dns nie odpowiadaja.

Próbuje podpiąć domenę pod własne rekordy dns utworzone przez vesta panel Te kroki co opisałeś własnie robiłem w panelu ovh aby móc podpiąć domenę pod vpsa

Witam Zaczynam swoje początki z vps i mam mały problem z podpięciem domeny do niego , na samym vpsie korzystam z vestpa panel. W panelu klienta ovh dla vps w zakładce dns secondary dodałem domenę, która została poprawnie dodana i mam teraz dns secondary sdns2.ovh.net W panelu vesta panel dodałem Domyślne serwery nazw of1.ovh.net oraz of2.ovh.net lecz gdy zmienie dns dla domeny wskazuje ona że owe serwery nie odpowiadają, czy jest ktoś w stanie wytłumaczyć mi krok po kroku jak poprawnie to skonfigurować

Po kupnie vpsa trochę się zraziłem do nich, może dużej wiedzy nie mam ale po skorzystaniu z gotowej konfiguracji z vestacp co było mi potrzebne posiadałem lecz okazało się że magicznym sposobem vps na którym po tym zabiegu zabiegu nie było nic robione został teoretycznie przejęty do prawdopodobnych ataków co skutkowało jego blokada, teraz posiadam vps u konkurencji w takiej samej konfiguracji odziwo vps chodzi miesiąc czasu i nie został przejęty ani razu do rzekomych ataków co przytrafiało się na hekko

Dodałem, zresetowałem vpsa i nadal to samo, musze w terminalu wklepać polecenie bo inaczej nie może się serwer z vps połączyć. Edit w poleceniu jest mała wpadka chodzi o TCP

Cześć, podkreślę od razu na wstępie że jestem dopiero początkującym użytkownikiem vpsa, przejdźmy do sedna mam mały problem z portem po instalacji vesta panel za każdym razem gdy zresetuje vpsa muszę dodawać w terminalu polecenie sudo iptables -A INPUT -p udp --dport 4765 -m state --state NEW -j ACCEPT i teraz moje pytanie jak to skonfigurować aby po każdym restarcie vpsa nie trzeba klepać w terminalu. Z góry dziękuje za pomoc. Pozdrawiam

Robiąc krop po kroku co było opisane na samym końcu pojawiła się informacja o poprawnej konfiguracji.

W szybciej odpowiedzi gdy dodajemy jakiś cytat mamy czarne tło z bardzo ciemną czcionką przez do zawartość cytatu jest praktycznie niewidoczna