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: 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
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.
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.
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.
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.
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'
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:
@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?
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.
The piped logging is not turned on by default so unless you enable it you don't really have to worry about it.