1 # SPDX-License-Identifier: LGPL-2.1+
3 # Message catalog for systemd's own messages
5 # The catalog format is documented on
6 # https://www.freedesktop.org/wiki/Software/systemd/catalog
8 # For an explanation why we do all this, see https://xkcd.com/1024/
10 -- f77379a8490b408bbe5f6940505a777b
11 Subject: The journal has been started
13 Support: %SUPPORT_URL%
15 The system journal process has started up, opened the journal
16 files for writing and is now ready to process requests.
18 -- d93fb3c9c24d451a97cea615ce59c00b
19 Subject: The journal has been stopped
21 Support: %SUPPORT_URL%
23 The system journal process has shut down and closed all currently
26 -- ec387f577b844b8fa948f33cad9a75e6
27 Subject: Disk space used by the journal
29 Support: %SUPPORT_URL%
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.
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.
41 -- a596d6fe7bfa4994828e72309e95d61e
42 Subject: Messages from a service have been suppressed
44 Support: %SUPPORT_URL%
45 Documentation: man:journald.conf(5)
47 A service has logged too many messages within a time period. Messages
48 from the service have been dropped.
50 Note that only messages from the service in question have been
51 dropped, other services' messages are unaffected.
53 The limits controlling when messages are dropped may be configured
54 with RateLimitIntervalSec= and RateLimitBurst= in
55 /etc/systemd/journald.conf or LogRateLimitIntervalSec= and LogRateLimitBurst=
56 in the unit file. See journald.conf(5) and systemd.exec(5) for details.
58 -- e9bf28e6e834481bb6f48f548ad13606
59 Subject: Journal messages have been missed
61 Support: %SUPPORT_URL%
63 Kernel messages have been lost as the journal system has been unable
64 to process them quickly enough.
66 -- fc2e22bc6ee647b6b90729ab34a250b1
67 Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
69 Support: %SUPPORT_URL%
70 Documentation: man:core(5)
72 Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
74 This usually indicates a programming error in the crashing program and
75 should be reported to its vendor as a bug.
77 -- 5aadd8e954dc4b1a8c954d63fd9e1137
78 Subject: Core file was truncated to @SIZE_LIMIT@ bytes.
80 Support: %SUPPORT_URL%
81 Documentation: man:coredump.conf(5)
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.
88 -- 8d45620c1a4348dbb17410da57c60c66
89 Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
91 Support: %SUPPORT_URL%
92 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
94 A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@.
96 The leading process of the session is @LEADER@.
98 -- 3354939424b4456d9802ca8333ed424a
99 Subject: Session @SESSION_ID@ has been terminated
101 Support: %SUPPORT_URL%
102 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
104 A session with the ID @SESSION_ID@ has been terminated.
106 -- fcbefc5da23d428093f97c82a9290f7b
107 Subject: A new seat @SEAT_ID@ is now available
109 Support: %SUPPORT_URL%
110 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
112 A new seat @SEAT_ID@ has been configured and is now available.
114 -- e7852bfe46784ed0accde04bc864c2d5
115 Subject: Seat @SEAT_ID@ has now been removed
117 Support: %SUPPORT_URL%
118 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
120 A seat @SEAT_ID@ has been removed and is no longer available.
122 -- c7a787079b354eaaa9e77b371893cd27
125 Support: %SUPPORT_URL%
127 The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
129 -- c7a787079b354eaaa9e77b371893cd27 de
130 Subject: Zeitänderung
132 Support: %SUPPORT_URL%
134 Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
136 -- 45f82f4aef7a4bbf942ce861d1f20990
137 Subject: Time zone change to @TIMEZONE@
139 Support: %SUPPORT_URL%
141 The system timezone has been changed to @TIMEZONE@.
143 -- b07a249cd024414a82dd00cd181378ff
144 Subject: System start-up is now complete
146 Support: %SUPPORT_URL%
148 All system services necessary queued for starting at boot have been
149 started. Note that this does not mean that the machine is now idle as services
150 might still be busy with completing start-up.
152 Kernel start-up required @KERNEL_USEC@ microseconds.
154 Initial RAM disk start-up required @INITRD_USEC@ microseconds.
156 Userspace start-up required @USERSPACE_USEC@ microseconds.
158 -- eed00a68ffd84e31882105fd973abdd1
159 Subject: User manager start-up is now complete
161 Support: %SUPPORT_URL%
163 The user manager instance for user @_UID@ has been started. All services queued
164 for starting have been started. Note that other services might still be starting
165 up or be started at any later time.
167 Startup of the manager took @USERSPACE_USEC@ microseconds.
169 -- 6bbd95ee977941e497c48be27c254128
170 Subject: System sleep state @SLEEP@ entered
172 Support: %SUPPORT_URL%
174 The system has now entered the @SLEEP@ sleep state.
176 -- 8811e6df2a8e40f58a94cea26f8ebf14
177 Subject: System sleep state @SLEEP@ left
179 Support: %SUPPORT_URL%
181 The system has now left the @SLEEP@ sleep state.
183 -- 98268866d1d54a499c4e98921d93bc40
184 Subject: System shutdown initiated
186 Support: %SUPPORT_URL%
188 System shutdown has been initiated. The shutdown has now begun and
189 all system services are terminated and all file systems unmounted.
191 -- 7d4958e842da4a758f6c1cdc7b36dcc5
192 Subject: Unit @UNIT@ has begun start-up
194 Support: %SUPPORT_URL%
196 Unit @UNIT@ has begun starting up.
198 -- 39f53479d3a045ac8e11786248231fbf
199 Subject: Unit @UNIT@ has finished start-up
201 Support: %SUPPORT_URL%
203 Unit @UNIT@ has finished starting up.
205 The start-up result is @JOB_RESULT@.
207 -- de5b426a63be47a7b6ac3eaac82e2f6f
208 Subject: Unit @UNIT@ has begun shutting down
210 Support: %SUPPORT_URL%
212 Unit @UNIT@ has begun shutting down.
214 -- 9d1aaa27d60140bd96365438aad20286
215 Subject: Unit @UNIT@ has finished shutting down
217 Support: %SUPPORT_URL%
219 Unit @UNIT@ has finished shutting down.
221 -- be02cf6855d2428ba40df7e9d022f03d
222 Subject: Unit @UNIT@ has failed
224 Support: %SUPPORT_URL%
226 Unit @UNIT@ has failed.
228 The result is @JOB_RESULT@.
230 -- d34d037fff1847e6ae669a370e694725
231 Subject: Unit @UNIT@ has begun reloading its configuration
233 Support: %SUPPORT_URL%
235 Unit @UNIT@ has begun reloading its configuration
237 -- 7b05ebc668384222baa8881179cfda54
238 Subject: Unit @UNIT@ has finished reloading its configuration
240 Support: %SUPPORT_URL%
242 Unit @UNIT@ has finished reloading its configuration
244 The result is @JOB_RESULT@.
246 -- 641257651c1b4ec9a8624d7a40a9e1e7
247 Subject: Process @EXECUTABLE@ could not be executed
249 Support: %SUPPORT_URL%
251 The process @EXECUTABLE@ could not be executed and failed.
253 The error number returned by this process is @ERRNO@.
255 -- 0027229ca0644181a76c4e92458afa2e
256 Subject: One or more messages could not be forwarded to syslog
258 Support: %SUPPORT_URL%
260 One or more messages could not be forwarded to the syslog service
261 running side-by-side with journald. This usually indicates that the
262 syslog implementation has not been able to keep up with the speed of
265 -- 1dee0369c7fc4736b7099b38ecb46ee7
266 Subject: Mount point is not empty
268 Support: %SUPPORT_URL%
270 The 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.
272 This does not interfere with mounting, but the pre-exisiting files in
273 this directory become inaccessible. To see those over-mounted files,
274 please manually mount the underlying file system to a secondary
277 -- 24d8d4452573402496068381a6312df2
278 Subject: A virtual machine or container has been started
280 Support: %SUPPORT_URL%
282 The virtual machine @NAME@ with its leader PID @LEADER@ has been
283 started is now ready to use.
285 -- 58432bd3bace477cb514b56381b8a758
286 Subject: A virtual machine or container has been terminated
288 Support: %SUPPORT_URL%
290 The virtual machine @NAME@ with its leader PID @LEADER@ has been
293 -- 36db2dfa5a9045e1bd4af5f93e1cf057
294 Subject: DNSSEC mode has been turned off, as server doesn't support it
296 Support: %SUPPORT_URL%
297 Documentation: man:systemd-resolved.service(8) resolved.conf(5)
299 The resolver service (systemd-resolved.service) has detected that the
300 configured DNS server does not support DNSSEC, and DNSSEC validation has been
301 turned off as result.
303 This event will take place if DNSSEC=allow-downgrade is configured in
304 resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
305 that using this mode permits DNSSEC downgrade attacks, as an attacker might be
306 able turn off DNSSEC validation on the system by inserting DNS replies in the
307 communication channel that result in a downgrade like this.
309 This event might be indication that the DNS server is indeed incompatible with
310 DNSSEC or that an attacker has successfully managed to stage such a downgrade
313 -- 1675d7f172174098b1108bf8c7dc8f5d
314 Subject: DNSSEC validation failed
316 Support: %SUPPORT_URL%
317 Documentation: man:systemd-resolved.service(8)
319 A DNS query or resource record set failed DNSSEC validation. This is usually
320 indication that the communication channel used was tampered with.
322 -- 4d4408cfd0d144859184d1e65d7c8a65
323 Subject: A DNSSEC trust anchor has been revoked
325 Support: %SUPPORT_URL%
326 Documentation: man:systemd-resolved.service(8)
328 A DNSSEC trust anchor has been revoked. A new trust anchor has to be
329 configured, or the operating system needs to be updated, to provide an updated
332 -- 5eb03494b6584870a536b337290809b3
333 Subject: Automatic restarting of a unit has been scheduled
335 Support: %SUPPORT_URL%
337 Automatic restarting of the unit @UNIT@ has been scheduled, as the result for
338 the configured Restart= setting for the unit.
340 -- ae8f7b866b0347b9af31fe1c80b127c0
341 Subject: Resources consumed by unit runtime
343 Support: %SUPPORT_URL%
345 The unit @UNIT@ completed and consumed the indicated resources.
347 -- 50876a9db00f4c40bde1a2ad381c3a1b
348 Subject: The system is configured in a way that might cause problems
350 Support: %SUPPORT_URL%
352 The following "tags" are possible:
353 - "split-usr" — /usr is a separate file system and was not mounted when systemd
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
362 Current system is tagged as @TAINT@.