-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hemant kumar schrieb:
> Also, are you telling us that, even plain scheduled worker scheduled
> through config file are not being scheduled?
Right, with the background.rb-file cited above the schedules dont work.
The Server- and the Monitoring- Workers get automatically started when i start
backgroundrb. The create-methods are working without problems ... also if i call
the update or check_services methods from within the according create-method
everything works fine ... only the triggers dont fire ...
I updated all gems (sudo gem update --system), doublechecked if all necessary
dependencies are installed (chronic and packet) ... everything ok ...
I also tested a completly new worker with following settings:
backgroundrb.yml:
> ---
> :backgroundrb:
> :port: 11006
> :ip: 0.0.0.0
> ---
> :schedules:
> :hello_worker:
> :worker_method: say
> :trigger_args: 0 * * * * * *
hello_worker:
> class HelloWorker < BackgrounDRb::MetaWorker
> set_worker_name :hello_worker
> def create(args = nil)
> # this method is called, when worker is loaded for the first time
> logger.info("#{Time.now}. worker started")
> end
> def say(args = "hello")
> logger.info("#{args} again, its #{Time.now}")
> end
> end
in backgroundrb_11006.log:
> Thu Apr 03 18:19:35 +0200 2008. worker started
> hello_worker started
> Schedules for worker loaded
thats all ... so i think, the trigger don't gets fired. Do you have a clue,
where i might have an error, or is there an error in trunk?
Unfortunaly there is no error logged in any of the logfiles, so i can not hunt
it ;)
many thanks for helping
Andi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH9Q2xW5GYaw3DxvwRAiFvAJ0WALHwWy+sPClnSTHC5DIFfNE+HgCgkNDl
4gmpRcL392g2qQt7zh+osro=
=nfoE
-----END PGP SIGNATURE-----
_______________________________________________
Backgroundrb-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/backgroundrb-devel
