search

Netflix-Skunkworks / Scumblr

Web framework that allows performing periodic syncs of data sources and performing analysis on the identified results
Apache License 2.0
2.64k stars 317 forks source link

Service falls over after a period of inactivity #136

Closed smoebot closed 7 years ago

smoebot commented 7 years ago

Hello,

Are there any reasons why scumblr will stop working after a period of inactivity? The web interface stops working and has to be restarted.

annbyl commented 7 years ago

What is the inactivity period for you? I think I've noticed similar issue.

smoebot commented 7 years ago

It's not long. I'll get on today and see if I can time it

ahoernecke commented 7 years ago

Hi guys,

Can you provide any other details on this? Are you running in development mode, which web server are you using, what OS are you on, are there any error messages, does anything get logged when you attempt to make requests after the app has become unresponsive, etc.?

ahoernecke commented 7 years ago

@smoebot,

Any update on this?

smoebot commented 7 years ago

@ahoernecke, sorry for the delay. Was on leave and forgot to get back.

Yes, I am running in development mode.
You won't like this - but I am using RedHat. I understand that it's not supported.

However, we had this issue on a previous install of Scumblr (prior to 2.0) that was running on Ubuntu. It was one of the reasons why we waited for Scumblr 2.0.

I don't get any error messages that I am aware of.

Is there any particular place I should looking for logs that might report the crash?

It may eventuate in my case that I'll have to just create scumblr as a virtual appliance, then get my infrastructure team to import it as an appliance and bypass the whole RedHat thing.

ahoernecke commented 7 years ago

Primarily I'd think in your development log that is under the scumblr root in /logs/development.log

And that is interesting, not really something I've encountered before except on my laptop if the database connection has been disrupted (i.e. I slept my laptop and woke it back up). Check the logs and let me know if you see anything.

All that said, running in development mode is not a good long term strategy regardless. There are a lot of other optimizations that come with switching over the production, so if you're considering using Scumblr for any real purpose, I'd recommend setting up in production mode.

ahoernecke commented 7 years ago

@espressobeanie, I got a notification you had added a comment that indicated you've seen the same problem on Ubuntu 16.04 but it's not showing up here. Can you please repost and include any logs you're seeing when this occurs?

As a side note, redis isn't a requirement for the Scumblr UI application. It's only used by sidekiq, which runs as a separate process. So redis going down should not affect the UI, but it would affect background jobs. If the postgres database goes down, this would impact the UI however.

smoebot commented 7 years ago

closed from my side of the fence - I don't have a solve for this, and am going to nuke our Red Hat install.