日志:服务器进程(PID 11748)被信号 11 终止:分段错误

发布于 2024-09-03 15:32:39 字数 832 浏览 7 评论 0原文

我在 fedora core 2 linux 机器上使用 Postgres-8.3.7。 Postgres 服务正在崩溃。 当我重新启动系统时,它可以正常工作一段时间。在某个随机时间它再次崩溃。

造成这种随机段错误的可能原因是什么?

FATAL:  the database system is in recovery mode
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections
LOG:  server process (PID 11748) was terminated by signal 11: Segmentation fault
LOG:  terminating any other active server processes
FATAL:  the database system is in recovery mode
FATAL:  the database system is in recovery mode
FATAL:  the database system is in recovery mode
FATAL:  the database system is in recovery mode
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted; last known up at 2010-05-24 13:28:06 PDT
LOG:  database system was not properly shut down; automatic recovery in progress

I am using Postgres-8.3.7 on fedora core 2 linux box. And Postgres service is crashing.
When I restart the system, it is working fine for some time. At some random time it is crashing again.

What could be the possible reasons for this segfaults which are random?

FATAL:  the database system is in recovery mode
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections
LOG:  server process (PID 11748) was terminated by signal 11: Segmentation fault
LOG:  terminating any other active server processes
FATAL:  the database system is in recovery mode
FATAL:  the database system is in recovery mode
FATAL:  the database system is in recovery mode
FATAL:  the database system is in recovery mode
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted; last known up at 2010-05-24 13:28:06 PDT
LOG:  database system was not properly shut down; automatic recovery in progress

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

囚我心虐我身 2024-09-10 15:32:39

有点太具体了,细节很少——也许更适合 serverfault.com 或 postgresql 邮件列表。

一些随机建议:

  • VACUUM ANALYZE VERBOSE ?
  • 不能升级到最新版本吗?
  • 某些特殊情况下会出现这种情况吗?磁盘快满了?高负载?操作系统日志 (/var/log/message) 中没有任何可疑内容吗?
  • 你不能提高postgresql的日志级别来记录查询并查看这是否与某些特定查询(例如函数)相关吗?

Postgresql 拥有一个响应迅速的开发人员社区

A little too specific, few details - and perhaps more appropiate to serverfault.com , or the postgresql mailing lists.

Some random suggestions:

  • VACUUM ANALYZE VERBOSE ?
  • Can't you upgrade to the last version ?
  • Some special circumnstances when this happens ? Disk nearly full ? High load ? Nothing suspicious in the OS logs ( /var/log/message ) ?
  • Can't you raise the log level of postgresql to log the queries and see if this is related to some particular query (e.g. function)?

Postgresql has a very responsive developers community.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文