• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Log entries displayed twice

Maris

Basic Pleskian
Hey there, just noticed for one subdomain - every log entry coming from "Apache SSL/TLS access" or "nginx SSL/TLS access" in Plesk is displayed twice. It goes like this

(entry A) Apache SSL/TLS access
(entry A) Apache SSL/TLS access
(entry B) nginx SSL/TLS access
(entry B) nginx SSL/TLS access

checked actual log files, all good - there's only one entry as it should be, but PLESK somehow displays everything two times.

At the same time - in the same log display view entries from "Apache access" are fine. Displaying for other domains - also fine. So only this domain is affected.

OS ‪CentOS Linux 7.4.1708 (Core)‬
Product Plesk Onyx
Version 17.8.11 Update #5, last updated on April 21, 2018 08:59 AM
 
Hello @Maris

I cannot reproduce the issue at the same OS and Plesk version. Please provide more details. Is it occurred during real-time updates mode? Does the issue persist after the page reloads?
 
Hey there, several days ago Plesk asked for big updated, i proceed.. then Advisor extension came up saying "hey, you are not using http 2 do you want to?", sure, installed it and then this started to happen... found how to manually disable http 2 and roll back to http 1, but issue still persisted. So today i restarted the server, and issue seems to be gone. Go figure
 
@Igor Losev Another observation - it happens only for the part of log displayed without clicking "Load previous entries". Additional entries loaded after clicking "load previous entries" - those are no more duplicating.
 
I guess some lines are in the wrong date/time order. Sometimes it happens but such situation is not expected by Plesk log browser - so looks like a bug.
@Maris , could you open your log file as is (e.g. via file manager viewer) and match line order with their date/time fields?
 
@Igor Losev Dates are correct, both in raw log file and in Plesk's output.

Raw Apache SSL/TLS access content:
xxx.xx.xxx.xx - - [25/Apr/2018:10:50:57 +0300] "GET /Asomething HTTP/1.0" 200 1918 "Google" "Mozilla/5.0"
xxx.xx.xxx.xx - - [25/Apr/2018:10:50:58 +0300] "GET /Bsomething HTTP/1.0" 200 443 "Asomething" "Mozilla/5.0"
xxx.xx.xxx.xx - - [25/Apr/2018:10:50:58 +0300] "GET /Csomething HTTP/1.0" 200 416 "Asomething" "Mozilla/5.0"

Plesk's output
2018-04-25 10:50:57 Access xxx.xx.xxx.xx 200 GET /Asomething HTTP/1.0 1.87 K Apache SSL/TLS access
2018-04-25 10:50:57 Access xxx.xx.xxx.xx 200 GET /Asomething HTTP/1.0 1.87 K Apache SSL/TLS access
2018-04-25 10:50:58 Access xxx.xx.xxx.xx 200 GET /Bsomething HTTP/1.0 443 Apache SSL/TLS access
2018-04-25 10:50:58 Access xxx.xx.xxx.xx 200 GET /Bsomething HTTP/1.0 443 Apache SSL/TLS access
2018-04-25 10:50:58 Access xxx.xx.xxx.xx 200 GET /Csomething HTTP/1.0 416 Apache SSL/TLS access
2018-04-25 10:50:58 Access xxx.xx.xxx.xx 200 GET /Csomething HTTP/1.0 416 Apache SSL/TLS access
 
Back
Top