8.1 peinit.boot.downgraded

  • Event type: peinit.boot.downgraded
  • Defined in: peinit.evman
  • Tier: essential
  • Gating: none
  • Cardinality: one per finding that forced the downgrade, at most once a boot in all

A full boot was downgraded to safe mode: the machine is running a reduced service set. The services named are not marked failed, because safe mode never meant to start them, so this record is the only one that names them as the cause. Essential because it is rare and changes what the whole machine is running.

Formerly boot.safe_mode_downgrade.

8.1.1 Fields #

FieldTypePresenceMeaning
outcome.reasonstr.enumrequiredThe finding that forced the downgrade.

Values here (open set): critical-cycle · critical-boot-conflict.
graph.servicesstr[]when outcome.reason == critical-cycleThe services a graph finding involves.
object.service.namestrwhen outcome.reason == critical-boot-conflictThe name of the service the event is about, as its definition names it.
object.service.conflict.namestrwhen outcome.reason == critical-boot-conflictThe name of the service this one conflicts with, on a finding that two services both triggered at boot declare a conflict and so cannot both start.

Every record also carries the header fields of the envelope, which no payload repeats.

Generated from peinit.evman by pkm/tools/gen-events-book.py. Edit the fragment, not this page.

Edit this page