5 answers
- 10-1
If you installed using the Opmantek installer, that file should exist.
It is not in the logs directory, it should be in the /usr/local/omk directory.
Add your comment... - 10-1
uma@ubuntu:/usr/local/omk$ cd log uma@ubuntu:/usr/local/omk/log$ ls auth.log omkd_out.log opDaemon.log open-audit.log
install.log file doesnt exist
Add your comment... - 10-1
/usr/local/omk/install.log does not exist. Please see my other posts too.
Add your comment... - 10-1
The great Mark Unwin , creator of OA and opmantek has replied!That file does not exist. But I was surprised that the script broke the existing mysql . I do have a snapshot so no big deal, I will loose 6 hours of work. Still just saying.
uma@ubuntu:/usr/local/omk$ cd log uma@ubuntu:/usr/local/omk/log$ ls auth.log omkd_out.log opDaemon.log open-audit.log
Add your comment... - 10-1
Have you checked the install.log in /usr/local/omk/install.log ?
This should show any packages that were installed.
There may be a conflict.
- Deepak Deshpande
MAy be somebody will want to see why mysql was broken. I can let you know which LAMP application were installed prior to running OA script. I can run the script again if somebody wants to debug the problem
Add your comment...
Using Ubuntu 20.04 server. I had already set up mysql server and php applications like phpmyadmin and Moodle etc. I tried installing Open audit by running OAE-Linux-x86_64-release_4.0.2-2.run. While running it mysql and mariadb cannot be connected. How do I recover mysql?
sudo service mysql restart [sudo] password for uma: Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. uma@ubuntu:/var/www/html$ systemctl status mariadb.service ● mariadb.service - MariaDB 10.3.25 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor prese> Active: failed (Result: exit-code) since Sun 2021-02-21 13:56:52 UTC; 20s > Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 3132 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var> Process: 3140 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_ST> Process: 3146 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && > Process: 3193 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $> Main PID: 3193 (code=exited, status=1/FAILURE) Feb 21 13:56:51 ubuntu systemd[1]: Starting MariaDB 10.3.25 database server... Feb 21 13:56:51 ubuntu mysqld[3193]: 2021-02-21 13:56:51 0 [Note] /usr/sbin/mys> Feb 21 13:56:51 ubuntu mysqld[3193]: 2021-02-21 13:56:51 0 [Warning] Could not > Feb 21 13:56:52 ubuntu systemd[1]: mariadb.service: Main process exited, code=e> Feb 21 13:56:52 ubuntu systemd[1]: mariadb.service: Failed with result 'exit-co> Feb 21 13:56:52 ubuntu systemd[1]: Failed to start MariaDB 10.3.25 database ser> mysql -u root -p Enter password: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) sudo apt purge mysql-common Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: default-mysql-client : Depends: mysql-client-8.0 but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.