Mongrel users - Feb 2007 - Problems getting mongrel service working

Hello list!

I have mongrel service 0.1.0 working on my current production machine.
 Upgrading to a new server and also moving to mongrel service 0.3.1
has not worked yet.  I am hoping someone will have an idea as to why.

I have mongrel installed properly (I think):
C:\rails\igacc>gem list --local

*** LOCAL GEMS ***
...

mongrel (1.0.1)
    A small fast HTTP library and server that runs Rails, Camping, Nitro
    and Iowa apps.

mongrel_service (0.3.1)
    Mongrel Native Win32 Service Plugin for Rails (debug build)

rails (1.2.2, 1.2.1)
    Web-application framework with template engine, control-flow layer,
    and ORM.

...

I install the service correctly (I think):

C:\rails\igacc>mongrel_rails service::install -N callcenter -p 4001 -e
production -c "C:\rails\igacc" -r "C:\rails\igacc" -l
"log/mongrel.log" -P "log/mongrel.pid" -t 0 -n 1024 -a
"http://localhost:4001"
Mongrel service ''callcenter'' installed as
''callcenter''.

I attempt to start the service correctly (I think):

C:\rails\igacc>net start callcenter
The callcenter service is starting.
The callcenter service could not be started.

The service did not report an error.

More help is available by typing NET HELPMSG 3534.

I appear to have a working setup.  When I start mongrel_rails I get a
working site:

C:\rails\igacc>mongrel_rails start -p 4001 -e production
** Starting Mongrel listening at 0.0.0.0:4001
** Starting Rails with production environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  INT => stop (no restart).
** Mongrel available at 0.0.0.0:4001
** Use CTRL-C to stop.

Ruby looks good:

C:\rails\igacc>ruby -v
ruby 1.8.5 (2006-08-25) [i386-mswin32]

C:\rails\igacc>irb
irb(main):001:0> exit

My program loads in the console fine:

C:\rails\igacc>ruby script/console production
Loading production environment.
>> exit
Any ideas? I am stumped.

-- 
(**********************************************************
* l*eter H. l3oling
* Web Application Designer - PanEther, LLC
* email:      peter.boling at gmail.com
* blog:        http://galtzo.blogspot.com/
* languages:  English, Spanish, Portuguese
***********************************************************)

On 2/23/07, Peter Boling <peter.boling at gmail.com>
wrote:
> Hello list!
>
Welcome to the list!
> I have mongrel service 0.1.0 working on my current production machine.
>  Upgrading to a new server and also moving to mongrel service 0.3.1
> has not worked yet.  I am hoping someone will have an idea as to why.
>
> I have mongrel installed properly (I think):
> C:\rails\igacc>gem list --local
>
> *** LOCAL GEMS ***
> ...
>
> mongrel (1.0.1)
>     A small fast HTTP library and server that runs Rails, Camping, Nitro
>     and Iowa apps.
>
> mongrel_service (0.3.1)
>     Mongrel Native Win32 Service Plugin for Rails (debug build)
>
> rails (1.2.2, 1.2.1)
>     Web-application framework with template engine, control-flow layer,
>     and ORM.
>
> ...
>
> I install the service correctly (I think):
>
> C:\rails\igacc>mongrel_rails service::install -N callcenter -p 4001 -e
> production -c "C:\rails\igacc" -r "C:\rails\igacc" -l
> "log/mongrel.log" -P "log/mongrel.pid" -t 0 -n 1024 -a
"http://localhost:4001"
> Mongrel service ''callcenter'' installed as
''callcenter''.
>
Ok, you didn''t install it properly.

-a takes an "address" parameter, some IP to bind to, like 127.0.0.1
(which is localhost) or, if you don''t provide it, will bind to any
available IP in your system (that''s why mongrel report 0.0.0.0)

Instead, you supplied a URL, which is not valid.

