Error codes

Every ScopePort log message has an error code. Use this list to get further information about errors.

ScopePort Server

#001: Could not update service response time. (Severity: 1): The measured service response time could not be stored in the database because the query failed. (Caused in: Method: RudeChecks::doChecks)
#002: Could not update alarms table (Severity: 2): The creation of an "sensor out of range" alarm did not succeed because the insert query failed. The notifications should have been sent but there will be no entry in the "Alarms" section of the web interface. (Caused in: Method: Services::sendWarning)
#003: Could not update service response time (Severity: 2): The measured response time of an SMTP protocol check could not be stored because of an database error. (Caused in: Method: SoftChecks::doChecks)
#004: Could not update service response time (Severity: 2): The measured response time of an HTTP protocol check could not be stored because of an database error. (Caused in: Method: SoftChecks::doChecks)
#005: Could not update service response time (Severity: 2): The measured response time of an IMAP protocol check could not be stored because of an database error. (Caused in: Method: SoftChecks::doChecks)
#006: Could not update service response time (Severity: 2): The measured response time of an POP3 protocol check could not be stored because of an database error. (Caused in: Method: SoftChecks::doChecks)
#007: Could not update service response time (Severity: 2): The measured response time of an SSH protocol check could not be stored because of an database error. (Caused in: Method: SoftChecks::doChecks)
#008: Could not update service response time (Severity: 2): The measured response time of an FTP protocol check could not be stored because of an database error. (Caused in: Method: SoftChecks::doChecks)
#009: Could not update alarms table (Severity: 1): The creation of an "sensor out of range" alarm did not succeed because the insert query failed. The notifications should have been sent but there will be no entry in the "Alarms" section of the web interface. (Caused in: Method: Warning::updateAlarms)
#010: Could not update alarms table (Severity: 1): The creation of an "sensor out of range" alarm did not succeed because no database connection could be established. The notifications should have been sent but there will be no entry in the "Alarms" section of the web interface. (Caused in: Method: Warning::updateAlarms)
#011: Could not send XMPP message to [JID] (Severity: 1): The XMPP message could not be sent because the XMPP server replied with an error message (<stream:error>). (Caused in: Method: XMPP::sendMessage)
#012: Could not send XMPP message to [JID] (Severity: 1): The XMPP message could not be sent because the XMPP server replied with an error message (<error *>). (Caused in: Method: XMPP::sendMessage)
#013: Could not send XMPP message to [JID] (Severity: 1): The XMPP message could not be sent because the XMPP server replied with an error message (<error *>). (Caused in: Method: XMPP::sendMessage)
#014: Could not XMPP connect to [HOST] (Severity: 1): The XMPP message could not be sent because the connection to the XMPP server was refused. (Caused in: Method: XMPP::sendMessage)
#015: Could not bind to socket for XMPP messaging (Severity: 1): The XMPP notification could not be sent because binding to the socket that is used for communication with the XMPP server failed. This error is not caused by the XMPP server. (Caused in: Method: XMPP::sendMessage)
#016: Could not refresh rudecheck table. Database error. (Severity: 2): The list of rudechecks to perform could not be fetched because the query failed or connecting to database failed. (Caused in: Thread: serviceChecks)
#017: Could not refresh service check table. Database error. (Severity: 2): The list of service checks to perform could not be fetched because the query failed or connecting to database failed. (Caused in: Thread: serviceChecks)
#018: Could not start service check module! (Database error) - Retry in 5 minutes. (Severity: 2): The serviceChecks thread did not completely start up because the database connection failed. There will be a retry in five minutes. The general notifications receiver should have been notified about this error. (Caused in: Thread: serviceChecks)
#019: Could not update conditions in online state module! (Severity: 2): The sensor conditions could not be fetched. There will be no online state checks until the sensor conditions can be fetched. (Caused in: Thread: onlineStateChecks)
#020: Could not start online state module! (Database error) - Retry in 5 minutes. (Severity: 2): The onlineStateChecks thread did not completely start up because the database connection failed. There will be a retry in five minutes. The general notifications receiver should have been notified about this error. (Caused in: Thread: onlineStateChecks)
#021: Could not delete old sensor data (Severity: 1): The outdated sensor data that is not used anymore could not be be deleted because the query failed. (Caused in: Thread: maintenanceThread)
#022: Could not delete old service data (Severity: 1): The outdated service data (e.g. response times) that is not used anymore could not be be deleted because the query failed. (Caused in: Thread: maintenanceThread)
#023: Error while semding emergency notification - Retry scheduled. (Severity: 2): A notification message about an declared emergency could not be sent because of an database error. There will be a retry in about one minute. (Caused in: Thread: messageMonkey)
#024: Could not update status of emergency receiver (Severity: 2): The information if an emergency message has been sent or not could not be written to database. This has likely been caused by an database error. (Caused in: Thread: messageMonkey)
#025: Error while semding emergency notification. - No retry scheduled (Severity: 2): A notification message about an declared emergency could not be sent because of an error in the data structure. To avoid loops, there will be no retry. (Caused in: Thread: messageMonkey)
#026: Could not update status of emergency receiver (Severity: 2): The information if an emergency message has been sent or not could not be written to database. This has likely been caused by an database error. (Caused in: Thread: messageMonkey)
#027: Could not update status of emergency receiver (Severity: 2): The information if an emergency message has been sent or not could not be written to database. This has likely been caused by an database error. (Caused in: Thread: messageMonkey)
#028: Could not send emergency notifications. Retry in one minute. (Severity: 2): The list of messages to send could not be fetched because of an database error. There will be a retry in about one minute. (Caused in: Thread: messageMonkey)
#029: Closed connection to client that did not complete transaction after 5 seconds. (Severity: 0): Timeout. A peer that connected to the port that is used for receiving sensor data (usually 12200) did not complete the transaction in five seconds. The connection was closed to avoid blocked processes. (Caused in: Function: killClient)
#030: Could not accept connection from client. (Severity: 1): The accept() function failed. The connection has been terminated. (Caused in: Process: clientHandler)
#031: Received package from Blacklisted host [HOST] (Severity: 0): A blacklisted host tried to send sensor data. The connection was closed immediately. (Caused in: Process: clientHandler)
#032: Could not refresh authentication table. (Severity: 2): The list of hosts and their passwords could not be loaded because the database query failed. (Caused in: Process: clientHandler)
#033: Handshake with client [HOST] failed (Severity: 1): The first, unencrypted handshake with the client did not succeed because of a protocol mismatch. (Caused in: Process: clientHandler)
#034: Handshake with client [HOST] failed (Severity: 1): The first, unencrypted handshake with the client did not succeed because of a protocol mismatch. (Client choose TLS encryption but did not send "STARTTLS") (Caused in: Process: clientHandler)
#035: TLS handshake with host [HOST] failed (Severity: 2): gnutls_handshake() failed. Look for GnuTLS error messages or disable TLS usage of client. (Caused in: Process: clientHandler)
#036: Received invalid TLS package from [HOST] (Severity: 1): gnutls_record_recv() failed. Look for GnuTLS error messages or disable TLS usage of client if this keeps happening. (Caused in: Process: clientHandler)
#037: Could not receive unencrypted sensor data from [HOST] (Severity: 1): There was an error while receiving unencrypted sensor data. This might have been caused by unstable connections. (Caused in: Process: clientHandler)
#038: Could not receive unencrypted sensor data from [HOST] (Severity: 1): There was an error while receiving unencrypted sensor data. This might have been caused by unstable connections. (Caused in: Process: clientHandler)
#039: Host [HOST] sent wrong password. Skipping. (Severity: 2): The host sent another password then the configured one and will get blacklisted. (Caused in: Process: clientHandler)
#040: Adding host [HOST] to blacklist! (Severity: 2): A host that sent a wrong password will be added to the blacklist. (Caused in: Process: clientHandler)
#041: Could not insert host that sent wrong password into blacklist. (Severity: 2): Blacklisting the host that sent a wrong password did not work because the query or database connection failed. (Caused in: Process: clientHandler)
#042: Could not reset alarm timer. (Severity: 1): The alarm timer of a host could not be reset because the query failed. (Caused in: Process: clientHandler)
#043: Could not update IP of host in database. (Severity: 1): The IP of a configured host could not be updated because the query failed. (Caused in: Process: clientHandler)
#044: Could not refresh warning conditions table. (Severity: 2): The list of warning conditions could not be updated because the query or database connection failed. (Caused in: Process: clientHandler)
#045: Could not store sensor data in database. (Severity: 2): Storing of sensor data did not work because the query failed. This could also mean that deleting outdated sensor data from the table "lastsensordata" did not work. (Caused in: Process: clientHandler)
#046: Received package from [HOST] which was not valid (Severity: 2): A client sent an invalid package of sensor data. This data has been refused and the client will be blacklisted. (Caused in: Process: clientHandler)
#047: Adding host [HOST] to blacklist! (Severity: 2): A host that sent invalid sensor data will be added to the blacklist. (Caused in: Process: clientHandler)
#048: Could not insert host that sent invalid package into blacklist. (Severity: 2): Blacklisting the host that sent invalid sensor data did not work because the query or database connection failed. (Caused in: Process: clientHandler)
#049: Client handler: Could not connect to database! Sensor package skipped. (Severity: 2): The sensor data was not accepted because connecting to the database failed. (Caused in: Process: clientHandler)
#050: Terminated. Could not create pidfile! (Severity: 2): The startup process was stopped because writing the pidfile failed. Check if you have proper permissions. (Caused in: main())
#051: Could not connect to database server. Aborting. (Severity: 2): The startup process was stopped because connecting to the database failed. (Caused in: main())
#052: Could not update health statistics. (Severity: 1): Writing of ScopePort health data did not work because the query failed. (Caused in: main())
#053: Could not update health statistics. (Severity: 1): Writing of ScopePort health data did not work because the query failed. (Caused in: Thread: maintenanceThread)
#TLS: Debug message from the GnuTLS library (Severity: 1): This is a message from the GnuTLS library, directly passed into the ScopePort log. (Caused in: Function: logTLS())
#054: Could not update state and time of last check of service. (Severity: 1): The database query that updates the time of the last check and the state (online/offline) of a service failed. (Caused in: ServiceChecks::doChecks)