Looking up, I'm still pretty sure it's the same problem, at least to the root. It's the exact same error, and more specifically, a refresh works just fine.
1) The database backend is SQL Server. This is required by the IT dept here. The bindings are system-wide. 2) I tried adding "console" before single, it didn't do anything helpful. 3) I tried psexec -l cmd.exe and running mongrel_rails. It worked perfectly and showed no errors. RE: Permissions: I gave the folder full permissions for all users, and it didn't help. Worst of all, the error seems to be "sometimes" now that I disabled pagination. I -think- it might be a login-limit to the scheduler user on the database. I'm communicating with the DB Admin regarding that now. If it -is- that, the error could use to be more clear. If it's -not- that, then I'll still be stuck at square one. Luis Lavena wrote: > On 2/26/07, C.jay Martin <[EMAIL PROTECTED]> wrote: >> >> Hi. >> >> I too am having the same symptoms: >> > > Mmm, not the same, let me ask you a few things: > > * What database backend are you using? > * Since the backend require native bindings (and also some dll). Are > these dlls (sqlite3.dll or libmysql.dll) available system wide? (try > putting them into windows\system32). > * if plain mongrel_rails start ... works, then you could try: > > mongrel_service console single "all the parameters you use with your > service": > > mongrel_service console single -e production -p 4001 -a 0.0.0.0 -l > "log/mongrel.log" -P "log/mongrel.pid" -c "C:/boxback" -t 0 -r > "public" -n 1024 > > And see if the application works or report errors. > > * In case it works, now you need to get if your environment (and the > permissions) are good to run the service. > > Please follow the instructions I posted to mongrel-users about similar > problems: > > http://rubyforge.org/pipermail/mongrel-users/2007-February/003004.html > > Using psexec -l cmd.exe you get a restricted console, try running > mongrel_rails in it and check the console for errors. > >> Finally, please note that this application was heavily tested and torn >> apart by a small QA group before the migration into >> IIS/lighttpd/mongrel. I haven't a clue what's wrong. >> > > Often is not a problem of test, but permissions of NTFS filesystem or > bugs in the Ruby VM and implementation under windows, who will guess > that? > > Anyway, a lot of these problems could be solved, like the one on the > list I make references previously. > > Hope could get a solution for the "missing log" of mongrel_service in > the following days. > > -- > 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 -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
