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