用户错误故障需要管理员干预。
在这种场景中，一个每夜都崩溃的构建可以很容易地说明，QA人员只能在第二天闲坐着，失去了宝贵的测试时间，而开发和构建团队却在寻找错误故障。
In this kind of scenario, a broken nightly build can easily mean that QA staff will sit idle the next day, losing precious testing time while the development and build teams troubleshoot the errors.
由模糊测试导致的许多故障都是内存分配错误及缓冲器溢出的直接结果。
Many of the crashes resulting from fuzz testing are direct results of memory allocation mistakes and buffer overflows.
而另一方面，用户错误和媒体故障则需要管理员进行交互。
User error and media failures, on the other hand, require the administrator to interact.
但是遗憾的是这个聊天室依然还没有完，因为它还需要处理错误和非暂时性故障。
But unfortunately the chat room is still not complete, because it needs to handle errors and non transient failures.
如果出现临时系统错误、网络故障或服务不可用，准备调用过程中使用的数据将丢失。
If temporary system errors, network failures, or service unavailability occur, the data used in preparation of the call is lost.
但是，当出现错误情况时，在SOAP部分传递附加的故障信息仍是很有用的。
However, it is useful to pass additional fault information in the SOAP section when an error state arises.
与RAID类似，IDA支持通过原始数据的子集重建数据，含有一定数量的代码错误开销(依赖于可接纳故障的数量)。
Similar to RAID, IDA permits the reconstruction of data from a subset of the original data, with some amount of overhead for error codes (dependent on the number of tolerated failures).
距离实际故障点（即，出现错误的位置）越近，执行此干预就越有效和越可行。
This intervention is the more effective and practicable the closer it is performed to the actual point of failure (that is, where the fault has been raised).
每当中介体发生故障时，都应该生成错误消息。
A fault message should be generated whenever a failure occurs at an intermediary.
一个构建发生故障时，我希望能够立即知道这一情况，以便就能够采取适当的行动来解决这一问题——不论那是编译错误、测试故障甚或是整体复杂性的增加。
When a build is broken, I want to know immediately so I can take the proper action to fix it — whether that be a compilation error, test failure, or even an increase in overall complexity.
如果测试失败，就报告错误消息，指出故障点，同时程序执行中断。
If a test fails, an error message is reported, indicating the point of failure, and program execution halts.
如果发生错误，遵循故障排除步骤，再次运行导出任务。
If there's an error, follow the troubleshooting steps, and run the export task again.
如果出现数据库连接故障，脚本将向电话报告错误。
In the case of failure to connect to the database, the script reports the error to the phone.
甚至在单个物理服务器上，您都有冗余电源、错误纠正ram、冗余磁盘和丰富的故障前诊断指示器监控。
Even on a single physical server, you can have redundant power supplies, error-correcting RAM, redundant disks, and copious monitoring of pre-fault indicators.
流程异常的原因通常是一些临时错误，比如连通性故障、超时、或设计时代码错误。
Process exceptions are often caused due to temporary errors such as connectivity failure, timeouts, or design time code errors.
他们也缺乏一个准确的方法去检测错误，或辨别出一个故障是本地故障还是通信故障。
They also lack accurate ways to detect failure, or to distinguish a local software/hardware failure from a communication failure.
此外，流程本身可能检测到导致内部故障的错误状况。
Furthermore, a process itself might detect erroneous situations that result in internal faults.
如果出现错误，请参考第4节排除故障。
If errors occur, refer to Section 4 for Troubleshooting tips.
在很多情况下(即便不是所有的情况)，您都希望在错误发生时生成自己的故障，否则Web服务无法返回值。
In many cases, if not all, you want to generate your own faults when errors happen; otherwise, the Web service cannot return a value.
但是，在出现严重错误或故障的情况下，dmesg有时可能是系统上所发生情况的唯一良好的信息源。
But in the case of a serious fault or failure, dmesg can sometimes be your only good source of information on what is happening on your system.
doWork方法会提供一个错误代码，表示这些故障发生的路径，还把问题原因作为链接的异常提供。
An error code is provided to indicate which of these failure paths occurred, and the cause of the problem is provided as a linked exception.
我还添加了fault方法，当发生故障时将发送XML - RPC错误响应。
I've also added a fault method that sends an XML-RPC fault response when something goes wrong.
因为我们现在生活在OSGi和动态运行时世界，所以我们想确保插件在不引起运行时故障或错误的情况下运行。
Because we now live in the world of OSGi and dynamic runtimes, we want to make sure our plug-in can run without causing a runtime crash or error.
如果存在错误，就会显示一个指明故障的消息框，详细错误列于Out putWindow的IBMMessage窗格中。
If there are any errors, a message box indicating failure is displayed, and detailed errors are listed in the IBM message pane of the Output Window.
在下列故障检修步骤中，我们假设他们这样做了，但是发生了一些错误。
In the following troubleshooting steps, we assume that they have done so but something went wrong.
这对于性能分析、错误检查和故障检修很有用。
This can be useful for performance analysis, error checking, and troubleshooting.
在这个错误场景中，节点之间的通信链发生故障，每个节点都认为自己是主节点。
In this error scenario, the communication link fails between the nodes, and both nodes believe that they are the primary node.
有些RAID配置可以继续运行直到大量的设备被禁用(故障)，无论是故意或是因错误或磁盘问题。
Some RAID configurations can continue functioning even if a number of devices are disabled (failed), either deliberately or due to an error or disk problem.
在开始考虑进行优化之前，您需要了解如何对冲突和错误问题进行故障排除。
You need to learn to troubleshoot collision and error problems before you even begin to think about tuning.
应用推荐