webserver - why g-wan loops on loading handler scripts and csp script each day at midnight? -
i have strange behavior on g-wan server: each day @ midnight g-wan loops on loading scripts. see in gwan.log:
[tue apr 09 00:00:00 2013 gmt] memory footprint: 1.47 mib. [tue apr 09 00:00:00 2013 gmt] host /var/www/gwan/0.0.0.0_8082/#0.0.0.0 [tue apr 09 00:00:00 2013 gmt] log files enabled [tue apr 09 00:00:00 2013 gmt] loaded main.c 39.13 kib md5:15795d7c-42184ef2-c8075784-a3aa84aa [tue apr 09 00:00:00 2013 gmt] loaded process_kv.c 44.44 kib md5:349b8978-bbebb4eb-120c6f1a-7d06f98e [tue apr 09 00:00:00 2013 gmt] loaded connection handler main.c 18.71 kib md5:f624bc05-f51507c3-61b20c9c-ecfe9e19 [tue apr 09 00:00:00 2013 gmt] host /var/www/gwan/0.0.0.0_8083/#0.0.0.0 [tue apr 09 00:00:00 2013 gmt] log files enabled [tue apr 09 00:00:00 2013 gmt] loaded main.c 39.13 kib md5:15795d7c-42184ef2-c8075784-a3aa84aa [tue apr 09 00:00:00 2013 gmt] loaded process_kv.c 44.44 kib md5:349b8978-bbebb4eb-120c6f1a-7d06f98e [tue apr 09 00:00:00 2013 gmt] loaded connection handler main.c 18.71 kib md5:525aa623-2728dd50-0e67a6ad-6763a30b [tue apr 09 00:00:00 2013 gmt] memory footprint: 5.45 mib. [tue apr 09 00:00:01 2013 gmt] memory footprint: 1.47 mib. [tue apr 09 00:00:01 2013 gmt] host /var/www/gwan/0.0.0.0_8082/#0.0.0.0 [tue apr 09 00:00:01 2013 gmt] log files enabled [tue apr 09 00:00:01 2013 gmt] loaded main.c 39.13 kib md5:15795d7c-42184ef2-c8075784-a3aa84aa [tue apr 09 00:00:01 2013 gmt] loaded process_kv.c 44.44 kib md5:349b8978-bbebb4eb-120c6f1a-7d06f98e [tue apr 09 00:00:01 2013 gmt] loaded connection handler main.c 18.71 kib md5:f624bc05-f51507c3-61b20c9c-ecfe9e19 [tue apr 09 00:00:01 2013 gmt] host /var/www/gwan/0.0.0.0_8083/#0.0.0.0 [tue apr 09 00:00:01 2013 gmt] log files enabled [tue apr 09 00:00:01 2013 gmt] loaded main.c 39.13 kib md5:15795d7c-42184ef2-c8075784-a3aa84aa [tue apr 09 00:00:01 2013 gmt] loaded process_kv.c 44.44 kib md5:349b8978-bbebb4eb-120c6f1a-7d06f98e [tue apr 09 00:00:01 2013 gmt] loaded connection handler main.c 18.71 kib md5:525aa623-2728dd50-0e67a6ad-6763a30b .... .... [tue apr 09 00:02:01 2013 gmt] memory footprint: 3.22 mib. [tue apr 09 00:02:01 2013 gmt] host /var/www/gwan/0.0.0.0_8082/#0.0.0.0 [tue apr 09 00:02:01 2013 gmt] log files enabled [tue apr 09 00:02:01 2013 gmt] loaded main.c 39.13 kib md5:15795d7c-42184ef2-c8075784-a3aa84aa [tue apr 09 00:02:01 2013 gmt] loaded process_kv.c 44.44 kib md5:349b8978-bbebb4eb-120c6f1a-7d06f98e [tue apr 09 00:02:01 2013 gmt] loaded connection handler main.c 18.71 kib md5:f624bc05-f51507c3-61b20c9c-ecfe9e19 [tue apr 09 00:02:01 2013 gmt] host /var/www/gwan/0.0.0.0_8083/#0.0.0.0 [tue apr 09 00:02:01 2013 gmt] log files enabled [tue apr 09 00:02:01 2013 gmt] loaded main.c 39.13 kib md5:15795d7c-42184ef2-c8075784-a3aa84aa [tue apr 09 00:02:01 2013 gmt] loaded process_kv.c 44.44 kib md5:349b8978-bbebb4eb-120c6f1a-7d06f98e [tue apr 09 00:02:01 2013 gmt] loaded connection handler main.c 18.71 kib md5:525aa623-2728dd50-0e67a6ad-6763a30b [tue apr 09 00:02:01 2013 gmt] memory footprint: 7.13 mib. [tue apr 09 00:02:11 2013 gmt] ------------------------------------------------ [tue apr 09 00:02:11 2013 gmt] g-wan 4.3.14 64-bit (mar 14 2013 07:33:12) [tue apr 09 00:02:11 2013 gmt] ------------------------------------------------ [tue apr 09 00:02:11 2013 gmt] local time: tue, 09 apr 2013 02:02:11 gmt+2 ....
so during 2 minutes g-wan loops , after g-wan started monit believe. have explanation , workaround?
i change web hosting provider , use vm under microsoft hyper-v. problem remains: g-wan restarted monit logged following events:
wed, 16 oct 2013 02:02:12: process pid changed 2171 20631 wed, 16 oct 2013 02:02:13: process ppid changed 1 2171 wed, 16 oct 2013 02:02:43: process pid changed 20631 20975 wed, 16 oct 2013 02:03:13: process pid changed 20975 21318 wed, 16 oct 2013 02:03:44: process pid changed 21318 21573 wed, 16 oct 2013 02:04:14: process pid changed 21573 2171 wed, 16 oct 2013 02:04:14: process ppid changed 2171 1 wed, 16 oct 2013 02:33:06: process not running wed, 16 oct 2013 02:33:37: process running pid 776
it happens every day on new vm hypervisor.
i not 1 behavior. have explanation , workaround?
thank jerome
the loop means child process not responding, hence parent killing old child , restarting new child.
could email whole log files (trace , gwan.log)? partial post missing the informative parts.
update
that new problem 4-years old code worked fine far platform issue, have found workaround, published next release in few weeks.
Comments
Post a Comment