[ { "category_ids" : [ "other" ], "description" : "NULL", "diagnosis" : "NULL", "extra_info" : "NULL", "id" : 2, "name" : "No such file or directory" }, { "category_ids" : [ "other" ], "description" : "Connection attempt interrupted.", "diagnosis" : "This type of error means that the initial phase of the connection to the server was started, but the TCP synchronization sequence was not completed. These errors most often occur when the monitored server is overloaded.", "extra_info" : "TIMEOUT-type error. It occurs relatively rarely.", "id" : 4, "name" : "Timeout Interrupted system call" }, { "category_ids" : [ "other" ], "description" : "NULL", "diagnosis" : "NULL", "extra_info" : "NULL", "id" : 9, "name" : "Bad file number" }, { "category_ids" : [ "network" ], "description" : "Invalid argument.", "diagnosis" : "This error most often indicates a problem with DNS servers. If they respond too slowly or do not respond at all, the domain name cannot be resolved and the connection attempt returns the Invalid Argument system error.", "extra_info" : "Check the performance and availability of the name servers. If the error occurs when using an IP address instead of a domain name, verify that the IP address is correct.", "id" : 22, "name" : "Invalid argument" }, { "category_ids" : [ "network", "timeout", "web_application", "web_server" ], "description" : "Timeout-type error; application, network, or service configuration error. It means that the service check process took too long.", "diagnosis" : "The service check process is performed in several steps. If the service shows a problem, the monitoring station retries the check. Only when the error is returned again does it report the problem to the monitoring center. An upper time limit is applied to the entire service check process to protect against deadlocks, hangs, or incorrect configuration. This error appears, for example, when the service is running very slowly but the timeout configured in the administration panel is set to a very high value. For example, if the timeout is set to 1 hour in the configuration, it will not be honored. If the service does not respond within a certain time window, the Timer expired error will be reported before a Connection/Reply Timeout error appears. This error is usually caused by an incorrect Connection Timeout or Reply Timeout value in the service administration panel. Its occurrence indicates that the service is running very slowly and, under normal conditions, error 110 would be reported. Verify the service settings in the Monit24.pl administration panel.", "extra_info" : "Timeout values in the administration panel are specified in milliseconds. This means that entering 5000 is equivalent to 5 seconds.", "id" : 62, "name" : "Timer expired" }, { "category_ids" : [ "network" ], "description" : "Cannot connect to the server: no routing path to the host could be found.", "diagnosis" : "This error indicates an incorrect router configuration on the path from the monitoring station to the server. If the error is short-lived and detected only by some monitoring stations, it may result from changes to network device configuration. If this type of error persists, it should be reported to the network administrator.", "extra_info" : "", "id" : 101, "name" : "Network is unreachable" }, { "category_ids" : [ "network", "web_application", "web_server" ], "description" : "Application, network, or server error. The connection to the server was unexpectedly interrupted.", "diagnosis" : "This error means that the connection to the server was established, but it was interrupted while active. If the next error is 111 Connection refused, it means that the application terminated unexpectedly. If the error repeats, it may indicate malfunctioning application behavior. In less common cases, the error is caused by the network layer and the connection being interrupted by a firewall or router. If the error repeats or lasts longer than a few minutes, report it to the network administrator or system administrator.", "extra_info" : "", "id" : 104, "name" : "Connection reset by peer" }, { "category_ids" : [ "network", "timeout" ], "description" : "Network or application error. The error means that a TCP/IP connection to the monitored service could not be established within the time specified in the service configuration panel. Unless the configured value is extremely low, this error means that there is a network-level problem, the monitored server is down, or the TCP port used by the service is blocked.", "diagnosis" : "If this error occurs frequently for a website, the server is probably overloaded enough that it cannot handle new connections within the specified time. This may result in slow page loading and timeout errors in users' browsers. The error may also indicate high network load. If it appears only from some locations, it may point to overloaded links to the operator from which the failed check was performed. Frequent occurrence may suggest poor service quality from the hosting provider where the monitored server is located. Errors of this type are difficult to detect without a monitoring system because they may affect only some users. Monit24 monitoring, by checking the service from multiple locations and at high frequency, can detect these errors, and eliminating them can improve website availability for all users. A system administrator can help resolve the issue. In extreme cases, changing the hosting provider may be necessary.", "extra_info" : "The value is set in milliseconds [ms]. For the HTTP service, the connection time configured in the service administration panel includes the total time between starting the connection (socket + connect + select), sending the request (HEAD/GET), and receiving the server response (read). It is therefore an indicator of server performance that directly affects page loading speed. Under normal conditions, this time should not exceed 500 ms. If the entire process takes less than 150 ms, the server can be considered exceptionally fast. Values from 150 to 500 ms are considered good. Above 500 ms, the page will load noticeably slowly, and above 2000 ms the value is insufficient.", "id" : 110, "name" : "Connection timed out" }, { "category_ids" : [ "network", "web_server" ], "description" : "Application error. The error means that a TCP/IP connection to the monitored service could not be established. Unlike timeout errors, this error indicates that the monitored server responded within the specified time but refused to handle the connection (the port is closed).", "diagnosis" : "This error most often indicates an application error, specifically that the application is stopped or the service is not running. If it appears only briefly (up to a few minutes), it may indicate a restart of the service or the entire application server. Some hosting providers perform such operations periodically, mainly when they are experiencing unclear server issues or are using outdated technology. If the error lasts longer, contact the system administrator or hosting provider. In extreme cases, and when the error occurs frequently, changing the hosting provider may be necessary.", "extra_info" : "", "id" : 111, "name" : "Connection refused" }, { "category_ids" : [ "network" ], "description" : "Network or server error. The routing path to the server was not found — the connection cannot be established.", "diagnosis" : "This is a relatively rare error that may indicate an incorrect router configuration or, in some cases, that the entire server is down. If the error appears only from some monitoring stations and lasts less than several minutes, it may mean that network operator administrators are changing network configuration, causing the server to be inaccessible from some network locations. If the error lasts longer or appears from all monitoring stations, it may indicate misconfigured network devices on the hosting provider's or network operator's side. This error should be reported to the network administrator.", "extra_info" : "", "id" : 113, "name" : "No route to host" } ]