> I attempt to start the service correctly (I think):
>
> C:\rails\igacc>net start callcenter
> The callcenter service is starting.
> The callcenter service could not be started.
>
> The service did not report an error.
>
> More help is available by typing NET HELPMSG 3534.
>
> I appear to have a working setup.  When I start mongrel_rails I get a
> working site:
>
> C:\rails\igacc>mongrel_rails start -p 4001 -e production
> ** Starting Mongrel listening at 0.0.0.0:4001
> ** Starting Rails with production environment...
> ** Rails loaded.
> ** Loading any Rails specific GemPlugins
> ** Signals ready.  INT => stop (no restart).
> ** Mongrel available at 0.0.0.0:4001
> ** Use CTRL-C to stop.
>
When you started mongrel "manually", you didn''t supplied all
the
parameters you used during installation of the service.

If you try to start mongrel_rails with these parameters, you will get an error.

mongrel_rails start -p 4001 -e production -c "C:\rails\igacc" -r
"C:\rails\igacc" -t 0 -n 1024 -a "http://localhost:4001"

> Ruby looks good:
>
> C:\rails\igacc>ruby -v
> ruby 1.8.5 (2006-08-25) [i386-mswin32]
>
> C:\rails\igacc>irb
> irb(main):001:0> exit
>
> My program loads in the console fine:
>
> C:\rails\igacc>ruby script/console production
> Loading production environment.
> >> exit
>
> Any ideas? I am stumped.
>
I''ll also suggest you add fastthread (mswin32) gem too:

gem install fastthread


-- 
Luis Lavena
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

I have the same problems:

C:\Documents and Settings\Administrator>mongrel_rails start -c "c: 
\Program Files
\xxx\xxx" -p 3000 -e production
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with production environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  INT => stop (no restart).
** Mongrel available at 0.0.0.0:3000
** Use CTRL-C to stop.
** INT signal received.
Terminate batch job (Y/N)? y

 >> At this point the application runs without problems

C:\Documents and Settings\Administrator>mongrel_service console  
single -c "C:\Pr
ogram Files\xxx\xxx" -p 3000 -e production -a 127.0.0.1 -B
Mongrel Win32 Service, version 0.3.1
(c) 2006 The Mongrel development team.

Starting service ''single'' in console mode, please wait...
Service is in running state.
Press Ctrl-C to stop it.
Stop signal received, stopping...
Waiting for onStart() to exit...
Service stopped, doing cleanup.
Done.

 >> The application is not running - no log files generated

C:\Documents and Settings\Administrator>mongrel_rails service::remove  
-N xxx

xxx service removed.

C:\Documents and Settings\Administrator>mongrel_rails  
service::install -N xxx
-c "C:\Program Files\xxx\xxx" -p 3000 -e production -a 127.0.0.1 -
B -l log -p log
Mongrel service ''xxx'' installed as ''xxx''.

C:\Documents and Settings\Administrator>net start xxx
The xxx service is starting.
The xxx service could not be started.

The service did not report an error.

More help is available by typing NET HELPMSG 3534.

 >> And of course no running service either...

Installed Gems:

fastthread (0.6.4.1)
gem_plugin (0.2.2)
mongrel (1.0.1)
mongrel_service (0.3.1)
win32-service (0.5.2)

and Rails 1.1.6

This is Windows 2003 Server

Any ideas?


thanks
Jens-Christian

On 2/24/07, Jens-Christian Fischer <jcfischer at gmail.com>
wrote:
> I have the same problems:
>
> C:\Documents and Settings\Administrator>mongrel_rails start -c "c:
> \Program Files
> \xxx\xxx" -p 3000 -e production
> ** Starting Mongrel listening at 0.0.0.0:3000
> ** Starting Rails with production environment...
> ** Rails loaded.
> ** Loading any Rails specific GemPlugins
> ** Signals ready.  INT => stop (no restart).
> ** Mongrel available at 0.0.0.0:3000
> ** Use CTRL-C to stop.
> ** INT signal received.
> Terminate batch job (Y/N)? y
>
>  >> At this point the application runs without problems
>
> C:\Documents and Settings\Administrator>mongrel_service console
> single -c "C:\Pr
> ogram Files\xxx\xxx" -p 3000 -e production -a 127.0.0.1 -B
> Mongrel Win32 Service, version 0.3.1
> (c) 2006 The Mongrel development team.
>
> Starting service ''single'' in console mode, please wait...
> Service is in running state.
> Press Ctrl-C to stop it.
> Stop signal received, stopping...
> Waiting for onStart() to exit...
> Service stopped, doing cleanup.
> Done.
>
>  >> The application is not running - no log files generated
>
Ok, at this point I should say what previously posted to the list:
test the environment in the same conditions, with the same options!

