ServerForum.org - The Professional IT Community

Hello, 

regarding a maintenance on the host system where my VPS is running the hoster have restart the server. Since the restart my MYSQL database server is not starting anymore. After trying to start the MYSQL server manually I can see the following message in the command line: 

Quote:mysqld_safe Can't log to error log and syslog at the same time.  Remove all --log-error configuration options for --syslog to take effect.

Currnent system setup:

‪Ubuntu 14.04.5 LTS‬
Intel Xeon X5650
Plesk Onyx Version 17.5
MYSQL Server-Version: 5.6.38 - MySQL Community Server

MYSQL error log file: 

Quote:170619 11:40:52 mysqld_safe Logging to '/var/log/mysql/error.log'.
170619 11:40:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2018-01-09 11:40:52 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
2018-01-09 11:40:52 0 [Warning] option 'thread_concurrency': unsigned value 0 adjusted to 1
2018-01-09 11:40:52 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2018-01-09 11:40:52 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-01-09 11:40:52 0 [Note] /usr/sbin/mysqld (mysqld 5.6.36) starting as process 29712 ...
2018-01-09 11:40:52 29712 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)

2018-01-09 11:40:52 29712 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 512)

2018-01-09 11:40:52 29712 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
2018-01-09 11:40:52 29712 [Note] Plugin 'FEDERATED' is disabled.
2018-01-09 11:40:52 7f2293e00780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2018-01-09 11:40:52 29712 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-01-09 11:40:52 29712 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-09 11:40:52 29712 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-01-09 11:40:52 29712 [Note] InnoDB: Memory barrier is not used
2018-01-09 11:40:52 29712 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-01-09 11:40:52 29712 [Note] InnoDB: Using Linux native AIO
2018-01-09 11:40:52 29712 [Note] InnoDB: Using CPU crc32 instructions
2018-01-09 11:40:52 29712 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2018-01-09 11:40:52 29712 [Note] InnoDB: Completed initialization of buffer pool
2018-01-09 11:40:52 29712 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-09 11:40:52 29712 [Note] InnoDB: Log scan progressed past the checkpoint lsn 20113308285
2018-01-09 11:40:52 29712 [Note] InnoDB: Database was not shutdown normally!
2018-01-09 11:40:52 29712 [Note] InnoDB: Starting crash recovery.
2018-01-09 11:40:52 29712 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-01-09 11:40:52 29712 [ERROR] InnoDB: Tried to read 16384 bytes at offset 0. Was only able to read 0.
2018-01-09 11:40:52 7f2293e00780  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2018-01-09 11:40:52 29712 [ERROR] InnoDB: File (unknown): 'read' returned OS error 71. Cannot continue operation
170619 11:40:52 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Can anyone please help on this issue the last backup is from 03.12.2017 a lot of mails and important data are saved on the MYSQL server. 


Thank you in advanced

Update

The forcing InnoDB Recovery solution has not working for me. I have fixed the issue as follows: 

1) remove the syslog entry under --> /etc/mysql/conf.d/mysqld_safe_syslog.cnf
2) backup & remove both ib_logfile0 & ib_logfile1 files under --> /var/lib/mysql
3) remov entry innodb_force_recovery = 1 from --> etc/mysql/my.cnf
4) command --> sudo service mysql start 
5) server is starting and works fine again without loosing any data