Bug: awstats not accessible: proxy error

**Starlight** · Oct 26th 2016

Version: i-MSCP >= 1.3.5
Tool: Awstats

Problem
running http(s)://example.com/stats throws a Proxy error 502:

Quote

Proxy Error
The proxy server received an invalidresponse from an upstream server.
The proxy server could not handle the request GET /stats/.
Reason: Error reading from remote server

error.log gives following information:

Quote

[Wed Oct 26 23:48:04.309078 2016] [proxy_http:error] [pid 9876:tid 139666770597632] (20014)Internal error: [client <IP>:45748] AH01102: error reading status line from remote server 127.0.0.1:8889
[Wed Oct 26 23:48:04.309116 2016] [proxy:error] [pid 9876:tid 139666770597632] [client <IP>:45748] AH00898: Error reading from remote server returned by /stats/

Workaround
None.

Fix

To investigate

**Nuxwin** · Oct 27th 2016

Distro? Codename?

**Nuxwin** · Oct 28th 2016

No answer...

Well, I cannot reproduce the problem

Environment

i-MSCP 1.3.x
Debian GNU/Linux 8.6 (jessie)

Access through http

stats_http.png

Access through https

stats_https.png

However such problem can be caused for many reasons. I'll commit a change to try to mitigate this issue.

**Nuxwin** · Oct 28th 2016

A fix has been added in the 1.3.x branch. See https://github.com/i-MSCP/imsc…dc8fde4dafd3edd4989177728
This fix will be part of next release.

Thank you for your report.

~~Thread closed.~~

**Starlight** · Oct 29th 2016

Sorry for the lat reply. My environment is:

i-MSCP 1.3.7
Debian GNU/Linux 8.6 (jessie)
Error on access via http and https
SQL-Server on another host

I tried your fix and I did not changed my problem. I will investigate a bit further and let you know.

**Nuxwin** · Oct 31st 2016

@Starlight

You use an external SQL server. I need to check if that could be the problem (mod_dbd apache module that cannot connect to your SQL server).

**Starlight** · Oct 31st 2016

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

**Nuxwin** · Nov 2nd 2016

@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

DBDMin 2
DBDKeep 5
DBDMax 10
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.

**Starlight** · Nov 2nd 2016

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

DBDMin 2

DBDKeep 5

DBDMax 10

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.

**Nuxwin** · Nov 3rd 2016

@Starlight

The problem of this setting set to a non-zero value is that if the MySQL server is not running, Apache will not start...
Furthermore, my thinking is that using MySQL as data source for credential is an error in that context (Basic Auth). I prefer back to the file authentication provider.

Anyway, thank you for your tests.

Bug: awstats not accessible: proxy error

Share

Daily visitors