I have three nodes, they are all in a cluster, works normal,and one of the node(node3) is shutdown by accident(this VM crashed ).
And in the node3, I use:
systemctl start mariadb.service
to start the mariadb, but get error:
Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
So I use systemctl status mariadb.service to check:
[root#ha-node3 ~]# systemctl status mariadb.service
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Tue 2017-07-25 00:33:23 CST; 3min 7s ago
Process: 6125 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 5861 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 5857 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 6125 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
Jul 25 00:33:22 ha-node3 mysqld[6125]: at gcomm/src/pc.cpp:PC():271
Jul 25 00:33:22 ha-node3 mysqld[6125]: 2017-07-25 0:33:22 140428190394560 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():208: Failed to o...overable)
Jul 25 00:33:22 ha-node3 mysqld[6125]: 2017-07-25 0:33:22 140428190394560 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1380: Failed to open chann...overable)
Jul 25 00:33:22 ha-node3 mysqld[6125]: 2017-07-25 0:33:22 140428190394560 [ERROR] WSREP: gcs connect failed: State not recoverable
Jul 25 00:33:22 ha-node3 mysqld[6125]: 2017-07-25 0:33:22 140428190394560 [ERROR] WSREP: wsrep::connect(gcomm://192.168.8.101,192.168.8.102,19...failed: 7
Jul 25 00:33:22 ha-node3 mysqld[6125]: 2017-07-25 0:33:22 140428190394560 [ERROR] Aborting
Jul 25 00:33:23 ha-node3 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jul 25 00:33:23 ha-node3 systemd[1]: Failed to start MariaDB database server.
Jul 25 00:33:23 ha-node3 systemd[1]: Unit mariadb.service entered failed state.
Jul 25 00:33:23 ha-node3 systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
And use journalctl -xe to check:
[root#ha-node3 ~]# journalctl -xe
Jul 25 00:37:17 ha-node3 xinetd[1179]: START: mysqlchk pid=8544 from=::ffff:192.168.8.103
Jul 25 00:37:17 ha-node3 xinetd[1179]: EXIT: mysqlchk signal=13 pid=8544 duration=0(sec)
Jul 25 00:37:18 ha-node3 xinetd[1179]: START: mysqlchk pid=8548 from=::ffff:192.168.8.101
Jul 25 00:37:18 ha-node3 xinetd[1179]: START: mysqlchk pid=8553 from=::ffff:192.168.8.102
Jul 25 00:37:18 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8548 duration=0(sec)
Jul 25 00:37:18 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8553 duration=0(sec)
Jul 25 00:37:19 ha-node3 xinetd[1179]: START: mysqlchk pid=8560 from=::ffff:192.168.8.103
Jul 25 00:37:19 ha-node3 xinetd[1179]: EXIT: mysqlchk signal=13 pid=8560 duration=0(sec)
Jul 25 00:37:20 ha-node3 xinetd[1179]: START: mysqlchk pid=8564 from=::ffff:192.168.8.102
Jul 25 00:37:20 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8564 duration=0(sec)
Jul 25 00:37:20 ha-node3 xinetd[1179]: START: mysqlchk pid=8569 from=::ffff:192.168.8.101
Jul 25 00:37:20 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8569 duration=0(sec)
Jul 25 00:37:21 ha-node3 xinetd[1179]: START: mysqlchk pid=8574 from=::ffff:192.168.8.103
Jul 25 00:37:22 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8574 duration=1(sec)
Jul 25 00:37:22 ha-node3 xinetd[1179]: START: mysqlchk pid=8579 from=::ffff:192.168.8.102
Jul 25 00:37:22 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8579 duration=0(sec)
Jul 25 00:37:22 ha-node3 xinetd[1179]: START: mysqlchk pid=8584 from=::ffff:192.168.8.101
Jul 25 00:37:22 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8584 duration=0(sec)
Jul 25 00:37:24 ha-node3 xinetd[1179]: START: mysqlchk pid=8590 from=::ffff:192.168.8.103
Jul 25 00:37:24 ha-node3 xinetd[1179]: EXIT: mysqlchk signal=13 pid=8590 duration=0(sec)
Jul 25 00:37:24 ha-node3 xinetd[1179]: START: mysqlchk pid=8594 from=::ffff:192.168.8.102
Jul 25 00:37:24 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8594 duration=0(sec)
Jul 25 00:37:24 ha-node3 xinetd[1179]: START: mysqlchk pid=8599 from=::ffff:192.168.8.101
Jul 25 00:37:25 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8599 duration=1(sec)
Jul 25 00:37:26 ha-node3 xinetd[1179]: START: mysqlchk pid=8604 from=::ffff:192.168.8.103
Jul 25 00:37:26 ha-node3 xinetd[1179]: EXIT: mysqlchk signal=13 pid=8604 duration=0(sec)
Jul 25 00:37:26 ha-node3 xinetd[1179]: START: mysqlchk pid=8608 from=::ffff:192.168.8.102
Jul 25 00:37:26 ha-node3 xinetd[1179]: EXIT: mysqlchk status=1 pid=8608 duration=0(sec)
Jul 25 00:37:26 ha-node3 xinetd[1179]: START: mysqlchk pid=8613 from=::ffff:192.168.8.101
Someone can tell me why it can not start?
Finally, I found the /var/lib/mysql/gvwstate.dat is empty, from this link:https://community.emc.com/docs/DOC-55350
but my solution is not that way, I reboot the VM(node3), and it rebuild the file(gvwstate.dat).
So, I can start the mariadb now.
Related
I have some trouble with my MariaDB Server, it was working ok but it won't start anymore. When I try to start the server it failed:
root#vps45223599:/var/log# /etc/init.d/mysql start
[....] Starting mysql (via systemctl): mysql.serviceJob for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
failed!
root#vps45223599:/var/log# systemctl status mariadb.service
● mariadb.service - MariaDB 10.1.41 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2023-01-10 21:20:58 UTC; 1min 15s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 1349 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 1274 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR
Process: 1272 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 1271 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 1349 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
Jan 10 21:20:55 vps45223599.local systemd[1]: Starting MariaDB 10.1.41 database server...
Jan 10 21:20:55 vps45223599.local mysqld[1349]: 2023-01-10 21:20:55 140599894461824 [Note] /usr/sbin/mysqld (mysqld 10.1.41-MariaDB-0+deb9u1) starting as process 1349 ...
Jan 10 21:20:58 vps45223599.local systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jan 10 21:20:58 vps45223599.local systemd[1]: Failed to start MariaDB 10.1.41 database server.
Jan 10 21:20:58 vps45223599.local systemd[1]: mariadb.service: Unit entered failed state.
Jan 10 21:20:58 vps45223599.local systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jan 10 21:15:43 vps45223599.local systemd[1]: Failed to start MariaDB 10.1.41 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Jan 10 21:15:43 vps45223599.local systemd[1]: mariadb.service: Unit entered failed state.
Jan 10 21:15:43 vps45223599.local systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jan 10 21:15:43 vps45223599.local sudo[1040]: pam_unix(sudo:session): session closed for user root
Jan 10 21:15:50 vps45223599.local sudo[1146]: root : TTY=pts/1 ; PWD=/var/log ; USER=root ; COMMAND=/bin/systemctl start mariadb
Jan 10 21:15:50 vps45223599.local sudo[1146]: pam_unix(sudo:session): session opened for user root by cbarca(uid=0)
Jan 10 21:15:50 vps45223599.local systemd[1]: Failed to set devices.allow on /system.slice/mariadb.service: Operation not permitted
Jan 10 21:15:50 vps45223599.local systemd[1]: Failed to set devices.allow on /system.slice/mariadb.service: Operation not permitted
Jan 10 21:15:50 vps45223599.local systemd[1]: Starting MariaDB 10.1.41 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has begun starting up.
Jan 10 21:15:51 vps45223599.local mysqld[1227]: 2023-01-10 21:15:51 139968422329728 [Note] /usr/sbin/mysqld (mysqld 10.1.41-MariaDB-0+deb9u1) starting as process 1227 ...
Jan 10 21:15:54 vps45223599.local systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jan 10 21:15:54 vps45223599.local systemd[1]: Failed to start MariaDB 10.1.41 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Jan 10 21:15:54 vps45223599.local systemd[1]: mariadb.service: Unit entered failed state.
Jan 10 21:15:54 vps45223599.local systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jan 10 21:15:54 vps45223599.local sudo[1146]: pam_unix(sudo:session): session closed for user root
Jan 10 21:20:55 vps45223599.local systemd[1]: Failed to set devices.allow on /system.slice/mariadb.service: Operation not permitted
Jan 10 21:20:55 vps45223599.local systemd[1]: Failed to set devices.allow on /system.slice/mariadb.service: Operation not permitted
Jan 10 21:20:55 vps45223599.local systemd[1]: Starting MariaDB 10.1.41 database server...
-- Subject: Unit mariadb.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has begun starting up.
Jan 10 21:20:55 vps45223599.local mysqld[1349]: 2023-01-10 21:20:55 140599894461824 [Note] /usr/sbin/mysqld (mysqld 10.1.41-MariaDB-0+deb9u1) starting as process 1349 ...
Jan 10 21:20:58 vps45223599.local systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jan 10 21:20:58 vps45223599.local systemd[1]: Failed to start MariaDB 10.1.41 database server.
-- Subject: Unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mariadb.service has failed.
--
-- The result is failed.
Jan 10 21:20:58 vps45223599.local systemd[1]: mariadb.service: Unit entered failed state.
Jan 10 21:20:58 vps45223599.local systemd[1]: mariadb.service: Failed with result 'exit-code'.
I don't know what happened. I also try
mysqlcheck
root#vps45223599:/var/log# mysqlcheck --all-databases -p
Enter password:
mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory") when trying to connect
I don't know what else I should try, can anyone helpe me, please?
Cheers
As #obe said this is likely a proxmox or whatever is instigating systemd without sufficient privileges is the issue.
The devices.allow error is probably requested by the PrivateDevices=true (seems confirmed based on MDEV-13207 which failed to provide more info) aspect of the systemd service file for MariaDB.
PrivateDevices=true allows:
/dev/null
/dev/zero
/dev/random
Based on this answer for a different device, doing the equivalent for these devices would be:
lxc config set mycontainer raw.lxc 'lxc.cgroup.devices.allow = c 1:3 rwm'
lxc config set mycontainer raw.lxc 'lxc.cgroup.devices.allow = c 1:8 rwm'
lxc config set mycontainer raw.lxc 'lxc.cgroup.devices.allow = c 1:5 rwm'
Major/minor device code determined by:
$ ls -la /dev/zero /dev/random /dev/null
crw-rw-rw-. 1 root root 1, 3 Jan 8 22:20 /dev/null
crw-rw-rw-. 1 root root 1, 8 Jan 8 22:20 /dev/random
crw-rw-rw-. 1 root root 1, 5 Jan 8 22:20 /dev/zero
Thanks all for the answer.
#danblack Nothing change, suddenly stop working, but reading this forum I found the solution in this thread.
Can't start MariaDB on debian 10
Basically the solution is ...
"Solved it by deleting/renaming the tc.log mv -vi /var/lib/mysql/tc.log /root And restarting the database service mysql restart"
And mariaddb start again.
"systemctl enable openresty"
What I get
Synchronizing state of openresty.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable openresty
Failed to reload daemon: Access denied
Failed to reload daemon: Access denied
Failed to enable unit: Access denied
This the the screenshot
systemctl status openresty
openresty.service - The NGINX HTTP and reverse proxy server
Loaded: loaded (/lib/systemd/system/openresty.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-08-11 17:01:13 UTC; 2h 37min ago
Process: 8875 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=203/EXEC)
Aug 11 17:01:13 instance-2 systemd{1]: Starting The NGINX HTTP and reverse proxy server...
Aug 11 17:01:13 instance-2 systemd[8875]: openresty.service: Failed to execute command: No such file or directory
Aug 11 17:01:13 instance-2 systemd[8875]: openresty.service: Failed at step EXEC spawning /usr/sbin/nginx: No such file or directory
Aug 11 17:01:13 instance-2 systemd(1]: openresty.service: Control process exited, code=exited, status=203/EXEC
Aug 11 17:01:13 instance-2 systemd(1]: openresty.service: Failed with result 'exit-code'.
Aug 11 17:01:13 instance-2 systemd(1]: Failed to start The NGINX HTTP and reverse proxy server.
This is screenshot
journalctl -u openresty
-- Logs begin at Tue 2021-08-10 17:42:07 UTC, end at Wed 2021-08-11 19:20:05 UTC. --
Aug 10 19:14:22 instance-2 systemd(1]: Starting The OpenResty Application Platform...
Aug 10 19:14:22 instance-2 systemd(1]: Started The OpenResty Application Platform.
Aug 10 22:00:10 instance-2 systemd(1]: Stopping The OpenResty Application Platform...
Aug 10 22:00:10 instance-2 systemd(1]: openresty.service: Succeeded.
Aug 10 22:00:10 instance-2 systemd(1]: Stopped The OpenResty Application Platform.
Aug 10 22:00:10 instance-2 systemd(1]: Starting The OpenResty Application Platform...
Aug 10 22:00:10 instance-2 nginx[4012]: nginx: [emerg] directive "server_name" is not terminated by ";" in /etc/openresty/sites-enabled/m.facebook.com.conf:7
Aug 10 22:00:10 instance-2 nginx[4012]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed
Aug 10 22:00:10 instance-2 systemd(1]: openresty.service: Control process exited, code=exited, status=1/FAILURE
Aug 10 22:00:10 instance-2 systemd(1]: openresty.service: Failed with result 'exit-code'.
Aug 10 22:00:10 instance-2 systemd(1]: Failed to start The OpenResty Application Platform.
Aug 10 22:01:15 instance-2 systemd(1]: Starting The OpenResty Application Platform...
Aug 10 22:01:15 instance-2 nginx[4034]: nginx: [emerg] directive "server_name" is not terminated by ";" in /etc/openresty/sites-enabled/m.facebook.com.conf:7
Aug 10 22:01:15 instance-2 nginx[4034]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx. conf test failed
Aug 10 22:01:15 instance-2 systemd(1]: openresty. service: Control process exited, code=exited, status=1/FAILURE
Aug 10 22:01:15 instance-2 systemd(1]: openresty.service: Failed with result 'exit-code'.
Aug 10 22:01:15 instance-2 systemd(1]: Failed to start The OpenResty Application Platform.
Aug 11 17:01:13 instance-2 systemd(1]: Starting The NGINX HTTP and reverse proxy server...
Aug 11 17:01:13 instance-2 systemd[8875]: openresty.service: Failed to execute command: No such file or directory
Aug 11 17:01:13 instance-2 systemd[8875]: openresty.service: Failed at step EXEC spawning / usr /sbin / nginx : No such file or directory
Aug 11 17:01:13 instance-2 systemd(1]: openresty.service: Control process exited, code=exited, status=203/EXEC
Aug 11 17:01:13 instance-2 systemd(1]: openresty.service: Failed with result 'exit-code'.
Aug 11 17:01:13 instance-2 systemd(1]: Failed to start The NGINX HTTP and reverse proxy server.
This is screenshot
Sounds like you are trying to enable a service, from an account that is not privileged.
You may be able to use sudo, if the system is configured to allow this:
sudo systemctl enable openresty
If not, you would have to login as root:
su
[enter your root password]
systemctl enable openresty
One of my node was down and it was also the donor for the node A, so from node A config I removed the down node as donor. This is so that node A should not have to wait for the node to come up.
As the node that originally went down was on slow storage and slow network connection I decided to remove it. As I removed it and restarted the cluster even the node A didn't come up, on restart it started reporting error:
● mariadb.service - MariaDB 10.1.47 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2020-12-13 22:06:50 GMT; 12h ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 32653 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 17439 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_STA
Process: 17436 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 17432 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 32653 (code=exited, status=1/FAILURE)
CPU: 801ms
Dec 13 22:06:50 rockpi sh[17439]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html
Dec 13 22:06:50 rockpi sh[17439]: 2020-12-13 22:06:50 548039303184 [ERROR] Plugin 'InnoDB' init function returned error.
Dec 13 22:06:50 rockpi sh[17439]: 2020-12-13 22:06:50 548039303184 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Dec 13 22:06:50 rockpi sh[17439]: 2020-12-13 22:06:50 548039303184 [Note] Plugin 'FEEDBACK' is disabled.
Dec 13 22:06:50 rockpi sh[17439]: 2020-12-13 22:06:50 548039303184 [ERROR] Unknown/unsupported storage engine: innodb
Dec 13 22:06:50 rockpi sh[17439]: 2020-12-13 22:06:50 548039303184 [ERROR] Aborting'
Dec 13 22:06:50 rockpi systemd[1]: mariadb.service: Control process exited, code=exited status=1
Dec 13 22:06:50 rockpi systemd[1]: mariadb.service: Failed with result 'exit-code'.
Dec 13 22:06:50 rockpi systemd[1]: Failed to start MariaDB 10.1.47 database server.
Why it started reporting Unknown/unsupported storage engine innodb now when it was working all this time?
Incidentally, I used another third node to bootstrap (start Galera_new_cluster).
I have installed ubuntu 16.04 on a VMware VM. Then I added the repo from mariadb website and I installed the latest version of mariadb 10.1.
The installation works fine
I have then created a file
sudo nano /etc/mysql/conf.d/cluster.cnf
with the following
[mysqld]
# Cluster node configurations
wsrep_cluster_address="gcomm://20.0.1.51"
wsrep_node_address="20.0.1.51"
innodb_buffer_pool_size=800M
# Mandatory settings to enable Galera
wsrep_on=ON
wsrep_provider=/usr/lib/galera/libgalera_smm.so
binlog_format=ROW
default-storage-engine=InnoDB
innodb_autoinc_lock_mode=2
innodb_doublewrite=1
query_cache_size=0
bind-address=0.0.0.0
# Galera synchronisation configuration
wsrep_sst_method=rsync
I want only to bootstrap the first node and then add new nodes
So I run
sudo service mysql bootstrap
But I get this error
Jul 03 02:38:07 db1 mysqld[14779]: at gcomm/src/pc.cpp:connect():162
Jul 03 02:38:07 db1 mysqld[14779]: 2016-07-03 2:38:07 140418873596160 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():208: Failed to open backend connection: -110 (Connection timed ou
Jul 03 02:38:07 db1 mysqld[14779]: 2016-07-03 2:38:07 140418873596160 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1379: Failed to open channel 'my_wsrep_cluster' at 'gcomm://20.0.1.51': -11
Jul 03 02:38:07 db1 mysqld[14779]: 2016-07-03 2:38:07 140418873596160 [ERROR] WSREP: gcs connect failed: Connection timed out
Jul 03 02:38:07 db1 mysqld[14779]: 2016-07-03 2:38:07 140418873596160 [ERROR] WSREP: wsrep::connect(gcomm://20.0.1.51) failed: 7
Jul 03 02:38:07 db1 mysqld[14779]: 2016-07-03 2:38:07 140418873596160 [ERROR] Aborting
Jul 03 02:38:08 db1 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jul 03 02:38:08 db1 systemd[1]: Failed to start MariaDB database server.
Jul 03 02:38:08 db1 systemd[1]: mariadb.service: Unit entered failed state.
Jul 03 02:38:08 db1 systemd[1]: mariadb.service: Failed with result 'exit-code'.
What am I doing wrong??
Its the systemd thing. On systems that has systemd, one should use galera_new_cluster to bootstrap a new cluster.
https://mariadb.com/kb/en/mariadb/systemd/
I can access the actual wordpress site via WAMP's localhost route, but I cannot log into the admin/dashboard page of the wordpress site.
I think it is a problem with apache.
Can anybody help me?
here are messages from the apache error logs:
[Sun Nov 03 07:11:17.294107 2013] [mpm_winnt:notice] [pid 2700:tid 416] AH00422: Parent: Received shutdown signal -- Shutting down the server.
[Sun Nov 03 07:11:19.296221 2013] [mpm_winnt:notice] [pid 5784:tid 324] AH00364: Child: All worker threads have exited.
[Sun Nov 03 07:11:19.328223 2013] [mpm_winnt:notice] [pid 2700:tid 416] AH00430: Parent: Child process 5784 exited successfully.
[Sun Nov 03 07:11:22.842424 2013] [mpm_winnt:notice] [pid 5408:tid 416] AH00455: Apache/2.4.4 (Win32) PHP/5.4.16 configured -- resuming normal operations
[Sun Nov 03 07:11:22.842424 2013] [mpm_winnt:notice] [pid 5408:tid 416] AH00456: Server built: Feb 23 2013 13:07:34
[Sun Nov 03 07:11:22.842424 2013] [core:notice] [pid 5408:tid 416] AH00094: Command line: 'c:\\wamp\\bin\\apache\\apache2.4.4\\bin\\httpd.exe -d C:/wamp/bin/apache/Apache2.4.4'
[Sun Nov 03 07:11:22.844424 2013] [mpm_winnt:notice] [pid 5408:tid 416] AH00418: Parent: Created child process 4348
[Sun Nov 03 07:11:24.173500 2013] [mpm_winnt:notice] [pid 4348:tid 324] AH00354: Child: Starting 150 worker threads.
More info:
The error is not a 404. Rather wordpress doesnt recognize my username/password.
final edit:
found a solution to my problem:
http://www.velvetblues.com/web-development-blog/how-to-add-an-admin-user-to-a-wordpress-database/