Fixed
Project:
Nagios Monitoring
Version:
8.x-1.26
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Jun 2026 at 09:59 UTC
Updated:
22 Jun 2026 at 16:08 UTC
Jump to comment: Most recent
In Drupal 11 drush nagios, drush nagios requirements and Nagios HTTP status page do not show outdated modules and core.
Only drush nagios-updates shows outdated module names.
Works with Drupal 10.
Some requirements hooks in Drupal core were moved to runtime_requirements and moved from .install to hooks directory in Drupal 11
Nagios settings: Cron + Requirements + Show outdated module/theme name
No ignored modules
Call hook_runtime_requirements.
None.
None.
None.
Comments
Comment #2
sleitner commentedComment #3
sleitner commentedComment #4
sleitner commentedComment #5
sleitner commentedComment #6
sleitner commentedComment #7
gogowitsch commentedThanks for reporting this! I’ll look into the problem within the next 2 weeks.
Comment #8
gogowitsch commentedThe relevant Change Record is Runtime requirements checks should use a dedicated hook (introduced in Drupal 11.2). Three things broke:
hook_runtime_requirements()wasn't being called at all — fixed by adding it to the per-module loop incollectRequirements()_update_requirement_check()was removed from D11 — fixed by addingcomputeContribRequirement()with guard for D10 compatibility.RequirementSeverityis now an enum (not int) in D11 — fixed by normalizing to int infindMostSevereProblem()@sleitner: feel free to test and give feedback for my fix if you have the time. I’ll release a new version in about a week or once I have confirmation that the fix works for you.
Comment #11
sleitner commentedCore and module updates are now listed with
drush nagios-updates,drush nagios requirementsanddrush nagiosComment #12
sleitner commented@gogowitsch thank you for the new version