catalog/systemd.catalog.in

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