the cron_submitter is fragile. submitter_app is stable, lets' use it!
Is the plan to run via crontabber or with it's own cron wrapper script? Until we can run parallel jobs with crontabber it's probably not a good idea to run this one there, and the cron_submitter.sh script locking mechanism should be re-written (I just found that it fails silently if the lock file already exists, whereas the custom socorro lock/unlock bash functions record the PID and override the lock if the job isn't really running)
my idea is to not have be a cron at all. submitter_app can be a long running deamon that submits crashes at a specific rate. submitter_app can sample crashes from anywhere that it can read from a primary storage location and query Postgres.
(In reply to K Lars Lohn [:lars] [:klohn] from comment #3) > my idea is to not have be a cron at all. submitter_app can be a long > running deamon that submits crashes at a specific rate. submitter_app can > sample crashes from anywhere that it can read from a primary storage > location and query Postgres. Oh ok that WFM
this was done a couple weeks ago
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.