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

Couchdb user - fs-manager is taking 100% of the cpu. #1074

Closed
ransanjeev opened this Issue Dec 18, 2017 · 5 comments

Comments

Projects
None yet
5 participants
@ransanjeev

ransanjeev commented Dec 18, 2017

I am running a single instance of couchdb with node app as a proxy.
I have 5 user databases which are synced with pouchdb.
Cpu utilization for the machine was at 5-10%. It was working fine and infact, it's still working fine but now cpu usage is at 100%.

There is "fs-manager" process taking 98% of cpu and it's constantly running on 98 for the last 24hr.

I restarted the machine and run for 1-2 hrs fine but after that cpu usage again went to 100%.

Expected Behavior

Cpu usage should be lower.

Current Behavior

There is "fs-manager" process taking 98% of cpu and it's constantly running on 98 for the last 24hr.

Possible Solution

Looking for the solutions.

Steps to Reproduce (for bugs)

NA

Context

I haven't seen any issue with the database. I can load the couchdb-client fine and interact with the db.

Your Environment

  • Version used: couchdb 2.1.0
  • Browser Name and version:
  • Operating System and version (desktop or mobile): ubuntu 16, xenial.
@eiri

This comment has been minimized.

Member

eiri commented Dec 18, 2017

fs-manager is not part of CouchDB, it seems that you've been hacked with crypto mining software. Check out this mail-thread with a similar case.

@eiri eiri closed this Dec 18, 2017

@ransanjeev

This comment has been minimized.

ransanjeev commented Dec 19, 2017

Thanks @eiri I think I figured out the problem.

@femiashiru1

This comment has been minimized.

femiashiru1 commented Jan 24, 2018

hi @ransanjeev I have a similar problem and I'm curious to know how you figured it out

@garrensmith

This comment has been minimized.

Member

garrensmith commented Jan 24, 2018

@wohali

This comment has been minimized.

Member

wohali commented Jan 24, 2018

This is likely someone exploiting your server via a previously disclosed security violation:

https://blog.couchdb.org/2017/11/14/apache-couchdb-cve-2017-12635-and-cve-2017-12636/

When re-installing your server, be sure to use one of the patched versions of CouchDB: 2.1.1 or 1.7.1.

@apache apache locked as resolved and limited conversation to collaborators Jan 24, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.