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

Error messages and high cpu usage while scanning #41

Closed
bxkx opened this issue Oct 1, 2016 · 5 comments
Closed

Error messages and high cpu usage while scanning #41

bxkx opened this issue Oct 1, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@bxkx
Copy link

bxkx commented Oct 1, 2016

Hello, can anybody help me? Every time I apt-get upgrade and needrestart starts scanning it also shows me the following:

# Use of runtime loader module Module::Implementation detected.  Results of static scanning may be incomplete.
# Use of runtime loader module Module::Runtime detected.  Results of static scanning may be incomplete.

The CPU usage is kind of spiking when that happens. I'm on Debian 8.

@r-lindner
Copy link

I get the same messages when it tries to detect updates in the Thruk package in Debian 8. This breaks the nagios plugin mode.

@liske liske added the bug label Oct 31, 2016
@liske liske added this to the v2.10 milestone Oct 31, 2016
@liske liske self-assigned this Oct 31, 2016
@liske
Copy link
Owner

liske commented Oct 31, 2016

Could you please provide the output of needrestart -v when the problem does occur? We need to figure out the conditions triggering those messages and the increased CPU load.

@r-lindner
Copy link

Here are the logs for -v and -p: out.txt

@r-lindner
Copy link

oh by the way: I am using 2.9-1~bpo8+1 (jessie-backports).
In 2.8.1 the CPU-usage was much higher and it needed about 10 seconds after displaying the "# Use of runtime..." messages.
This has vanished in 2.9.1 - only the messages remain, which are bad in the Nagios-plugin output.

@liske
Copy link
Owner

liske commented Nov 3, 2016

Thanks for the logs!

  • Warnings: This is triggered by Module::ScanDeps for dynamic loaded modules. The warning messages seems to be hard coded - I need to check how to supress them...
  • CPU usage: There was a caching layer added in 2.9 (Debian Bug#826247) to stop parsing interpreter source files twice which improves the scan time if you have many interpreter instances running.

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

No branches or pull requests

3 participants