![]() ![]() frequent, spurious 10054 and/or 10061 error records in firebird.log.there are messages in service.log (formerly iphost.log) file telling that a SQL query can’t be executed.IPHost monitoring service stops soon after it’s started, or refuses to start.The following are typical syndromes of monitoring database inconsistency that could suggest checking the database When shall I check my monitoring database? Unless you fully understand what you are doing, you can irreversibly damage database, so the remaining option would be to install IPHost Network Monitor with clean database. If unsure, either find and ask someone with DBA experience to do that for you, or ask us to help. ![]() Make sure you have DBA (database administration) experience before going on. Important! Fixing IPHost monitoring database is a set of advanced techniques. How do I check whether monitoring data and settings are fine?Ī: try following the steps below, or contact our Tech. Q: IPHost monitoring service gets stopped right after it’s started. You can read up-to-date monitoring database recovery instructions here. To learn which IPHost version you are using: start IPHost GUI client and proceed to “Settings > About IPHost Network Monitor”. Starting from v5.1 build 13751, IPHost uses Firebird engine version 3.* the below instructions don’t support it. Important notice: the below article is only applicable to IPHost versions up to v5.1 build 13330 (inclusive), published in July 27, 2018.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |