Webalizer fails miserably with multiple server backends

To review Synology NAS Server Web services usage statistics
Forum rules
1) This is a user forum for Synology users to share experience/help out each other: if you need direct assistance from the Synology technical support team, please use the following form:

https://account.synology.com/support/su ... p?lang=enu

2) To avoid putting users' DiskStation at risk, please don't paste links to any patches provided by our Support team as we will systematically remove them. Our Support team will provide the correct patch for your DiskStation model.
Posts: 284
Joined: Fri May 02, 2014 8:36 pm

Webalizer fails miserably with multiple server backends

Unread post by pezball » Fri Apr 21, 2017 12:57 pm

With DSM 6.1 comes the ability to run several web server backends, and Webalizer gets totally confused. I use Apache 2.4 for my web site, and there is no sign of any access log from that server, where Webalizer wants it to be. The current version of the Webalizer package, will ONLY report access to ... guess what? Yes, the Webalizer pages! So I can at least see who has been visiting the Webalizer stats, wonderful. :roll:

With multiple backends it's vital that logging is enabled for ALL backends, and that logs are stored where Webalizer expects to find them, and that Webalizer reads ALL the separate logs, combined as one.
Nobody wants separate stats for Nginx, Apache 2.2, and Apache 2.4, so either Webalizer package should be cancelled, and nobody use it anymore, or make sure it works for all possible combinations of server backends, without config file editing.

Manual editing of config files is always possible, but a graphical interface which allows easy changes for the most useful options, would be most welcome.
DS214, 2 x WD30EFRX, Raid 1

Post Reply

Return to “Webalizer”