]> git.ipfire.org Git - thirdparty/systemd.git/blame - catalog/systemd.catalog.in
core: implement per unit journal rate limiting
[thirdparty/systemd.git] / catalog / systemd.catalog.in
CommitLineData
f0465e73 1# SPDX-License-Identifier: LGPL-2.1+
5d6a86d7
LP
2
3# Message catalog for systemd's own messages
4
5# The catalog format is documented on
f628d6d7 6# https://www.freedesktop.org/wiki/Software/systemd/catalog
5d6a86d7 7
ef7963b5
LP
8# For an explanation why we do all this, see https://xkcd.com/1024/
9
5d6a86d7 10-- f77379a8490b408bbe5f6940505a777b
2057124e 11Subject: The journal has been started
5d6a86d7 12Defined-By: systemd
4b930ded 13Support: %SUPPORT_URL%
5d6a86d7 14
2057124e 15The system journal process has started up, opened the journal
5d6a86d7
LP
16files for writing and is now ready to process requests.
17
18-- d93fb3c9c24d451a97cea615ce59c00b
2057124e 19Subject: The journal has been stopped
5d6a86d7 20Defined-By: systemd
4b930ded 21Support: %SUPPORT_URL%
5d6a86d7
LP
22
23The system journal process has shut down and closed all currently
24active journal files.
25
282c5c4e
ZJS
26-- ec387f577b844b8fa948f33cad9a75e6
27Subject: Disk space used by the journal
28Defined-By: systemd
4b930ded 29Support: %SUPPORT_URL%
282c5c4e
ZJS
30
31@JOURNAL_NAME@ (@JOURNAL_PATH@) is currently using @CURRENT_USE_PRETTY@.
32Maximum allowed usage is set to @MAX_USE_PRETTY@.
33Leaving at least @DISK_KEEP_FREE_PRETTY@ free (of currently available @DISK_AVAILABLE_PRETTY@ of disk space).
34Enforced usage limit is thus @LIMIT_PRETTY@, of which @AVAILABLE_PRETTY@ are still available.
35
36The limits controlling how much disk space is used by the journal may
37be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
38RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
39/etc/systemd/journald.conf. See journald.conf(5) for details.
40
5d6a86d7
LP
41-- a596d6fe7bfa4994828e72309e95d61e
42Subject: Messages from a service have been suppressed
43Defined-By: systemd
4b930ded 44Support: %SUPPORT_URL%
5d6a86d7 45Documentation: man:journald.conf(5)
5d6a86d7
LP
46
47A service has logged too many messages within a time period. Messages
48from the service have been dropped.
49
50Note that only messages from the service in question have been
51dropped, other services' messages are unaffected.
52
2057124e 53The limits controlling when messages are dropped may be configured
f0367da7 54with RateLimitIntervalSec= and RateLimitBurst= in
90fc172e
AZ
55/etc/systemd/journald.conf or LogRateLimitIntervalSec= and LogRateLimitBurst=
56in the unit file. See journald.conf(5) and systemd.exec(5) for details.
5d6a86d7
LP
57
58-- e9bf28e6e834481bb6f48f548ad13606
59Subject: Journal messages have been missed
60Defined-By: systemd
4b930ded 61Support: %SUPPORT_URL%
5d6a86d7
LP
62
63Kernel messages have been lost as the journal system has been unable
64to process them quickly enough.
65
d4205751
LP
66-- fc2e22bc6ee647b6b90729ab34a250b1
67Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
68Defined-By: systemd
4b930ded 69Support: %SUPPORT_URL%
5d6a86d7 70Documentation: man:core(5)
d4205751
LP
71
72Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
73
74This usually indicates a programming error in the crashing program and
5d6a86d7 75should be reported to its vendor as a bug.
d4205751 76
73a99163
ZJS
77-- 5aadd8e954dc4b1a8c954d63fd9e1137
78Subject: Core file was truncated to @SIZE_LIMIT@ bytes.
79Defined-By: systemd
80Support: %SUPPORT_URL%
81Documentation: man:coredump.conf(5)
82
83The process had more memory mapped than the configured maximum for processing
84and storage by systemd-coredump(8). Only the first @SIZE_LIMIT@ bytes were
85saved. This core might still be usable, but various tools like gdb(1) will warn
86about the file being truncated.
87
5d6a86d7
LP
88-- 8d45620c1a4348dbb17410da57c60c66
89Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
90Defined-By: systemd
4b930ded 91Support: %SUPPORT_URL%
f628d6d7 92Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
5d6a86d7
LP
93
94A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
95
96The leading process of the session is @LEADER@.
97
98-- 3354939424b4456d9802ca8333ed424a
2057124e 99Subject: Session @SESSION_ID@ has been terminated
5d6a86d7 100Defined-By: systemd
4b930ded 101Support: %SUPPORT_URL%
f628d6d7 102Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
5d6a86d7
LP
103
104A session with the ID @SESSION_ID@ has been terminated.
105
106-- fcbefc5da23d428093f97c82a9290f7b
107Subject: A new seat @SEAT_ID@ is now available
108Defined-By: systemd
4b930ded 109Support: %SUPPORT_URL%
f628d6d7 110Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
5d6a86d7
LP
111
112A new seat @SEAT_ID@ has been configured and is now available.
113
114-- e7852bfe46784ed0accde04bc864c2d5
2057124e 115Subject: Seat @SEAT_ID@ has now been removed
5d6a86d7 116Defined-By: systemd
4b930ded 117Support: %SUPPORT_URL%
f628d6d7 118Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
5d6a86d7 119
5190bbb2 120A seat @SEAT_ID@ has been removed and is no longer available.
d4205751
LP
121
122-- c7a787079b354eaaa9e77b371893cd27
123Subject: Time change
124Defined-By: systemd
4b930ded 125Support: %SUPPORT_URL%
d4205751 126
772c552f 127The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
d4205751
LP
128
129-- c7a787079b354eaaa9e77b371893cd27 de
130Subject: Zeitänderung
131Defined-By: systemd
4b930ded 132Support: %SUPPORT_URL%
d4205751 133
772c552f 134Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
d4205751
LP
135
136-- 45f82f4aef7a4bbf942ce861d1f20990
5d6a86d7 137Subject: Time zone change to @TIMEZONE@
d4205751 138Defined-By: systemd
4b930ded 139Support: %SUPPORT_URL%
d4205751 140
e9dd9f95 141The system timezone has been changed to @TIMEZONE@.
d4205751 142
5d6a86d7
LP
143-- b07a249cd024414a82dd00cd181378ff
144Subject: System start-up is now complete
d4205751 145Defined-By: systemd
4b930ded 146Support: %SUPPORT_URL%
d4205751 147
5d6a86d7 148All system services necessary queued for starting at boot have been
5a1d6cb1
ZJS
149started. Note that this does not mean that the machine is now idle as services
150might still be busy with completing start-up.
d4205751 151
772c552f 152Kernel start-up required @KERNEL_USEC@ microseconds.
5d6a86d7 153
772c552f 154Initial RAM disk start-up required @INITRD_USEC@ microseconds.
5d6a86d7 155
ba9904e9 156Userspace start-up required @USERSPACE_USEC@ microseconds.
5d6a86d7 157
5a1d6cb1
ZJS
158-- eed00a68ffd84e31882105fd973abdd1
159Subject: User manager start-up is now complete
160Defined-By: systemd
161Support: %SUPPORT_URL%
162
163The user manager instance for user @_UID@ has been started. All services queued
164for starting have been started. Note that other services might still be starting
165up or be started at any later time.
166
167Startup of the manager took @USERSPACE_USEC@ microseconds.
168
5d6a86d7
LP
169-- 6bbd95ee977941e497c48be27c254128
170Subject: System sleep state @SLEEP@ entered
d4205751 171Defined-By: systemd
4b930ded 172Support: %SUPPORT_URL%
d4205751 173
5d6a86d7 174The system has now entered the @SLEEP@ sleep state.
d4205751 175
5d6a86d7
LP
176-- 8811e6df2a8e40f58a94cea26f8ebf14
177Subject: System sleep state @SLEEP@ left
d4205751 178Defined-By: systemd
4b930ded 179Support: %SUPPORT_URL%
d4205751 180
5d6a86d7 181The system has now left the @SLEEP@ sleep state.
d4205751 182
5d6a86d7
LP
183-- 98268866d1d54a499c4e98921d93bc40
184Subject: System shutdown initiated
d4205751 185Defined-By: systemd
4b930ded 186Support: %SUPPORT_URL%
d4205751 187
c96528fa 188System shutdown has been initiated. The shutdown has now begun and
5d6a86d7 189all system services are terminated and all file systems unmounted.
d4205751 190
5d6a86d7 191-- 7d4958e842da4a758f6c1cdc7b36dcc5
2057124e 192Subject: Unit @UNIT@ has begun start-up
5d6a86d7 193Defined-By: systemd
4b930ded 194Support: %SUPPORT_URL%
d4205751 195
5d6a86d7
LP
196Unit @UNIT@ has begun starting up.
197
198-- 39f53479d3a045ac8e11786248231fbf
199Subject: Unit @UNIT@ has finished start-up
d4205751 200Defined-By: systemd
4b930ded 201Support: %SUPPORT_URL%
d4205751 202
5d6a86d7 203Unit @UNIT@ has finished starting up.
d4205751 204
65d51875 205The start-up result is @JOB_RESULT@.
d4205751 206
5d6a86d7
LP
207-- de5b426a63be47a7b6ac3eaac82e2f6f
208Subject: Unit @UNIT@ has begun shutting down
209Defined-By: systemd
4b930ded 210Support: %SUPPORT_URL%
5d6a86d7
LP
211
212Unit @UNIT@ has begun shutting down.
213
214-- 9d1aaa27d60140bd96365438aad20286
215Subject: Unit @UNIT@ has finished shutting down
216Defined-By: systemd
4b930ded 217Support: %SUPPORT_URL%
5d6a86d7
LP
218
219Unit @UNIT@ has finished shutting down.
220
221-- be02cf6855d2428ba40df7e9d022f03d
222Subject: Unit @UNIT@ has failed
223Defined-By: systemd
4b930ded 224Support: %SUPPORT_URL%
5d6a86d7
LP
225
226Unit @UNIT@ has failed.
227
65d51875 228The result is @JOB_RESULT@.
5d6a86d7
LP
229
230-- d34d037fff1847e6ae669a370e694725
2057124e 231Subject: Unit @UNIT@ has begun reloading its configuration
5d6a86d7 232Defined-By: systemd
4b930ded 233Support: %SUPPORT_URL%
5d6a86d7 234
2057124e 235Unit @UNIT@ has begun reloading its configuration
5d6a86d7
LP
236
237-- 7b05ebc668384222baa8881179cfda54
238Subject: Unit @UNIT@ has finished reloading its configuration
239Defined-By: systemd
4b930ded 240Support: %SUPPORT_URL%
5d6a86d7
LP
241
242Unit @UNIT@ has finished reloading its configuration
243
65d51875 244The result is @JOB_RESULT@.
5d6a86d7
LP
245
246-- 641257651c1b4ec9a8624d7a40a9e1e7
247Subject: Process @EXECUTABLE@ could not be executed
248Defined-By: systemd
4b930ded 249Support: %SUPPORT_URL%
5d6a86d7
LP
250
251The process @EXECUTABLE@ could not be executed and failed.
252
2057124e 253The error number returned by this process is @ERRNO@.
5d6a86d7
LP
254
255-- 0027229ca0644181a76c4e92458afa2e
5190bbb2 256Subject: One or more messages could not be forwarded to syslog
5d6a86d7 257Defined-By: systemd
4b930ded 258Support: %SUPPORT_URL%
5d6a86d7
LP
259
260One or more messages could not be forwarded to the syslog service
261running side-by-side with journald. This usually indicates that the
262syslog implementation has not been able to keep up with the speed of
263messages queued.
20ad4cfd
ZJS
264
265-- 1dee0369c7fc4736b7099b38ecb46ee7
266Subject: Mount point is not empty
267Defined-By: systemd
4b930ded 268Support: %SUPPORT_URL%
20ad4cfd
ZJS
269
270The directory @WHERE@ is specified as the mount point (second field in
271/etc/fstab or Where= field in systemd unit file) and is not empty.
272This does not interfere with mounting, but the pre-exisiting files in
273this directory become inaccessible. To see those over-mounted files,
274please manually mount the underlying file system to a secondary
275location.
9444b1f2
LP
276
277-- 24d8d4452573402496068381a6312df2
278Subject: A virtual machine or container has been started
279Defined-By: systemd
4b930ded 280Support: %SUPPORT_URL%
9444b1f2
LP
281
282The virtual machine @NAME@ with its leader PID @LEADER@ has been
283started is now ready to use.
284
285-- 58432bd3bace477cb514b56381b8a758
286Subject: A virtual machine or container has been terminated
287Defined-By: systemd
4b930ded 288Support: %SUPPORT_URL%
9444b1f2
LP
289
290The virtual machine @NAME@ with its leader PID @LEADER@ has been
291shut down.
f25f9e8d
LP
292
293-- 36db2dfa5a9045e1bd4af5f93e1cf057
294Subject: DNSSEC mode has been turned off, as server doesn't support it
295Defined-By: systemd
4b930ded 296Support: %SUPPORT_URL%
f25f9e8d
LP
297Documentation: man:systemd-resolved.service(8) resolved.conf(5)
298
299The resolver service (systemd-resolved.service) has detected that the
300configured DNS server does not support DNSSEC, and DNSSEC validation has been
301turned off as result.
302
303This event will take place if DNSSEC=allow-downgrade is configured in
304resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
305that using this mode permits DNSSEC downgrade attacks, as an attacker might be
306able turn off DNSSEC validation on the system by inserting DNS replies in the
307communication channel that result in a downgrade like this.
308
309This event might be indication that the DNS server is indeed incompatible with
310DNSSEC or that an attacker has successfully managed to stage such a downgrade
311attack.
312
313-- 1675d7f172174098b1108bf8c7dc8f5d
314Subject: DNSSEC validation failed
315Defined-By: systemd
4b930ded 316Support: %SUPPORT_URL%
f25f9e8d
LP
317Documentation: man:systemd-resolved.service(8)
318
319A DNS query or resource record set failed DNSSEC validation. This is usually
320indication that the communication channel used was tampered with.
321
322-- 4d4408cfd0d144859184d1e65d7c8a65
323Subject: A DNSSEC trust anchor has been revoked
324Defined-By: systemd
4b930ded 325Support: %SUPPORT_URL%
f25f9e8d
LP
326Documentation: man:systemd-resolved.service(8)
327
328A DNSSEC trust anchor has been revoked. A new trust anchor has to be
329configured, or the operating system needs to be updated, to provide an updated
330DNSSEC trust anchor.
173f30eb
LP
331
332-- 5eb03494b6584870a536b337290809b3
333Subject: Automatic restarting of a unit has been scheduled
334Defined-By: systemd
335Support: %SUPPORT_URL%
336
337Automatic restarting of the unit @UNIT@ has been scheduled, as the result for
338the configured Restart= setting for the unit.
339
340-- ae8f7b866b0347b9af31fe1c80b127c0
341Subject: Resources consumed by unit runtime
342Defined-By: systemd
343Support: %SUPPORT_URL%
344
345The unit @UNIT@ completed and consumed the indicated resources.
b2e7486c
ZJS
346
347-- 50876a9db00f4c40bde1a2ad381c3a1b
348Subject: The system is configured in a way that might cause problems
349Defined-By: systemd
350Support: %SUPPORT_URL%
351
352The following "tags" are possible:
353- "split-usr" — /usr is a separate file system and was not mounted when systemd
354 was booted
355- "cgroups-missing" — the kernel was compiled without cgroup support or access
356 to expected interface files is resticted
357- "var-run-bad" — /var/run is not a symlink to /run
358- "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with
359 NFS or user namespaces) is not 65534
360- "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with
361 NFS or user namespaces) is not 65534
362Current system is tagged as @TAINT@.