Search results

Well here is an instance of it happening on cpanel server. the sites started lagging badly and load was super high. I logged in server, here is the commands and output. This happens everyonce in a while on cpanel servers and frequently with directadmin servers. Please look into this, surely Im...

delete this post just delete pls sorry for the troubles

Sorry didnt see your reply on this But anyway, thi seems to happen more so on directadmin server. When it happens it makes server completely unresponsive. Sending login info now

Never seen this before. Was a freshly installed server. Cewntos 5 32 bit with cpanel. Went to replace apache with lsws and when it started gave this errors, I cant get it to run

This is a real bug no matter how you look at it. It does this on da servers most but does it on apache as well. So here is how it usually goes like today. Found out all sites were down on the server, a directadmin server. I go in and , well here is copy and paste for you The processes...

Oh yeah its confirmed, new version will take over any listening ip whether its in config or not. I rolled back and fixed the problem

not sure, may have been something with that setup But on the process thing, if you use the lswsctrl stop, will still take some time to stop. Should be able to kill the pids Sometimes the lsws restarts and the old processes are still remaining and it just freezes up everything, makes sites...

This has been a big for a while now where lshttpd will restart or something and the old processes are still going causing everything to go haywire. You cannot kill the processes with killall. and you have to kill -9 the root lshttpd process over and over to get it to kill. And since the...

looks like from the last versions of lsws and php sapi that the core file thng is back, multiple gbit core files taking over all disk space. Php thing or not. I have core files disabled in limits.conf and it still does it! core files are disabled in lsws admin as well. I know Ive heard from...

well if you have apache off in the directadmin service monitor it should not start back. I tried this though every which way, using the apache wrapper and everything with the monitor, it still done it. Only solution was to downgrade to the version before the latest. I would have normally...

I setup a server today and they have a script where a user signs up and it gives them a subdomain. They use wildcard on their dns and in httpd.conf this line here: VirtualDocumentRoot /home/admin/domains/blogabet.com/public_html/users/%1.0/ So when a user enters their subdomain like...

yep new version is a dud with directadmin. I just tried to setup a vps with it today, brand new vps, is doing the same thing Installing the .12 version fixed issue in both situations

rolling back seems to have resolved the problem

it keeps on doing this 2008-06-01 02:40:25.838 [NOTICE] Server Restart Request via Signal... Im gonna roll back and see if it helps. Nothing is giving it signal, its just doing it

oh wow, since I had to come in and startt it back up tonight its killing itself every few minutes. Here is usual log entries 008-06-01 02:34:59.929 [NOTICE] [Child: 7501] Setup swapping space... 2008-06-01 02:34:59.929 [NOTICE] [Child: 7501] LiteSpeed/3.3.13 Enterprise starts successfully...

I notice another problem too but its before this version. Sometimes lshttpd makes too many processes for itself. For example a one core license restarts or something and then has 2 root processes and 2 apache process and its very hard to kill the processes, they do not die immediately. Not sure...

Since I upgraded the other night I been getting random shutdowns for no reaosn at all. Server just stops. Upon looking at the logs for the last shutdown here is what it has 2008-06-01 02:09:18.773 [ERROR] HttpListener::start(): Can't listen at address adminListener: Address already in use...

Well i know it was posted here before but I just cant find it. Ive tried nearly all on google for rewriting urls and forcing app types to no avail. What would be the .htaccess code to make the server read the php files as php4 or php5?

Well you may wanna set your core limits in limits.conf to 0 otherwise if a user has a script that doesnt agree with lsphp it can fill up your entire disk space pretty fast. Trust me Ive been there lol. Also it wouldnt hurt to disable core dumps in litespeed admin. As far as being php error...

true true, even if they supplied php5 most would have to recompile to get what they need, still think it would be a lot handier though to get a server up and running quicker.