SAPStartSrv-alert-timeout(8)

📦 version 0.9.6+git.1791548114.2a86b96, in opensuse-leap 16.0

💅 SAPStartSrv-alert-timeout(8) — the alert agent for cluster resources timeout alerts

okay bestie, so this is a page from the SAPStartSrv manual set, and it's about a lil alert agent that goes off when your Linux cluster resources time out. she's a technology preview, she's dramatic, she's useful. let's get into it 🎀

✨ NAME ✨

SAPStartSrv-alert-timeout — the alert agent that handles timeout alerts for cluster resources. yes that's her whole job and she does it gorgeously 💅

🌸 DESCRIPTION 🌸

So SAPStartSrv-alert-timeout is what you use to react when your Linux cluster resources throw timeout alerts. that's the vibe.

Here's the lore: the Linux cluster gives you an interface to kick off external actions whenever a cluster event happens (that's an alert). and then the cluster literally calls an external program — the alert agent — to handle that alert. main character energy, honestly.

When a Linux cluster resource agent runs into resources timeout, the cluster can call SAPStartSrv-alert-timeout on each active cluster node. the main purpose? collecting data in case of resource agent timeouts. that's it, that's the gig 🫶

also peep the manual pages SAPStartSrv-helper(8) and ocf_heartbeat_SAPInstance(7) — they're part of this universe too.

⚠️ real talk: SAPStartSrv-alert-timeout is a technology preview. keep that in mind, bestie.

🦋 SUPPORTED PARAMETERS 🦋

  • timeout — if the alert agent doesn't finish within this amount of time, it gets terminated. no negotiating. it's optional, default is "30s", minimum is "30s", and an example looks like "meta timeout=30s". ⏰
  • alert_sid — the SAP SID of the instance to handle. might get used by your custom helper scripts. optional, default "EN2", example "attributes alert_sid=ADA". 🍓
  • alert_ino — the SAP instance number of the instance to handle. might also get used by custom helper scripts. optional, default "00", example "attributes alert_ino=22". 🔢
  • alert_cmd — the command to call. this is your hook for naming a custom helper script. SAPStartSrv-alert-timeout calls the command like this:
(sudo "$alert_cmd" "$alert_subcmd" "$inst_name" "$alert_sid" "$alert_ino" 2>&1)

optional, default "/usr/bin/SAPStartSrv-helper", example "alert_cmd=/usr/local/bin/dumpstack". 🔥

  • alert_subcmd — the subcommand to call SAPStartSrv-helper with. optional, default "log", example "alert_subcmd=log+stack". and yeah, go read SAPStartSrv-helper(8) for the full story. 📖

💀 RETURN CODES 💀

  • 0 — successful program execution. slay ✨
  • >0 — usage, syntax or execution errors. 😭

and on top of that, log entries get written, which you can scan with a pattern like "SAPStartSrv-alert-timeout". handy iykyk.

🌈 EXAMPLES 🌈

the simple one: resource timeout alert agent config

you add these lines to the cluster´s CIB:

alert resources-1 "/usr/bin/SAPStartSrv-alert-timeout" \
 select resources

the other simple one: config via crm

alternate way to configure the alert agent:

# crm configure alert resources-1 \
 "/usr/bin/SAPStartSrv-alert-timeout" \
 select resources

the advanced one 👑

a custom script /usr/local/bin/dumpstack is used, SID is ADA, instance number 00.

alert resources-1 "/usr/bin/SAPStartSrv-alert-timeout" \
 select resources \
 attributes alert_sid=ADA alert_ino=00 \
 alert_cmd=/usr/local/bin/dumpstack

peeking at all your configured alert agents 👀

# crm configure show type:alert

peeking at the alert agent messages 💬

# grep SAPStartSrv-alert-timeout /var/log/messages

the sudo permissions example, in /etc/sudoers.d/SAPStartSrv

also check the manual pages sudoers(5) and SAPStartSrv-helper(8) while you're here.

# SAPStartSrv-alert-timeout needs
hacluster ALL=(ALL) NOPASSWD: /usr/bin/SAPStartSrv-helper *

🧚 FILES 🧚

  • /usr/bin/SAPStartSrv-alert-timeout — the alert agent herself 💖
  • /usr/bin/SAPStartSrv-helper — the default agent helper 🛠️
  • /etc/sudoers.d/ — the directory for sudoers config files 📂

👑 REQUIREMENTS 👑

  • SAPStartSrv-alert-timeout should be activated only when support asks for it. not just for funsies, bestie.
  • No other alert agent should be configured for the resources alert.
  • User hacluster is a member of group haclient. both are defined locally on all cluster nodes.
  • User hacluster needs password-less sudo permission on "/usr/bin/SAPStartSrv-helper". if a custom script is used, respective permissions might be needed too. 🔐
  • The customer is responsible for any custom script called by the alert agent. any custom script should return within the alert agent timeout — no lingering, no loitering.
  • To allow the SAPStartSrv-helper command "stack", you need gdb. 🐛
  • To allow the SAPStartSrv-helper command "log", you need ClusterTool2 3.1.4 or newer. 📦
  • The alert agent runtime almost completely depends on call-outs to OS and Linux cluster. so the alert agent timeout should be 30s at least. fr fr.

🙈 BUGS 🙈

if anything goes sideways, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. that's the move 💜

⭐ SEE ALSO ⭐

ocf_suse_SAPStartSrv(7) , ocf_heartbeat_SAPInstance(7) , SAPStartSrv-helper(8) , crm(8), sudoers(5) , https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Administration/singlehtml/#alert-agents

💖 AUTHORS 💖

F.Herschel, L.Pinne.

(c) 2026 SUSE LLC

SAPStartSrv-alert-timeout comes with ABSOLUTELY NO WARRANTY. For details see the GNU General Public License at http://www.gnu.org/licenses/gpl.html

and that's the whole page, bestie 🫶 this was SAPStartSrv-alert-timeout(8) from the SAPStartSrv manual, dated 16 Aug 2026. go forth and collect your timeout data, icon ✨💅

📦 where this page comes from