In your first mongrel_rails call, you let mongrel choose the default
options for you. Under windows isn''t possible right now, and debug
information is disabled (by default).

Now, when you tested the "console", you passed -B, debug mode, which
help you pinpoint some leacks of Ruby VM and your application.

In your statement, you said no log files where created, that is true,
but the application works???
> C:\Documents and Settings\Administrator>mongrel_rails service::remove
> -N xxx
>
> xxx service removed.
>
> C:\Documents and Settings\Administrator>mongrel_rails
> service::install -N xxx
> -c "C:\Program Files\xxx\xxx" -p 3000 -e production -a 127.0.0.1
-
> B -l log -p log
> Mongrel service ''xxx'' installed as
''xxx''.
>
You passed "-l log" which is invalid, since -l expect a file and not a
folder.
One important thing: -p is PORT parameter, and you used to pass your
PID (-p log), which will generate some problems, please review you
command parameters.

The service will fail, since if you type that command in plain mongrel_rails:

C:\Program Files\yyyy\zzzz>mongrel_rails start -c "C:\Program
Files\yyyy\zzzz" -p 3000 -e production -a 127.0.0.1 -B -l log -p log

** Starting Mongrel listening at 127.0.0.1:log
** Installing debugging prefixed filters. Look in log/mongrel_debug
for the files.

Its good to know that log port is always available! (sarcasm).

==
If I perform some checkings, I get everything working:

C:\Program Files\yyyy\zzzz>type config\environment.rb
...
# Specifies gem version of Rails to use when vendor/rails is not present
RAILS_GEM_VERSION = ''1.1.6''
...


C:\Program Files\yyyy\zzzz>type config\database.yml
# SQLite version 3.x
#   gem install sqlite3-ruby
...
production:
  adapter: sqlite3
  database: db/production.sqlite3


# Test WEBrick
C:\Program Files\yyyy\zzzz>ruby script\server webrick -e production
./script/../config/boot.rb:28:Warning: require_gem is obsolete.  Use
gem instead.
=> Booting WEBrick...
=> Rails application started on http://0.0.0.0:3000
=> Ctrl-C to shutdown server; call with --help for options
[2007-02-25 13:03:25] INFO  WEBrick 1.3.1
[2007-02-25 13:03:25] INFO  ruby 1.8.4 (2005-12-24) [i386-mswin32]
[2007-02-25 13:03:25] INFO  WEBrick::HTTPServer#start: pid=1396 port=3000

Browsing to the default rails info page:
Ruby version	1.8.4 (i386-mswin32)
RubyGems version	0.9.2
Rails version	1.1.6
Active Record version	1.14.4
Action Pack version	1.12.5
Action Web Service version	1.1.6
Action Mailer version	1.2.5
Active Support version	1.3.1
Application root	C:/Program Files/yyyy/zzzz
Environment	production
Database adapter	sqlite3


# Now running mongrel_rails
C:\Program Files\yyyy\zzzz>mongrel_rails start --help
Usage: mongrel_rails <command> [options]
    -e, --environment ENV            Rails environment to run as
    -p, --port PORT                  Which port to bind to
    -a, --address ADDR               Address to bind to
    -l, --log FILE                   Where to write log messages
    -P, --pid FILE                   Where to write the PID
    -c, --chdir PATH                 Change to dir before starting
