Specifications

Data Replication
Description
steeleye-lighttpd process fails to start if Port 778 is in use
If a process is using Port 778 when steeleye-lighttpd starts up, steeleye-lighttpd fails causing a
failure to connect to the GUI.
Solution: Set the following tunable on all nodes in the cluster and then restart LifeKeeper on all the
nodes:
Add the following line to /etc/default/LifeKeeper:
API_SSL_PORT=port_number
where port_number is the new port to use.
Data Replication
Description
In symmetric active SDR configurations with significant I/O traffic on both servers, the
filesystem mounted on the netraid device (mirror) stops responding and eventually the
whole system hangs
Due to the single threaded nature of the Linux buffer cache, the buffer cache flushing daemon can
hang trying to flush out a buffer which needs to be committed remotely. While the flushing daemon
is hung, all activities in the Linux system with dirty buffers will stop if the number of dirty buffers
goes over the system accepted limit (set in/proc/sys/kernel/vm/bdflush).
Usually this is not a serious problem unless something happens to prevent the remote system from
clearing remote buffers (e.g. a network failure). LifeKeeper will detect a network failure and stop
replication in that event, thus clearing a hang condition. However, if the remote system is also
replicating to the local system (i.e. they are both symmetrically replicating to each other), they can
deadlock forever if they both get into this flushing daemon hang situation.
The deadlock can be released by manually killing the nbd-client daemons on both systems (which
will break the mirrors). To avoid this potential deadlock entirely, however, symmetric active
replication is not recommended.
GUI does not show proper state on SLES 10 SP2 system
This issue is due to a SLES 10 SP2 kernel bug and has been fixed in update kernel version
2.6.16.60-0.23. On SLES 10 SP2, netstat is broken due to a new format in /proc/<PID>/fd.
Solution:Please upgrade kernel version 2.6.16.60-0.23 if running on SLES 10 SP2.
Note: Beginning with SPS 8.1, when performing a kernel upgrade on RedHat Enterprise Linux
systems, it is no longer a requirement that the setup script (./setup) from the installation image
be rerun. Modules should be automatically available to the upgraded kernel without any intervention
as long as the kernel was installed from a proper RedHat package (rpm file).
SteelEye Protection Suite for Linux231