catalog/systemd.catalog.in

   1 # SPDX-License-Identifier: LGPL-2.1+
   2
   3 # Message catalog for systemd's own messages
   4
   5 # The catalog format is documented on
   6 # https://www.freedesktop.org/wiki/Software/systemd/catalog
   7
   8 # For an explanation why we do all this, see https://xkcd.com/1024/
   9
  10 -- f77379a8490b408bbe5f6940505a777b
  11 Subject: The journal has been started
  12 Defined-By: systemd
  13 Support: %SUPPORT_URL%
  14
  15 The system journal process has started up, opened the journal
  16 files for writing and is now ready to process requests.
  17
  18 -- d93fb3c9c24d451a97cea615ce59c00b
  19 Subject: The journal has been stopped
  20 Defined-By: systemd
  21 Support: %SUPPORT_URL%
  22
  23 The system journal process has shut down and closed all currently
  24 active journal files.
  25
  26 -- ec387f577b844b8fa948f33cad9a75e6
  27 Subject: Disk space used by the journal
  28 Defined-By: systemd
  29 Support: %SUPPORT_URL%
  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
  41 -- a596d6fe7bfa4994828e72309e95d61e
  42 Subject: Messages from a service have been suppressed
  43 Defined-By: systemd
  44 Support: %SUPPORT_URL%
  45 Documentation: man:journald.conf(5)
  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
  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.
  57
  58 -- e9bf28e6e834481bb6f48f548ad13606
  59 Subject: Journal messages have been missed
  60 Defined-By: systemd
  61 Support: %SUPPORT_URL%
  62
  63 Kernel messages have been lost as the journal system has been unable
  64 to process them quickly enough.
  65
  66 -- fc2e22bc6ee647b6b90729ab34a250b1
  67 Subject: Process @COREDUMP_PID@ (@COREDUMP_COMM@) dumped core
  68 Defined-By: systemd
  69 Support: %SUPPORT_URL%
  70 Documentation: man:core(5)
  71
  72 Process @COREDUMP_PID@ (@COREDUMP_COMM@) crashed and dumped core.
  73
  74 This usually indicates a programming error in the crashing program and
  75 should be reported to its vendor as a bug.
  76
  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
  88 -- 8d45620c1a4348dbb17410da57c60c66
  89 Subject: A new session @SESSION_ID@ has been created for user @USER_ID@
  90 Defined-By: systemd
  91 Support: %SUPPORT_URL%
  92 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
  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
  99 Subject: Session @SESSION_ID@ has been terminated
 100 Defined-By: systemd
 101 Support: %SUPPORT_URL%
 102 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
 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
 109 Support: %SUPPORT_URL%
 110 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
 111
 112 A new seat @SEAT_ID@ has been configured and is now available.
 113
 114 -- e7852bfe46784ed0accde04bc864c2d5
 115 Subject: Seat @SEAT_ID@ has now been removed
 116 Defined-By: systemd
 117 Support: %SUPPORT_URL%
 118 Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
 119
 120 A seat @SEAT_ID@ has been removed and is no longer available.
 121
 122 -- c7a787079b354eaaa9e77b371893cd27
 123 Subject: Time change
 124 Defined-By: systemd
 125 Support: %SUPPORT_URL%
 126
 127 The system clock has been changed to @REALTIME@ microseconds after January 1st, 1970.
 128
 129 -- c7a787079b354eaaa9e77b371893cd27 de
 130 Subject: Zeitänderung
 131 Defined-By: systemd
 132 Support: %SUPPORT_URL%
 133
 134 Die System-Zeit wurde geändert auf @REALTIME@ Mikrosekunden nach dem 1. Januar 1970.
 135
 136 -- 45f82f4aef7a4bbf942ce861d1f20990
 137 Subject: Time zone change to @TIMEZONE@
 138 Defined-By: systemd
 139 Support: %SUPPORT_URL%
 140
 141 The system timezone has been changed to @TIMEZONE@.
 142
 143 -- b07a249cd024414a82dd00cd181378ff
 144 Subject: System start-up is now complete
 145 Defined-By: systemd
 146 Support: %SUPPORT_URL%
 147
 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.
 151
 152 Kernel start-up required @KERNEL_USEC@ microseconds.
 153
 154 Initial RAM disk start-up required @INITRD_USEC@ microseconds.
 155
 156 Userspace start-up required @USERSPACE_USEC@ microseconds.
 157
 158 -- eed00a68ffd84e31882105fd973abdd1
 159 Subject: User manager start-up is now complete
 160 Defined-By: systemd
 161 Support: %SUPPORT_URL%
 162
 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.
 166
 167 Startup of the manager took @USERSPACE_USEC@ microseconds.
 168
 169 -- 6bbd95ee977941e497c48be27c254128
 170 Subject: System sleep state @SLEEP@ entered
 171 Defined-By: systemd
 172 Support: %SUPPORT_URL%
 173
 174 The system has now entered the @SLEEP@ sleep state.
 175
 176 -- 8811e6df2a8e40f58a94cea26f8ebf14
 177 Subject: System sleep state @SLEEP@ left
 178 Defined-By: systemd
 179 Support: %SUPPORT_URL%
 180
 181 The system has now left the @SLEEP@ sleep state.
 182
 183 -- 98268866d1d54a499c4e98921d93bc40
 184 Subject: System shutdown initiated
 185 Defined-By: systemd
 186 Support: %SUPPORT_URL%
 187
 188 System shutdown has been initiated. The shutdown has now begun and
 189 all system services are terminated and all file systems unmounted.
 190
 191 -- 7d4958e842da4a758f6c1cdc7b36dcc5
 192 Subject: A start job for unit @UNIT@ has begun execution
 193 Defined-By: systemd
 194 Support: %SUPPORT_URL%
 195
 196 A start job for unit @UNIT@ has begun execution.
 197
 198 The job identifier is @JOB_ID@.
 199
 200 -- 39f53479d3a045ac8e11786248231fbf
 201 Subject: A start job for unit @UNIT@ has finished successfully
 202 Defined-By: systemd
 203 Support: %SUPPORT_URL%
 204
 205 A start job for unit @UNIT@ has finished successfully.
 206
 207 The job identifier is @JOB_ID@.
 208
 209 -- be02cf6855d2428ba40df7e9d022f03d
 210 Subject: A start job for unit @UNIT@ has failed
 211 Defined-By: systemd
 212 Support: %SUPPORT_URL%
 213
 214 A start job for unit @UNIT@ has finished with a failure.
 215
 216 The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
 217
 218 -- de5b426a63be47a7b6ac3eaac82e2f6f
 219 Subject: A stop job for unit @UNIT@ has begun execution
 220 Defined-By: systemd
 221 Support: %SUPPORT_URL%
 222
 223 A stop job for unit @UNIT@ has begun execution.
 224
 225 The job identifier is @JOB_ID@.
 226
 227 -- 9d1aaa27d60140bd96365438aad20286
 228 Subject: A stop job for unit @UNIT@ has finished
 229 Defined-By: systemd
 230 Support: %SUPPORT_URL%
 231
 232 A stop job for unit @UNIT@ has finished.
 233
 234 The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
 235
 236 -- d34d037fff1847e6ae669a370e694725
 237 Subject: A reload job for unit @UNIT@ has begun execution
 238 Defined-By: systemd
 239 Support: %SUPPORT_URL%
 240
 241 A reload job for unit @UNIT@ has begun execution.
 242
 243 The job identifier is @JOB_ID@.
 244
 245 -- 7b05ebc668384222baa8881179cfda54
 246 Subject: A reload job for unit @UNIT@ has finished
 247 Defined-By: systemd
 248 Support: %SUPPORT_URL%
 249
 250 A reload job for unit @UNIT@ has finished.
 251
 252 The job identifier is @JOB_ID@ and the job result is @JOB_RESULT@.
 253
 254 -- 641257651c1b4ec9a8624d7a40a9e1e7
 255 Subject: Process @EXECUTABLE@ could not be executed
 256 Defined-By: systemd
 257 Support: %SUPPORT_URL%
 258
 259 The process @EXECUTABLE@ could not be executed and failed.
 260
 261 The error number returned by this process is @ERRNO@.
 262
 263 -- 0027229ca0644181a76c4e92458afa2e
 264 Subject: One or more messages could not be forwarded to syslog
 265 Defined-By: systemd
 266 Support: %SUPPORT_URL%
 267
 268 One or more messages could not be forwarded to the syslog service
 269 running side-by-side with journald. This usually indicates that the
 270 syslog implementation has not been able to keep up with the speed of
 271 messages queued.
 272
 273 -- 1dee0369c7fc4736b7099b38ecb46ee7
 274 Subject: Mount point is not empty
 275 Defined-By: systemd
 276 Support: %SUPPORT_URL%
 277
 278 The directory @WHERE@ is specified as the mount point (second field in
 279 /etc/fstab or Where= field in systemd unit file) and is not empty.
 280 This does not interfere with mounting, but the pre-exisiting files in
 281 this directory become inaccessible. To see those over-mounted files,
 282 please manually mount the underlying file system to a secondary
 283 location.
 284
 285 -- 24d8d4452573402496068381a6312df2
 286 Subject: A virtual machine or container has been started
 287 Defined-By: systemd
 288 Support: %SUPPORT_URL%
 289
 290 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 291 started is now ready to use.
 292
 293 -- 58432bd3bace477cb514b56381b8a758
 294 Subject: A virtual machine or container has been terminated
 295 Defined-By: systemd
 296 Support: %SUPPORT_URL%
 297
 298 The virtual machine @NAME@ with its leader PID @LEADER@ has been
 299 shut down.
 300
 301 -- 36db2dfa5a9045e1bd4af5f93e1cf057
 302 Subject: DNSSEC mode has been turned off, as server doesn't support it
 303 Defined-By: systemd
 304 Support: %SUPPORT_URL%
 305 Documentation: man:systemd-resolved.service(8)
 306 Documentation: man:resolved.conf(5)
 307
 308 The resolver service (systemd-resolved.service) has detected that the
 309 configured DNS server does not support DNSSEC, and DNSSEC validation has been
 310 turned off as result.
 311
 312 This event will take place if DNSSEC=allow-downgrade is configured in
 313 resolved.conf and the configured DNS server is incompatible with DNSSEC. Note
 314 that using this mode permits DNSSEC downgrade attacks, as an attacker might be
 315 able turn off DNSSEC validation on the system by inserting DNS replies in the
 316 communication channel that result in a downgrade like this.
 317
 318 This event might be indication that the DNS server is indeed incompatible with
 319 DNSSEC or that an attacker has successfully managed to stage such a downgrade
 320 attack.
 321
 322 -- 1675d7f172174098b1108bf8c7dc8f5d
 323 Subject: DNSSEC validation failed
 324 Defined-By: systemd
 325 Support: %SUPPORT_URL%
 326 Documentation: man:systemd-resolved.service(8)
 327
 328 A DNS query or resource record set failed DNSSEC validation. This is usually
 329 indication that the communication channel used was tampered with.
 330
 331 -- 4d4408cfd0d144859184d1e65d7c8a65
 332 Subject: A DNSSEC trust anchor has been revoked
 333 Defined-By: systemd
 334 Support: %SUPPORT_URL%
 335 Documentation: man:systemd-resolved.service(8)
 336
 337 A DNSSEC trust anchor has been revoked. A new trust anchor has to be
 338 configured, or the operating system needs to be updated, to provide an updated
 339 DNSSEC trust anchor.
 340
 341 -- 5eb03494b6584870a536b337290809b3
 342 Subject: Automatic restarting of a unit has been scheduled
 343 Defined-By: systemd
 344 Support: %SUPPORT_URL%
 345
 346 Automatic restarting of the unit @UNIT@ has been scheduled, as the result for
 347 the configured Restart= setting for the unit.
 348
 349 -- ae8f7b866b0347b9af31fe1c80b127c0
 350 Subject: Resources consumed by unit runtime
 351 Defined-By: systemd
 352 Support: %SUPPORT_URL%
 353
 354 The unit @UNIT@ completed and consumed the indicated resources.
 355
 356 -- 7ad2d189f7e94e70a38c781354912448
 357 Subject: Unit succeeded
 358 Defined-By: systemd
 359 Support: %SUPPORT_URL%
 360
 361 The unit @UNIT@ has successfully entered the 'dead' state.
 362
 363 -- 0e4284a0caca4bfc81c0bb6786972673
 364 Subject: Unit skipped
 365 Defined-By: systemd
 366 Support: %SUPPORT_URL%
 367
 368 The unit @UNIT@ was skipped due to an ExecCondition= command failure, and has
 369 entered the 'dead' state with result '@UNIT_RESULT@'.
 370
 371 -- d9b373ed55a64feb8242e02dbe79a49c
 372 Subject: Unit failed
 373 Defined-By: systemd
 374 Support: %SUPPORT_URL%
 375
 376 The unit @UNIT@ has entered the 'failed' state with result '@UNIT_RESULT@'.
 377
 378 -- 98e322203f7a4ed290d09fe03c09fe15
 379 Subject: Unit process exited
 380 Defined-By: systemd
 381 Support: %SUPPORT_URL%
 382
 383 An @COMMAND@= process belonging to unit @UNIT@ has exited.
 384
 385 The process' exit code is '@EXIT_CODE@' and its exit status is @EXIT_STATUS@.
 386
 387 -- 50876a9db00f4c40bde1a2ad381c3a1b
 388 Subject: The system is configured in a way that might cause problems
 389 Defined-By: systemd
 390 Support: %SUPPORT_URL%
 391
 392 The following "tags" are possible:
 393 - "split-usr" — /usr is a separate file system and was not mounted when systemd
 394   was booted
 395 - "cgroups-missing" — the kernel was compiled without cgroup support or access
 396   to expected interface files is restricted
 397 - "var-run-bad" — /var/run is not a symlink to /run
 398 - "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with
 399   NFS or user namespaces) is not 65534
 400 - "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with
 401   NFS or user namespaces) is not 65534
 402 Current system is tagged as @TAINT@.
 403
 404 -- fe6faa94e7774663a0da52717891d8ef
 405 Subject: A process of @UNIT@ unit has been killed by the OOM killer.
 406 Defined-By: systemd
 407 Support: %SUPPORT_URL%
 408
 409 A process of unit @UNIT has been killed by the Linux kernel out-of-memory (OOM)
 410 killer logic. This usually indicates that the system is low on memory and that
 411 memory needed to be freed. A process associated with @UNIT@ has been determined
 412 as the best process to terminate and has been forcibly terminated by the
 413 kernel.
 414
 415 Note that the memory pressure might or might not have been caused by @UNIT@.
 416
 417 -- b61fdac612e94b9182285b998843061f
 418 Subject: Accepting user/group name @USER_GROUP_NAME@, which does not match strict user/group name rules.
 419 Defined-By: systemd
 420 Support: %SUPPORT_URL%
 421 Documentation: https://systemd.io/USER_NAMES
 422
 423 The user/group name @USER_GROUP_NAME@ has been specified, which is accepted
 424 according the relaxed user/group name rules, but does not qualify under the
 425 strict rules.
 426
 427 The strict user/group name rules written as regular expression are:
 428
 429 ^[a-zA-Z_][a-zA-Z0-9_-]{0,30}$
 430
 431 The relaxed user/group name rules accept all names, except for the empty
 432 string; names containing NUL bytes, control characters, colon or slash
 433 characters; names not valid UTF-8; names with leading or trailing whitespace;
 434 the strings "." or ".."; fully numeric strings, or strings beginning in a
 435 hyphen and otherwise fully numeric.
 436
 437 -- 1b3bb94037f04bbf81028e135a12d293
 438 Subject: Failed to generate valid unit name from path '@MOUNT_POINT@'.
 439 Defined-By: systemd
 440 Support: %SUPPORT_URL%
 441
 442 The following mount point path could not be converted into a valid .mount
 443 unit name:
 444
 445     @MOUNT_POINT@
 446
 447 Typically this means that the path to the mount point is longer than allowed
 448 for valid unit names.
 449
 450 systemd dynamically synthesizes .mount units for all mount points appearing on
 451 the system. For that a simple escaping algorithm is applied: the absolute path
 452 name is used, with all "/" characters replaced by "-" (the leading one is
 453 removed). Moreover, any non-alphanumeric characters (as well as any of ":",
 454 "-", "_", ".", "\") are replaced by "\xNN" where "NN" is the hexadecimal code
 455 of the character. Finally, ".mount" is suffixed. The resulting string must be
 456 under 256 characters in length to be a valid unit name. This restriction is
 457 made in order for all unit names to also be suitable as file names. If a mount
 458 point appears that — after escaping — is longer than this limit it cannot be
 459 mapped to a unit. In this case systemd will refrain from synthesizing a unit
 460 and cannot be used to manage the mount point. It will not appear in the service
 461 manager's unit table and thus also not be torn down safely and automatically at
 462 system shutdown.
 463
 464 It is generally recommended to avoid such overly long mount point paths, or —
 465 if used anyway – manage them independently of systemd, i.e. establish them as
 466 well as tear them down automatically at system shutdown by other software.
 467
 468 -- b480325f9c394a7b802c231e51a2752c
 469 Subject: Special user @OFFENDING_USER@ configured, this is not safe!
 470 Defined-By: systemd
 471 Support: %SUPPORT_URL%
 472 Documentation: https://systemd.io/UIDS-GIDS
 473
 474 The unit @UNIT@ is configured to use User=@OFFENDING_USER@.
 475
 476 This is not safe. The @OFFENDING_USER@ user's main purpose on Linux-based
 477 operating systems is to be the owner of files that otherwise cannot be mapped
 478 to any local user. It's used by the NFS client and Linux user namespacing,
 479 among others. By running a unit's processes under the identity of this user
 480 they might possibly get read and even write access to such files that cannot
 481 otherwise be mapped.
 482
 483 It is strongly recommended to avoid running services under this user identity,
 484 in particular on systems using NFS or running containers. Allocate a user ID
 485 specific to this service, either statically via systemd-sysusers or dynamically
 486 via the DynamicUser= service setting.
 487
 488 -- 1c0454c1bd2241e0ac6fefb4bc631433
 489 Subject: systemd-udev-settle.service is deprecated.
 490 Defined-By: systemd
 491 Support: %SUPPORT_URL%
 492
 493 Usage of the systemd service unit systemd-udev-settle.service is deprecated. It
 494 inserts artificial delays into the boot process without providing the
 495 guarantees other subsystems traditionally assumed it provides. Relying on this
 496 service is racy, and it is generally a bug to make use of it and depend on it.
 497
 498 Traditionally, this service's job was to wait until all devices a system
 499 possesses have been fully probed and initialized, delaying boot until this
 500 phase is completed. However, today's systems and hardware generally don't work
 501 this way anymore, hardware today may show up any time and take any time to be
 502 probed and initialized. Thus, in the general case, it's no longer possible to
 503 correctly delay boot until "all devices" have been processed, as it is not
 504 clear what "all devices" means and when they have been found. This is in
 505 particular the case if USB hardware or network-attached hardware is used.
 506
 507 Modern software that requires some specific hardware (such as a network device
 508 or block device) to operate should only wait for the specific devices it needs
 509 to show up, and otherwise operate asynchronously initializing devices as they
 510 appear during boot and during runtime without delaying the boot process.
 511
 512 It is a defect of the software in question if it doesn't work this way, and
 513 still pulls systemd-udev-settle.service into the boot process.
 514
 515 Please file a bug report against the following units, with a request for it to
 516 be updated to operate in a hotplug fashion without depending on
 517 systemd-udev-settle.service:
 518
 519     @OFFENDING_UNITS@