-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SensorCacheJob issue #166
Comments
This is the stop error I get from the process New Day: 2011-03-21T16:00:00-04:00 - 2011-03-21T16:30:00-04:00 Processing Batch 1 of 2... |
Have a look at bug #102. I had the same problem you did until I started running vineyard's SQL query from a cron job. The dashboard SensorCache job still crashes on me from time to time, so I had to come up with a cron job and shell script to restart it periodically. #!/bin/sh
. /usr/local/rvm/environments/default
exec $GEM_HOME/bin/rails r 'Snorby::Jobs.start_all!' I had to add this to lib/snorby/jobs.rb to get that to work: def self.start_all!
Snorby::Jobs.sensor_cache.destroy! if Snorby::Jobs.sensor_cache?
Delayed::Job.enqueue(Snorby::Jobs::SensorCacheJob.new(false), :priority => 1)
Snorby::Jobs.daily_cache.destroy! if Snorby::Jobs.daily_cache?
Delayed::Job.enqueue(Snorby::Jobs::DailyCacheJob.new(false), :priority => 1, :run_at => Time.now.tomorrow.beginning_of_day)
Snorby::Jobs.geoip_update.destroy! if Snorby::Jobs.geoip_update?
Delayed::Job.enqueue(Snorby::Jobs::GeoipUpdatedbJob.new(false), :priority => 1, :run_at => 1.week.from_now.beginning_of_day)
end I eagerly await a real bugfix! |
@therock11 I've had that problem a lot. Here is my solution: First, log on to mysql:
Type in your database password, then type (in this case, my database is "snorby"):
After you've done that, type in the following, line by line:
Then just exit the mysql prompt. Now it's time to go in to the Rails prompt:
Then type in the following:
After it's done, type in this:
If you didn't get any errors, your dashboard should now be working with graphs and everything. |
@therock11 @cventers @ermalm This issue should be resolved in Snorby 2.3.12 - we now ignore nil columns in the cache jobs. Let me know if this fixes the problem. |
I have been stuck unable to get past events from months ago in the sensor cache job. Is there a way to force it past the date and only read new events without deleting them from the snortdb? The following is how far back I am.
New Day: 2011-03-21T14:00:00-04:00 - 2011-03-21T14:30:00-04:00
Sensor 1: 20624 events found. Processing.
The text was updated successfully, but these errors were encountered: