Thanks dude. I finally found where it went wrong. However, I’m getting a
new exception after fixing it.
================================================================================
scheduler caught exception:
wrong number of arguments (1 for 2)
/root/dashtest/lib/graphite.rb:31:in points' /root/dashtest/jobs/graphite.rb:13:inblock in <top (required)>’
/var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in call' /var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:intrigger_block’
/var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:in block in trigger' /var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:incall’
/var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in
`block in trigger_job’
Yeah, I had it fixed right after I posted but still getting this
================================================================================
scheduler caught exception:
wrong number of arguments (0 for 2)
/root/dashtest/lib/graphite.rb:31:in points' /root/dashtest/lib/graphite.rb:43:inpoints’
/root/dashtest/jobs/graphite.rb:13:in block in <top (required)>' /var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:incall’
/var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in trigger_block' /var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:inblock in trigger’
/var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in call' /var/lib/gems/1.9.1/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:inblock in trigger_job’
I’m guessing it couldn’t have been that one.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.