(will be expanded)
    -B, --debug                      Enable debugging mode

C:\Program Files\yyyy\zzzz>mongrel_rails start -c "C:\Program
Files\yyyy\zzzz" -p 3000 -e production -a 127.0.0.1
** Starting Mongrel listening at 127.0.0.1:3000
** Starting Rails with production environment...
C:0:Warning: require_gem is obsolete.  Use gem instead.
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  INT => stop (no restart).
** Mongrel available at 127.0.0.1:3000
** Use CTRL-C to stop.

# Browsing to that address:port report me the same results as previosly listed.

# Testing using ''console''
C:\Program Files\yyyy\zzzz>mongrel_service console single -e
production -p 3000 -a 127.0.0.1
Mongrel Win32 Service, version 0.3.1
(c) 2006 The Mongrel development team.

Starting service ''single'' in console mode, please wait...
Service is in running state.
Press Ctrl-C to stop it.

# Browsing to the site show me the page, and also got the rails information too.
# Pressing Ctrl-C...

Stop signal received, stopping...
Waiting for onStart() to exit...
Service stopped, doing cleanup.
Done.

# Now install the service.
C:\Program Files\yyyy\zzzz>mongrel_rails service::install -N myservice
-c "C:\Program Files\yyyy\zzzz" -p 3000 -e production -a 127.0.0.1
** Copying native mongrel_service executable...
Mongrel service ''myservice'' installed as
''myservice''.

# Verify the Executable Path (ImagePath) installed by service::install:
(Administrative Tools -> Services, locate ''myservice'' and
get properties):

"C:/Ruby/bin/mongrel_service.exe" single -e production -p 3000 -a
127.0.0.1 -l "log/mongrel.log" -P "log/mongrel.pid" -c
"C:/Program
Files/yyyy/zzzz" -t 0 -r "public" -n 1024

# Now start the service.
C:\Program Files\yyyy\zzzz>net start myservice
The myservice service is starting.
The myservice service was started successfully.

# Check if ruby process is actually running:
C:\Program Files\yyyy\zzzz>tasklist /SVC /FI "SERVICES eq
myservice"

Image Name                   PID Services
mongrel_service.exe          300 myservice


C:\Program Files\yyyy\zzzz>tasklist /FI "SERVICES eq myservice"

Image Name                   PID Session Name     Session#    Mem Usage
mongrel_service.exe          300 Console                 0      1.452 K


C:\Program Files\yyyy\zzzz>tasklist /FI "IMAGENAME eq ruby.exe"

Image Name                   PID Session Name     Session#    Mem Usage
ruby.exe                    1312 Console                 0     25.796 K


# With Process Explorer [1] you could see that ruby.exe process is a
child process of mongrel_service.exe

# Stopping the service
C:\Program Files\yyyy\zzzz>net stop myservice
The myservice service is stopping.
The myservice service was stopped successfully.

> C:\Documents and Settings\Administrator>net start xxx
> The xxx service is starting.
> The xxx service could not be started.
>
If you get this is because mongrel_service couldn''t get ruby and
mongrel_rails to start properly.

Also, PLEASE REMEMBER that the default configuration for a service is
run under NT AUTHORITY\SYSTEM account, and NOT YOUR account.

That could show problems due NTFS permissions in your folders and/or files.
> Installed Gems:
>
> fastthread (0.6.4.1)
> gem_plugin (0.2.2)
> mongrel (1.0.1)
> mongrel_service (0.3.1)
> win32-service (0.5.2)
>
> and Rails 1.1.6
>
I mimic-ed your environment with the same gems, even reinstalled rails 1.1.6 :-)
> This is Windows 2003 Server
>
Tested under Windows XP SP2 and Windows Storage Server 2003 R2 (which
is the same, but optimized for file serving NAS like functionality).
> Any ideas?
>
Please, try perform the comparisons/tests with the same parameters.
Also check permission issues which often show no error but there are
present and brake almost every application "transparently".

