Background Job - setup error

rubyonrails-talk
1

Greetings!

I'm trying to use Ara's Background Job on Windows and running into a problem. I've installed it as a gem and added "require 'bj'" at the end of environment.rb. When I run 'bj setup' i'm getting a "FATAL -- : not opened for reading (IOError)" message. The line in the stack trace before/under it takes me into instance_method.rb where there's a call to Logger.new(*log). The documentation says bj will write to its own log file, but it doesn't say anything about needing to set that up manually.

Anybody got experience getting Background Job set up on Windows? Or just some experience with Background Job and any ideas re: how I might get it setup?

Thanks much and in advance for any assistance.

Best regards, Bill

2

same error here. Were you able to get around this?

Thanks,

Changpeng

3

Hi Changpeng,

same error here. Were you able to get around this?

Yes, I was. I removed the '*' from (*log).

Line 80 in bj/lib/main/program/instance_methods.rb now reads:

@logger = Logger.new(log)

Still don't understand what the '*' was for. If you know (or anyone else can jump in here), I'd be very pleased to hear.

Best regards, Bill

4

A timely thread, since I hit the same thing just now.

Still don't understand what the '*' was for. If you know (or anyone else can jump in here), I'd be very pleased to hear.

Would it be trying to expand an array? Dunno why, though.

I hit another problem shortly after: the automatic rake db:migrate step failed. Not a big deal, I ran it manually and commented out the line that failed.

Shortly after that, I got a job to submit and execute. Now to try in on a (Linux) server...

Mike

5

Yeah, I hit the same rake error, but that was easier to over come.

I have a different problem now. (should I change the subject line?)

I am using BJ together with Worklings and Workling_mailer (AsynchMail). I can see the job being added to the db and executed, with exit_status 10752. But the email is not sent out. The env field is NULL.

I don’t know where is the problem now? Is it BJ, or workling? or incorrect SMTP setup? If I comment out the “include AsynchMail” line, emails works.

Changpeng Zhao