Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

we have a database server MySQL 5.1 on it. Every two days it "stops" responding.

The following happens:

  • it doesn't respond to ping
  • we can't login with SSH
  • we don't get any answer from MySQL
  • there is no entry in the error logs! neither from linux neither from MySQL.
  • we have already changed to a completely new hardware, we have the same problem, so it's definitely not a hardware problem.
  • we do not have any other software installed except a firewall (iptables rule)
  • we can restart the server from another server using rsyslog (www.rsyslog.com)(software reset)

Our system parameters and settings: - System-Memory: 12GB - Processor: Intel 7-920 Quadcore - Operating system: Debian 5 (lenny) 64bit - MySQL 5.1.49

The firewall script is below

# Generated Manually
*filter
:FORWARD ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:MyChain - [0:0]
# -A OUTPUT -o eth0 -j LOG  --log-level 7 --log-prefix BANDWIDTH_OUT:
-A MyChain -i lo -j ACCEPT
-A MyChain -p tcp -m tcp -m state -i eth0 --dport 22 --state NEW -j ACCEPT
-A MyChain -p tcp -m tcp -m state -i eth0 --dport 10000 --state NEW -j ACCEPT
-A MyChain -p tcp -m tcp -m state -i eth0 --dport 80 --state NEW -j ACCEPT

# Allow access to mysql from web1
-A MyChain -p tcp -m tcp -m state -s web1.ip -i eth0 --dport 3306 --state NEW -j ACCEPT

# Allow access to mysql from web2
-A MyChain -p tcp -m tcp -m state -s web2.ip -i eth0 --dport 3306 --state NEW -j ACCEPT

# Allow access to mysql from web2
-A MyChain -p tcp -m tcp -m state -s web3.ip -i eth0 --dport 3306 --state NEW -j ACCEPT

-A MyChain -p icmp --icmp-type 0 -j ACCEPT
-A MyChain -p icmp --icmp-type 3 -j ACCEPT
-A MyChain -p icmp --icmp-type 11 -j ACCEPT
-A MyChain -p icmp --icmp-type 8 -m limit --limit 1/second -j ACCEPT
-A INPUT -j MyChain
-A FORWARD -j MyChain
-A MyChain -m state -i eth0 --state ESTABLISHED,RELATED -j ACCEPT
-A MyChain -j REJECT
COMMIT
# Completed
*mangle
:FORWARD ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed
*nat
:OUTPUT ACCEPT [0:0]
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed

The script is started after from the /etc/network/interfaces I replaced the real-ip addresses with spaces...

# Loopback device: auto lo iface lo inet loopback # device: eth0 auto eth0 iface eth0 inet static address ---.--.--.--- broadcast ---.--.--.--- netmask ---.--.--.--- gateway ---.--.--.--- # default route to access subnet up route add -net ---.--.--.--- netmask ---.--.--.--- gw ---.--.--.--- eth0 post-up iptables-restore

Could someone help me with this please ? Thanks. Max.

share|improve this question
    
With "completely new hardware" do you mean "the same server model, but the vendor brought as a completely new box" or "the hardware really is different than it was last time"? Does the freeze happen exactly after the same uptime? –  Janne Pikkarainen Sep 15 '10 at 8:25
    
Sounds to me like it loses its IP address. Is there maybe a DHCP client running on eth0? Or something else interfering with the static IP address assignment? –  wolfgangsz Sep 15 '10 at 8:55
    
With new hardware i mean, same model but new box. The freeze has to do something with the amount of traffic.When we had low traffic it worked well. Now that the the traffic grown several times it freezes every 2 days sometimes 1 day. –  maximus Sep 15 '10 at 14:23

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.