1# Copyright (C) 2017-2021 Internet Systems Consortium, Inc. ("ISC") 2 3$NAMESPACE isc::ha 4 5% HA_BUFFER4_RECEIVE_FAILED buffer4_receive callout failed: %1 6This error message is issued when the callout for the buffer4_receive hook 7point failed. This may occur as a result of an internal server error. 8The argument contains a reason for the error. 9 10% HA_BUFFER4_RECEIVE_NOT_FOR_US %1: dropping query to be processed by another server 11This debug message is issued when the received DHCPv4 query is dropped 12by this server because it should be served by another server. This 13is the case when the remote server was designated to process the packet 14as a result of load balancing or because it is a primary server in the 15hot standby configuration. The argument provides client identification 16information retrieved from the query. 17 18% HA_BUFFER4_RECEIVE_PACKET_OPTIONS_SKIPPED an error unpacking an option, caused subsequent options to be skipped: %1 19A debug message issued when an option failed to unpack correctly, making it 20impossible to unpack the remaining options in the DHCPv4 query. The server 21will still attempt to service the packet. The sole argument provides a 22reason for unpacking error. 23 24% HA_BUFFER4_RECEIVE_UNPACK_FAILED failed to parse query from %1 to %2, received over interface %3, reason: %4 25This debug message is issued when received DHCPv4 query is malformed and 26can't be parsed by the buffer4_receive callout. The query will be 27dropped by the server. The first three arguments specify source IP address, 28destination IP address and the interface. The last argument provides a 29reason for failure. 30 31% HA_BUFFER6_RECEIVE_FAILED buffer6_receive callout failed: %1 32This error message is issued when the callout for the buffer6_receive hook 33point failed. This may occur as a result of an internal server error. 34The argument contains a reason for the error. 35 36% HA_BUFFER6_RECEIVE_NOT_FOR_US %1: dropping query to be processed by another server 37This debug message is issued when the received DHCPv6 query is dropped 38by this server because it should be served by another server. This 39is the case when the remote server was designated to process the packet 40as a result of load balancing or because it is a primary server in the 41hot standby configuration. The argument provides client identification 42information retrieved from the query. 43 44% HA_BUFFER6_RECEIVE_PACKET_OPTIONS_SKIPPED an error unpacking an option, caused subsequent options to be skipped: %1 45A debug message issued when an option failed to unpack correctly, making it 46impossible to unpack the remaining options in the DHCPv6 query. The server 47will still attempt to service the packet. The sole argument provides a 48reason for unpacking error. 49 50% HA_BUFFER6_RECEIVE_UNPACK_FAILED failed to parse query from %1 to %2, received over interface %3, reason: %4 51This debug message is issued when received DHCPv6 query is malformed and 52can't be parsed by the buffer6_receive callout. The query will be 53dropped by the server. The first three arguments specify source IP address, 54destination IP address and the interface. The last argument provides a 55reason for failure. 56 57% HA_COMMAND_PROCESSED_FAILED command_processed callout failed: %1 58This error message is issued when the callout for the command_processed hook 59point failed. The argument contains a reason for the error. 60 61% HA_COMMUNICATION_INTERRUPTED communication with %1 is interrupted 62This warning message is issued by the server which discovered that the 63communication to the active partner has been interrupted for a time 64period longer than the configured heartbeat-delay time. At this stage 65the server starts the failover procedure by monitoring the DHCP traffic 66sent to the partner and checking whether the partner server responds to 67this traffic. If the max-unacked-clients value is set to 0 such 68verification is disabled in which case the server will transition to 69the partner-down state. 70 71% HA_COMMUNICATION_INTERRUPTED_CLIENT4 %1: new client attempting to get a lease from the partner 72This informational message is issued when the surviving server observes 73a DHCP packet sent to the partner with which the communication is interrupted. 74The client whose packet is observed is not yet considered "unacked" because 75the secs field value does not exceed the configured threshold specified 76with max-ack-delay. 77 78% HA_COMMUNICATION_INTERRUPTED_CLIENT4_UNACKED %1: partner server failed to respond, %2 clients unacked so far, %3 clients left before transitioning to the partner-down state 79This informational message is issued when the surviving server determines 80that its partner failed to respond to the DHCP query and that this client 81is considered to not be served by the partner. The surviving server counts 82such clients and if the number of such clients exceeds the max-unacked-clients 83threshold, the server will transition to the partner-down state. The first 84argument contains client identification information. The second argument 85specifies the number of clients to which the server has failed to respond. 86The third argument specifies the number of additional clients which, if not 87provisioned, will cause the server to transition to the partner-down state. 88 89% HA_COMMUNICATION_INTERRUPTED_CLIENT6 %1: new client attempting to get a lease from the partner 90This informational message is issued when the surviving server observes 91a DHCP packet sent to the partner with which the communication is interrupted. 92The client whose packet is observed is not yet considered "unacked" because 93the elapsed time option value does not exceed the configured threshold 94specified with max-ack-delay. The sole argument specifies client 95identification information. 96 97% HA_COMMUNICATION_INTERRUPTED_CLIENT6_UNACKED %1: partner server failed to respond, %2 clients unacked so far, %3 clients left before transitioning to the partner-down state 98This informational message is issued when the surviving server determines 99that its partner failed to respond to the DHCP query and that this client 100is considered to not be served by the partner. The surviving server counts 101such clients and if the number of such clients exceeds the max-unacked-clients 102threshold, the server will transition to the partner-down state. The first 103argument contains client identification information. The second argument 104specifies the number of clients to which the server has failed to respond. 105The third argument specifies the number of additional clients which, if not 106provisioned, will cause the server to transition to the partner-down state. 107 108% HA_CONFIGURATION_FAILED failed to configure High Availability hooks library: %1 109This error message is issued when there is an error configuring the HA hooks 110library. The argument provides the detailed error message. 111 112% HA_CONFIGURATION_SUCCESSFUL HA hook library has been successfully configured 113This informational message is issued when the HA hook library configuration 114parser successfully parses and validates the new configuration. 115 116% HA_CONFIG_AUTO_FAILOVER_DISABLED auto-failover disabled for %1 117This warning message is issued to indicate that the 'auto-failover' parameter 118was administratively disabled for the specified server. The server will not 119automatically start serving partner's scope when the partner failure is detected. 120The server administrator will need to enable this scope manually by 121sending appropriate ha-scopes command. 122 123% HA_CONFIG_DHCP_MT_DISABLED HA multi-threading has been disabled, it cannot be enabled when Kea global multi-threading is disabled 124This informational message is issued when HA configuration has enabled 125multi-threading while Kea global configuration has multi-threading disabled. 126 127% HA_CONFIG_LEASE_SYNCING_DISABLED lease database synchronization between HA servers is disabled 128This warning message is issued when the lease database synchronization is 129administratively disabled. This is valid configuration if the leases are 130replicated between lease databases via some other mechanism, e.g. SQL 131database replication. 132 133% HA_CONFIG_LEASE_SYNCING_DISABLED_REMINDER bypassing SYNCING state because lease database synchronization is administratively disabled 134This informational message is issued as a reminder that lease database 135synchronization is administratively disabled and therefore the server 136transitions directly from the "waiting" to "ready" state. 137 138% HA_CONFIG_LEASE_UPDATES_AND_SYNCING_DIFFER unusual configuration where "send-lease-updates": %1 and "sync-leases": %2 139This warning message is issued when the configuration values of the 140send-lease-updates and sync-leases parameters differ. This may be a 141valid configuration but is unusual. Normally, if the lease database 142with replication is in use, both values are set to false. If a lease 143database without replication is in use (e.g. memfile), both values 144are set to true. Providing different values for those parameters means 145that an administrator either wants the server to not synchronize 146leases upon startup but later send lease updates to the partner, or 147the lease database should be synchronized upon startup, but no lease 148updates are later sent as a result of leases allocation. 149 150% HA_CONFIG_LEASE_UPDATES_DISABLED lease updates will not be generated 151This warning message is issued when the lease updates are administratively 152disabled. This is valid configuration if the leases are replicated to the 153partner's database via some other mechanism, e.g. SQL database replication. 154 155% HA_CONFIG_LEASE_UPDATES_DISABLED_REMINDER lease updates are administratively disabled and will not be generated while in %1 state 156This informational message is issued as a reminder that the lease updates 157are administratively disabled and will not be issued in the HA state to 158which the server has transitioned. The sole argument specifies the state 159into which the server has transitioned. 160 161% HA_CONFIG_SYSTEM_MT_UNSUPPORTED HA multi-threading has been disabled, auto-detection of thread support reports 0 162This informational message is issued when HA multi-threading configuration has 163specified auto-detection for the number of threads to use and the system 164reports the number of concurrent threads as 0. If you know your system can 165support multiple threads, then you may override this condition by specifying 166explicit values for http-listener-threads and http-client-threads. 167 168% HA_CONTINUE_HANDLER_FAILED ha-continue command failed: %1 169This error message is issued to indicate that the ha-continue command handler 170failed while processing the command. The argument provides the reason for 171failure. 172 173% HA_DEINIT_OK unloading High Availability hooks library successful 174This informational message indicates that the High Availability hooks library 175has been unloaded successfully. 176 177% HA_DHCP4_START_SERVICE_FAILED failed to start DHCPv4 HA service in dhcp4_srv_configured callout: %1 178This error message is issued when an attempt to start High Availability service 179for the DHCPv4 server failed in the dhcp4_srv_configured callout. This 180is internal server error and a bug report should be created. 181 182% HA_DHCP6_START_SERVICE_FAILED failed to start DHCPv4 HA service in dhcp6_srv_configured callout: %1 183This error message is issued when an attempt to start High Availability service 184for the DHCPv4 server failed in the dhcp4_srv_configured callout. This 185is internal server error and a bug report should be created. 186 187% HA_DHCP_DISABLE_COMMUNICATIONS_FAILED failed to send request to disable DHCP service of %1: %2 188This warning message indicates that there was a problem in communication with a 189HA peer while sending the dhcp-disable command. The first argument provides the 190remote server's name. The second argument provides a reason for failure. 191 192% HA_DHCP_DISABLE_FAILED failed to disable DHCP service of %1: %2 193This warning message indicates that a peer returned an error status code 194in response to a dhcp-disable command. The first argument provides the 195remote server's name. The second argument provides a reason for failure. 196 197% HA_DHCP_ENABLE_COMMUNICATIONS_FAILED failed to send request to enable DHCP service of %1: %2 198This warning message indicates that there was a problem in communication with a 199HA peer while sending the dhcp-enable command. The first argument provides the 200remote server's name. The second argument provides a reason for failure. 201 202% HA_DHCP_ENABLE_FAILED failed to enable DHCP service of %1: %2 203This warning message indicates that a peer returned an error status code 204in response to a dhcp-enable command. The first argument provides the 205remote server's name. The second argument provides a reason for failure. 206 207% HA_HEARTBEAT_COMMUNICATIONS_FAILED failed to send heartbeat to %1: %2 208This warning message indicates that there was a problem in communication with a 209HA peer while sending a heartbeat. This is a first sign that the peer may be 210down. The server will keep trying to send heartbeats until it considers that 211communication is interrupted. 212 213% HA_HEARTBEAT_FAILED heartbeat to %1 failed: %2 214This warning message indicates that a peer returned an error status code 215in response to a heartbeat. This is the sign that the peer may not function 216properly. The server will keep trying to send heartbeats until it considers 217that communication is interrupted. 218 219% HA_HEARTBEAT_HANDLER_FAILED heartbeat command failed: %1 220This error message is issued to indicate that the heartbeat command handler 221failed while processing the command. The argument provides the reason for 222failure. 223 224% HA_HIGH_CLOCK_SKEW %1, please synchronize clocks! 225This warning message is issued when the clock skew between the active servers 226exceeds 30 seconds. The HA service continues to operate but may not function 227properly, especially for low lease lifetimes. The administrator should 228should synchronize the clocks, e.g. using NTP. If the clock skew exceeds 22960 seconds, the HA service will terminate. 230 231% HA_HIGH_CLOCK_SKEW_CAUSES_TERMINATION %1, causing HA service to terminate 232This warning message is issued when the clock skew between the active servers 233exceeds 60 seconds. The HA service stops. The servers will continue to respond 234to the DHCP queries but won't exchange lease updates or send heartbeats. 235The administrator is required to synchronize the clocks and then restart the 236servers to resume the HA service. 237 238% HA_INIT_OK loading High Availability hooks library successful 239This informational message indicates that the High Availability hooks library 240has been loaded successfully. 241 242% HA_INVALID_PARTNER_STATE_COMMUNICATION_RECOVERY partner is in the communication-recovery state unexpectedly 243This warning message is issued when a partner is in the communication-recovery 244state, and this server is not running in the load balancing mode. The server 245may only transition to the communication-recovery state when it runs in the 246load balancing mode. The HA mode of both servers must be the same. 247 248% HA_INVALID_PARTNER_STATE_HOT_STANDBY partner is in the hot-standby state unexpectedly 249This warning message is issued when a partner is in the hot-standby state, 250and this server is not running in the hot standby mode. The server may only 251transition to the hot-standby state when it runs in the hot standby mode. 252The HA mode of both servers must be the same. 253 254% HA_INVALID_PARTNER_STATE_LOAD_BALANCING partner is in the load-balancing state unexpectedly 255This warning message is issued when a partner is in the load-balancing state, 256and this server is not running in the load balancing mode. The server may only 257transition to the load-balancing state when it runs in the load balancing mode. 258The HA mode of both servers must be the same. 259 260% HA_LEASES4_COMMITTED_FAILED leases4_committed callout failed: %1 261This error message is issued when the callout for the leases4_committed hook 262point failed. This includes unexpected errors like wrong arguments provided to 263the callout by the DHCP server (unlikely internal server error). 264The argument contains a reason for the error. 265 266% HA_LEASES4_COMMITTED_NOTHING_TO_UPDATE %1: leases4_committed callout was invoked without any leases 267This debug message is issued when the "leases4_committed" callout returns 268because there are neither new leases nor deleted leases for which updates 269should be sent. The sole argument specifies the details of the client 270which sent the packet. 271 272% HA_LEASES6_COMMITTED_FAILED leases6_committed callout failed: %1 273This error message is issued when the callout for the leases6_committed hook 274point failed. This includes unexpected errors like wrong arguments provided to 275the callout by the DHCP server (unlikely internal server error). 276The argument contains a reason for the error. 277 278% HA_LEASES6_COMMITTED_NOTHING_TO_UPDATE %1: leases6_committed callout was invoked without any leases 279This debug message is issued when the "leases6_committed" callout returns 280because there are neither new leases nor deleted leases for which updates 281should be sent. The sole argument specifies the details of the client 282which sent the packet. 283 284% HA_LEASES_BACKLOG_COMMUNICATIONS_FAILED failed to communicate with %1 while sending lease updates backlog: %2 285This error message is issued to indicate that there was a communication error 286with a partner server while sending outstanding lease updates after resuming 287connection. The second argument contains a reason for the error. 288 289% HA_LEASES_BACKLOG_FAILED failed to send lease updates backlog to %1: %2 290This error message is issued to indicate that sending lease updates backlog 291to a partner server failed. The lease updates backlog is sent to the partner 292after resuming temporarily broken communication with the partner. If this 293operation fails the server will transition to the waiting state to initiate 294full lease database synchronization. 295 296% HA_LEASES_BACKLOG_NOTHING_TO_SEND no leases in backlog after communication recovery 297This informational message is issued when there are no outstanding leases to 298be sent after communication recovery with a partner. This means that the 299communication interruption was short enough that no DHCP clients obtained 300any leases from the server while it was in the communication-recovery state. 301The server may now transition to the load-balancing state. 302 303% HA_LEASES_BACKLOG_START starting to send %1 outstanding lease updates to %2 304This informational message is issued when the server starts to send outstanding 305lease updates to the partner after resuming communications. The first argument 306specifies the number of lease updates to be sent. The name of the partner is 307specified with the second argument. 308 309% HA_LEASES_BACKLOG_SUCCESS sending lease updates backlog to %1 successful in %2 310This informational message is issued when server successfully completes 311sending lease updates backlog to the partner. The first argument specifies the 312name of the remote server. The second argument specifies the duration of 313this operation. 314 315% HA_LEASES_SYNC_COMMUNICATIONS_FAILED failed to communicate with %1 while syncing leases: %2 316This error message is issued to indicate that there was a communication error 317with a partner server while trying to fetch leases from its lease database. 318The argument contains a reason for the error. 319 320% HA_LEASES_SYNC_FAILED failed to synchronize leases with %1: %2 321This error message is issued to indicate that there was a problem while 322parsing a response from the server from which leases have been fetched for 323local database synchronization. The argument contains a reason for the error. 324 325% HA_LEASES_SYNC_LEASE_PAGE_RECEIVED received %1 leases from %2 326This informational message is issued during lease database synchronization 327to indicate that a bulk of leases have been received. The first argument 328holds the count of leases received. The second argument specifies the 329partner server name. 330 331% HA_LEASE_SYNC_FAILED synchronization failed for lease: %1, reason: %2 332This warning message is issued when creating or updating a lease in the 333local lease database fails. The lease information in the JSON format is 334provided as a first argument. The second argument provides a reason for 335the failure. 336 337% HA_LEASE_SYNC_STALE_LEASE4_SKIP skipping stale lease %1 in subnet %2 338This debug message is issued during lease database synchronization, when 339fetched IPv4 lease instance appears to be older than the instance in the 340local database. The newer instance is left in the database and the fetched 341lease is dropped. The remote server will still hold the older lease instance 342until it synchronizes its database with this server. The first argument specifies 343leased address. The second argument specifies a subnet to which the lease 344belongs. 345 346% HA_LEASE_SYNC_STALE_LEASE6_SKIP skipping stale lease %1 in subnet %2 347This debug message is issued during lease database synchronization, when 348fetched IPv6 lease instance appears to be older than the instance in the 349local database. The newer instance is left in the database and the fetched 350lease is dropped. The remote server will still hold the older lease instance 351until it synchronizes its database with this server. The first argument specifies 352leased address. The second argument specifies a subnet to which the lease 353belongs. 354 355% HA_LEASE_UPDATES_DISABLED lease updates will not be sent to the partner while in %1 state 356This informational message is issued to indicate that lease updates will 357not be sent to the partner while the server is in the current state. The 358argument specifies the server's current state name. The lease updates 359are still sent to the backup servers if they are configured but any 360possible errors in communication with the backup servers are ignored. 361 362% HA_LEASE_UPDATES_ENABLED lease updates will be sent to the partner while in %1 state 363This informational message is issued to indicate that lease updates will 364be sent to the partner while the server is in the current state. The 365argument specifies the server's current state name. 366 367% HA_LEASE_UPDATE_COMMUNICATIONS_FAILED %1: failed to communicate with %2: %3 368This warning message indicates that there was a problem in communication with a 369HA peer while processing a DHCP client query and sending lease update. The 370client's DHCP message will be dropped. 371 372% HA_LEASE_UPDATE_CREATE_UPDATE_FAILED_ON_PEER %1: failed to create or update the lease having type %2 for address %3, reason: %4 373This informational message is issued when one of the leases failed to be 374created or updated on the HA peer while processing the lease updates sent 375from this server. This may indicate an issue with communication between 376the peer and its lease database. 377 378% HA_LEASE_UPDATE_DELETE_FAILED_ON_PEER %1: failed to delete the lease having type %2 for address %3, reason: %4 379This informational message is issued when one of the leases failed to delete 380on the HA peer while processing lease updates sent from this server. Typically, 381the lease fails to delete when it doesn't exist in the peer's database. 382 383% HA_LEASE_UPDATE_FAILED %1: lease update to %2 failed: %3 384This warning message indicates that a peer returned an error status code 385in response to a lease update. The client's DHCP message will be dropped. 386 387% HA_LOAD_BALANCING_DUID_MISSING load balancing failed for the DHCPv6 message (transaction id: %1) because DUID is missing 388This debug message is issued when the HA hook library was unable to load 389balance an incoming DHCPv6 query because neither client identifier nor 390HW address was included in the query. The query will be dropped. The 391sole argument contains transaction id. 392 393% HA_LOAD_BALANCING_IDENTIFIER_MISSING load balancing failed for the DHCPv4 message (transaction id: %1) because HW address and client identifier are missing 394This debug message is issued when the HA hook library was unable to load 395balance an incoming DHCPv4 query because neither client identifier nor 396HW address was included in the query. The query will be dropped. The 397sole argument contains transaction id. 398 399% HA_LOCAL_DHCP_DISABLE local DHCP service is disabled while the %1 is in the %2 state 400This informational message is issued to indicate that the local DHCP service 401is disabled because the server remains in a state in which the server 402should not respond to DHCP clients, e.g. the server hasn't synchronized 403its lease database. The first argument specifies server name. The second 404argument specifies server's state. 405 406% HA_LOCAL_DHCP_ENABLE local DHCP service is enabled while the %1 is in the %2 state 407This informational message is issued to indicate that the local DHCP service 408is enabled because the server remains in a state in which it should 409respond to the DHCP clients. The first argument specifies server name. 410The second argument specifies server's state. 411 412% HA_MAINTENANCE_CANCEL_HANDLER_FAILED ha-maintenance-cancel command failed: %1 413This error message is issued to indicate that the ha-maintenance-cancel command 414handler failed while processing the command. The argument provides the reason for 415failure. 416 417% HA_MAINTENANCE_NOTIFY_CANCEL_COMMUNICATIONS_FAILED failed to send ha-maintenance-notify to %1 in attempt to cancel its maintenance: %2 418This warning message indicates that there was a problem in communication with a 419HA peer while sending the ha-maintenance-notify command with the cancel flag 420set to true. The first argument provides the remote server's name. The second 421argument provides a reason for failure. 422 423% HA_MAINTENANCE_NOTIFY_CANCEL_FAILED error returned while processing ha-maintenance-notify by %1 in attempt to cancel its maintenance: %2 424This warning message indicates that a peer returned an error status code 425in response to a ha-maintenance-notify command with the cancel flag set to 426true. The first argument provides the remote server's name. The second 427argument provides a reason for failure. 428 429% HA_MAINTENANCE_NOTIFY_COMMUNICATIONS_FAILED failed to send ha-maintenance-notify to %1: %2 430This warning message indicates that there was a problem in communication with a 431HA peer while sending the ha-maintenance-notify command. The first argument provides the 432remote server's name. The second argument provides a reason for failure. 433 434% HA_MAINTENANCE_NOTIFY_FAILED error returned while processing ha-maintenance-notify by %1: %2 435This warning message indicates that a peer returned an error status code 436in response to a ha-maintenance-notify command. The first argument provides the 437remote server's name. The second argument provides a reason for failure. 438 439% HA_MAINTENANCE_NOTIFY_HANDLER_FAILED ha-maintenance-notify command failed: %1 440This error message is issued to indicate that the ha-maintenance-notify command 441handler failed while processing the command. The argument provides the reason for 442failure. 443 444% HA_MAINTENANCE_SHUTDOWN_SAFE the server can now be shutdown for maintenance as the partner has taken over the DHCP traffic 445This informational message is displayed after the server transitions to the 446in-maintenance state. This server no longer responds to any DHCP queries and its 447partner - in partner-in-maintenance state - has taken over the DHCP traffic. 448When the server in-maintenance state is shut down, the partner moves to 449the partner-down state immediately. 450 451% HA_MAINTENANCE_STARTED the server is now in the partner-in-maintenance state and the partner is in-maintenance state 452This informational message is displayed when the server receiving the 453ha-maintenance-start command transitions to the partner-in-maintenance 454state. The server does it after sending the ha-maintenance-notify to 455its partner to put the partner in the in-maintenance state. From now on, 456the server in the partner-in-maintenance state will be responding to all 457queries and the partner will respond to no queries. The partner may be 458safely shut down for maintenance in which case this server will 459automatically transition from the partner-in-maintenance state to the 460partner-down state. 461 462% HA_MAINTENANCE_STARTED_IN_PARTNER_DOWN the server is now in the partner-down mode as a result of requested maintenance 463This informational message is displayed when the server receiving the 464ha-maintenance-start command transitions to the partner-down state 465because it was unable to communicate with the partner while receiving 466the command. It is assumed that in such situation the partner is 467already offline for the maintenance. Note that in this case the 468normal failover procedure does not take place. The server does not wait 469for a heartbeat to fail several times, nor it monitors the DHCP traffic 470for not responded queries. In the maintenance case the server transitions 471to the partner-down state when it first encounters a communication 472problem with the partner. 473 474% HA_MAINTENANCE_START_HANDLER_FAILED ha-maintenance-start command failed: %1 475This error message is issued to indicate that the ha-maintenance-start command 476handler failed while processing the command. The argument provides the reason for 477failure. 478 479% HA_MISSING_CONFIGURATION high-availability parameter not specified for High Availability hooks library 480This error message is issued to indicate that the configuration for the 481High Availability hooks library hasn't been specified. The 'high-availability' 482parameter must be specified for the hooks library to load properly. 483 484% HA_PAUSE_CLIENT_LISTENER_FAILED Pausing multi-threaded HTTP processing failed: %1 485This error message is emitted when attempting to pause HA's HTTP client and 486listener threads. This error is highly unlikely and indicates a programmatic 487issue that should be reported as a defect. 488 489% HA_PAUSE_CLIENT_LISTENER_ILLEGAL Pausing multi-threaded HTTP processing failed: %1 490This error message is emitted when attempting to pause HA's HTTP client or 491listener thread pools from a worker thread. This error indicates that a command 492run on the listener threads is trying to use a critical section which would 493result in a dead-lock. 494 495% HA_RESET_COMMUNICATIONS_FAILED failed to send ha-reset command to %1: %2 496This warning message indicates a problem with communication with a HA peer 497while sending the ha-reset command. The first argument specifies a remote 498server name. The second argument specifies a reason for failure. 499 500% HA_RESET_FAILED failed to reset HA state machine of %1: %2 501This warning message indicates that a peer returned an error status code 502in response to the ha-reset command. The first argument specifies a 503remote server name. The second argument specifies a reason for failure. 504 505% HA_RESET_HANDLER_FAILED ha-reset command failed: %1 506This error message is issued to indicate that the ha-reset command handler 507failed while processing the command. The argument provides the reason for 508failure. 509 510% HA_RESUME_CLIENT_LISTENER_FAILED Resuming multi-threaded HTTP processing failed: %1 511This error message is emitted when attempting to resume HA's HTTP client and 512listener threads. This error is highly unlikely and indicates a programmatic 513issue that should be reported as a defect. 514 515% HA_SCOPES_HANDLER_FAILED ha-scopes command failed: %1 516This error message is issued to indicate that the ha-scopes command handler 517failed while processing the command. The argument provides reason for 518the failure. 519 520% HA_SERVICE_STARTED started high availability service in %1 mode as %2 server 521This informational message is issued when the HA service is started as a result 522of server startup or reconfiguration. The first argument provides the HA mode. 523The second argument specifies the role of this server instance in this 524configuration. 525 526% HA_STATE_MACHINE_CONTINUED state machine is un-paused 527This informational message is issued when the HA state machine is un-paused. 528This unlocks the server from the current state. It may transition to any 529other state if it needs to do so, e.g. 'partner-down' if its partner appears 530to be offline. The server may also remain in the current state if the HA 531setup state warrants such behavior. 532 533% HA_STATE_MACHINE_PAUSED state machine paused in state %1 534This informational message is issued when the HA state machine is paused. 535HA state machine may be paused in certain states specified in the HA hooks library 536configuration. When the state machine is paused, the server remains in the given 537state until it is explicitly unpaused (via the ha-continue command). If the state 538machine is paused, the server operates normally but cannot transition to any 539other state. 540 541% HA_STATE_TRANSITION server transitions from %1 to %2 state, partner state is %3 542This informational message is issued when the server transitions to a new 543state as a result of some interaction (or lack of thereof) with its partner. 544The arguments specify initial server state, new server state and the partner's 545state. 546 547% HA_STATE_TRANSITION_PASSIVE_BACKUP server transitions from %1 to %2 state 548This informational message is issued when the server in passive-backup 549mode transitions to a new state. The arguments specify initial server state and 550a new server state. 551 552% HA_SYNC_COMPLETE_NOTIFY_COMMUNICATIONS_FAILED failed to send ha-sync-complete-notify to %1: %2 553This warning message indicates that there was a problem in communication with an 554HA peer while sending the ha-sync-complete-notify command. The first argument 555provides the remote server's name. The second argument provides a reason for 556failure. 557 558% HA_SYNC_COMPLETE_NOTIFY_FAILED error processing ha-sync-complete-notify command on %1: %2 559This warning message indicates that a peer returned an error status code 560in response to the ha-sync-complete-notify command. The first argument provides 561the remote server's name. The second argument provides a reason for failure. 562 563% HA_SYNC_COMPLETE_NOTIFY_HANDLER_FAILED ha-sync-complete-notify command failed: %1 564This error message is issued to indicate that the ha-sync-complete-notify command 565handler failed while processing the command. The argument provides the reason for 566failure. 567 568% HA_SYNC_FAILED lease database synchronization with %1 failed: %2 569This error message is issued to indicate that the lease database synchronization 570failed. The first argument provides the partner server's name. The second argument 571provides a reason for the failure. 572 573% HA_SYNC_HANDLER_FAILED ha-sync command failed: %1 574This error message is issued to indicate that the ha-sync command handler 575failed while processing the command. The argument provides the reason for 576failure. 577 578% HA_SYNC_START starting lease database synchronization with %1 579This informational message is issued when the server starts lease database 580synchronization with a partner. The name of the partner is specified with the 581sole argument. 582 583% HA_SYNC_SUCCESSFUL lease database synchronization with %1 completed successfully in %2 584This informational message is issued when the server successfully completed 585lease database synchronization with the partner. The first argument specifies 586the name of the partner server. The second argument specifies the duration of 587the synchronization. 588 589% HA_TERMINATED HA service terminated due to an unrecoverable condition. Check previous error message(s), address the problem and restart! 590This error message is issued to indicate that the HA service has been stopped 591due to an unacceptable condition (e.g. too large of a clock skew). The exact 592cause should appear in a previous error message. Address the condition 593reported then restart the servers to resume service. 594 595% HA_TERMINATED_RESTART_PARTNER waiting for the partner in the TERMINATED state to be restarted 596This informational message is issued when the server has been restarted after 597correcting the clock skew. The partner server is still in the terminated 598state. The partner must be restarted before the server can synchronize the 599database and start normal operation. 600