Check this thread on Rubyforge about same problems with services under
managed environments:

http://rubyforge.org/forum/forum.php?thread_id=11060&forum_id=5450


[1] http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx


Regards,

-- 
Luis Lavena
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

Hi Luis
>
> Ok, at this point I should say what previously posted to the list:
> test the environment in the same conditions, with the same options!
I did :-)
> In your first mongrel_rails call, you let mongrel choose the default
> options for you. Under windows isn''t possible right now, and debug
> information is disabled (by default).
ok - thanks, didn''t realize that....
> You passed "-l log" which is invalid, since -l expect a file and
> not a folder.
> One important thing: -p is PORT parameter, and you used to pass your
> PID (-p log), which will generate some problems, please review you
> command parameters.
gnnnn - it was quite late when I tried this - sorry.
>
>
> Also, PLEASE REMEMBER that the default configuration for a service is
> run under NT AUTHORITY\SYSTEM account, and NOT YOUR account.
>
> That could show problems due NTFS permissions in your folders and/ 
> or files.
Users, Adminstrators and SYSTEM have "Full control" over the relevant
folder.

Ok, some progress:

I removed everything and reinstalled Ruby 1.8.4 (down from 1.8.5)

Even with the correct parameters (I checked, double checked and  
everything) I get the same results:
* mongrel_rails .... -> Application runs
* mongrel_service console single .... -> Can''t connect to  
application. I looked at "netstat -a" and no process is bound to port
3000
* service -> doesn''t run

Then on the same machine, I created a brand new application:
 > rails test
 > cd test
 > mongrel_rails start -> Application runs
 > mongrel_service console single -e development -p 3000 -a 127.0.0.1  
-l "log/mongrel.log" -P "log/mongrel.pid" -t 0 -r
"public" -n 1024 -c
"c:\Program Files\xxx\test" -B

And now the application runs....  So there must be something in my  
application that makes it fail, when it''s run as a service. Without  
any logfiles, that''s pretty difficult to diagnose though...

Any more ideas?

thanks for your help
jc

On 2/25/07, Jens-Christian Fischer <jcfischer at gmail.com>
wrote:
> [...]
>
> Users, Adminstrators and SYSTEM have "Full control" over the
relevant
> folder.
>
> Ok, some progress:
>
> I removed everything and reinstalled Ruby 1.8.4 (down from 1.8.5)
>
> Even with the correct parameters (I checked, double checked and
> everything) I get the same results:
> * mongrel_rails .... -> Application runs
> * mongrel_service console single .... -> Can''t connect to
> application. I looked at "netstat -a" and no process is bound to
port
> 3000
> * service -> doesn''t run
>
> Then on the same machine, I created a brand new application:
>  > rails test
>  > cd test
>  > mongrel_rails start -> Application runs
>  > mongrel_service console single -e development -p 3000 -a 127.0.0.1
> -l "log/mongrel.log" -P "log/mongrel.pid" -t 0 -r
"public" -n 1024 -c
> "c:\Program Files\xxx\test" -B
>
> And now the application runs....  So there must be something in my
> application that makes it fail, when it''s run as a service.
Without
> any logfiles, that''s pretty difficult to diagnose though...
>
Ok, what are you using in your application? any gems, libs?

Sorry for the logfiles, didn''t have time to re implement them in the
new service executable (work was too much the past months).
> Any more ideas?
>
Yeah, download psexec [1] from Sysinternals, and using it start a new
cmd console with stripped rights:
>psexec -l cmd.exe
This will pop a new cmd.exe window, and try starting your application
(mongrel_rails start ...) from it.

That console is the safest console you could get, and would show the
problems since you will be logging to STDOUT :-)


[1] http://www.microsoft.com/technet/sysinternals/utilities/psexec.mspx

-- 
Luis Lavena
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

>
>> psexec -l cmd.exe
>
> This will pop a new cmd.exe window, and try starting your application
> (mongrel_rails start ...) from it.
>
> That console is the safest console you could get, and would show the
> problems since you will be logging to STDOUT :-)
we are getting there:

