]>
Commit | Line | Data |
---|---|---|
db9ecf05 | 1 | # SPDX-License-Identifier: LGPL-2.1-or-later |
5d6a86d7 LP |
2 | |
3 | # Message catalog for systemd's own messages | |
4 | ||
5 | # The catalog format is documented on | |
03d35b5d | 6 | # https://systemd.io/CATALOG |
5d6a86d7 | 7 | |
ef7963b5 LP |
8 | # For an explanation why we do all this, see https://xkcd.com/1024/ |
9 | ||
5d6a86d7 | 10 | -- f77379a8490b408bbe5f6940505a777b |
2057124e | 11 | Subject: The journal has been started |
5d6a86d7 | 12 | Defined-By: systemd |
4b930ded | 13 | Support: %SUPPORT_URL% |
5d6a86d7 | 14 | |
2057124e | 15 | The system journal process has started up, opened the journal |
5d6a86d7 LP |
16 | files for writing and is now ready to process requests. |
17 | ||
18 | -- d93fb3c9c24d451a97cea615ce59c00b | |
2057124e | 19 | Subject: The journal has been stopped |
5d6a86d7 | 20 | Defined-By: systemd |
4b930ded | 21 | Support: %SUPPORT_URL% |
5d6a86d7 LP |
22 | |
23 | The system journal process has shut down and closed all currently | |
24 | active journal files. | |
25 | ||
282c5c4e ZJS |
26 | -- ec387f577b844b8fa948f33cad9a75e6 |
27 | Subject: Disk space used by the journal | |
28 | Defined-By: systemd | |
4b930ded | 29 | Support: %SUPPORT_URL% |
282c5c4e ZJS |
30 | |
31 | @JOURNAL_NAME@ (@JOURNAL_PATH@) is currently using @CURRENT_USE_PRETTY@. | |
32 | Maximum allowed usage is set to @MAX_USE_PRETTY@. | |
33 | Leaving at least @DISK_KEEP_FREE_PRETTY@ free (of currently available @DISK_AVAILABLE_PRETTY@ of disk space). | |
34 | Enforced usage limit is thus @LIMIT_PRETTY@, of which @AVAILABLE_PRETTY@ are still available. | |
35 | ||
36 | The limits controlling how much disk space is used by the journal may | |
37 | be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=, | |
38 | RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in | |
39 | /etc/systemd/journald.conf. See journald.conf(5) for details. | |
40 | ||
5d6a86d7 LP |
41 | -- a596d6fe7bfa4994828e72309e95d61e |
42 | Subject: Messages from a service have been suppressed | |
43 | Defined-By: systemd | |
4b930ded | 44 | Support: %SUPPORT_URL% |
5d6a86d7 | 45 | Documentation: man:journald.conf(5) |
5d6a86d7 LP |
46 | |
47 | A service has logged too many messages within a time period. Messages | |
48 | from the service have been dropped. | |
49 | ||
50 | Note that only messages from the service in question have been | |
51 | dropped, other services' messages are unaffected. | |
52 | ||
2057124e | 53 | The limits controlling when messages are dropped may be configured |
f0367da7 | 54 | with RateLimitIntervalSec= and RateLimitBurst= in |
90fc172e AZ |
55 | /etc/systemd/journald.conf or LogRateLimitIntervalSec= and LogRateLimitBurst= |
56 | in the unit file. See journald.conf(5) and systemd.exec(5) for details. | |
5d6a86d7 LP |
57 | |
58 | -- e9bf28e6e834481bb6f48f548ad13606 | |
59 | Subject: Journal messages have been missed | |
60 | Defined-By: systemd | |
4b930ded | 61 | Support: %SUPPORT_URL% |
5d6a86d7 LP |
62 | |
63 | Kernel messages have been lost as the journal system has been unable | |
64 | to process them quickly enough. | |
65 | ||
d4205751 LP |
66 | -- fc2e22bc6ee647b6b90729ab34a250b1 |
67 | Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core | |
68 | Defined-By: systemd | |
4b930ded | 69 | Support: %SUPPORT_URL% |
5d6a86d7 | 70 | Documentation: man:core(5) |
d4205751 LP |
71 | |
72 | Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core. | |
73 | ||
74 | This usually indicates a programming error in the crashing program and | |
5d6a86d7 | 75 | should be reported to its vendor as a bug. |
d4205751 | 76 | |
73a99163 ZJS |
77 | -- 5aadd8e954dc4b1a8c954d63fd9e1137 |
78 | Subject: Core file was truncated to @SIZE_LIMIT@ bytes. | |
79 | Defined-By: systemd | |
80 | Support: %SUPPORT_URL% | |
81 | Documentation: man:coredump.conf(5) | |
82 | ||
83 | The process had more memory mapped than the configured maximum for processing | |
84 | and storage by systemd-coredump(8). Only the first @SIZE_LIMIT@ bytes were | |
85 | saved. This core might still be usable, but various tools like gdb(1) will warn | |
86 | about the file being truncated. | |
87 | ||
5d6a86d7 LP |
88 | -- 8d45620c1a4348dbb17410da57c60c66 |
89 | Subject: A new session @SESSION_ID@ has been created for user @USER_ID@ | |
90 | Defined-By: systemd | |
4b930ded | 91 | Support: %SUPPORT_URL% |
515736d0 | 92 | Documentation: sd-login(3) |
5d6a86d7 LP |
93 | |
94 | A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@. | |
95 | ||
96 | The leading process of the session is @LEADER@. | |
97 | ||
98 | -- 3354939424b4456d9802ca8333ed424a | |
2057124e | 99 | Subject: Session @SESSION_ID@ has been terminated |
5d6a86d7 | 100 | Defined-By: systemd |
4b930ded | 101 | Support: %SUPPORT_URL% |
515736d0 | 102 | Documentation: sd-login(3) |
5d6a86d7 LP |
103 | |
104 | A session with the ID @SESSION_ID@ has been terminated. | |
105 | ||
106 | -- fcbefc5da23d428093f97c82a9290f7b | |
107 | Subject: A new seat @SEAT_ID@ is now available | |
108 | Defined-By: systemd | |
4b930ded | 109 | Support: %SUPPORT_URL% |
515736d0 | 110 | Documentation: sd-login(3) |
5d6a86d7 LP |
111 | |
112 | A new seat @SEAT_ID@ has been configured and is now available. | |
113 | ||
114 | -- e7852bfe46784ed0accde04bc864c2d5 | |
2057124e | 115 | Subject: Seat @SEAT_ID@ has now been removed |
5d6a86d7 | 116 | Defined-By: systemd |
4b930ded | 117 | Support: %SUPPORT_URL% |
515736d0 | 118 | Documentation: sd-login(3) |
5d6a86d7 | 119 | |
5190bbb2 | 120 | A seat @SEAT_ID@ has been removed and is no longer available. |
d4205751 | 121 | |
952b26c7 | 122 | -- b2bcbaf5edf948e093ce50bbea0e81ec |
123 | Subject: The Secure Attention Key (SAK) was pressed on @SEAT_ID@ | |
124 | Defined-By: systemd | |
125 | Support: %SUPPORT_URL% | |
126 | Documentation: man:systemd-logind.service(8) | |
127 | ||
128 | The Secure Attention Key (SAK), Ctrl+Alt+Shift+Esc, was pressed on @SEAT_ID@. | |
129 | ||
130 | Pressing the SAK indicates an explicit request by the user for the system to display a secure login dialog or greeter. | |
131 | ||
d4205751 LP |
132 | -- c7a787079b354eaaa9e77b371893cd27 |
133 | Subject: Time change | |
134 | Defined-By: systemd | |
4b930ded | 135 | Support: %SUPPORT_URL% |
d4205751 | 136 | |
772c552f | 137 | The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970. |
d4205751 | 138 | |
d4205751 | 139 | -- 45f82f4aef7a4bbf942ce861d1f20990 |
5d6a86d7 | 140 | Subject: Time zone change to @TIMEZONE@ |
d4205751 | 141 | Defined-By: systemd |
4b930ded | 142 | Support: %SUPPORT_URL% |
d4205751 | 143 | |
e9dd9f95 | 144 | The system timezone has been changed to @TIMEZONE@. |
d4205751 | 145 | |
5d6a86d7 LP |
146 | -- b07a249cd024414a82dd00cd181378ff |
147 | Subject: System start-up is now complete | |
d4205751 | 148 | Defined-By: systemd |
4b930ded | 149 | Support: %SUPPORT_URL% |
d4205751 | 150 | |
5d6a86d7 | 151 | All system services necessary queued for starting at boot have been |
5a1d6cb1 ZJS |
152 | started. Note that this does not mean that the machine is now idle as services |
153 | might still be busy with completing start-up. | |
d4205751 | 154 | |
772c552f | 155 | Kernel start-up required @KERNEL_USEC@ microseconds. |
5d6a86d7 | 156 | |
1485925d | 157 | Initrd start-up required @INITRD_USEC@ microseconds. |
5d6a86d7 | 158 | |
ba9904e9 | 159 | Userspace start-up required @USERSPACE_USEC@ microseconds. |
5d6a86d7 | 160 | |
5a1d6cb1 ZJS |
161 | -- eed00a68ffd84e31882105fd973abdd1 |
162 | Subject: User manager start-up is now complete | |
163 | Defined-By: systemd | |
164 | Support: %SUPPORT_URL% | |
165 | ||
166 | The user manager instance for user @_UID@ has been started. All services queued | |
167 | for starting have been started. Note that other services might still be starting | |
168 | up or be started at any later time. | |
169 | ||
170 | Startup of the manager took @USERSPACE_USEC@ microseconds. | |
171 | ||
5d6a86d7 LP |
172 | -- 6bbd95ee977941e497c48be27c254128 |
173 | Subject: System sleep state @SLEEP@ entered | |
d4205751 | 174 | Defined-By: systemd |
4b930ded | 175 | Support: %SUPPORT_URL% |
d4205751 | 176 | |
5d6a86d7 | 177 | The system has now entered the @SLEEP@ sleep state. |
d4205751 | 178 | |
5d6a86d7 LP |
179 | -- 8811e6df2a8e40f58a94cea26f8ebf14 |
180 | Subject: System sleep state @SLEEP@ left | |
d4205751 | 181 | Defined-By: systemd |
4b930ded | 182 | Support: %SUPPORT_URL% |
d4205751 | 183 | |
5d6a86d7 | 184 | The system has now left the @SLEEP@ sleep state. |
d4205751 | 185 | |
5d6a86d7 LP |
186 | -- 98268866d1d54a499c4e98921d93bc40 |
187 | Subject: System shutdown initiated | |
d4205751 | 188 | Defined-By: systemd |
4b930ded | 189 | Support: %SUPPORT_URL% |
d4205751 | 190 | |
c96528fa | 191 | System shutdown has been initiated. The shutdown has now begun and |
5d6a86d7 | 192 | all system services are terminated and all file systems unmounted. |
d4205751 | 193 | |
836fb00f YA |
194 | -- c14aaf76ec284a5fa1f105f88dfb061c |
195 | Subject: System factory reset initiated | |
196 | Defined-By: systemd | |
197 | Support: %SUPPORT_URL% | |
198 | ||
199 | System factory reset has been initiated. The precise operation this | |
200 | executes is implementation-defined, but typically has the effect of | |
201 | reverting the system's state and configuration to vendor defaults. | |
202 | ||
1dc604d8 MY |
203 | -- d9ec5e95e4b646aaaea2fd05214edbda |
204 | Subject: Container init crashed | |
ad5db940 OJ |
205 | Defined-By: systemd |
206 | Support: %SUPPORT_URL% | |
207 | ||
1dc604d8 | 208 | Container init has crashed and exited. |
ad5db940 OJ |
209 | The details of the crash can be obtained from the container manager. |
210 | ||
ad5db940 | 211 | -- 3ed0163e868a4417ab8b9e210407a96c |
1dc604d8 | 212 | Subject: System reboot failed after crash |
ad5db940 OJ |
213 | Defined-By: systemd |
214 | Support: %SUPPORT_URL% | |
215 | ||
216 | Reboot has failed when systemd attempted to reboot after a crash. | |
217 | ||
218 | -- 645c735537634ae0a32b15a7c6cba7d4 | |
8a5aba5b | 219 | Subject: Init execution froze |
ad5db940 OJ |
220 | Defined-By: systemd |
221 | Support: %SUPPORT_URL% | |
222 | ||
8a5aba5b | 223 | Systemd froze execution after fatal error. |
ad5db940 OJ |
224 | |
225 | -- 5addb3a06a734d3396b794bf98fb2d01 | |
1dc604d8 | 226 | Subject: Init received fatal signal while coredump is disabled |
ad5db940 OJ |
227 | Defined-By: systemd |
228 | Support: %SUPPORT_URL% | |
229 | ||
1dc604d8 | 230 | Systemd received fatal signal, but core dumping is disabled. |
ad5db940 OJ |
231 | |
232 | -- 5c9e98de4ab94c6a9d04d0ad793bd903 | |
1dc604d8 | 233 | Subject: Init received fatal signal but fork failed |
ad5db940 OJ |
234 | Defined-By: systemd |
235 | Support: %SUPPORT_URL% | |
236 | ||
1dc604d8 MY |
237 | Systemd received fatal signal, but failed to fork to dump the core. |
238 | ||
ad5db940 | 239 | -- 5e6f1f5e4db64a0eaee3368249d20b94 |
1dc604d8 | 240 | Subject: Init received fatal signal from unknown sender process |
ad5db940 OJ |
241 | Defined-By: systemd |
242 | Support: %SUPPORT_URL% | |
243 | ||
244 | -- 83f84b35ee264f74a3896a9717af34cb | |
1dc604d8 | 245 | Subject: Init received fatal signal from our own process |
ad5db940 OJ |
246 | Defined-By: systemd |
247 | Support: %SUPPORT_URL% | |
248 | ||
249 | -- 3a73a98baf5b4b199929e3226c0be783 | |
1dc604d8 | 250 | Subject: Init received fatal signal from other process |
ad5db940 OJ |
251 | Defined-By: systemd |
252 | Support: %SUPPORT_URL% | |
253 | ||
254 | -- 2ed18d4f78ca47f0a9bc25271c26adb4 | |
1dc604d8 | 255 | Subject: Init received fatal signal but waitpid() failed |
ad5db940 OJ |
256 | Defined-By: systemd |
257 | Support: %SUPPORT_URL% | |
258 | ||
1dc604d8 MY |
259 | Systemd received fatal signal, but waitpid() failed when |
260 | trying to dump the core. | |
261 | ||
ad5db940 | 262 | -- 56b1cd96f24246c5b607666fda952356 |
1dc604d8 | 263 | Subject: Init received fatal signal but coredump failed |
ad5db940 OJ |
264 | Defined-By: systemd |
265 | Support: %SUPPORT_URL% | |
266 | ||
267 | -- 4ac7566d4d7548f4981f629a28f0f829 | |
1dc604d8 | 268 | Subject: Init received fatal signal and dumped core |
ad5db940 OJ |
269 | Defined-By: systemd |
270 | Support: %SUPPORT_URL% | |
271 | ||
272 | -- 38e8b1e039ad469291b18b44c553a5b7 | |
1dc604d8 | 273 | Subject: Init failed to fork crash shell |
ad5db940 OJ |
274 | Defined-By: systemd |
275 | Support: %SUPPORT_URL% | |
276 | ||
1dc604d8 MY |
277 | Systemd crashed and failed to fork off crash shell. |
278 | ||
ad5db940 | 279 | -- 872729b47dbe473eb768ccecd477beda |
1dc604d8 | 280 | Subject: Crash shell failed to execute |
ad5db940 OJ |
281 | Defined-By: systemd |
282 | Support: %SUPPORT_URL% | |
283 | ||
1dc604d8 MY |
284 | Systemd crashed and failed to spawn crash shell. |
285 | ||
ad5db940 | 286 | -- 658a67adc1c940b3b3316e7e8628834a |
1dc604d8 | 287 | Subject: Manager failed to load SELinux policy |
ad5db940 OJ |
288 | Defined-By: systemd |
289 | Support: %SUPPORT_URL% | |
290 | ||
291 | -- e6f456bd92004d9580160b2207555186 | |
1dc604d8 | 292 | Subject: Battery level critically low, waiting for charger |
ad5db940 OJ |
293 | Defined-By: systemd |
294 | Support: %SUPPORT_URL% | |
295 | ||
1dc604d8 MY |
296 | Battery level is critically low. Please connect your charger |
297 | or the system will power off in 10 seconds. | |
298 | ||
ad5db940 | 299 | -- 267437d33fdd41099ad76221cc24a335 |
1dc604d8 | 300 | Subject: Battery level critically low, powering off |
ad5db940 OJ |
301 | Defined-By: systemd |
302 | Support: %SUPPORT_URL% | |
303 | ||
304 | -- 79e05b67bc4545d1922fe47107ee60c5 | |
1dc604d8 | 305 | Subject: Manager failed to run main loop |
ad5db940 OJ |
306 | Defined-By: systemd |
307 | Support: %SUPPORT_URL% | |
308 | ||
309 | -- dbb136b10ef4457ba47a795d62f108c9 | |
1dc604d8 | 310 | Subject: User manager failed to determine $XDG_RUNTIME_DIR path |
ad5db940 OJ |
311 | Defined-By: systemd |
312 | Support: %SUPPORT_URL% | |
313 | ||
314 | -- ed158c2df8884fa584eead2d902c1032 | |
1dc604d8 | 315 | Subject: Init failed to drop capability bounding set of usermode helpers |
ad5db940 OJ |
316 | Defined-By: systemd |
317 | Support: %SUPPORT_URL% | |
318 | ||
319 | -- 42695b500df048298bee37159caa9f2e | |
1dc604d8 | 320 | Subject: Init failed to drop capability bounding set |
ad5db940 OJ |
321 | Defined-By: systemd |
322 | Support: %SUPPORT_URL% | |
323 | ||
324 | -- bfc2430724ab44499735b4f94cca9295 | |
1dc604d8 | 325 | Subject: User manager failed to disable new privileges |
ad5db940 OJ |
326 | Defined-By: systemd |
327 | Support: %SUPPORT_URL% | |
328 | ||
329 | -- 59288af523be43a28d494e41e26e4510 | |
1dc604d8 | 330 | Subject: Manager failed to start default target |
ad5db940 OJ |
331 | Defined-By: systemd |
332 | Support: %SUPPORT_URL% | |
333 | ||
334 | -- 689b4fcc97b4486ea5da92db69c9e314 | |
1dc604d8 | 335 | Subject: Manager failed to isolate default target |
ad5db940 OJ |
336 | Defined-By: systemd |
337 | Support: %SUPPORT_URL% | |
338 | ||
339 | -- 5ed836f1766f4a8a9fc5da45aae23b29 | |
1dc604d8 | 340 | Subject: Manager failed to collect passed file descriptors |
ad5db940 OJ |
341 | Defined-By: systemd |
342 | Support: %SUPPORT_URL% | |
343 | ||
344 | -- 6a40fbfbd2ba4b8db02fb40c9cd090d7 | |
1dc604d8 | 345 | Subject: Init failed to fix up environment variables |
ad5db940 OJ |
346 | Defined-By: systemd |
347 | Support: %SUPPORT_URL% | |
348 | ||
349 | -- 0e54470984ac419689743d957a119e2e | |
350 | Subject: Failed to allocate manager object | |
351 | Defined-By: systemd | |
352 | Support: %SUPPORT_URL% | |
353 | ||
354 | -- d67fa9f847aa4b048a2ae33535331adb | |
1dc604d8 | 355 | Subject: Manager failed to write Smack onlycap list |
ad5db940 OJ |
356 | Defined-By: systemd |
357 | Support: %SUPPORT_URL% | |
358 | ||
359 | -- af55a6f75b544431b72649f36ff6d62c | |
360 | Subject: Critical error while doing system shutdown | |
361 | Defined-By: systemd | |
362 | Support: %SUPPORT_URL% | |
363 | ||
364 | -- d18e0339efb24a068d9c1060221048c2 | |
1dc604d8 | 365 | Subject: Init failed to fork off valgrind helper |
ad5db940 OJ |
366 | Defined-By: systemd |
367 | Support: %SUPPORT_URL% | |
368 | ||
5d6a86d7 | 369 | -- 7d4958e842da4a758f6c1cdc7b36dcc5 |
0b999d34 | 370 | Subject: A start job for unit @UNIT@ has begun execution |
5d6a86d7 | 371 | Defined-By: systemd |
4b930ded | 372 | Support: %SUPPORT_URL% |
d4205751 | 373 | |
0b999d34 LP |
374 | A start job for unit @UNIT@ has begun execution. |
375 | ||
376 | The job identifier is @JOB_ID@. | |
5d6a86d7 LP |
377 | |
378 | -- 39f53479d3a045ac8e11786248231fbf | |
0b999d34 | 379 | Subject: A start job for unit @UNIT@ has finished successfully |
d4205751 | 380 | Defined-By: systemd |
4b930ded | 381 | Support: %SUPPORT_URL% |
d4205751 | 382 | |
0b999d34 | 383 | A start job for unit @UNIT@ has finished successfully. |
d4205751 | 384 | |
0b999d34 | 385 | The job identifier is @JOB_ID@. |
d4205751 | 386 | |
0b999d34 LP |
387 | -- be02cf6855d2428ba40df7e9d022f03d |
388 | Subject: A start job for unit @UNIT@ has failed | |
5d6a86d7 | 389 | Defined-By: systemd |
4b930ded | 390 | Support: %SUPPORT_URL% |
5d6a86d7 | 391 | |
0b999d34 | 392 | A start job for unit @UNIT@ has finished with a failure. |
5d6a86d7 | 393 | |
0b999d34 LP |
394 | The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@. |
395 | ||
396 | -- de5b426a63be47a7b6ac3eaac82e2f6f | |
397 | Subject: A stop job for unit @UNIT@ has begun execution | |
5d6a86d7 | 398 | Defined-By: systemd |
4b930ded | 399 | Support: %SUPPORT_URL% |
5d6a86d7 | 400 | |
0b999d34 | 401 | A stop job for unit @UNIT@ has begun execution. |
5d6a86d7 | 402 | |
0b999d34 LP |
403 | The job identifier is @JOB_ID@. |
404 | ||
405 | -- 9d1aaa27d60140bd96365438aad20286 | |
406 | Subject: A stop job for unit @UNIT@ has finished | |
5d6a86d7 | 407 | Defined-By: systemd |
4b930ded | 408 | Support: %SUPPORT_URL% |
5d6a86d7 | 409 | |
0b999d34 | 410 | A stop job for unit @UNIT@ has finished. |
5d6a86d7 | 411 | |
0b999d34 | 412 | The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@. |
5d6a86d7 LP |
413 | |
414 | -- d34d037fff1847e6ae669a370e694725 | |
0b999d34 | 415 | Subject: A reload job for unit @UNIT@ has begun execution |
5d6a86d7 | 416 | Defined-By: systemd |
4b930ded | 417 | Support: %SUPPORT_URL% |
5d6a86d7 | 418 | |
0b999d34 LP |
419 | A reload job for unit @UNIT@ has begun execution. |
420 | ||
421 | The job identifier is @JOB_ID@. | |
5d6a86d7 LP |
422 | |
423 | -- 7b05ebc668384222baa8881179cfda54 | |
0b999d34 | 424 | Subject: A reload job for unit @UNIT@ has finished |
5d6a86d7 | 425 | Defined-By: systemd |
4b930ded | 426 | Support: %SUPPORT_URL% |
5d6a86d7 | 427 | |
0b999d34 | 428 | A reload job for unit @UNIT@ has finished. |
5d6a86d7 | 429 | |
0b999d34 | 430 | The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@. |
5d6a86d7 LP |
431 | |
432 | -- 641257651c1b4ec9a8624d7a40a9e1e7 | |
433 | Subject: Process @EXECUTABLE@ could not be executed | |
434 | Defined-By: systemd | |
4b930ded | 435 | Support: %SUPPORT_URL% |
5d6a86d7 LP |
436 | |
437 | The process @EXECUTABLE@ could not be executed and failed. | |
438 | ||
2057124e | 439 | The error number returned by this process is @ERRNO@. |
5d6a86d7 LP |
440 | |
441 | -- 0027229ca0644181a76c4e92458afa2e | |
5190bbb2 | 442 | Subject: One or more messages could not be forwarded to syslog |
5d6a86d7 | 443 | Defined-By: systemd |
4b930ded | 444 | Support: %SUPPORT_URL% |
5d6a86d7 LP |
445 | |
446 | One or more messages could not be forwarded to the syslog service | |
447 | running side-by-side with journald. This usually indicates that the | |
448 | syslog implementation has not been able to keep up with the speed of | |
449 | messages queued. | |
20ad4cfd ZJS |
450 | |
451 | -- 1dee0369c7fc4736b7099b38ecb46ee7 | |
452 | Subject: Mount point is not empty | |
453 | Defined-By: systemd | |
4b930ded | 454 | Support: %SUPPORT_URL% |
20ad4cfd ZJS |
455 | |
456 | The directory @WHERE@ is specified as the mount point (second field in | |
457 | /etc/fstab or Where= field in systemd unit file) and is not empty. | |
458 | This does not interfere with mounting, but the pre-exisiting files in | |
459 | this directory become inaccessible. To see those over-mounted files, | |
460 | please manually mount the underlying file system to a secondary | |
461 | location. | |
9444b1f2 LP |
462 | |
463 | -- 24d8d4452573402496068381a6312df2 | |
464 | Subject: A virtual machine or container has been started | |
465 | Defined-By: systemd | |
4b930ded | 466 | Support: %SUPPORT_URL% |
9444b1f2 LP |
467 | |
468 | The virtual machine @NAME@ with its leader PID @LEADER@ has been | |
469 | started is now ready to use. | |
470 | ||
471 | -- 58432bd3bace477cb514b56381b8a758 | |
472 | Subject: A virtual machine or container has been terminated | |
473 | Defined-By: systemd | |
4b930ded | 474 | Support: %SUPPORT_URL% |
9444b1f2 LP |
475 | |
476 | The virtual machine @NAME@ with its leader PID @LEADER@ has been | |
477 | shut down. | |
f25f9e8d LP |
478 | |
479 | -- 36db2dfa5a9045e1bd4af5f93e1cf057 | |
480 | Subject: DNSSEC mode has been turned off, as server doesn't support it | |
481 | Defined-By: systemd | |
4b930ded | 482 | Support: %SUPPORT_URL% |
b965ec7a LP |
483 | Documentation: man:systemd-resolved.service(8) |
484 | Documentation: man:resolved.conf(5) | |
f25f9e8d LP |
485 | |
486 | The resolver service (systemd-resolved.service) has detected that the | |
487 | configured DNS server does not support DNSSEC, and DNSSEC validation has been | |
488 | turned off as result. | |
489 | ||
490 | This event will take place if DNSSEC=allow-downgrade is configured in | |
491 | resolved.conf and the configured DNS server is incompatible with DNSSEC. Note | |
492 | that using this mode permits DNSSEC downgrade attacks, as an attacker might be | |
493 | able turn off DNSSEC validation on the system by inserting DNS replies in the | |
494 | communication channel that result in a downgrade like this. | |
495 | ||
496 | This event might be indication that the DNS server is indeed incompatible with | |
497 | DNSSEC or that an attacker has successfully managed to stage such a downgrade | |
498 | attack. | |
499 | ||
500 | -- 1675d7f172174098b1108bf8c7dc8f5d | |
501 | Subject: DNSSEC validation failed | |
502 | Defined-By: systemd | |
4b930ded | 503 | Support: %SUPPORT_URL% |
f25f9e8d LP |
504 | Documentation: man:systemd-resolved.service(8) |
505 | ||
506 | A DNS query or resource record set failed DNSSEC validation. This is usually | |
507 | indication that the communication channel used was tampered with. | |
508 | ||
509 | -- 4d4408cfd0d144859184d1e65d7c8a65 | |
510 | Subject: A DNSSEC trust anchor has been revoked | |
511 | Defined-By: systemd | |
4b930ded | 512 | Support: %SUPPORT_URL% |
f25f9e8d LP |
513 | Documentation: man:systemd-resolved.service(8) |
514 | ||
515 | A DNSSEC trust anchor has been revoked. A new trust anchor has to be | |
516 | configured, or the operating system needs to be updated, to provide an updated | |
517 | DNSSEC trust anchor. | |
173f30eb LP |
518 | |
519 | -- 5eb03494b6584870a536b337290809b3 | |
520 | Subject: Automatic restarting of a unit has been scheduled | |
521 | Defined-By: systemd | |
522 | Support: %SUPPORT_URL% | |
523 | ||
524 | Automatic restarting of the unit @UNIT@ has been scheduled, as the result for | |
525 | the configured Restart= setting for the unit. | |
526 | ||
527 | -- ae8f7b866b0347b9af31fe1c80b127c0 | |
528 | Subject: Resources consumed by unit runtime | |
529 | Defined-By: systemd | |
530 | Support: %SUPPORT_URL% | |
531 | ||
532 | The unit @UNIT@ completed and consumed the indicated resources. | |
b2e7486c | 533 | |
523ee2d4 LP |
534 | -- 7ad2d189f7e94e70a38c781354912448 |
535 | Subject: Unit succeeded | |
536 | Defined-By: systemd | |
537 | Support: %SUPPORT_URL% | |
538 | ||
539 | The unit @UNIT@ has successfully entered the 'dead' state. | |
540 | ||
31cd5f63 AZ |
541 | -- 0e4284a0caca4bfc81c0bb6786972673 |
542 | Subject: Unit skipped | |
543 | Defined-By: systemd | |
544 | Support: %SUPPORT_URL% | |
545 | ||
09c73ee7 AZ |
546 | The unit @UNIT@ was skipped due to an ExecCondition= command failure, and has |
547 | entered the 'dead' state with result '@UNIT_RESULT@'. | |
31cd5f63 | 548 | |
7c047d74 LP |
549 | -- d9b373ed55a64feb8242e02dbe79a49c |
550 | Subject: Unit failed | |
551 | Defined-By: systemd | |
552 | Support: %SUPPORT_URL% | |
553 | ||
554 | The unit @UNIT@ has entered the 'failed' state with result '@UNIT_RESULT@'. | |
555 | ||
91bbd9b7 LP |
556 | -- 98e322203f7a4ed290d09fe03c09fe15 |
557 | Subject: Unit process exited | |
558 | Defined-By: systemd | |
559 | Support: %SUPPORT_URL% | |
560 | ||
561 | An @COMMAND@= process belonging to unit @UNIT@ has exited. | |
562 | ||
563 | The process' exit code is '@EXIT_CODE@' and its exit status is @EXIT_STATUS@. | |
564 | ||
b2e7486c ZJS |
565 | -- 50876a9db00f4c40bde1a2ad381c3a1b |
566 | Subject: The system is configured in a way that might cause problems | |
567 | Defined-By: systemd | |
568 | Support: %SUPPORT_URL% | |
569 | ||
570 | The following "tags" are possible: | |
ea814428 MY |
571 | - "unmerged-usr" - /bin, /sbin, /lib* are not symlinks to their counterparts |
572 | under /usr/ | |
844863c6 | 573 | - "unmerged-bin" - /usr/sbin is not a symlink to /usr/bin/ |
ea814428 MY |
574 | - "var-run-bad" — /var/run is not a symlink to /run/ |
575 | - "cgroupsv1" - the system is using the deprecated cgroup v1 hierarchy | |
576 | - "local-hwclock" - the local hardware clock (RTC) is configured to be in | |
577 | local time rather than UTC | |
578 | - "support-ended" - the system is running past the end of support declared | |
579 | by the vendor | |
580 | - "old-kernel" - the system is running a kernel version that is older than | |
581 | the minimum supported by this version of systemd | |
b2e7486c ZJS |
582 | - "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with |
583 | NFS or user namespaces) is not 65534 | |
584 | - "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with | |
585 | NFS or user namespaces) is not 65534 | |
ea814428 MY |
586 | - "short-uid-range" - the UID range assigned to the running systemd instance |
587 | covers less than 0…65534 | |
588 | - "short-gid-range" - the GID range assigned to the running systemd instance | |
589 | covers less than 0…65534 | |
b2e7486c | 590 | Current system is tagged as @TAINT@. |
34e86947 LP |
591 | |
592 | -- fe6faa94e7774663a0da52717891d8ef | |
593 | Subject: A process of @UNIT@ unit has been killed by the OOM killer. | |
594 | Defined-By: systemd | |
595 | Support: %SUPPORT_URL% | |
596 | ||
597 | A process of unit @UNIT has been killed by the Linux kernel out-of-memory (OOM) | |
598 | killer logic. This usually indicates that the system is low on memory and that | |
599 | memory needed to be freed. A process associated with @UNIT@ has been determined | |
600 | as the best process to terminate and has been forcibly terminated by the | |
601 | kernel. | |
602 | ||
603 | Note that the memory pressure might or might not have been caused by @UNIT@. | |
ad313ec3 LP |
604 | |
605 | -- b61fdac612e94b9182285b998843061f | |
606 | Subject: Accepting user/group name @USER_GROUP_NAME@, which does not match strict user/group name rules. | |
607 | Defined-By: systemd | |
608 | Support: %SUPPORT_URL% | |
b965ec7a | 609 | Documentation: https://systemd.io/USER_NAMES |
ad313ec3 LP |
610 | |
611 | The user/group name @USER_GROUP_NAME@ has been specified, which is accepted | |
612 | according the relaxed user/group name rules, but does not qualify under the | |
613 | strict rules. | |
614 | ||
615 | The strict user/group name rules written as regular expression are: | |
616 | ||
617 | ^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$ | |
618 | ||
619 | The relaxed user/group name rules accept all names, except for the empty | |
620 | string; names containing NUL bytes, control characters, colon or slash | |
621 | characters; names not valid UTF-8; names with leading or trailing whitespace; | |
622 | the strings "." or ".."; fully numeric strings, or strings beginning in a | |
623 | hyphen and otherwise fully numeric. | |
624 | ||
2c905207 LP |
625 | -- 1b3bb94037f04bbf81028e135a12d293 |
626 | Subject: Failed to generate valid unit name from path '@MOUNT_POINT@'. | |
627 | Defined-By: systemd | |
628 | Support: %SUPPORT_URL% | |
629 | ||
630 | The following mount point path could not be converted into a valid .mount | |
631 | unit name: | |
632 | ||
633 | @MOUNT_POINT@ | |
634 | ||
635 | Typically this means that the path to the mount point is longer than allowed | |
636 | for valid unit names. | |
637 | ||
638 | systemd dynamically synthesizes .mount units for all mount points appearing on | |
639 | the system. For that a simple escaping algorithm is applied: the absolute path | |
640 | name is used, with all "/" characters replaced by "-" (the leading one is | |
641 | removed). Moreover, any non-alphanumeric characters (as well as any of ":", | |
642 | "-", "_", ".", "\") are replaced by "\xNN" where "NN" is the hexadecimal code | |
643 | of the character. Finally, ".mount" is suffixed. The resulting string must be | |
644 | under 256 characters in length to be a valid unit name. This restriction is | |
645 | made in order for all unit names to also be suitable as file names. If a mount | |
646 | point appears that — after escaping — is longer than this limit it cannot be | |
647 | mapped to a unit. In this case systemd will refrain from synthesizing a unit | |
648 | and cannot be used to manage the mount point. It will not appear in the service | |
649 | manager's unit table and thus also not be torn down safely and automatically at | |
650 | system shutdown. | |
651 | ||
652 | It is generally recommended to avoid such overly long mount point paths, or — | |
653 | if used anyway – manage them independently of systemd, i.e. establish them as | |
654 | well as tear them down automatically at system shutdown by other software. | |
bed0b7df LP |
655 | |
656 | -- b480325f9c394a7b802c231e51a2752c | |
657 | Subject: Special user @OFFENDING_USER@ configured, this is not safe! | |
658 | Defined-By: systemd | |
659 | Support: %SUPPORT_URL% | |
660 | Documentation: https://systemd.io/UIDS-GIDS | |
661 | ||
662 | The unit @UNIT@ is configured to use User=@OFFENDING_USER@. | |
663 | ||
664 | This is not safe. The @OFFENDING_USER@ user's main purpose on Linux-based | |
665 | operating systems is to be the owner of files that otherwise cannot be mapped | |
666 | to any local user. It's used by the NFS client and Linux user namespacing, | |
667 | among others. By running a unit's processes under the identity of this user | |
668 | they might possibly get read and even write access to such files that cannot | |
669 | otherwise be mapped. | |
670 | ||
671 | It is strongly recommended to avoid running services under this user identity, | |
672 | in particular on systems using NFS or running containers. Allocate a user ID | |
673 | specific to this service, either statically via systemd-sysusers or dynamically | |
674 | via the DynamicUser= service setting. | |
77ee1783 LP |
675 | |
676 | -- 1c0454c1bd2241e0ac6fefb4bc631433 | |
677 | Subject: systemd-udev-settle.service is deprecated. | |
678 | Defined-By: systemd | |
679 | Support: %SUPPORT_URL% | |
680 | ||
681 | Usage of the systemd service unit systemd-udev-settle.service is deprecated. It | |
682 | inserts artificial delays into the boot process without providing the | |
683 | guarantees other subsystems traditionally assumed it provides. Relying on this | |
684 | service is racy, and it is generally a bug to make use of it and depend on it. | |
685 | ||
686 | Traditionally, this service's job was to wait until all devices a system | |
687 | possesses have been fully probed and initialized, delaying boot until this | |
688 | phase is completed. However, today's systems and hardware generally don't work | |
689 | this way anymore, hardware today may show up any time and take any time to be | |
690 | probed and initialized. Thus, in the general case, it's no longer possible to | |
691 | correctly delay boot until "all devices" have been processed, as it is not | |
692 | clear what "all devices" means and when they have been found. This is in | |
693 | particular the case if USB hardware or network-attached hardware is used. | |
694 | ||
695 | Modern software that requires some specific hardware (such as a network device | |
696 | or block device) to operate should only wait for the specific devices it needs | |
697 | to show up, and otherwise operate asynchronously initializing devices as they | |
698 | appear during boot and during runtime without delaying the boot process. | |
699 | ||
700 | It is a defect of the software in question if it doesn't work this way, and | |
701 | still pulls systemd-udev-settle.service into the boot process. | |
702 | ||
703 | Please file a bug report against the following units, with a request for it to | |
704 | be updated to operate in a hotplug fashion without depending on | |
705 | systemd-udev-settle.service: | |
706 | ||
707 | @OFFENDING_UNITS@ | |
b016e77e LP |
708 | |
709 | -- 7c8a41f37b764941a0e1780b1be2f037 | |
710 | Subject: Initial clock synchronization | |
711 | Defined-By: systemd | |
712 | Support: %SUPPORT_URL% | |
713 | ||
714 | For the first time during the current boot an NTP synchronization has been | |
715 | acquired and the local system clock adjustment has been initiated. | |
708d7524 LP |
716 | |
717 | -- 3f7d5ef3e54f4302b4f0b143bb270cab | |
718 | Subject: TPM PCR Extended | |
719 | Defined-By: systemd | |
720 | Support: %SUPPORT_URL% | |
721 | ||
86a06615 ZJS |
722 | The Trusted Platform Module's (TPM) Platform Configuration Register (PCR) |
723 | @PCR@, on banks @BANKS@, has been extended with the string '@MEASURING@'. | |
708d7524 | 724 | |
86a06615 ZJS |
725 | Whenever the system transitions to a new runtime phase, the specified PCR is |
726 | extended with a different string, to ensure that security policies for | |
727 | TPM-bound secrets and other resources are limited to specific phases of the | |
728 | runtime. | |
158fe190 LP |
729 | |
730 | -- f9b0be465ad540d0850ad32172d57c21 | |
731 | Subject: Memory Trimmed | |
732 | Defined-By: systemd | |
733 | Support: %SUPPORT_URL% | |
734 | ||
735 | Memory of process @_PID@ (@_COMM@) has been trimmed. | |
736 | ||
737 | Either on user request or as result of a memory pressure event, memory of the | |
c73676dc | 738 | process has been trimmed, returning unneeded allocation caches and other |
158fe190 LP |
739 | resources back to the OS kernel, making them available for other components of |
740 | the OS. | |
741 | ||
742 | @TRIMMED_BYTES@ of memory were returned to the OS, which took @TRIMMED_USEC@ | |
e503019b | 743 | micro-seconds (μs). |
f4d4ca6e LP |
744 | |
745 | -- a8fa8dacdb1d443e9503b8be367a6adb | |
746 | Subject: SysV Service Found | |
747 | Defined-By: systemd | |
748 | Support: %SUPPORT_URL% | |
749 | ||
750 | A System V service script @SYSVSCRIPT@ has been found on the system that lacks | |
751 | a native systemd unit. An automatic unit file @UNIT@ has been generated for | |
752 | compatibility. | |
753 | ||
754 | Note that these automatically generated compatibility unit files cannot replace | |
755 | native unit files as they generally slow down the system (by creating | |
756 | unnecessary, additional synchronization points), are less robust (as SysV services | |
55e40b0b | 757 | cannot properly be lifecycle tracked or automatically restarted) and less |
f4d4ca6e LP |
758 | secure (as no sandboxing restrictions can be enforced). |
759 | ||
760 | Compatibility support for System V services in systemd is deprecated. Please | |
761 | make sure to update the package in question to provide proper, native systemd | |
d19434fb | 762 | unit files. Contact vendor if necessary. Compatibility support for System V |
f4d4ca6e | 763 | services is deprecated and will be removed soon. |
a0cca4d1 LB |
764 | |
765 | -- 187c62eb1e7f463bb530394f52cb090f | |
766 | Subject: A Portable Service has been attached | |
767 | Defined-By: systemd | |
768 | Support: %SUPPORT_URL% | |
769 | Documentation: https://systemd.io/PORTABLE_SERVICES/ | |
770 | ||
771 | A new Portable Service @PORTABLE_ROOT@ (with extensions: @PORTABLE_EXTENSION@) has | |
772 | been attached to the system and is now available for use. The list of attached | |
773 | Portable Services can be queried with 'portablectl list'. | |
774 | ||
775 | -- 76c5c754d628490d8ecba4c9d042112b | |
776 | Subject: A Portable Service has been detached | |
777 | Defined-By: systemd | |
778 | Support: %SUPPORT_URL% | |
779 | Documentation: https://systemd.io/PORTABLE_SERVICES/ | |
780 | ||
781 | A Portable Service @PORTABLE_ROOT@ (with extensions: @PORTABLE_EXTENSION@) has been | |
782 | detached from the system and is no longer available for use. The list of attached | |
783 | Portable Services can be queried with 'portablectl list'. | |
d6518003 DDM |
784 | |
785 | -- ad7089f928ac4f7ea00c07457d47ba8a | |
786 | Subject: Authorization failure while attempting to enroll SRK into TPM | |
787 | Defined-By: systemd | |
788 | Support: %SUPPORT_URL% | |
789 | Documentation: man:systemd-tpm2-setup.service(8) | |
790 | ||
9d63491f LP |
791 | An authorization failure occurred while attempting to enroll a Storage Root Key |
792 | (SRK) on the Trusted Platform Module (TPM). Most likely this means that a | |
793 | PIN/Password (authValue) has been set on the Owner hierarchy of the TPM. | |
d6518003 | 794 | |
9d63491f LP |
795 | Automatic SRK enrollment on TPMs in such scenarios is not supported. In order |
796 | to unset the PIN/password protection on the owner hierarchy issue a command | |
797 | like the following: 'tpm2_changeauth -c o -p <OLDPW> ""'. | |
6d9ef22a MC |
798 | |
799 | -- 9cf56b8baf9546cf9478783a8de42113 | |
e1f9d3c8 | 800 | Subject: A foreign process changed a sysctl systemd-networkd manages |
6d9ef22a MC |
801 | Defined-By: systemd |
802 | Support: %SUPPORT_URL% | |
803 | ||
e1f9d3c8 LP |
804 | The sysctl configuration setting @SYSCTL@, which is managed by |
805 | systemd-networkd, has been changed by another, unrelated process | |
806 | ("@OBJECT_COMM@", PID @OBJECT_PID@). This represents a conflict of ownership | |
807 | and will likely result in problems later on. | |
808 | ||
809 | Value changed to "@NEWVALUE@", which should be "@OURVALUE@". |