ABRT-SERVER(1)

Okay bestie, welcome to the ABRT Manual 🎀 and we're about to get into the absolutely iconic abrt-server 🦋

✨ NAME ✨

abrt-server is basically a Unix socket for ABRT 💜

✨ SYNOPSIS ✨

abrt-server [-u UID] [-spv[v]...]

✨ DESCRIPTION ✨

abrt-server gets run by the abrtd daemon whenever it needs to handle socket connections 💅 No cap, every application on the system can ask for a brand new problem directory just by following the communication protocol. We'll get to that in section PROTOCOL 🫶

✨ OPTIONS ✨

• -u UID — Use UID as the client uid 🎀
• -s — Log to the system log 📜
• -p — Add program names to the log 🌸
• -v — Get more detailed debugging info, the deep-dive mode 🔍

✨ PROTOCOL ✨

Initializing new dump 🦋

Connect to the UNIX domain socket /var/run/abrt.socket and you're in, bestie ✨

Providing data 💌

Here's the whole exchange when you're writing data to the socket:

-> "POST / HTTP/1.1\r\n"
-> "\r\n"
-> "type=string\0"
-> "reason=string\0"
-> "pid=number\0"
-> "executable=string\0"
-> "backtrace=string\0"
-> (close writing half of the socket)
<- "HTTP/1.1 201 \r\n"
<- "\r\n"

And here's what each field is allowed to be, lowkey important stuff 👀

• type=string\0 — string, maximum length 100 bytes
• reason=string\0 — string, maximum length 512 bytes
• pid=number\0 — number, 0 - PID_MAX (/proc/sys/kernel/pid_max)
• executable=string\0 — string, maximum length ~MAX_PATH
• backtrace=string\0 — string, maximum length 1 MB

Deleting problem directory 🧹

When you want a problem directory gone, this is the vibe:

-> "DELETE <directory_name> HTTP/1.1\r\n"
-> "\r\n"
-> (close writing half of the socket)
<- "HTTP/1.1 200 \r\n"
<- "\r\n"

✨ AUTHORS ✨

• ABRT team 💖

---

Bestie, this page belongs to abrt 2.17.9, dated 08/03/2026, and it's all about ABRT-SERVER(1) 🌈 Now go be iconic 💅✨