Mongrel as service on windows 2003

Hello,

I’m trying to run Mongrel as a service under Windows 2003 Server.
Everything is fine with my application (I’ve tested it locally with
Webrick and Mongrel as well). I’ve tested it on server, too, and it
works, except when I install it as a service. It’s not problem with path
to executable and parameters (I’ve copied the line that appears in the
services panel and pasted it on cmd and it works fine). I’ve already
read all posts that I could and I couldn’t find any answer.

Does anybody have any idea? :frowning:

Thanks in advance.

Marcia

Hi,

I was forgetting.
This is the error message that i get when i try to start the service
through ‘net star myapp’:

The service is not responding to the control function.
More help is available by typing NET HELPMSG 2186.

Thanks.
Marcia

There is a good How To for mongrel server as service at
http://mongrel.rubyforge.org/docs/win32.html

On May 31, 9:25 pm, Marcia A. [email protected]

On 5/31/07, Marcia A. [email protected] wrote:

Unfortunately, How Tos weren’t enough to solve my problem till now. And
I’ve already read a lot of them.

Marcia, could you check no other application collide with the port
used by the service?

Also, there a two useful files inside ruby\bin:

servicefb.log and mongrel_service.log

Clear them and start fresh, then copy and paste the results here.

There must be a reason why the service fails to start…


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

Hello, Luis

It’s exactly the same problem as described in
http://rubyforge.org/forum/message.php?msg_id=16915. I read all messages
of this post and did every single step as suggested, unsuccessfully,
including try to run service with a local user, clear log files, etc.

Marcia

p.s: below is the content of servicefb.log. The file mongrel_service.log
was not generated.

_initialize() constructor
_initialize() constructor done
ServiceProcess(new_name)
ServiceProcess(new_name) done
ServiceHost()
ServiceHost() done
ServiceHost.Add()
_add_to_references()
_add_to_references() done
ServiceHost.Add() done
ServiceController.RunMode()
CurrentPID: 9300
ParentPID: 408
Parent Name:
ServiceController.RunMode() done
ServiceHost() destructor
ServiceHost() destructor done
ServiceProcess() destructor
ServiceProcess() destructor done
_terminate() destructor
_terminate() destructor done

Luis L. wrote:

On 5/31/07, Marcia A. [email protected] wrote:

Unfortunately, How Tos weren’t enough to solve my problem till now. And
I’ve already read a lot of them.

Marcia, could you check no other application collide with the port
used by the service?

Also, there a two useful files inside ruby\bin:

servicefb.log and mongrel_service.log

Clear them and start fresh, then copy and paste the results here.

There must be a reason why the service fails to start…


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

Unfortunately, How Tos weren’t enough to solve my problem till now. And
I’ve already read a lot of them.

Thanks, anyway.

Marcia

dima wrote:

There is a good How To for mongrel server as service at
http://mongrel.rubyforge.org/docs/win32.html

On May 31, 9:25 pm, Marcia A. [email protected]

Luis,

It’s x64.

Thanks a lot for the realease!

Marcia

Luis L. wrote:

On 6/1/07, Marcia A. [email protected] wrote:

p.s: below is the content of servicefb.log. The file mongrel_service.log
was not generated.

[… snipped until important text …]

CurrentPID: 9300
ParentPID: 408
Parent Name:

Marcia, could I ask you what version of Windows 2003 Server are you
using? I guess x64, since is the only platform that shows the same
behavior.

(This is due API incompatibilities between x86 and x64).

Guess, until 0.5 is done, a patch for 0.3.1 is needed.

Will patch it and do a release tonight to address this issue.


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

On 6/1/07, Marcia A. [email protected] wrote:

p.s: below is the content of servicefb.log. The file mongrel_service.log
was not generated.

[… snipped until important text …]

CurrentPID: 9300
ParentPID: 408
Parent Name:

Marcia, could I ask you what version of Windows 2003 Server are you
using? I guess x64, since is the only platform that shows the same
behavior.

(This is due API incompatibilities between x86 and x64).

Guess, until 0.5 is done, a patch for 0.3.1 is needed.

Will patch it and do a release tonight to address this issue.


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

On 6/1/07, Marcia A. [email protected] wrote:

Luis,

It’s x64.

Thanks a lot for the realease!

Done!

Please update your gems and re-install the service for the executable
(mongrel_service.exe) gets replaced by new version.

Let me know of any problems.

Regards,


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

Luis,

It works perfectly.
Again, thanks a lot for your help.

My best regards,

Marcia

Luis L. wrote:

On 6/1/07, Marcia A. [email protected] wrote:

Luis,

It’s x64.

Thanks a lot for the realease!

Done!

Please update your gems and re-install the service for the executable
(mongrel_service.exe) gets replaced by new version.

Let me know of any problems.

Regards,


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi