Ben Chambers wrote:

Try:

cd /var/lib/system-mysql/

/usr/clearos/sandbox/usr/bin/innochecksum -d ibdata1

service mariadb start

Any joy?

B.

Thanks Ben

Heres what Ive got for both

[root@server ~]# systemctl status mariadb
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2016-04-19 11:30:59 CDT; 6h ago
Process: 994 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS)
Process: 647 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 993 (mysqld_safe)
CGroup: /system.slice/mariadb.service
├─ 993 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
└─1468 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysq...

Apr 19 11:30:34 server.the-killians.com systemd[1]: Starting MariaDB database server...
Apr 19 11:30:38 server.the-killians.com mysqld_safe[993]: 160419 11:30:38 mysqld_safe Logging to '/var/...g'.
Apr 19 11:30:39 server.the-killians.com mysqld_safe[993]: 160419 11:30:39 mysqld_safe Starting mysqld d...sql
Apr 19 11:30:59 server.the-killians.com systemd[1]: Started MariaDB database server.
Apr 19 17:35:50 server.the-killians.com systemd[1]: Started MariaDB database server.
Hint: Some lines were ellipsized, use -l to show in full.

Ben Chambers wrote:

Try:

cd /var/lib/system-mysql/

/usr/clearos/sandbox/usr/bin/innochecksum -d ibdata1

service mariadb start

Any joy?

B.

[root@server ~]# cd /var/lib/system-mysql/
[root@server system-mysql]# /usr/clearos/sandbox/usr/bin/innochecksum -d ibdata1
file ibdata1 = 60817408 bytes (3712 pages)...
checking pages in range 0 to 3711
page 0: log sequence number: first = 265548142; second = 265531498
page 0 invalid (fails log sequence number check)
[root@server system-mysql]# service mariadb start
Redirecting to /bin/systemctl start mariadb.service
[root@server system-mysql]#

Try:

cd /var/lib/system-mysql/

/usr/clearos/sandbox/usr/bin/innochecksum -d ibdata1

service mariadb start

Any joy?

B.

Try to start either one and Im getting "command execution failed"

.

That seems like a different problem entirely.

Let's get some more information from the command line:

service mariadb start

systemctl status mariadb

B.

Im guessing theres no way to fix this?

Output of my system-mariadb log after reboot
Not much showing




160419 11:30:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/system-mysql
160419 11:30:46 InnoDB: The InnoDB memory heap is disabled
160419 11:30:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160419 11:30:46 InnoDB: Compressed tables use zlib 1.2.7
160419 11:30:46 InnoDB: Using Linux native AIO
160419 11:30:47 InnoDB: Initializing buffer pool, size = 500.0M
160419 11:30:47 InnoDB: Completed initialization of buffer pool
InnoDB: Error: checksum mismatch in data file ./ibdata1
160419 11:30:47 InnoDB: Could not open or create data files.
160419 11:30:47 InnoDB: If you tried to add new data files, and it failed here,
160419 11:30:47 InnoDB: you should now edit innodb_data_file_path in my.cnf back
160419 11:30:47 InnoDB: to what it was, and remove the new ibdata files InnoDB created
160419 11:30:47 InnoDB: in this failed attempt. InnoDB only wrote those files full of
160419 11:30:47 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
160419 11:30:47 InnoDB: remove old data files which contain your precious data!
160419 11:30:47 [ERROR] Plugin 'InnoDB' init function returned error.
160419 11:30:47 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160419 11:30:48 [Note] Plugin 'FEEDBACK' is disabled.
160419 11:30:49 [ERROR] Unknown/unsupported storage engine: InnoDB
160419 11:30:49 [ERROR] Aborting

160419 11:30:49 [Note] /usr/clearos/sandbox/usr/libexec/mysqld: Shutdown complete

160419 11:30:49 mysqld_safe mysqld from pid file /var/run/system-mariadb/mariadb.pid ended

Did anyone come up with a fix for this? My system-mariadb has crashed and wont restart. Naturally my zarafa server is offline as well.
Try to start either one and Im getting "command execution failed"
My regular mariadb is running but the system one is dead.
I noticed that a few days ago mariadb got an update.

Anyone
TIA

Now my Samba wont initialize after the reinstall.

I could duplicate this issue and made Pete aware...created a bug tracker here. There's actually a suggested fix in that tracker that worked for me..a one line change to /usr/clearos/apps/samba/libraries/OpenLDAP_Driver.php...however, this is not my area of expertise, and Pete may have more to say on the subject in due time.

B.

Thanks for the help. I didnt really have anything of importance on the server yet so I just wiped and reinstalled.
Now my Samba wont initialize after the reinstall. Friggin wonderful Im back to that again and this is on the home edition.
I Just want to go back to 6.6 or 6.7
This 7 is a disaster for me every time I install it. The only thing holding me back is the home essentials I purchased. If I could put home essentials on 6.7 I would be set

Seems your sandboxed MySQL (system-mariadb) database is up and running, no? Can you get a SQL console connected to the Zarafa DB?

cat /var/clearos/system_database/zarafa

/usr/clearos/sandbox/usr/bin/mysql zarafa -uzarafa -p"xxx"

show tables

B

[root@server ~]# /bin/systemctl start system-mariadb.service
Job for system-mariadb.service failed because the control process exited with error code. See "systemctl status system-mariadb.service" and "journalctl -xe" for details.
[root@server ~]# systemctl status mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2016-01-10 14:50:23 CST; 54min ago
Process: 1007 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS)
Process: 708 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 1006 (mysqld_safe)
CGroup: /system.slice/mariadb.service
├─1006 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
└─1223 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-di...

Jan 10 14:50:02 server.the-killians.com systemd[1]: Starting MariaDB database server...
Jan 10 14:50:04 server.the-killians.com mysqld_safe[1006]: 160110 14:50:04 mysqld_safe L....
Jan 10 14:50:05 server.the-killians.com mysqld_safe[1006]: 160110 14:50:05 mysqld_safe S...l
Jan 10 14:50:23 server.the-killians.com systemd[1]: Started MariaDB database server.
Hint: Some lines were ellipsized, use -l to show in full.

What's in your /var/log/messages log file?

If you try and start system-mariadb, does it start?

/bin/systemctl start  system-mariadb.service

systemctl status mariadb.service

B

Got a fatal error

[root@server ~]# cat /var/clearos/system_database/root
password = SxR+GcRkpuHXTyY+hKLEfk/SweWFduFSJaKDcuN0
[root@server ~]# /usr/clearos/sandbox/usr/bin/mysql_upgrade -uroot -p
Enter password:
Version check failed. Got the following error when calling the 'mysql' command line client
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/system-mysql/mysql.sock' (2)
FATAL ERROR: Upgrade failed
[root@server ~]#

I wonder if this may be of some help...

B