vBulletin 发出非常古老的错误

发布于 2024-10-02 19:07:48 字数 914 浏览 1 评论 0原文

如果您经常使用 vBulletin,您以前可能见过这种类型的错误。

vBulletin 中的数据库错误:

mysql_connect() [function.mysql-connect]: 无法连接到本地 MySQL 服务器 通过插座 '/var/lib/mysql/mysql.sock' (2) /home/detroit/public_html/blab/includes/class_core.php 在第 311 行

MySQL 错误:错误号: 请求日期:11 月 16 日星期二 2010 @ 10:57:57 AM 错误日期: 2010 年 11 月 16 日星期二 @ 10:57:57 上午脚本: url_removed_to_avoid_spam_flagging 推荐人: IP 地址: xx.xx.xx.xxx 用户名:类名:vB_Database MySQL 版本:

我的问题不考虑错误本身,而是考虑它的年龄。

我们的团队每小时大约会收到 20-30 封此类电子邮件,这些电子邮件在每小时的第三分钟到第七分钟之间集中到达。奇怪的是,所有错误似乎都来自今天早上的同一个五分钟块。

我正在 grep 查找错误本身,但万一有人在这里有更快的答案(因为 grep 很慢,而且我一眼看不到任何本地化的 PHP 错误文件):是否有一种简单的方法可以真实地查看这些错误时间?

我担心的是,我们根本没有解决我们的数据库问题,而是生成了如此多的错误,以至于消息路径上某处的电子邮件过滤器禁止了错误消息,将它们缓慢地排出以致于毫无用处。错误的实时视图将使我们能够知道我们是否真的已经处理了事情,(正如我们认为的那样——在这种情况下,我们可以寻找一种方法来阻止旧错误消息的传播) )或者我们是否需要采取额外的行动。

预先感谢您对此的任何评论。你们这些人摇滚。

If you work regularly with vBulletin, you've probably seen this type of error before.

Database error in vBulletin :

mysql_connect() [function.mysql-connect]: Can't connect to local MySQL server
through socket
'/var/lib/mysql/mysql.sock' (2)
/home/detroit/public_html/blab/includes/class_core.php
on line 311

MySQL Error : Error Number :
Request Date : Tuesday, November 16th
2010 @ 10:57:57 AM Error Date :
Tuesday, November 16th 2010 @ 10:57:57
AM Script :
url_removed_to_avoid_spam_flagging
Referrer : IP Address :
xx.xx.xx.xxx Username : Classname : vB_Database MySQL
Version :

My question doesn't regard the error itself, but rather its age.

Our team is receiving roughly 20-30 of these each hour, with the e-mails arriving in a cluster between the third and seventh minute of the hour. The weird thing is that all of the errors appear to be from the same five-minute block from this morning.

I'm grepping for the errors themselves, but in case someone has a faster answer here (since grep is slow and I don't see any localized PHP error files at a glance): Is there an easy way to see these errors in real time?

My fear is that, far from solving our database problem, we've simply generated so many errors that an e-mail filter somewhere along the messages' route is embargoing the error messages, dribbling them out so slowly as to be useless. A real-time view of the errors will allow us to know whether we've actually got a handle on things, (as we think we do -- in which case we can then look for a way to stop the dribble of old error messages) or whether we need to take additional action.

Thanks in advance for any comments on this. You people rock.

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

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

发布评论

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

评论(1

如何视而不见 2024-10-09 19:07:48

您现在可能已经解决了这个问题,但是:

  1. 每当我在 vBulletin 邮件上看到奇怪的时间戳时,都是由于电子邮件提供商的限制造成的。如果您查看邮件标题中 Received: 行上的时间戳,您可能会看到限制发生的位置。
  2. 如果您在特定时间遇到一系列错误,那么开始寻找罪魁祸首的最佳位置是管理控制面板的 vBulletin“计划任务”部分。某些计划任务可能会很昂贵,具体取决于您的站点大小、流量情况等,其中一个任务可能正在运行昂贵的查询,该查询可能会锁定一两个表很长时间。
  3. 您是否尝试过在发生错误时使用mtop查看数据库?

You probably have fixed this problem by now but:

  1. Any time I've seen weird timestamps on vBulletin mails it has been due to throttling by e-mail providers. If you have a look at the timestamps on the Received: lines in the headers of the mails you'll probably see where the throttling is happening.
  2. If you're getting clusters of errors at specific times, then the best place to start looking for culprits is the vBulletin "Scheduled Tasks" section of the Admin Control Panel. Some of the scheduled tasks can be expensive, depending on your site size, traffic profile, etc and one of them may be running an expensive query which might be locking a table or two for a very long time.
  3. Have you tried looking at the DB using mtop at the times when the errors occur?
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文