Skip to content
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

rf-hub charshes #71

Open
aaltat opened this issue Sep 29, 2016 · 3 comments
Open

rf-hub charshes #71

aaltat opened this issue Sep 29, 2016 · 3 comments

Comments

@aaltat
Copy link

aaltat commented Sep 29, 2016

I have quite large amount of keyword, like in thousands and amount is growing. Lately the rf-hub has been starting to hang/crash randomly. I get error ERR_CONNECTION_REFUSED with when using chrome.

I can not see error in the output which the rf-hub produces nor I can find any obvious problems in the Windows machine where the service is running. I am wondering where I could start debugging the problem more deeply to find out the reason for the server crash?

@aaltat
Copy link
Author

aaltat commented Sep 29, 2016

And did forget to post the environment details: Windows 7 (64bit), Python 2.7 and using rf-hub 0.9 version.

@boakley
Copy link
Owner

boakley commented Sep 29, 2016

Thousands of keywords, or thousands of resource or library files? Are you
sure rfhub is "crashing"? Connection refused could just mean that it's
temporarily too busy to service a request. Does the rfhub process actually
die?

On Thu, Sep 29, 2016 at 2:29 AM, Tatu Aalto [email protected]
wrote:

And did forget to post the environment details: Windows 7 (64bit), Python
2.7 and using rf-hub 0.9 version.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#71 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABEmYpjcwXGZ3kpp4N1zdtsWhyKtnW4hks5qu2i8gaJpZM4KJpy6
.

@aaltat
Copy link
Author

aaltat commented Oct 17, 2016

Sorry that it did take so long to respond to this but other priorities. The process is actually running in the server side, but it looks like it is hanging to something and can not serve any new request. The console does not show any resent activity and time stamp on the console is several days old and new events are not flushed to the console. The process is idling, it does consume any disk I/O or hardly (0 - 1%) any CPU.

The problem is resolved if I reboot the service and for a while it works fine but after some while it seems to hang again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants