Posts by Starlight

Quote from Nuxwin

It is ok now? We can close that thread?

sure, can be closed

I figured out, that there was a misspelling inside my 10_php_confoptions_override.pl listener. fixed it.
Sorry for bugging.

P.S.: System information are added in the first post.

Environment: Debian Jessie, I-MSCP 1.3.15, PHP-FPM, PHP 5.6.29 (Debian), opcache.enabled = 1, apc.enabled = 1

Since upgrading to 1.3.15, the login to any Software written in PHP is not possible any more.

Entering correct credentials e.g. to to joomla! or owncoud redirect back to the login site without error message. Nothing to see in the Log files.

Server sessions or OPcache might create the problem.

Update: OwnCloud shows:

Update II: Not sure, if it is related with the update, but it coincidentally occurred after it.

When installing (or updating to 1.3.15) with (here mariadb) remote database, i-mscp tries to figure out the data base type and version. Unfortunately, SQLD_TYPE seems to be not set. Therefore, line 112 of engine/PerlLib/Servers/sqld/remote_server.pm fails.

Just a minor enhancement: I would expect the Let's Encrypt Link on Admin level (Panel / Services) in the menu system tools not under settings. Would appreciate a move.

The proposed change will be a benefit for all and I actually handle it exactly like this, so I can provide SSL access for each user through one SSL file.

However, such a change should not be in a bug fix release like 1.3.9 but in 1.4.x, because it changes the behavior of the system.

Dear @Nuxwin,

the i-MSCP team and especially you are doing a tremendous job to fix and enhance this control panel. Thank you for this.

However, there is one thing, I'd like to discuss is your release management. I do understand, you have a Major, Minor and Bugfix version, displayed by the version number (e. g. 1.3.7). What you do is introducing changes in the Bugfix versions (see Planned changes regarding DNS managements for 1.3.9) that should actually belong to a minor release. I know, that maintaining code for several versions and back porting fixes to older versions can be painful; nevertheless, I would like to see only bug fixes in bug fix releases.

The reason is, that new features need to be tested before rolled out to the customers, but security and bug fixes should be available immediately they are provided.

Would it be possible to maintain at least two to three minor versions with bug fixes and add features in never minor or major versions?

Quote from Nuxwin

@Starlight

Can you give a try by setting manually the mod_dbd params as follow in the 01_awstats.conf file, and restarting apache?:

Code

1. DBDMin 2
2. DBDKeep 5
3. DBDMax 10
4. DBDExptime 300

Also please, do you use an IP or hostname for access to your remote SQL server?

Anyway, I think that I'll drop dbd and back to File auth provider.

Display More

Dear @Nuxwin your proposed settings work

The connection string contains the hostname of the DB-Server (what resolves perfectly, because it is added to the server's host-file).

I played a bit around with the settings and it looks like, that DBDMin 0 not a valid option is (DBDmin 1 works).

Thank you for your debugging.

That's right. The DBDParams contain host, port, user, pass, dbname. Everything, looks sane.

That works great! Thank you @Nuxwin.

I used nsX so for me no problem.