this in a psexec''d shell:

C:\Program Files\xxx\xxxx>mongrel_rails start
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment...
C:/Program Files/ruby/bin/mongrel_rails: No such file or directory -  
uname
C:/Program Files/ruby/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/ 
active_record/connection_adapters/abstract_adapter.rb:120:in `log'':  
SQLite3::SQLException: SQL logic error or missing database: INSERT  
INTO wantypes ("name", "bandwidth", "latency")
VALUES(''E1'', 2048, 10)
(ActiveRecord::StatementInvalid)

It seems, that SQLite does not find the database. I get a similar  
error when running the console.

HOWEVER: doing the following works:

 > Wantype.find :all
=> [... array of wantypes ]

while

 >> w = Wantype.create( :name => ''gaga'', :bandwidth
=> 12, :latency
=> 10)
ActiveRecord::StatementInvalid: SQLite3::SQLException: SQL logic  
error or missing database: INSERT INTO wantypes ("name",
"bandwidth",
"latency") VALUES(''gaga'', 12, 10)

fails.

That led me to examine the security properties for the log and db  
directory and the db files in it. Giving everybody full access to  
everything makes mongrel_rails start in the psexec shell.

However:
mongrel_service console single -e production -p 3000 -a 127.0.0.1 -l  
"log/mongrel.log" -P "log/mongrel.pid" -t 0 -r
"public" -n 1024 -c "c:
\Program Files\xxx\xxx"

still fails. The server doesn''t start, no log or pid files written.

More ideas?

thanks for your help
jc

Thanks Luis!  Your help solved my problem:

C:\rails\igacc>mongrel_rails start -p 4001 -e production -c
"C:\rails\igacc" -r "C:\rails\igacc" -t 0 -n 1024 -a
"127.0.0.1"
** Starting Mongrel listening at 127.0.0.1:4001
** Starting Rails with production environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready.  INT => stop (no restart).
** Mongrel available at 127.0.0.1:4001
** Use CTRL-C to stop.
** INT signal received.
Terminate batch job (Y/N)? Y

C:\rails\igacc>mongrel_rails service::remove -N callcenter
callcenter service removed.

C:\rails\igacc>mongrel_rails service::install -N callcenter -p 4001 -e
production -c "C:\rails\igacc" -r "C:\rails\igacc" -t
0 -n 1024 -a "127.0.0.1" -l "log/mongrel.log" -P
"log/mongrel.pid"
Mongrel service ''callcenter'' installed as
''callcenter''.

C:\rails\igacc>net start callcenter
The callcenter service is starting..
The callcenter service was started successfully.

And the app functions normally!
-- 
(**********************************************************
* l*eter H. l3oling
* Web Application Designer - PanEther, LLC
* email:      peter.boling at gmail.com
* blog:        http://galtzo.blogspot.com/
* languages:  English, Spanish, Portuguese
***********************************************************)

On 2/26/07, Jens-Christian Fischer <jcfischer at gmail.com>
wrote:
> >
> >> psexec -l cmd.exe
> >
> > This will pop a new cmd.exe window, and try starting your application
> > (mongrel_rails start ...) from it.
> >
> > That console is the safest console you could get, and would show the
> > problems since you will be logging to STDOUT :-)
>
> we are getting there:
>
> this in a psexec''d shell:
>
> C:\Program Files\xxx\xxxx>mongrel_rails start
> ** Starting Mongrel listening at 0.0.0.0:3000
> ** Starting Rails with development environment...
> C:/Program Files/ruby/bin/mongrel_rails: No such file or directory -
> uname
> C:/Program Files/ruby/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/
> active_record/connection_adapters/abstract_adapter.rb:120:in
`log'':
> SQLite3::SQLException: SQL logic error or missing database: INSERT
> INTO wantypes ("name", "bandwidth",
"latency") VALUES(''E1'', 2048, 10)
> (ActiveRecord::StatementInvalid)
>
That''s is good news! (err, well, they are actually).
> It seems, that SQLite does not find the database. I get a similar
> error when running the console.
>
Could you post info of your config/database.yml?
Also, you''re using sqlite3-ruby gem? You *really* need this (there are
problems with the Ruby/DL binding of previous versions).

