plz guys i need some help
all my site is down about week ago and i can’t find the problem came from
Did you have databases created already?
Looks like you did.
If you look in the /var/lib/mysql/
folder, can you see a ib_logfile0
file?
This message here is kind of indicative that something has happened to your log file:
201231 12:59:34 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
This might have been good advice but maybe it was too long after trying to start the db to be of use?
Try the restart followed by journalctl -xe
and see if there is Mariadb related info.
of course
and all this problem when webmin give me the update
> # journalctl -xe
> Oct 13 20:14:09 ???.contaboserver.net named[1492]: network unreachable resolving 'ns2.opendns.pw/A/IN': 2610:a1:1025::200#53
> Oct 13 20:14:09 ???.contaboserver.net named[1492]: network unreachable resolving 'ns1.opendns.pw/A/IN': 2610:a1:1025::200#53
> Oct 13 20:14:09 ???.contaboserver.net named[1492]: network unreachable resolving 'ns2.opendns.pw/AAAA/IN': 2610:a1:1025::200#53
> Oct 13 20:14:09 ???.contaboserver.net named[1492]: network unreachable resolving 'ns1.opendns.pw/AAAA/IN': 2610:a1:1025::200#53
> Oct 13 20:14:10 ???.contaboserver.net named[1492]: network unreachable resolving '51.76.80.in-addr.arpa/DS/IN': 2001:500:14:6100:ad::1#53
> Oct 13 20:14:10 ???.contaboserver.net postfix/smtpd[18848]: connect from unknown[80.76.51.74]
> Oct 13 20:14:10 ???.contaboserver.net saslauthd[564]: pam_unix(smtp:auth): check pass; user unknown
> Oct 13 20:14:10 ???.contaboserver.net saslauthd[564]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
> Oct 13 20:14:12 ???.contaboserver.net saslauthd[564]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module
> Oct 13 20:14:12 ???.contaboserver.net saslauthd[564]: do_auth : auth failure: [user=postoffice] [service=smtp] [realm=] [mech=pam] [reason=PAM au
> Oct 13 20:14:12 ???.contaboserver.net postfix/smtpd[18848]: warning: unknown[80.76.51.74]: SASL LOGIN authentication failed: authentication failure
> Oct 13 20:14:12 ???.contaboserver.net postfix/smtpd[18848]: disconnect from unknown[80.76.51.74]
> Oct 13 20:15:01 ???.contaboserver.net systemd[1]: Created slice User Slice of root.
> -- Subject: Unit user-0.slice has finished start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit user-0.slice has finished starting up.
> --
> -- The start-up result is done.
> Oct 13 20:15:01 ???.contaboserver.net systemd[1]: Started Session 1753 of user root.
> -- Subject: Unit session-1753.scope has finished start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit session-1753.scope has finished starting up.
> --
> -- The start-up result is done.
> Oct 13 20:15:01 ???.contaboserver.net CROND[18950]: (root) CMD (/etc/webmin/status/monitor.pl)
> Oct 13 20:15:01 ???.contaboserver.net systemd[1]: Removed slice User Slice of root.
> -- Subject: Unit user-0.slice has finished shutting down
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit user-0.slice has finished shutting down.
> Oct 13 20:15:12 ???.contaboserver.net sshd[19049]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.101.88.240
> Oct 13 20:15:12 ???.contaboserver.net sshd[19049]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
> Oct 13 20:15:14 ???.contaboserver.net sshd[19049]: Failed password for root from 180.101.88.240 port 53564 ssh2
> Oct 13 20:15:14 ???.contaboserver.net sshd[19049]: pam_succeed_if(sshd:auth): requirement "uid >= 1000" not met by user "root"
You can wrap logs in a code block (using triple backticks, like this: ``` at top and bottom of the pasted text) to make them show up in a fixed width typeface for easier reading.
I’ve edited your comment.
Please post the following output:
systemctl status mariadb
Then, if mariadb is in a failed/non-running state do the following in one terminal:
journalctl -fu mariadb
While running this in another terminal:
systemctl restart mariadb
We need to see relevant logs for why it’s failing. Most of the stuff you’re posting isn’t relevant to mariadb or why it isn’t starting (though the actual Mariadb logs you posted seem to indicate it is starting, so I’m confused why you think it isn’t starting).
i try all of theme and nothing happen
systemctl status mariadb
systemctl status mariadb
● mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2023-10-13 21:18:40 CEST; 2min 11s ago
Process: 28321 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
Process: 28319 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
Process: 28284 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
Main PID: 28319 (code=exited, status=0/SUCCESS)
Oct 13 21:18:39 xxx.contaboserver.net systemd[1]: Starting MariaDB database server...
Oct 13 21:18:39 xxx.contaboserver.net mariadb-prepare-db-dir[28284]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Oct 13 21:18:39 xxx.contaboserver.net mariadb-prepare-db-dir[28284]: If this is not the case, make sure the /var/lib/mysql is empty before runni...b-dir.
Oct 13 21:18:39 xxx.contaboserver.net mysqld_safe[28319]: 231013 21:18:39 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Oct 13 21:18:39 xxx.contaboserver.net mysqld_safe[28319]: 231013 21:18:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Oct 13 21:18:40 xxx.contaboserver.net systemd[1]: mariadb.service: control process exited, code=exited status=1
Oct 13 21:18:40 xxx.contaboserver.net systemd[1]: Failed to start MariaDB database server.
Oct 13 21:18:40 xxx.contaboserver.net systemd[1]: Unit mariadb.service entered failed state.
Oct 13 21:18:40 xxx.contaboserver.net systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@xxx~]#
journalctl -fu mariadb
journalctl -fu mariadb
-- Logs begin at Wed 2023-10-11 06:08:48 CEST. --
Oct 13 21:18:27 xxx.contaboserver.net systemd[1]: mariadb.service failed.
Oct 13 21:18:39 xxx.contaboserver.net systemd[1]: Starting MariaDB database server...
Oct 13 21:18:39 xxx.contaboserver.net mariadb-prepare-db-dir[28284]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Oct 13 21:18:39 xxx.contaboserver.net mariadb-prepare-db-dir[28284]: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
Oct 13 21:18:39 xxx.contaboserver.net mysqld_safe[28319]: 231013 21:18:39 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Oct 13 21:18:39 xxx.contaboserver.net mysqld_safe[28319]: 231013 21:18:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Oct 13 21:18:40 xxx.contaboserver.net systemd[1]: mariadb.service: control process exited, code=exited status=1
Oct 13 21:18:40 xxx.contaboserver.net systemd[1]: Failed to start MariaDB database server.
Oct 13 21:18:40 xxx.contaboserver.net systemd[1]: Unit mariadb.service entered failed state.
Oct 13 21:18:40 xxx.contaboserver.net systemd[1]: mariadb.service failed.
systemctl restart mariadb
systemctl restart mariadb
Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
Stop saying nothing happened. Information happened. There is no magic command that fixes all problems. We’re trying to gather data so we understand the problem, and that’s what happened (and that’s what was supposed to happen, it was not supposed to fix it).
For some reason it looks like mariadb is trying to perform initialization steps; like it’s a fresh install. Did you uninstall and reinstall mariadb? (Don’t do that. I’m not telling you to do that, I’m asking if you did, which is a bad idea, but usually recoverable.)
I’m going to drop this here, as a thing you can start reading through while I try to figure out what I think the best next step is: What to Do if MariaDB Doesn't Start - MariaDB Knowledge Base
Also, we probably want to see /var/log/mariadb/mariadb.log
entries that appeared immediately after a restart attempt.
uninstall and reinstall mariadb
no
@joe This has been all over the place but I think this is what you are looking for.
how u can see it did i send it to you or what ?
want to see /var/log/mariadb/mariadb.log
We do not provide Mariadb. Webmin/Virtualmin tells you about available updates from the system package manager. Normal system updates should not break anything (and if they do, it’s a bug in the vendors package). I just want to be clear that Webmin did not break Mariadb (because Webmin does not have anything to do with packages from your OS vendor, we’re just running apt-get
like you normally would on the command line when updating a system), and updating should not be a thing you’re afraid of in the general case.
I just want to see the relevant lines. I do not want the whole file.
Copy and paste the lines that appear immediately when you restart mariadb
.
i dont 'even know how to uninstall and reinstall mariadb
OK, good. Don’t do it.
this some of them
201231 12:59:34 [Note] /usr/libexec/mysqld (mysqld 5.5.68-MariaDB) starting as process 17740 …
201231 12:59:34 InnoDB: The InnoDB memory heap is disabled
201231 12:59:35 Percona XtraDB (http://www.percona.com) 5.5.61-MariaDB-38.13 started; log sequence number 0
201231 12:59:35 [Note] Plugin ‘FEEDBACK’ is disabled.
201231 12:59:35 [Note] Server socket created on IP: ‘0.0.0.0’.
201231 12:59:35 [Note] Event Scheduler: Loaded 0 events
201231 12:59:35 [Note] /usr/libexec/mysqld: ready for connections.
Version: ‘5.5.68-MariaDB’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 MariaDB Server
201231 13:03:35 [Note] /usr/libexec/mysqld: Normal shutdown