RTAS_ERRD(8)

πŸ“¦ version 2.7.10, in opensuse-leap 16.0

πŸ’… RTAS_ERRD β€” bestie's guide to the platform error daemon

okay so this is rtas_errd, and it lives in the ppc64-diag manual, section 8. she's a daemon, she's iconic, she handles platform errors and events, and honestly? she carries the whole pSeries vibe. let's get into it 🫢


✨ SYNOPSIS ✨

rtas_errd [-c|--config=CONFIG_FILE]
rtas_errd [-d|--debug]
rtas_errd [-d|--debug [[-f|--file=TEST_FILE]|[-s|--scenario=SCENARIO_FILE]]]
rtas_errd [-e|--epowfile=EPOW_FILE]
rtas_errd [-h|--help]
rtas_errd [-l|--logfile=LOG_FILE]
rtas_errd [-m|--msgsfile=MSG_FILE]
rtas_errd [-p|--platformfile=PLATFORM_FILE]
rtas_errd [-R|--nodrmgr]

like, that's the whole menu. every combo, right there. no cap πŸ’–


🌸 DESCRIPTION 🌸

rtas_errd is a daemon that runs on the pSeries platform and handles all the platform-generated events and errors. she's basically the main character of error handling, fr fr πŸ‘‘

the way she works: she gets platform-generated events via procfs, parses them, and then takes appropriate actions β€” things like extracting platform dumps, calling drmgr for hotplug events, etc. she also provides automated responses for urgent events, like environmental conditions and predictive failures. very on top of things, very demure πŸ’…

and because she's a generous queen, she also converts the events into human-readable format and logs them to the servicelog database, so the system administrator can view these events and take appropriate actions. she's not just doing the work, she's making it readable. periodt ✨


πŸŽ€ OPTIONS πŸŽ€

  • -c, --config=CONFIG_FILE β€” path to the config file. default is /etc/ppc64-diag/ppc64-diag.config. she needs her settings, okay? πŸ“
  • -d, --debug β€” don't daemonize, used for debugging. so she stays right there in the foreground with you. lowkey clingy but we love her for it πŸ’œ
  • -f, --file=TEST_FILE β€” the test file contains the sample PEL event that rtas_errd daemon can process. your little test-run bestie 🧚
  • -e, --epowfile=EPOW_FILE β€” path to the EPOW status file (default: /var/log/epow_status). by default we use this path to store EPOW status, which is used by the "rc.powerfail" script to check the EPOW status. iykyk ⚑
  • -h, --help β€” help (this message). hi bestie, here's the menu πŸ’–
  • -l, --logfile=FILE β€” path to the rtas_errd debug log file (default: /var/log/rtas_errd.log). by default we log events to this file. her diary, basically πŸ“”
  • -m, --msgsfile=MSG_FILE β€” path to syslog. used to read any PEL events that exist in syslog (it happens when we enable the RTAS debug flag in the kernel). so she goes digging through syslog for the lore πŸ”
  • -p, --platformfile=PLATFORM_FILE β€” path to the platform log (default: /var/log/platform). by default we log hex output with some description to this file. hex and vibes, honestly πŸ¦‹
  • -s, --scenario=SCENARIO_FILE β€” the scenario file contains a list of files that contain PEL logs. it's giving playlist of errors 🌈
  • -R, --nodrmgr β€” no drmgr. do not call the drmgr command to perform hotplug operations. sometimes you just don't want her to call him, and that's valid πŸ™ˆ

⚠️ quick vibe check: -d is the don't daemonize flag, so if you're expecting a nice background daemon, she's gonna be standing right next to you instead. debugging mode only, bestie πŸ’€

πŸ‘‘ sign-off πŸ‘‘

that's the whole page, bestie β€” Linux, dated 2020-05-09, straight out of ppc64-diag. go forth and let the daemon handle it, she's got this πŸ’–πŸŽ€βœ¨

πŸ“¦ where this page comes from