Search results

This is on a Joyent Accelerator (Solaris): Right as the actual installation seems to be taking place Im getting this: Setup up PHP [Y/n]: n Installing, please wait... ./install.sh: test: argument expected And it quits. Im using lsws-3.3.15-std-i386-solaris.tar.gz I've checked...

Im having some odd issue where redirects in the development environment result in a white page rendered and the logs show that the redirect was not followed (redirected to action never hit). This is with 3.2.2 and ruby-lsapi 2.7, in rails development environment Production does not seem to...

I'm proxying lsws to a mongrel backend serving my rails app in my development environment. Ive noticed that a url such as /locations/6/edit? causes lsws and mongrel to go crazy. Mongrel ends up dying. lsws debug output of what its trying to do is here: http://stat.im/lsws.error.log.txt...

on the download page: http://www.litespeedtech.com/packages/3.0/lsws-3.1.1.1-std-i386-osx.tar.gz should be: http://www.litespeedtech.com/packages/3.0/lsws-3.1.1-std-i386-osx.tar.gz

I just checked the LSAPI page and it says version 2.2 (the actual link is still pointing to 2.1 by the way). Looks like a lot has changed in the LSAPI since I last updated it. I'm still using 1.13. I don't see anything in the Release Log on the site, nor the README in the package. I feel...

I have no idea what is going on with one of my rails apps. The only thing Ive done was upgrade ruby-lsapi to 1.13 recently. All of the sudden at 11:30 today one of my apps is just completely inaccessible, very odd. Nothing in stderr.log, and definitely different output in debug mode when I try...

Not sure if this is a bug or something that just needs configuration tweaks to work correctly, I'll do my best to explain: Im running into a Broken Pipe issue with the following code running on 2.2.5. The same thing under Mongrel works fine, so I assume there is something I can do to get...

I have ftp access set up to the log directory so clients can pull their access logs. Using the nice log rotation and gzip seems to be the perfect fit, but its creating the gzip's as root. This results in the files being Permission denied when attempting to download them. Is that any way I can...

Not sure if this is a bug but I can not seem to work around this issue unless I am simply overlooking a setting. Ive successfully set up rails apps on litespeed when running litespeed and all the rails apps under the same (one) username. Now what im attempting is running litespeed as nobody...

Not quite a bug, not quite a feature.... hopefully it would be a quick fix: The log files (stderr.log for example) get locked/closed/something on a server restart: tail -f stderr.log & (logs tailed) lswsctrl restart (no more logs from tail show up) in which case you need to break out...

I understand that litespeed/lsapi manages the RailsRunner.rb running processes, shuts them down when they arent being used etc. But just for the sake of knowing, is it possible to make them all stay running until the webserver is shut down? Example: mysite.test, 5 max conn. in rails context...

Ive been able to get SSL working on a test server running CentOS, however when I try to do the same configuration on my production FreeBSD 6.0 server, I run into problems. As soon as I put the SSL configuration in place and click Graceful restart, the server never comes back up. The logs do...

Not sure if this is a bug or a lack of me setting a certain config option: ALL sites are _working_ perfectly through the browser, just noticed this odd thing when using curl -I: PHP sites respond fine: $ curl -I http://www.mpoweredbaseball.com HTTP/1.1 200 OK X-Powered-By: PHP/4.4.4...