My bad, it appears to have been a permissions problem. When I change the service from the system account to logon as myself, the service starts nicely. And handles the segfault condition relatively gracefully (the process terminates, closing the socket, but restarts). The only problem I see now is that this abnormal condition does not appear in the mongrel/rails log or in the windows event log. Is there somewhere else I should be looking to find these?
- donald > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Ball, Donald A Jr (Library) > Sent: Thursday, December 21, 2006 12:49 PM > To: mongrel-users@rubyforge.org > Subject: [Mongrel] mongrel_service-0.3.1 problems - service > will not start > > Hey, I just finished a round of testing my app with > mongrel-1.0rc1 (pretty good, four segfaults and a gc error in > maybe ten thousands > requests) and was moving on to mongrel_service to see if it > could cope with said segfaults and gc errors. Sadly, the > service will not start. I installed using: > > mongrel_rails service::install -N nplrails -e development -p 3000 > > claims to be happy. When I try to start either via "net > start" or the services control panel, windows says that the > service started and then stopped immediately. I saw nothing > interesting in the windows application event log, or in > c:\sites\npl\log for that matter. The service reports its > command-line as: > > "c:/ruby/bin/mongrel_service.exe" single -e development -p > 3000 -a 0.0.0.0 -l "log/mongrel.log" -P "log/mongrel.pid" -c > "C:/sites/npl" -t 0 -r "public" -n 1024 > > which looks appropriate to me. Any suggestions for how to > correct this problem? Many thanks. > > - donald > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users