Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id F312BA5CB38 for ; Wed, 15 Feb 2012 04:54:17 -0400 (AST) Received: from [2001:4d88:1ffc:463::1] (helo=uvena.de) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Rxacz-0000hC-8N for pgsql-admin@postgresql.org; Wed, 15 Feb 2012 08:54:17 +0000 Received: from [141.35.39.175] (c319808.zuv.uni-jena.de [141.35.39.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by uvena.de (Postfix) with ESMTPSA id 9B6E7254011 for ; Wed, 15 Feb 2012 08:54:02 +0000 (UTC) Message-ID: <4F3B72BD.2090109@frank.uvena.de> Date: Wed, 15 Feb 2012 09:54:21 +0100 From: Frank Lanitz User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Error in log X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2001:4d88:1ffc:463::1 (failed) X-Pg-Spam-Score: 0.8 (/) X-Archive-Number: 201202/60 X-Sequence-Number: 39120 Hi folks, Currently I'm not sure about the reason for a error entry inside syslog. Maybe you can point me to right direction. During last night I received this log entries: > Feb 15 02:08:18 dbsrv kernel: [1158600.676036] INFO: task postgres:2358 blocked for > more than 120 seconds. > Feb 15 02:08:18 dbsrv kernel: [1158600.676102] "echo 0 > > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > Feb 15 02:08:18 dbsrv kernel: [1158600.676201] postgres D ffff88000180fc40 0 > 2358 2279 0x00000000 > Feb 15 02:08:18 dbsrv kernel: [1158600.676206] ffffffff814891f0 0000000000000086 > 0000000000000000 000000010000000e > Feb 15 02:08:18 dbsrv kernel: [1158600.676210] ffff8800f2ba4520 ffff8800f39e1e18 > 000000000000f9e0 ffff8800f39e1fd8 > Feb 15 02:08:18 dbsrv kernel: [1158600.676213] 0000000000015780 0000000000015780 > ffff8800f3f446a0 ffff8800f3f44998 > Feb 15 02:08:18 dbsrv kernel: [1158600.676217] Call Trace: > Feb 15 02:08:18 dbsrv kernel: [1158600.676225] [] ? > wait_on_page_writeback_range+0xce/0x11b > Feb 15 02:08:18 dbsrv kernel: [1158600.676238] [] ? > log_wait_commit+0xbf/0x112 [jbd] > Feb 15 02:08:18 dbsrv kernel: [1158600.676242] [] ? > autoremove_wake_function+0x0/0x2e > Feb 15 02:08:18 dbsrv kernel: [1158600.676249] [] ? > ext3_sync_file+0x94/0xc8 [ext3] > Feb 15 02:08:18 dbsrv kernel: [1158600.676254] [] ? > vfs_fsync_range+0x73/0x9e > Feb 15 02:08:18 dbsrv kernel: [1158600.676257] [] ? During this time it could be that autovacuum was running (its manually set to run after a data update has been successfuly done before.) Its a 8.4.10 running on Debian Stable. Now I'm wondering whether an issue with postgres itself or hardware or any other part of debian.... cheers, Frank