-
It looks like after the script finished I am missing users in mariadb. How do I fix this? Ubuntu 20.04 LTS Error on webpage login /var/log/mysql/error.log MariaDB [(none)]> SELECT User, Db, Host from mysql.db; MariaDB [(none)]> SELECT User FROM mysql.user; |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 5 replies
-
I'm guessing you got some errors during install. Can you provide the install script log located under the same directory you started the installation script? Thanks |
Beta Was this translation helpful? Give feedback.
-
There is nothing in that log file besides the following entry:
This looks like something went very wrong with the installation. Did anything get installed? You can also jump in Matrix if you wish to have more real time discussion on the issue you are experiencing: https://matrix.to/#/#hermesseg:matrix.org Thanks |
Beta Was this translation helpful? Give feedback.
-
install_log-10-14-2022-1604.log Unfortunately I've run through the installer a few times trying to get things working. That is the earliest I have that has data in it |
Beta Was this translation helpful? Give feedback.
-
I supplied them. I believe the log file is from the 2nd completion of the
install attempt. I no longer have the first install log file
…On Thu, Oct 20, 2022 at 1:47 PM deeztek ***@***.***> wrote:
ok this one has more data in it. So this particular file says that you did
not supply a MySQL root password:
Access denied for user 'root'@'localhost' (using password: NO)
When you start the installation, the script asks you to create passwords
for the MySQL root as well as usernames and passwords for the hermes,
Syslog, opendmar and djigzo databases. Did you supply those credentials you
wish to use? Because it looks like you did not (Note the user is blank in
the lines below):
[10/14/2022-16:07] Creating Hermes SEG database and assigning user to it
ERROR 1007 (HY000) at line 1: Can't create database 'hermes'; database exists
[10/14/2022-16:07] Creating Syslog database and assigning user to it
ERROR 1007 (HY000) at line 1: Can't create database 'Syslog'; database exists
[10/14/2022-16:07] Creating Opendmarc database and assigning user to it
ERROR 1007 (HY000) at line 1: Can't create database 'opendmarc'; database exists
[10/14/2022-16:07] Creating Ciphermail database and assigning user to it
ERROR 1007 (HY000) at line 1: Can't create database 'djigzo'; database exists
If so, did the passwords you chose contain any special characters? If so,
what special characters were they?
Thanks
—
Reply to this email directly, view it on GitHub
<#35 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3VW24J4RMICTZN6KVZH2JLWEGARNANCNFSM6AAAAAARIESA54>
.
You are receiving this because you authored the thread.Message ID:
<deeztek/Hermes-Secure-Email-Gateway/repo-discussions/35/comments/3927101@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
Install ended in some errors. install_log-10-20-2022-1443.log Errors on the webpage after login: Lucee 5.2.9.31 Error (database)Message | Access denied for user ''@'localhost' (using password: YES) |
Beta Was this translation helpful? Give feedback.
-
log file is unedited. During install I would be prompted for something like
this
Enter MySQL(MariaDB) Hermes SEG user username you wish to use (Example:
hermes):
I would hit enter. Does a username need entered or does it default to the
suggested?
…On Thu, Oct 20, 2022 at 4:18 PM deeztek ***@***.***> wrote:
Looking at the new install_log-10-20-2022-1443.log file you sent, I'm
still noticing the following errors:
[10/20/2022-14:44] Starting MySQL(MariaDB) Database
[10/20/2022-14:44] Creating Hermes SEG database and assigning user to it
[10/20/2022-14:44] Creating Syslog database and assigning user to it
[10/20/2022-14:44] Creating Opendmarc database and assigning user to it
[10/20/2022-14:44] Creating Ciphermail database and assigning user to it
[10/20/2022-14:44] Creating Hermes SEG Database Schema
[10/20/2022-14:45] Creating Opendmarc database schema.
For instance the line:
Creating Hermes SEG database and assigning user to it
is supposed to say:
Creating Hermes SEG database and assigning user [someuser] to it
where *[someuser]* is the username you entered when the script prompted
you.
So, the question is, are you removing the actual usernames from the
install_log before you send it in order to sanitize it or are you not
entering the username when prompted?
This is what it's supposed to look like where *hermes, rsyslog, opendmarc*
and *ciphermail* are the usernames I entered when the script prompted me:
[08/01/2022-12:33] Creating Hermes SEG database and assigning user hermes to it
[08/01/2022-12:33] Creating Syslog database and assigning user rsyslog to it
[08/01/2022-12:33] Creating Opendmarc database and assigning user opendmarc to it
[08/01/2022-12:33] Creating Ciphermail database and assigning user ciphermail to it
[08/01/2022-12:33] Creating Hermes SEG Database Schema
[08/01/2022-12:33] Creating Opendmarc database schema.
—
Reply to this email directly, view it on GitHub
<#35 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3VW24PGRERHMJCGJ5A3ER3WEGSIBANCNFSM6AAAAAARIESA54>
.
You are receiving this because you authored the thread.Message ID:
<deeztek/Hermes-Secure-Email-Gateway/repo-discussions/35/comments/3928160@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
Added new enhancement #36 for next release. |
Beta Was this translation helpful? Give feedback.
-
Actually typing usernames did the trick. Thanks for pointing that out
…On Thu, Oct 20, 2022 at 5:24 PM deeztek ***@***.***> wrote:
Added new enhancement #36
<#36> for
next release.
—
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3VW24J3OZQGZTQP5JJF2WLWEG2APANCNFSM6AAAAAARIESA54>
.
You are receiving this because you authored the thread.Message ID:
<deeztek/Hermes-Secure-Email-Gateway/repo-discussions/35/comments/3928541@
github.com>
|
Beta Was this translation helpful? Give feedback.
Added new enhancement #36 for next release.