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