I tried to install a 2nd Mediwiki on my ISPC on PHP-FPM but get an error 1044: The database can be accessed by phpMyAdmin & command line without issues But the ftp account creation didn't open the FTP port for the new site for local and remote access and FTP gives an error: 530 Login authentication failed Any ideas how I can get that fixed? Thank you rfnX
Is this a new installation or is the issue just fot your web18 ? I assume you did try the obvious and update the passwords ( to the same as you set before ) again? Depending on the setup a second update of the password can be needed. yes I read that, but I can't know if you tried as root to see if the database is there or you tried with the actual credentials for the web. Might sounds pendantic but also this has been overlooked and can't hurt to ask, nothing personal. Also important, when trying local, have you tried mysql -hlocalhost or mysql -h127.0.0.1 ? Is this a remote database server? Have you tried setting up SSH/SFTP access to see if that works? While you try to connect, have a tail -f /var/log/auth.log open in a seperate ssh session to see if there are any issues when trying sftp.
The installation is 2 years old, just made a new site to have new wiki for a project Had set it up with new passwords but hat to reconfigure all because it wasn't working as it should, without success all done as root, as it wasnt working after the configuration over ISPC As the FTP upload didt work I hat to do a wget and change of the user credentials and permissions,... think there must sth be crashed in the installation, but the old sites all still work well ... # mysql -hlocalhost ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) ERROR 2002 (HY000): Can't connect to server on '127.0.0.1' (115) nice idea! tought it must be listening as the old sites are all working well but, restarting mariadb produced an error Tried that: journalctl -xeu mariadb.service ░░ ░░ The job identifier is 411202. Jun 05 08:58:23 maran mariadbd[2772335]: 2024-06-05 8:58:23 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 2772335 Jun 05 08:58:23 maran mariadbd[2772335]: 2024-06-05 8:58:23 0 [ERROR] mariadbd: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seco> Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] mariadbd: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria con> Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Number of transaction pools: 1 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Using liburing Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Completed initialization of buffer pool Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Check that you do not already have another mariadbd process using the same InnoDB data or log files. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Starting shutdown... Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] Plugin 'FEEDBACK' is disabled. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Failed to initialize plugins. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Aborting Jun 05 08:58:53 maran systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit mariadb.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jun 05 08:58:53 maran systemd[1]: mariadb.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit mariadb.service has entered the 'failed' state with result 'exit-code'. Jun 05 08:58:53 maran systemd[1]: Failed to start mariadb.service - MariaDB 10.11.6 database server. ░░ Subject: A start job for unit mariadb.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit mariadb.service has finished with a failure. ░░ ░░ The job identifier is 411202 and the job result is failed. lines 1020-1062/1062 (END) ░░ ░░ The job identifier is 411202. Jun 05 08:58:23 maran mariadbd[2772335]: 2024-06-05 8:58:23 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 2772335 Jun 05 08:58:23 maran mariadbd[2772335]: 2024-06-05 8:58:23 0 [ERROR] mariadbd: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] mariadbd: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control' Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Number of transaction pools: 1 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Using liburing Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Completed initialization of buffer pool Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Check that you do not already have another mariadbd process using the same InnoDB data or log files. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Starting shutdown... Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] Plugin 'FEEDBACK' is disabled. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Failed to initialize plugins. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Aborting Jun 05 08:58:53 maran systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit mariadb.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jun 05 08:58:53 maran systemd[1]: mariadb.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit mariadb.service has entered the 'failed' state with result 'exit-code'. Jun 05 08:58:53 maran systemd[1]: Failed to start mariadb.service - MariaDB 10.11.6 database server. ░░ Subject: A start job for unit mariadb.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit mariadb.service has finished with a failure. ░░ ░░ The job identifier is 411202 and the job result is failed. ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1020-1062/1062 (END) ░░ ░░ The job identifier is 411202. Jun 05 08:58:23 maran mariadbd[2772335]: 2024-06-05 8:58:23 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 2772335 Jun 05 08:58:23 maran mariadbd[2772335]: 2024-06-05 8:58:23 0 [ERROR] mariadbd: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] mariadbd: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_contro> Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Number of transaction pools: 1 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Using liburing Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Completed initialization of buffer pool Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Check that you do not already have another mariadbd process using the same InnoDB data or log files. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] InnoDB: Starting shutdown... Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [Note] Plugin 'FEEDBACK' is disabled. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Failed to initialize plugins. Jun 05 08:58:53 maran mariadbd[2772335]: 2024-06-05 8:58:53 0 [ERROR] Aborting Jun 05 08:58:53 maran systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStart= process belonging to unit mariadb.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jun 05 08:58:53 maran systemd[1]: mariadb.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit mariadb.service has entered the 'failed' state with result 'exit-code'. Jun 05 08:58:53 maran systemd[1]: Failed to start mariadb.service - MariaDB 10.11.6 database server. ░░ Subject: A start job for unit mariadb.service has failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit mariadb.service has finished with a failure. ░░ ░░ The job identifier is 411202 and the job result is failed. ~ ~ ~ ~ ~ ~ ~ ~ root@maran:~# ^C root@maran:~# service mariadb start Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details. mess MAN. I'M A NOOB! The database server is down now and doesn't start anymore. Have a snapshot, but's just the worst case solution ... SSH is working gut SFTP does not! get a critical error: Failed to connect to server The user is unknown now, but as the database is no more running it cant be found, if I'm not wrong!?! sure! her the output: Any better ideas than resetting to the snapshot? [/QUOTE]
This was a not-so-good idea, as you messed up your system with that. If ISPConfig is unable to configure it, then there are always good reasons for that, and instead of enforcing it and destroy your setup manually, you should have just investigated why ISPConfig could not apply the config. Regarding your original problem: Maybe you changed the root password of your MySQL or MariaDB server and forgot to change it in the file /usr/local/ispconfig/server/lib/mysql_clientdb.conf ? And regarding the new problem you have now with non-staring MySQL, seems as if you deleted some files of the database setup. What exactly have you done with the database that caused this? And yes, it might be necessary to restore a backup, depending on which parts of the database setup were deleted. So the next step is to try to find out why parts of the mariadb installation are missing and if you can fix that by installing mariadb with --reinstall switch again using apt. In case you use the restore approach instead, do not manually create anything. Instead, simply look in debug mode why the system could not be configured anymore.
please make sure your /var/lib/mysql folder is owned by the user mysql:mysql ( recursively ). or at least Code: sudo chown mysql:mysql /var/lib/mysql/aria_log_control sudo chmod 660 /var/lib/mysql/aria_log_control IF AND ONLY IF the above steps do not work ( check recursively ownership! ) and there is no stale mariadb process running ( check your ps aux ) Code: sudo mv /var/lib/mysql/aria_log_control /root/aria_log_control Also for 10.11 version is a common issue ( for me ) to have the need to update the user with the same password again after adding. This might not have been an issue 2 years ago for your older sites. exactly, repeat after you got your database running again. Make sure there is no zombie process running lsof /var/lib/mysql
well my command was more an example how to connect, of course I'd expect you to try the web18 credentials for the database so your database server is listening on socket mode only, which is usually a good thing, though not if you want all IspConfig features to work. After you veryfied your database port 3306 is not open to public you can modify your bind-address like explained in https://www.howtoforge.com/perfect-server-debian-12-buster-apache-bind-dovecot-ispconfig-3-2/ ( look for nano /etc/mysql/mariadb.conf.d/50-server.cnf , which is the part to allow connection from 127.0.0.1 ) edit: *snip* some dangerous parts removed
It's actually a bad thing as it means his setup is broken, as some parts of the setup do use 127.0.0.1. Doing this results e.g. in non-working FTP, exactly as reported by this user. If you do not want to allow external access to MySQL, then all you do is to close port 3306 in the firewall. But you must be are that database config in ISPConfig will not work then anymore when it comes to settings that configure external access. Maybe you should not suggest things that are not supported and will likely break his setup. I know you have your fun with suggesting setup changes to people that might work with manual changes to the ISPConfig code by an expert, but you should not suggest something like this to normal users as you should know they will break their setups completely. Especially as you even admit that you do not have tested this on an ISPConfig system. In general, only the MariaDB version that ships with a specific version of an OS has been tested and is working, do not use MariaDB from external sources or directly from MariaDB. Also the need of having to save a MySQL password more then once does not happen on systems that are installed according to spec, so if you have encountered such an issue, then its likely caused by your manually crafted non-standard setup and not by ISPConfig, so this won't happen on any regular ISPConfig setups. I'm aware that you are not really familiar with current ISPConfig setups and, therefore, suggest steps that are incompatible with ISPConfig. But then please try to not confuse users and do not suggest changes that will destroy their systems!
Yah, I changed the SQL root pwd because it didn't work no more, don't know what could have caused that and was wondering why but I now know that I need to check mysql_clientdb.conf in the next attempt. I've deleted deleted 100% nothing but I got a 2nd with access, cant imagine that he did but anyway there seems to be no way around to set the snapshot back ... Thanks for your hints and I will get back un this tomorrow as I banged the night through ... Will set the snapshot back and try a new respecting all your hints ...
Thanks, and I think your advice will help me to avoid that in the next attempt when I start back the snapshot. I will inform y'all about how I got that solved as soon I got it ... Thanks a lot <3
OK, got both wikis running well now. After I turned back the snapshot I just had to install the second wiki, I will take care to inform ISPC over mysql_clientdb.conf in case I need to reset the SQL root password Thank you
Argh it doesn't work - sorry! I just assumed it would work because it was so easy before, but after the upload I get a 403 error! Have started a new thread: https://forum.howtoforge.com/threads/error-403-on-new-web.92503/ Hope you can help me BTW: The first MediaWiki is running perfect !
