its been a while since we last spoke which to me is a good testiment to how reliable CrossRoads, however i do have a minor problem that popped up this morning.
Basically we have a linux box that is running fedora this is running XR 2.55 which serves as a load balancer for us for HTTP and HTTPS (dont panic i will post configs and logs shortly just want to explain whats going on first).
for no reason i can find other than one entry in a log file both of the XR services fell over today and refused to restart no matter what i tried, the entry i found in the log file is as follows.
- Code: Select all
2834385808 ERROR: Write/send failed: errno=104, Connection reset by peer, result=-1
not sure if this is the reason for the crash earlier today or not but this is all that i could find, there was no hint to a problem in /usr/log/messages and all previous files in there were also clear of XR errors.
here is our config file for XR (sensitive info removed).
- Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system>
<uselogger>true</uselogger>
<logdir>/tmp</logdir>
</system>
<service>
<name>web_http_IP_167</name>
<server>
<address>INTERNAL_IP:80</address>
<type>tcp</type>
<dispatchmode>first-available</dispatchmode>
<clienttimeout>60:60</clienttimeout>
<backendtimeout>60:60</backendtimeout>
</server>
<backend>
<address>62.254.243.69:80</address>
</backend>
<backend>
<address>89.151.84.163:80</address>
</backend>
<backend>
<address>127.0.0.1:81</address>
</backend>
</service>
<service>
<name>web_ssl_IP_167</name>
<server>
<address>INTERNAL_IP:443</address>
<type>tcp</type>
<dispatchmode>first-available</dispatchmode>
<clienttimeout>60:60</clienttimeout>
<backendtimeout>60:60</backendtimeout>
</server>
<backend>
<address>62.254.243.69:443</address>
</backend>
<backend>
<address>89.151.84.163:443</address>
</backend>
<backend>
<address>127.0.0.1:81</address>
</backend>
</service>
<configuration>
here is a copy of what gets generated from XR -V
- Code: Select all
XR version : 2.55
Written by : Karel Kubat <karel@kubat.nl>
Maintained by : Karel Kubat <karel@kubat.nl>
Primary site : http://crossroads.e-tunity.com
Compiled with : /usr/bin/g++
Optimization : -O3
System : Linux
Libraries : -L/usr/lib -lnsl -lpthread -lm
Type sizes : ssize_t=4, int=4, long=4, double=8, ptr=4
getopt.h : present
INADDR_NONE : present
getopt_long() : present
inet_aton() : present
strnstr() : absent
apart from it being an old version of XR I cannot really find a reason for the crash, we ended up having to reboot the linux box before XR would start again.
i was just hoping for some advice and answers to the questions below if possible.
1: how do i go about investigating a crash like within XR for future reference as having no reason for this sort of crash upsets my IT Manager.
2: what's the easiest way to upgrade from the version we are using now to the latest version and do we need to make any config file or server changes to accommodate this upgrade?
3: im still a very basic Linux user so i would appreciate any advice given made as clear as possible
that way i get the work done in one go and don't have to keep pestering everyone 
