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] [<ffffffff810b4e8f>] ?
> wait_on_page_writeback_range+0xce/0x11b
> Feb 15 02:08:18 dbsrv kernel: [1158600.676238] [<ffffffffa0226e20>] ?
> log_wait_commit+0xbf/0x112 [jbd]
> Feb 15 02:08:18 dbsrv kernel: [1158600.676242] [<ffffffff8106502a>] ?
> autoremove_wake_function+0x0/0x2e
> Feb 15 02:08:18 dbsrv kernel: [1158600.676249] [<ffffffffa02373f8>] ?
> ext3_sync_file+0x94/0xc8 [ext3]
> Feb 15 02:08:18 dbsrv kernel: [1158600.676254] [<ffffffff8110c02c>] ?
> vfs_fsync_range+0x73/0x9e
> Feb 15 02:08:18 dbsrv kernel: [1158600.676257] [<ffffffff8110c0d6>] ?
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