Also, sqlite3.dll must be in the PATH (I prefer put it
windows\system32 since I use with other tools).

Please note that versions higher than 3.3.7 of Sqlite3 have issues
with Rails, only solved in 1.2.2 (in your case didn''t apply).
> HOWEVER: doing the following works:
>
>  > Wantype.find :all
> => [... array of wantypes ]
>
> while
>
>  >> w = Wantype.create( :name => ''gaga'',
:bandwidth => 12, :latency
> => 10)
> ActiveRecord::StatementInvalid: SQLite3::SQLException: SQL logic
> error or missing database: INSERT INTO wantypes ("name",
"bandwidth",
> "latency") VALUES(''gaga'', 12, 10)
>
> fails.
>
> That led me to examine the security properties for the log and db
> directory and the db files in it. Giving everybody full access to
> everything makes mongrel_rails start in the psexec shell.
>
> However:
> mongrel_service console single -e production -p 3000 -a 127.0.0.1 -l
> "log/mongrel.log" -P "log/mongrel.pid" -t 0 -r
"public" -n 1024 -c "c:
> \Program Files\xxx\xxx"
>
Since console will run in the current user context (which differ from
psexec env.), I guess the problem is outside mongrel faults, and
specific to your environment... could you contact me via gtalk or msn?
(same username @hotmail.com).
> still fails. The server doesn''t start, no log or pid files
written.
>
No log or pid will be written, since that functionality isn''t set in
the current version... will try to fix that ASAP.
> More ideas?
>
Contact me via IM and we could check whats happening.

-- 
Luis Lavena
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 2/26/07, Peter Boling <peter.boling at gmail.com>
wrote:
> Thanks Luis!  Your help solved my problem:
>
Thats good to know!

Could you share what you changed to get it working? that will help others :-)

< [...]
>
> And the app functions normally!
> --
-- 
Luis Lavena
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 2/26/07, Luis Lavena <luislavena at gmail.com>
wrote:
> On 2/26/07, Peter Boling <peter.boling at gmail.com> wrote:
> > Thanks Luis!  Your help solved my problem:
>
> Thats good to know!
>
> Could you share what you changed to get it working? that will help others
:-)
Your tip on the ''-a'' parameter fixed it.  That was apparently
the
hangup for me.  Once I changed it from a URL ( -a
"http://localhost:4001") to an IP (-a "127.0.0.1")
everything worked!
Didn''t need the port number in the -a parameter as I had assumed.

-- 
(**********************************************************
* l*eter H. l3oling
* Web Application Designer - PanEther, LLC
* email:      peter.boling at gmail.com
* blog:        http://galtzo.blogspot.com/
* languages:  English, Spanish, Portuguese
***********************************************************)

> Could you post info of your config/database.yml?
> Also, you''re using sqlite3-ruby gem? You *really* need this (there
are
> problems with the Ruby/DL binding of previous versions).
I was using both the sqlit3-ruby gem and the one bundled by _why  
(which includes the DLL). Because I can actually read the DB (and  
write to it, when not running as a service) I don''t think
that''s the
problem.

Here''s my database.yml for good measure:

   development:
     adapter: sqlite3
     dbfile: db/com_prod.db

   test:
     adapter: sqlite3
     dbfile: db/com_test.db

   production:
     adapter: sqlite3
     dbfile: db/com_prod.db
> Since console will run in the current user context (which differ from
> psexec env.), I guess the problem is outside mongrel faults, and
> specific to your environment... could you contact me via gtalk or msn?
> (same username @hotmail.com).
I have added you to my gtalk account.
>
> Contact me via IM and we could check whats happening.
>
I''ll catch you :-) Thanks for the help!

cheers jc