New logging method for cPanel 11.25

ffeingol

ffeingol

Well-Known Member
#1
#1
Hello Guys,

Over in the cPanel forum they just posted this thread: http://forums.cpanel.net/f5/cpanel-11-25-log-processing-145417.html This item in section 2 has me particularly nervous:

To account for the Apache behavior, and to retain the data integrity of the domain and bytes logs, a new method for Apache to log information is being introduced. Rather than logging directly to files, Apache will log directly to a pipe. Both virtual host data, as well as the service level access data, will be written to the pipe. This feature is only available to servers using Apache 2.0 or 2.2.
Click to expand...
Is LSWS (both version 3.x and 4.x) going to be able to deal with the pipe based log files? I don't have a real 'warm fuzzy' about this one :D
 
T

Tony

Well-Known Member
#2
#2
lsws does support piped logging so I assume it should work fine. Going to test it though once it is actually part of 11.25.
 
M

mistwang

LiteSpeed Staff
#4
#4
Other hosting control panels like Plesk uses piped logger, it works well with LiteSpeed, so I think it will work well.
We have update our cPanel to Edge, but it does not use piped logger. If you know how to enable it, please let us know.
 
T

Tony

Well-Known Member
#5
#5
mistwang said:
Other hosting control panels like Plesk uses piped logger, it works well with LiteSpeed, so I think it will work well.
We have update our cPanel to Edge, but it does not use piped logger. If you know how to enable it, please let us know.
Click to expand...
They say it's in builds later than 42552 according to http://forums.cpanel.net/f5/cpanel-11-25-log-processing-145417.html and when you run the update it rebuilds the httpd.conf. Might want to try running /scripts/rebuildhttpdconf and see if it then adds the piped logging. My only other guess is it won't turn on unless it's apache 2 or 2.2 is what cPanel is set to having on.
 
M

mistwang

LiteSpeed Staff
#6
#6
I got 42994 with the EDGE, tried rebuild httpd.conf, apache 2.2 is used, no piped logger in httpd.conf. Go back to RELEASE see what happen.
 
ffeingol

ffeingol

Well-Known Member
#7
#7
We just switched our testing VPS to edge and it's running the file based logging also. We're on Apache 2.2.14. I posted on the cPanel forum for 'clarification' :D
 
ffeingol

ffeingol

Well-Known Member
#8
#8
OK, they just posted in the cPanel forum (I missed it before). You have to open a support ticket to get the new piped logging. They only want 'real word, production enviroments' (Yea, we're going t run edge in production).

Having said that this sounds even worse:

When the piped logging method is enabled Apache will pipe logs to a common target process, a program started by Apache that is listening on the pipe; the receiving process will then automatically split the logs into their expected per-domain version.
Assuming I understand this correctly, Apache will be writing all logs to a pipe. This new daemon/process will then read the pipe and split the logs into the individual sites log files. Since the program to read the pipe is 'started by Apache' and we're not running Apache this does not sound good.
Click to expand...
Click to expand...
 
ffeingol

ffeingol

Well-Known Member
#10
#10
@mistwang,

Ok, I'm gland that I understand it correctly and it is support. My real question (and I don't know that anyone has the answer yet) is how does the 2nd process (the one that reads the pipe and splits the files) get started. From the cPanel post it's started by Apache, so the question is if we're not running Apache (because we've go to 4.x) what will start up the 2nd process?
 
ffeingol

ffeingol

Well-Known Member
#12
#12
Awsome! That is exactly what I wanted to hear. We've requested that our test server have the new logging enabled. I'm assuming you have already done the same. Since it's not a 'production' server like they requested we're just in the queue to be enabled.
 
You must log in or register to reply here.
Top