Search results

I asked a few days before. Just change 3.2 to 3.2.1 in the download link. Frank

sorry about that then. My misunderstanding. Frank

Are you guys talking about the same thing? bbennett sounds like he wants to limit the total server to 10 mbps. I though the settings in LSWS are per IP not in total? Frank

Our results bounce around way too much to be meaningful with those parms: LSWS: Requests per second: 316.58 [#/sec] (mean) Requests per second: 251.63 [#/sec] (mean) Requests per second: 215.95 [#/sec] (mean) Apache: Requests per second: 674.75 [#/sec] (mean) Requests...

Its more bad client code/sql calls that mysql tuning. It's hard to get clients to change their code, but they are usually happy if we get them better sql that speeds up their sites. If I understand this coorect -c 20 -n 100 is 20 clients doing 100 calls (so 5 calls each)? I don't think...

I can certainly do that. It seems to mostly be a php/mysql issue and our backups may be playing a wee part of the issue also. Any suggestions for ab parms? I'd like a good test, but I don't want to totally knock the server over either (it's a prod box). TIA, Frank

Great, Please let me know if I can assist in any way. Frank

OK, I've attached a sample of the phpLsapi connection graph that just makes not sense to me: - How can anything in the "now" column not be a whole number? Per the wiki it's a snapshot with the snmp query runs so it should be whole number? - Something in the In Use Conn just seems...

OK, I think I understand this setting, but we're getting notice messages in the error log. Here is the notice: 2007-08-08 08:02:17.537 [NOTICE] [config:server:epsr:phpLsapi]'Process Limit' probably is too low, adjust the limit to: 340. If I understand this correctly there is a soft/hard...

Just an update on this one. I went in and deleted all the LSAPI graphs from this host (graphs and associated RRD's). On the device screen (in cacti) I clicked on "verbose query" under "Associated Data Queries". That came back with 4 items, 1 row. I'm once again able to graph LSAPI's but only...

I will do some more testing. I'm quite sure this "did" work but I'll double check that a upcp etc. did not wack things. The initial host.domain.tld~user kind of works (images don't show) but then any relative links don't work. The "~user" part gets dropped out. Frank

Hello Guys, Sorry to be a pain, but just trying to get all the pieces working. Last night I upgraded our PHP version and got LSWS/SNMP/Cacti working. Everything was going great. Then suddenly at 2:00 am the LSAPI: phpLsapi: Conn graph just stopped. In looking at the Cacti error log I see...

Hello, We have a couple of accounts that don't have DNS setup so they just use host.xxx.yyy/~account. It was working fine yesterday. Today we just added a new account (via WHM) to the server and it suddenly stopped working. I've diff'ed the backup httpd.conf and the current httpd.conf...

Sorry, I forgot to mention, eAccelerator is working fine. From the eAcceletaor control page: Caching enabled: yes Optimizer enabled: yes Memory usage: 99.99% (32.00MB/ 32.00MB) Free memory: 0.00MB Cached scripts: 410 Removed scripts: 0 Cached keys: 0

Done. I'd also love to get the cacti plugin working but we don't have php V5 on our cacti box, so I can't. That (I think) would help at least know what we're dealing with. Unfortunately this is not something that can be easily done (unless I'm totally missing things). We have dozens of...

Some background, We're running LSWS 3.2.1 On a Dual Xeon 3.0 ghz, 2 gb of memory. It's a cPanel box and it was running Apache. PHP is a fresh build of 4.4.7 with eAccelerator. The PHP LSAPI is set: Max Connections: 30 PHP_LSAPI_CHILDREN=30 Initial Request Timeout: 60 Process Soft...

Well we have to have Zend (for encoded programs) so eAccelerator it is. We'll be putting the other changes in a bit later this morning and hopefully it levels things out just a bit. TIA, Frank

It's still "fair to partly cloudy" :D We were able to get eaccelerator back in but loads are still bouncing all over the place. We simply have not had time to play with any of the other suggested configs yet. That will be tomorrows task. To make it more fun, one of the Blogs we host got...

medialayer, We had left it at the default (60 I believe) but we'll be adjusting it later tonight. Trying to not tweak too many things at once ;) mistwang, We have recompiled and re-enabled eaccelerator. Frank

Anything else we should be looking at? The I/O Event Dispatcher looked "interesting" but we're just on the default "best". We're running CentOS 4 with a 2.6 kernel. Performance is not bad per-se, but the load is actually a bit higher than when we ran Apache. For now I think it's because...