Search results

it's basically: #include virtual="cgi-bin/blah.cgi" Where blah.cgi is a perl script. Works fine when .shtml's are proxied to Apache (which we are trying to turn off). We don't see anything in the error log.

we're setting this issue and we're past the .14 release.

http://www.litespeedtech.com/support/forum/showthread.php?t=4059 last post in the thread.

Your mileage may vary, but we have several VPS clients running LSWS. There sites (bigger blogs etc.) run perfectly on LSWS where Apache would crash eating all the VPS's memory.

So basically we can just rm -rf all the folders under the swap dir and LSWS will just recreate the structure? Does LSWS need to be down when we do that?

I'll second this one.

I think this is pretty 'typical' LSWS treatment. 1st they put the new package up (but not links) for early adopters to test. After that they update the download links. Finally, after the upload link have been out a bit the push it out via the auto-upload.

Yup, just pick one and then strace -p #### (process-id). The output will then go wizzing by on your console/ssh session.

If the process are still running you can also use strace against the process. That will give you the system calls being issued (not the PHP code) but it should give you an idea of what it's doing.

Our 'updateagent' seems be hanging up trying to connect to the LiteSpeed server. The forum also appeared to be down for a bit this afternoon. Are there issues?

And I'll throw in a 'me too'. It's very confusing where a new release comes out with the same build number. If you re-release, change the build number.

That's a problem with your php.ini. LiteSpeed is prob. reading a different one than your cPanel one. Check the 'memory_limit' value in the old/new php.ini

/usr/local/cpanel/bin/safeapacherestart It's not a script, it's a compiled program.

The piped logging is not turned on by default so unless you enable it you don't really have to worry about it.

@nolnet, And if you are running cPanel 11.25, what version of LSWS do you have running and do you still have Apache running?

We see them also. Some of them are from cPanel restarting tings after you add a domain. There also was an issue with 11.25 where it was not properly rotating logs (the main apache error or access log) and it was restarting things every 15 minutes or so.

Do you happen to be running cPanel?

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.

@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...

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: