You are here: Troubleshooting > Administration Messages

Administration Messages

The following important administration messages are produced by LifeKeeper.

lifekeeper: can’t get service lcm_server, protocol tcp

When LifeKeeper is installed, a line (lcm_server<tab>7365/tcp) is added to the /etc/services file. If for any  reason the LifeKeeper communication module (lcm) cannot find this required line in the file, this message is printed. Check the /etc/services file and either reinstall LifeKeeper or add the required line to the file.


lifekeeper: can’t get host name system_name

The LifeKeeper communication module (lcm) could not find the system name in the /etc/hosts file. This could happen if a TCP communications path to another system, over /dev/tcp, was being set up and the /etc/hosts file did not have the address of the other system. Be sure the name of the other system was typed correctly. If so, add the address to the /etc/hosts file. Be sure you can ping the specified host.


***FATAL*** process_name[line#,init.c] date: wait period of 300 seconds for LCM to become available has been exceeded (lock file"/tmp/LCM_IS_UNAVAIL" not removed)

LifeKeeper failed to initialize properly because lcm did not come up after a given wait period. Stop LifeKeeper and try restarting it. If the same message is printed again, remove LifeKeeper and reinstall it. If the message persists, contact your authorized LifeKeeper support organization.


***FATAL*** process_name[line#,lock.c] date; can’t initialize semaphores without LCD daemon running: No such file or directory


***ERROR*** process_name[line#,lock.c] date; can’t wait for semaphores:Invalid argument


***ERROR*** process_name[line#,lock.c] date; semctl: Invalid argument

The system was shut down, or LifeKeeper was stopped before LifeKeeper had initialized properly (that is, before lifekeeper: RESOURCE PROTECTION NOW ACTIVATED was printed). Stop LifeKeeper by entering

/opt/LifeKeeper/bin/lkstop -n.

Then reboot the system and restart LifeKeeper.


***ERROR*** process_name[line#,net.c] date: no response heard from system "system_name" on TTY port "port_name" to reply box "box_name" in #secs seconds.

There was a problem with the TTY communications path using this port.  However, the message will be re-sent over the TCP path. Make sure that the baud rate is not set higher than 9600 baud. Test the TTY port connection by first deleting the communications path and then using the portio(1M) command. If the port is not functioning properly, delete this communications path and use another port (this will involve changing cables).


***ERROR*** process_name[line#,mes.c] date: destination system"system_name" is dead.

A process could not communicate with the named system. If any of the following three conditions is true, this message is informational and should be ignored:

1. LifeKeeper is not running on the named system.

2. LifeKeeper is running on the named system, but all the paths are not marked ALIVE.

3. The named system is down.

If none of these three conditions is true, contact your authorized LifeKeeper support organization.


***FATAL*** process_name[line#,base.c] date: index index# past range 0-#ondx=#

As a result of a timing bug during initialization, a process did not get semaphores and ended up in a race condition with another process. Stop LifeKeeper by entering /opt/LifeKeeper/bin/lkstop -n. Then reboot the system and restart LifeKeeper. If this condition persists, contact your support organization.



This informational message requires no action.


lifekeeper: communication to system_name by device_name FAILED at: date

A heartbeat has been missed over the given communications path. If the device name is /dev/tcp, the TCP communications path has failed; if the device name is /dev/tty0[01], the TTY communications path has failed.

There are cases where this message is to be expected. For example, when one system is shut down, the other system will print this message because the communications path has obviously disappeared.

If this failure message is followed by a RESTORED message, then there is no cause for concern; a heartbeat was skipped, and then restored. However, if LifeKeeper is running on both systems and there is no RESTORED message, then the particular communications path (TTY or TCP) has failed.

If the TCP path has failed, examine the status of the network. If the network is down, it needs to be restored to service. If the TTY path has failed, make sure the baud rate is no higher than 9600. Also, diagnose the physical port, and if necessary, change to another port.

It may also be an indication of problems if the pair of FAILED and RESTORED messages occurs frequently.


***ERROR*** process_name[line#,mes.c] date: func_name:::receive(300) did not receive message within 300 seconds on incoming_mailbox box_name

A communications path (TTY or TCP) has failed. This normally occurs when a process sends a message and, due to a switchover, no response is received.  When one communications path fails, the message is resent using the other path. Therefore, no action is necessary when only one of these messages is printed. If there are multiple messages, and no switchover is initiated, both communications paths have failed. Try to re-establish both of them. If you are unsuccessful, contact your authorized LifeKeeper support organization.

© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.