Nicolas Buduroi's questions

I've got an ASP.NET JSON-RPC web service which work well using the Visual Studio development web server. It has three dependencies: Jayrock, Log4net and a COM DLL (AcoSDK) to be able to access a C++ application.

I'm trying to deploy it on IIS7 in a SBS 2008 server, but I'm having lots of troubles. The application files are in "C:\intepub\wwwroot\AcombaConnect_Deploy" include the bin folder with the compiled binaries. The folder has been converted to an application, but the application would not start so I had to add the following section to the Web.config file:

<system.webServer>
  <handlers>
    <add name="AcombaConnect.Acomba" verb="*" path="*" scriptProcessor="C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll" type="AcombaConnect.Acomba, AcombaConnect" resourceType="Unspecified"/>
  </handlers>
  <directoryBrowse enabled="false"/>
</system.webServer>

At that point the app was throwing: "bad module "ManagedPipelineHandler" in its module list" and I've tried everything from https://stackoverflow.com/questions/8659862 to no avail. I then tried to switch the application pool to the integrated one and added the following to the Web.config file:

<system.webServer>
  <validation validateIntegratedModeConfiguration="false"/>
  ...

Now, it seems the application is starting, but I only get "HTTP Error 503. The service is unavailable."

Does anybody know where to go from there?

P.S.: I don't have much experience with IIS7. I'm not sure where to look for more detailed error messages.

Possible Duplicate:
Deploying an ASP.NET JSON-RPC web service on IIS 7

I've tried to deploy an ASP.NET web application manually and I'm just getting a directory listing. I've copied the published folder to "C:\intepub\wwwroot", then converted to application. Is there a step I'm missing?

Edit: One thing to note is that this application doesn't contains any .aspx pages, it's a web service using Jayrock which provide it's own pages to explore the service interface. When using the application through the VS development web server everything work as expected, I can see the web interface and connect to the service without any problem. But when deployed on IIS, it does nothing at all.

Edit: I think it got to do with IIS not able to figure how to start the application handler properly.

I'm trying to setup a Resque worker as an Upstart init script to be used by Monit in a Rails app. I'm not a sysop and I've tried to write this using examples from other init script we have on our server, here's what I got:

start on startup
stop on shutdown

pre-start script
   cd /var/www/my-app/current
end script

script
   exec bundle exec rake environment resque:work RAILS_ENV=staging PIDFILE=/var/run/resque.pid QUEUE=sync >> /var/log/resque.log
end script

But it doesn't work, if I try sudo start resque I get:

resque start/running, process XXXX

Nothing is being started as far as I know, there's no Resque process to be found nor there's log file. I'm quite lost as to how to get it working.

Update: I've found the syslog file and it says:

Nov  4 17:20:09 fantasysports init: resque main process (3057) terminated with status 2

Update: I've tried to run it using sudo (yeah that doesn't make sense!) and removed the output redirection to the log file and now I get a different status code:

Nov  4 17:29:44 fantasysports init: resque main process (3276) terminated with status 10

Update: Ended up ditching Upstart for init.d, as start-stop-daemon is much better documented and it give me complete control of what's going on.

I've got a staging server running nginx 1.0.5 using Rails 3.1 under Passenger 3.0.9. The problem is that a request sent just after one where there's an application error return 502 Bad Gateway. To test it I've set up a simple controller with an action that just raise a dummy exception. One request will show the Rails error message and the next one will show nginx 502 Bad Gateway error, then it goes back to the Rails application error, etc.

While investigating this problem I've found out that load testing the application (which increase the number of application processes) make that issue disapear. That is until the extra processes are shutdown, then it reappear. I've tried setting the passenger_min_instances option, but doing so doesn't change anything and in this case each time an application error happen one instance is killed while after load testing all instances are kept alive.

P.S.: Some people on my team told me that they've seen the 502 error even when there's no application error but I've not been able to reproduce that.

Update: Just found out how to display the responses status codes using ab and most of them are 502!

I'm trying to use mod_rewrite through the .htaccess files and I have a big problem, the .htaccess files don't seems to be read. The machine is running Debian 5.0 and it's using the stable apache2 package.

I've followed instructions from this page: http://www.debian-administration.org/articles/136. Enabled mod_rewrite like that:

a2enmod rewrite

In my /etc/apache2/apache2.conf file I've added this:

<Directory "/var/www">
  AllowOverride ALL
  Options FollowSymLinks
</Directory>

In the root directory, I've created a .htaccess file with this content:

RewriteEngine on
RewriteRule ^test$ foo.html

I've tried lots of suggestion from answers to similar questions to no avail. The error message I get when visiting foo.com/test is a 404 Page Not Found. All files are readable by everyone. There's no problem when accessing foo.html directly. I've also tried to put garbage in another .htaccess to see if apache would complains about it, nothing changed. Maybe I'm just too tired!

Thanks