New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

install problem with version 4.1.5 #17

Closed
arch7 opened this Issue Oct 15, 2016 · 5 comments

Comments

Projects
None yet
6 participants
@arch7

arch7 commented Oct 15, 2016

Hi, there is still a problem during the install phase with the new release.
in the install.php file there are still calls to mysql_* API
If I change those 2 calls with the new mysqli_* the install phase locks at the DB discovery (after logging in) with the message
ERROR: Cannot use the database 'loganalyzer'! If the database does not exists, create it or check user access permissions! Mysql Error - Description:

The database is present and the user has all the needed permissions: I can even login with that user in the mysql cli.

I can add that commenting out the lines
if(!$db_selected) RevertOneStep( $content['INSTALL_STEP']-1, GetAndReplaceLangStr( $content['LN_INSTALL_ERRORACCESSDENIED'], $_SESSION['UserDBName']) . "<br>" . DB_ReturnSimpleErrorMsg());
it is possible to conclude the installation.

@alorbach alorbach closed this in 5ae2ddd Oct 20, 2016

@st0rmi

This comment has been minimized.

Show comment
Hide comment
@st0rmi

st0rmi Jan 9, 2017

It might be a good idea to create a minor release for this fix. When trying to install loganalyzer using the latest release tag, I ran into the same problem.

st0rmi commented Jan 9, 2017

It might be a good idea to create a minor release for this fix. When trying to install loganalyzer using the latest release tag, I ran into the same problem.

@vinceroi

This comment has been minimized.

Show comment
Hide comment
@vinceroi

vinceroi Oct 23, 2017

I ran into the same problem with the latest release 4.1.5 on Debian 9 / MariaDB10.1.26 / Apache/2.4.25 (Debian) / PHP 7.0.19-1
Why this reported issue has been closed?

vinceroi commented Oct 23, 2017

I ran into the same problem with the latest release 4.1.5 on Debian 9 / MariaDB10.1.26 / Apache/2.4.25 (Debian) / PHP 7.0.19-1
Why this reported issue has been closed?

@FabioPedretti

This comment has been minimized.

Show comment
Hide comment
@FabioPedretti

FabioPedretti Nov 3, 2017

This was likely closed because it was fixed with 29174ec and 5ae2ddd, however as it was suggested a 4.1.6 release with the fixes would be welcome!

FabioPedretti commented Nov 3, 2017

This was likely closed because it was fixed with 29174ec and 5ae2ddd, however as it was suggested a 4.1.6 release with the fixes would be welcome!

@rgerhards

This comment has been minimized.

Show comment
Hide comment
@rgerhards

rgerhards Nov 3, 2017

Member

@alorbach new release sounds like a good idea -- what do you think?

Member

rgerhards commented Nov 3, 2017

@alorbach new release sounds like a good idea -- what do you think?

alorbach added a commit that referenced this issue Nov 6, 2017

@alorbach

This comment has been minimized.

Show comment
Hide comment
@alorbach

alorbach Nov 6, 2017

Member

Yes, indeed. I have finalized release 4.1.6.

Member

alorbach commented Nov 6, 2017

Yes, indeed. I have finalized release 4.1.6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment