Drakath Posted November 4, 2014 Share Posted November 4, 2014 Sometimes (about once a month) my server randomly shutdowns by itself and the Screen is gone. I have to attach my server to Screen again to make it work. I thought it was a host problem but when I contacted the support, they said everything is fine on their side and something is wrong with the software I use, which is a MTA server. Can someone help me to find what causes this problem? I run Debian 7.0 64 bit. Logs look fine. Link to comment
MTA Team ccw Posted November 4, 2014 MTA Team Share Posted November 4, 2014 What is the MTA build number? Is there a crash dump created in mods/deathmatch/dumps/ ? Check the OS logs to see if it reports stopping the MTA server for some reason: /var/log/syslog Link to comment
Drakath Posted November 4, 2014 Author Share Posted November 4, 2014 There is a crash dump: http://www67.zippyshare.com/v/87594783/file.html Link to comment
MTA Team ccw Posted November 4, 2014 MTA Team Share Posted November 4, 2014 That crash dump is two weeks old. Was that when you last had this problem? Link to comment
Drakath Posted November 4, 2014 Author Share Posted November 4, 2014 syslog looks fine: Nov 4 04:42:06 vps82376 syslog-ng[1581]: Configuration reload request received, reloading configuration; Nov 4 04:42:06 vps82376 syslog-ng[1581]: EOF on control channel, closing connection; Nov 4 05:12:01 vps82376 named[1679]: client 162.212.181.242#15740: query (cache) 'wwww.jrdga.info/A/IN' denied Nov 4 05:26:01 vps82376 /USR/SBIN/CRON[15154]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 05:53:09 vps82376 -- MARK -- Nov 4 06:13:09 vps82376 -- MARK -- Nov 4 06:15:35 vps82376 named[1679]: client 162.212.181.242#34370: query (cache) 'wwww.jrdga.info/A/IN' denied Nov 4 06:26:01 vps82376 /USR/SBIN/CRON[15542]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 06:46:01 vps82376 -- MARK -- Nov 4 07:20:54 vps82376 syslog-ng[1581]: syslog-ng starting up; version='3.3.5' Nov 4 07:20:54 vps82376 syslog-ng[1581]: EOF on control channel, closing connection; Nov 4 07:20:55 vps82376 named[1660]: starting BIND 9.8.4-rpz2+rl005.12-P1 -u bind Nov 4 07:20:55 vps82376 named[1660]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' Nov 4 07:20:55 vps82376 named[1660]: ---------------------------------------------------- Nov 4 07:20:55 vps82376 named[1660]: BIND 9 is maintained by Internet Systems Consortium, Nov 4 07:20:55 vps82376 named[1660]: Inc. (ISC), a non-profit 501©(3) public-benefit Nov 4 07:20:55 vps82376 named[1660]: corporation. Support and training for BIND 9 are Nov 4 07:20:55 vps82376 named[1660]: available at https://www.isc.org/support Nov 4 07:20:55 vps82376 named[1660]: ---------------------------------------------------- Nov 4 07:20:55 vps82376 named[1660]: adjusted limit on open files from 4096 to 1048576 Nov 4 07:20:55 vps82376 named[1660]: found 3 CPUs, using 3 worker threads Nov 4 07:20:55 vps82376 named[1660]: using up to 4096 sockets Nov 4 07:20:55 vps82376 named[1660]: loading configuration from '/etc/bind/named.conf' Nov 4 07:20:55 vps82376 named[1660]: reading built-in trusted keys from file '/etc/bind/bind.keys' Nov 4 07:20:55 vps82376 named[1660]: using default UDP/IPv4 port range: [1024, 65535] Nov 4 07:20:55 vps82376 named[1660]: using default UDP/IPv6 port range: [1024, 65535] Nov 4 07:20:55 vps82376 named[1660]: listening on IPv6 interfaces, port 53 Nov 4 07:20:55 vps82376 named[1660]: listening on IPv4 interface lo, 127.0.0.1#53 Nov 4 07:20:55 vps82376 named[1660]: listening on IPv4 interface venet0, 127.0.0.2#53 Nov 4 07:20:55 vps82376 named[1660]: listening on IPv4 interface venet0:0, 92.222.172.187#53 Nov 4 07:20:55 vps82376 named[1660]: generating session key for dynamic DNS Nov 4 07:20:55 vps82376 named[1660]: sizing zone task pool based on 5 zones Nov 4 07:20:55 vps82376 named[1660]: using built-in root key for view _default Nov 4 07:20:55 vps82376 named[1660]: set up managed keys zone for view _default, file 'managed-keys.bind' Nov 4 07:20:55 vps82376 named[1660]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 254.169.IN-ADDR.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: D.F.IP6.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 8.E.F.IP6.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 9.E.F.IP6.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: A.E.F.IP6.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: B.E.F.IP6.ARPA Nov 4 07:20:55 vps82376 named[1660]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Nov 4 07:20:55 vps82376 named[1660]: command channel listening on 127.0.0.1#953 Nov 4 07:20:55 vps82376 named[1660]: command channel listening on ::1#953 Nov 4 07:20:55 vps82376 named[1660]: zone 0.in-addr.arpa/IN: loaded serial 1 Nov 4 07:20:55 vps82376 named[1660]: zone 127.in-addr.arpa/IN: loaded serial 1 Nov 4 07:20:55 vps82376 named[1660]: zone 255.in-addr.arpa/IN: loaded serial 1 Nov 4 07:20:55 vps82376 named[1660]: zone localhost/IN: loaded serial 2 Nov 4 07:20:55 vps82376 named[1660]: managed-keys-zone ./IN: loaded serial 115 Nov 4 07:20:55 vps82376 named[1660]: running Nov 4 07:20:55 vps82376 /usr/sbin/cron[1725]: (CRON) INFO (pidfile fd = 3) Nov 4 07:20:55 vps82376 /usr/sbin/cron[1726]: (CRON) STARTUP (fork ok) Nov 4 07:20:55 vps82376 /usr/sbin/cron[1726]: (CRON) INFO (Running @reboot jobs) Nov 4 07:26:01 vps82376 /USR/SBIN/CRON[1763]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 08:26:01 vps82376 /USR/SBIN/CRON[1840]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 08:31:54 vps82376 named[1660]: client 74.82.47.4#38804: query (cache) 'dnsscan.shadowserver.org/A/IN' denied Nov 4 09:26:01 vps82376 /USR/SBIN/CRON[1915]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 09:26:14 vps82376 named[1660]: client 162.212.181.242#53712: query (cache) 'wwww.jrdga.info/A/IN' denied Nov 4 10:26:01 vps82376 /USR/SBIN/CRON[1992]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 11:04:05 vps82376 named[1660]: client 124.232.142.220#49796: query (cache) 'www.google.com/A/IN' denied Nov 4 11:26:01 vps82376 /USR/SBIN/CRON[2069]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 12:26:01 vps82376 /USR/SBIN/CRON[2144]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 13:02:20 vps82376 named[1660]: client 162.212.181.242#41207: query (cache) 'wwww.jrdga.info/A/IN' denied Nov 4 13:26:01 vps82376 /USR/SBIN/CRON[2261]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 14:26:01 vps82376 /USR/SBIN/CRON[2351]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 4 15:26:01 vps82376 /USR/SBIN/CRON[2431]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Link to comment
Drakath Posted November 26, 2014 Author Share Posted November 26, 2014 Ah, I had it again today. Any idea who could cause this? Link to comment
Woovie Posted November 26, 2014 Share Posted November 26, 2014 Provide a newer crash log. Link to comment
Drakath Posted November 26, 2014 Author Share Posted November 26, 2014 There is no newer crash log. Link to comment
Woovie Posted November 26, 2014 Share Posted November 26, 2014 Sounds like maybe it's hitting resource limits? Link to comment
Drakath Posted November 26, 2014 Author Share Posted November 26, 2014 It looks fine to me: http://i.imgur.com/Iy1BejU.png I am a concerned about the traffic though. Here are the specs: RAM: 4 GB Bandwidth: 100 Mbps (10000 GB per month) CPU: 3 vCores Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now