Results 1 to 12 of 12
  1. #1

    [help] system getting hanged (Cent OS)

    Well I happen to have a system operating on cent OS...its got APF with BFD installed...along with a BOA server...it happens to hang automatically after almost every 24 hrs..its been happening for the past month or so...been using the system for more than a year now and never before the problem been surfaced..also using cPanel. Any help to sort out the issue, I would be grateful...thank you and merry Christmas.

  2. #2
    Join Date
    Apr 2002
    Location
    Auckland - New Zealand
    Posts
    1,572
    What logs have you checked?

    Hanged, I assume means the server locks up and needs to be rebooted, check your logs for the time of the crash, quite honestly it could be anything, bad ram, bad drive, evil scripts, kernel panic, overheating - Have a good look through the systems logs and see if you can see anything there first.
    Last edited by StevenG; 12-24-2006 at 07:49 AM.

  3. #3
    Have same issue here, Centos 4.4 x86_64, tyan motehrboard, dual xeon 265, 3ware raid controler, 4 gigs of ram, 2.6.9-42.0.3ELsmp kernel, machine was stable for a two months, now it restarts it self every day or two in random times, i see nothing in logs what can point me what is going on.

  4. #4
    Join Date
    Apr 2004
    Location
    Singapore
    Posts
    1,506
    Quote Originally Posted by gemby
    Have same issue here, Centos 4.4 x86_64, tyan motehrboard, dual xeon 265, 3ware raid controler, 4 gigs of ram, 2.6.9-42.0.3ELsmp kernel, machine was stable for a two months, now it restarts it self every day or two in random times, i see nothing in logs what can point me what is going on.
    Check whether the motherboard temperature is ok or fan is not working, first thing come to my mind.
    tanfwc
    Singapore Managed Colocation
    Singapore BGP Announcement

  5. #5
    Join Date
    Mar 2003
    Location
    Saint Paul, MN
    Posts
    826
    At the risk of sounding like a broken record, try compiling a custom kernel with preemption disabled. Fixes nearly all CentOS problems like this, from what I've seen.
    redpin.com - offering amazingly competent email, dns, and web hosting since 2002... because someone has to!
    Because Simple Things Should Be Simple - YouCANHasDNS

  6. #6
    Quote Originally Posted by tanfwc
    Check whether the motherboard temperature is ok or fan is not working, first thing come to my mind.
    I checked it first, no this is not a case, temps are all ok, vents also.

  7. #7
    Quote Originally Posted by Ankheg
    At the risk of sounding like a broken record, try compiling a custom kernel with preemption disabled. Fixes nearly all CentOS problems like this, from what I've seen.
    Oh, this sounds like posible solution, have some links in stories with centos similar to mine?

  8. #8
    Quote Originally Posted by Ankheg
    At the risk of sounding like a broken record, try compiling a custom kernel with preemption disabled. Fixes nearly all CentOS problems like this, from what I've seen.
    I compiled vanilla 2.6.19.1 from source using centos .config, doublechecked that preeemption is disabled ( it is by default now), other thing that worried me before was old 3ware driver in centos kernel, so this is both fixed now. Machine is rebooted, machine is online again, will see if it helps. Thank you for pointing me out.

  9. #9
    well after facing a hanged system frequently..I recompiled the kernel and upgraded to the latest one..but the problem is still occuring

    These are the last messages before system restart

    Code:
    Dec 24 23:42:12 server1 named[6909]: lame server resolving '201.160.178.190.cableonline.com.mx' (in 'cableonline.com.MX'?): 201.134.141.211#53
    Dec 25 00:52:38 server1 named[6909]: lame server resolving 'ld.so' (in 'so'?): 205.166.226.38#53
    Dec 25 01:36:37 server1 named[6909]: lame server resolving '90.101.56.124.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 02:35:36 server1 named[6909]: client 152.160.1.3#4668: error sending response: host unreachable
    Dec 25 02:35:40 server1 last message repeated 2 times
    Dec 25 03:07:11 server1 sshd(pam_unix)[7596]: session closed for user root
    Dec 25 03:49:14 server1 sshd(pam_unix)[32447]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:18 server1 sshd(pam_unix)[32451]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:22 server1 sshd(pam_unix)[32453]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:27 server1 sshd(pam_unix)[32456]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:31 server1 sshd(pam_unix)[32458]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:33 server1 sshd(pam_unix)[32460]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:36 server1 sshd(pam_unix)[32462]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:37 server1 sshd(pam_unix)[32464]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:40 server1 sshd(pam_unix)[32466]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:42 server1 sshd(pam_unix)[32468]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:44 server1 sshd(pam_unix)[32471]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:46 server1 sshd(pam_unix)[32473]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:48 server1 sshd(pam_unix)[32475]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:49 server1 sshd(pam_unix)[32477]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:50 server1 sshd(pam_unix)[32479]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:51 server1 sshd(pam_unix)[32481]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:52 server1 sshd(pam_unix)[32483]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:52 server1 sshd(pam_unix)[32485]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:53 server1 sshd(pam_unix)[32487]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:55 server1 sshd(pam_unix)[32490]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:56 server1 sshd(pam_unix)[32492]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:56 server1 sshd(pam_unix)[32496]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:57 server1 sshd(pam_unix)[32498]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:58 server1 sshd(pam_unix)[32501]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:49:59 server1 sshd(pam_unix)[32503]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:50:00 server1 sshd(pam_unix)[32506]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:50:01 server1 sshd(pam_unix)[32508]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:50:01 server1 sshd(pam_unix)[32512]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:50:02 server1 sshd(pam_unix)[32514]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:50:04 server1 sshd(pam_unix)[32583]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=202.82.148.27  user=root
    Dec 25 03:50:04 server1 BFD(32528): {sshd} 202.82.148.27 exceeded login failures; executed ban command '/etc/apf/apf -d 202.82.148.27 {bfd.sshd}'.
    Dec 25 04:02:40 server1 mod_evasive[32493]: Blacklisting address 68.8.251.159: possible attack.
    Dec 25 04:07:16 server1 named[6909]: lame server resolving '46.41.155.198.in-addr.arpa' (in '155.198.in-addr.arpa'?): 198.155.167.248#53
    Dec 25 04:07:16 server1 named[6909]: lame server resolving '46.41.155.198.in-addr.arpa' (in '155.198.in-addr.arpa'?): 198.155.223.8#53
    Dec 25 04:07:16 server1 named[6909]: lame server resolving '46.41.155.198.in-addr.arpa' (in '155.198.in-addr.arpa'?): 198.155.167.250#53
    Dec 25 04:48:07 server1 named[6909]: lame server resolving '117.94.104.142.in-addr.arpa' (in '104.142.in-addr.arpa'?): 199.60.118.2#53
    Dec 25 04:49:58 server1 named[6909]: lame server resolving '249.32.182.85.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 04:50:57 server1 named[6909]: lame server resolving '164.21.4.122.iadb.isipp.com' (in 'iadb.isipp.com'?): 66.223.40.121#53
    Dec 25 04:54:01 server1 mod_evasive[2717]: Blacklisting address 190.40.118.53: possible attack.
    Dec 25 05:31:40 server1 named[6909]: lame server resolving '161.255.24.133.in-addr.arpa' (in '255.24.133.in-addr.arpa'?): 133.24.252.1#53
    Dec 25 05:31:42 server1 named[6909]: lame server resolving '161.255.24.133.in-addr.arpa' (in '255.24.133.in-addr.arpa'?): 61.44.129.12#53
    Dec 25 05:31:48 server1 named[6909]: lame server resolving 'cpan.dcc.uchile.cl' (in 'dcc.uchile.CL'?): 200.89.70.3#53
    Dec 25 07:05:14 server1 named[6909]: lame server resolving '193.175.226.209.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 08:58:52 server1 named[6909]: lame server resolving '238.84.2.87.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 09:15:40 server1 named[6909]: lame server resolving '70.127.203.81.list.dsbl.org' (in 'dsbl.ORG'?): 204.13.249.82#53
    Dec 25 09:15:40 server1 named[6909]: lame server resolving '70.127.203.81.list.dsbl.org' (in 'dsbl.ORG'?): 63.208.196.93#53
    Dec 25 09:24:38 server1 named[6909]: client 193.251.90.92#1234: error sending response: host unreachable
    Dec 25 09:41:35 server1 named[6909]: lame server resolving '53.219.30.226.in-addr.arpa' (in '226.in-addr.arpa'?): 192.52.71.4#53
    Dec 25 09:46:39 server1 named[6909]: lame server resolving '53.143.252.82.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 10:27:14 server1 named[6909]: lame server resolving '144.36.80.68.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 10:46:45 server1 mod_evasive[28180]: Blacklisting address 210.212.45.144: possible attack.
    Dec 25 10:46:45 server1 mod_evasive[8928]: Blacklisting address 210.212.45.144: possible attack.
    Dec 25 11:27:40 server1 named[6909]: lame server resolving '38.188.153.141.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 11:44:40 server1 named[6909]: client 202.156.1.46#1434: error sending response: host unreachable
    Dec 25 11:45:20 server1 last message repeated 10 times
    Dec 25 12:00:34 server1 last message repeated 2 times
    Dec 25 12:01:13 server1 last message repeated 5 times
    Dec 25 13:44:53 server1 named[6909]: lame server resolving '228.66.57.66.list.dsbl.org' (in 'dsbl.ORG'?): 204.13.249.82#53
    Dec 25 13:44:53 server1 named[6909]: lame server resolving '228.66.57.66.list.dsbl.org' (in 'dsbl.ORG'?): 213.155.150.206#53
    Dec 25 13:50:10 server1 named[6909]: lame server resolving '33.168.9.88.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 17:29:26 server1 named[6909]: lame server resolving '15.140.160.201.in-addr.arpa' (in '140.160.201.in-addr.arpa'?): 200.95.144.4#53
    Dec 25 17:43:28 server1 named[6909]: lame server resolving 'voices.org' (in 'voices.ORG'?): 206.46.254.13#53
    Dec 25 17:51:20 server1 named[6909]: lame server resolving '179.9.160.201.in-addr.arpa' (in '9.160.201.in-addr.arpa'?): 200.95.144.4#53
    Dec 25 17:51:20 server1 named[6909]: lame server resolving '201.160.9.179.cableonline.com.mx' (in 'cableonline.com.MX'?): 201.134.141.211#53
    Dec 25 18:12:33 server1 named[6909]: lame server resolving '31.56.236.132.iadb.isipp.com' (in 'iadb.isipp.com'?): 66.223.40.121#53
    Dec 25 18:55:06 server1 named[6909]: lame server resolving '158.248.177.203.list.dsbl.org' (in 'dsbl.ORG'?): 204.13.249.82#53
    Dec 25 18:56:48 server1 named[6909]: lame server resolving '5.175.138.89.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 20:18:25 server1 named[6909]: lame server resolving '48.91.209.24.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 20:48:11 server1 pure-ftpd: ([email protected]) [INFO] New connection from 72.68.0.57
    Dec 25 20:48:35 server1 last message repeated 2 times
    Dec 25 20:48:36 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 25 20:56:19 server1 pure-ftpd: ([email protected]@72.68.0.57) [INFO] Logout.
    Dec 25 21:26:20 server1 mod_evasive[13892]: Blacklisting address 71.90.166.233: possible attack.
    Dec 25 22:25:12 server1 named[6909]: lame server resolving '195.141.153.66.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 25 23:24:02 server1 sshd(pam_unix)[11602]: session opened for user root by (uid=0)
    Dec 25 23:26:11 server1 sshd(pam_unix)[11657]: session opened for user root by (uid=0)
    Dec 26 00:03:05 server1 named[6909]: lame server resolving '188.128.236.211.in-addr.arpa' (in '128.236.211.in-addr.arpa'?): 211.236.192.11#53
    Dec 26 00:03:07 server1 last message repeated 7 times
    Dec 26 00:04:37 server1 sshd(pam_unix)[11657]: session closed for user root
    Dec 26 00:05:04 server1 sshd(pam_unix)[11602]: session closed for user root
    Dec 26 00:07:21 server1 named[6909]: lame server resolving '186.29.230.80.in-addr.arpa' (in '230.80.in-addr.arpa'?): 192.116.192.9#53
    Dec 26 01:50:50 server1 mod_evasive[18436]: Blacklisting address 76.187.13.22: possible attack.
    Dec 26 02:07:37 server1 named[6909]: client 208.255.152.227#6888: error sending response: host unreachable
    Dec 26 02:46:23 server1 named[6909]: lame server resolving '10.4.95.168.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 26 02:47:29 server1 named[6909]: lame server resolving '184.109.25.167.in-addr.arpa' (in '25.167.in-addr.arpa'?): 208.218.214.6#53
    Dec 26 02:47:30 server1 named[6909]: lame server resolving '184.109.25.167.in-addr.arpa' (in '25.167.in-addr.arpa'?): 208.218.214.44#53
    Dec 26 02:58:21 server1 named[6909]: lame server resolving '55.94.210.233.in-addr.arpa' (in '233.in-addr.arpa'?): 192.52.71.4#53
    Dec 26 02:58:21 server1 named[6909]: lame server resolving '55.94.210.233.in-addr.arpa' (in '233.in-addr.arpa'?): 128.9.128.127#53
    Dec 26 03:08:17 server1 mod_evasive[7974]: Blacklisting address 24.17.70.3: possible attack.
    Dec 26 04:35:28 server1 named[6909]: lame server resolving '142.1.197.134.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 26 04:55:11 server1 pure-ftpd: ([email protected]) [INFO] New connection from 222.253.229.229
    Dec 26 04:55:14 server1 pure-ftpd: ([email protected]) [WARNING] Authentication failed for user [[email protected]]
    Dec 26 04:56:52 server1 pure-ftpd: ([email protected]) [INFO] Logout.
    Dec 26 04:57:27 server1 named[6909]: lame server resolving 'nivoart.com' (in 'nivoart.com'?): 66.218.71.205#53
    Dec 26 05:29:21 server1 named[6909]: lame server resolving 'rhett.online.bg' (in 'online.bg'?): 195.138.133.10#53
    Dec 26 05:41:19 server1 filelimits: Increasing file system limits succeeded
    Dec 26 05:54:09 server1 named[6909]: lame server resolving '158.250.110.61.in-addr.arpa' (in '250.110.61.in-addr.arpa'?): 203.240.193.11#53
    Dec 26 06:00:38 server1 named[6909]: lame server resolving '91.213.32.201.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 26 06:20:43 server1 named[6909]: lame server resolving '6.244.41.213.list.dsbl.org' (in 'dsbl.ORG'?): 204.13.249.82#53
    Dec 26 06:20:43 server1 named[6909]: lame server resolving '6.244.41.213.list.dsbl.org' (in 'dsbl.ORG'?): 213.155.150.206#53
    Dec 26 06:20:43 server1 named[6909]: lame server resolving '6.244.41.213.list.dsbl.org' (in 'dsbl.ORG'?): 204.13.250.82#53
    Dec 26 06:20:43 server1 named[6909]: lame server resolving '6.244.41.213.list.dsbl.org' (in 'dsbl.ORG'?): 63.208.196.93#53
    Dec 26 06:28:48 server1 named[6909]: lame server resolving '228.243.54.202.in-addr.arpa' (in '243.54.202.in-addr.arpa'?): 203.197.12.42#53
    Dec 26 06:32:19 server1 last message repeated 8 times
    Dec 26 06:33:56 server1 last message repeated 4 times
    Dec 26 06:34:52 server1 last message repeated 15 times
    Dec 26 07:43:26 server1 named[6909]: lame server resolving '144.70.8.59.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 26 07:47:43 server1 named[6909]: lame server resolving '74.170.100.193.in-addr.arpa' (in '170.100.193.in-addr.arpa'?): 192.76.144.15#53
    Dec 26 07:47:44 server1 named[6909]: lame server resolving '74.170.100.193.in-addr.arpa' (in '170.100.193.in-addr.arpa'?): 192.54.47.66#53
    Dec 26 07:47:44 server1 named[6909]: lame server resolving '74.170.100.193.in-addr.arpa' (in '170.100.193.in-addr.arpa'?): 194.128.171.101#53
    Dec 26 08:24:27 server1 named[6909]: lame server resolving '225.176.233.125.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 26 08:25:10 server1 named[6909]: lame server resolving 'ns1.kombinasi.net' (in 'kombinasi.NET'?): 202.162.33.14#53
    Dec 26 08:25:11 server1 named[6909]: lame server resolving 'ns1.kombinasi.net' (in 'kombinasi.NET'?): 202.162.32.14#53
    Dec 26 08:55:36 server1 mod_evasive[18943]: Blacklisting address 161.200.255.162: possible attack.
    Dec 26 11:25:50 server1 named[6909]: lame server resolving '108.181.167.168.in-addr.arpa' (in '167.168.in-addr.arpa'?): 196.33.171.36#53
    Dec 26 11:25:51 server1 named[6909]: lame server resolving '108.181.167.168.in-addr.arpa' (in '167.168.in-addr.arpa'?): 196.26.5.8#53
    Dec 26 11:31:37 server1 named[6909]: lame server resolving '112.175.248.210.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 26 11:44:07 server1 named[6909]: lame server resolving '122.137.225.125.iadb.isipp.com' (in 'iadb.isipp.com'?): 66.223.40.121#53
    Dec 26 12:35:06 server1 mod_evasive[20051]: Blacklisting address 80.3.160.9: possible attack.
    Dec 26 13:03:44 server1 mod_evasive[24361]: Blacklisting address 80.5.160.8: possible attack.
    Dec 26 13:16:14 server1 mod_evasive[23832]: Blacklisting address 89.253.139.91: possible attack.
    Dec 26 13:16:29 server1 mod_evasive[17155]: Blacklisting address 139.133.7.37: possible attack.
    Dec 26 13:20:52 server1 named[6909]: lame server resolving '176.255.240.66.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 26 13:27:27 server1 mod_evasive[23832]: Blacklisting address 86.7.98.183: possible attack.
    Dec 26 13:46:03 server1 pure-ftpd: ([email protected]) [INFO] New connection from 59.95.161.252
    Dec 26 13:46:05 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 26 13:46:10 server1 pure-ftpd: ([email protected]) [INFO] New connection from 59.95.161.252
    Dec 26 13:46:12 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 26 13:54:14 server1 pure-ftpd: ([email protected]@59.95.161.252) [INFO] Can't change directory to /588/01- BEEDI (OMKARA).mp3: No such file or directory
    Dec 26 13:56:14 server1 pure-ftpd: ([email protected]@59.95.161.252) [ERROR] Error during read from data connection: Connection reset by peer
    Dec 26 13:56:14 server1 pure-ftpd: ([email protected]@59.95.161.252) [INFO] Timeout (no new data for 300 seconds)
    Dec 26 13:56:17 server1 pure-ftpd: ([email protected]) [INFO] New connection from 59.95.161.252
    Dec 26 13:56:19 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 26 13:57:17 server1 pure-ftpd: ([email protected]@59.95.161.252) [NOTICE] Restarting at 136800
    Dec 26 13:58:20 server1 pure-ftpd: ([email protected]@59.95.161.252) [ERROR] Error during read from data connection: Connection reset by peer
    Dec 26 13:58:20 server1 pure-ftpd: ([email protected]@59.95.161.252) [INFO] Timeout (no new data for 300 seconds)
    Dec 26 13:58:23 server1 pure-ftpd: ([email protected]) [INFO] New connection from 59.95.161.252
    Dec 26 13:58:25 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 26 13:59:23 server1 pure-ftpd: ([email protected]@59.95.161.252) [NOTICE] Restarting at 200160
    Dec 26 14:06:44 server1 pure-ftpd: ([email protected]@59.95.161.252) [ERROR] Error during read from data connection: Connection reset by peer
    Dec 26 14:06:44 server1 pure-ftpd: ([email protected]@59.95.161.252) [INFO] Timeout (no new data for 300 seconds)
    Dec 26 14:06:46 server1 pure-ftpd: ([email protected]) [INFO] New connection from 59.95.161.252
    Dec 26 14:06:48 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 26 14:07:49 server1 pure-ftpd: ([email protected]@59.95.161.252) [NOTICE] Restarting at 1733968
    Dec 26 14:08:52 server1 pure-ftpd: ([email protected]@59.95.161.252) [ERROR] Error during read from data connection: Connection reset by peer
    Dec 26 14:08:52 server1 pure-ftpd: ([email protected]@59.95.161.252) [INFO] Timeout (no new data for 300 seconds)
    Dec 26 14:08:55 server1 pure-ftpd: ([email protected]) [INFO] New connection from 59.95.161.252
    Dec 26 14:08:59 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 26 14:09:55 server1 pure-ftpd: ([email protected]@59.95.161.252) [NOTICE] Restarting at 1759888
    Dec 26 14:14:39 server1 named[6909]: lame server resolving '6.29.50.212.sa-trusted.bondedsender.org' (in 'sa-trusted.bondedsender.ORG'?): 216.32.88.90#53
    Dec 26 14:18:48 server1 pure-ftpd: ([email protected]@59.95.161.252) [INFO] Timeout (no new data for 300 seconds)
    Dec 26 14:18:54 server1 pure-ftpd: ([email protected]) [INFO] New connection from 59.95.161.252
    Dec 26 14:19:04 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 26 14:20:09 server1 pure-ftpd: ([email protected]@59.95.161.252) [NOTICE] Restarting at 2878768
    Dec 26 14:21:16 server1 pure-ftpd: ([email protected]@59.95.161.252) [ERROR] Error during read from data connection: Connection reset by peer
    Dec 26 14:21:16 server1 pure-ftpd: ([email protected]@59.95.161.252) [INFO] Timeout (no new data for 300 seconds)
    Dec 26 14:21:24 server1 pure-ftpd: ([email protected]) [INFO] New connection from 59.95.161.252
    Dec 26 14:21:26 server1 pure-ftpd: ([email protected]) [INFO] [email protected] is now logged in
    Dec 26 14:22:15 server1 pure-ftpd: ([email protected]@59.95.161.252) [INFO] Timeout - try typing a little faster next time
    Dec 26 14:55:04 server1 syslogd 1.4.1: restart.

  10. #10
    Me too even with 2.6.19.1 machine is restarting, btw, navyseal what machine do you have? What hw is inside?

  11. #11
    its an Intel pentium 3 ghz 1 GB RAM with 120*2 GB HDD

  12. #12
    Quote Originally Posted by navyseal
    its an Intel pentium 3 ghz 1 GB RAM with 120*2 GB HDD
    Maybe have 3ware raid controler?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •