I now receive the following error when I try to open EventSentry: OdbcExpandError: [08001]

+1 vote
asked Feb 23, 2018 in EventSentry by msimmons13 (600 points)
After attempting to install the latest update I now receive the following error when I try to open EventSentry: OdbcExpandError: [08001] FATAL: the database system is shutting down (101) at SQLConnect

 

This is on a webserver, using the MySQL that EventSentry installed. Please let me know what further info I can provide.

Also, it seems the "Heartbeat agent" will not update... I continue to receive the "Version Information" popup showing the installed version is not current.

1 Answer

0 votes
answered Feb 24, 2018 by Ingmar (7,190 points)
selected Feb 26, 2018 by msimmons13
 
Best answer
The error you are getting would imply that the database server was being shut down during the update, which is a standard procedure since the built-in database is sometimes patched. Please open "Services" on this host and locate the "EventSentry Database" service - is the service running? If it's not, please start it. Please note that EventSentry does not install a MySQL database, the database which ships with EventSentry is a PostgreSQL-based database.

In regards to the Heartbeat service not updating, in the management console please click on "Heartbeat" and then click the "Update ..." button on the bottom left. When prompted, browse to the EventSentry installation directory, usually C:\Program Files (x86)\EventSentry. This will copy the eventsentry_hb_svc.exe to the C:\Windows\syswow64\eventsentry directory.

If the EventSentry Database service was stopped then we'd definitely want to investigate this further, this service should always restart automatically when you apply a patch.
commented Jun 17 by msimmons13 (600 points)
Hi,

I seem to be having this exact issue again after upgrading to 4.0.3.6, but this time I see no evidence of multiple versions of postgres.exe running from EventSentry's "rollback" folder.

Any suggestions?
commented Jun 18 by Sally (2,460 points)
Maybe something stole the port that the database normally uses?  You would find out when restarting the EventSentry Database service, upgrading the postgres, rebooting the server, etc.
Can you please use Administrator command prompt to run this:
Netstat -aon | find “5432”

Nothing should match while the EventSentry Database service is stopped, if something matches while that is stopped you have some other program stealing your database port.  You can look in task manager (details tab) to see which program has the same PID as the matching result, and that would be the port-stealing program, which you can hopefully configure to use a different port than 5432 so that your database will be able to start again.

If nothing matches that netstat command while the EventSentry Database service is stopped, can you use Administrator command prompt to run this and see if it throws a more detailed error:
"C:\Program Files (x86)\EventSentry\postgresql96\bin\pg_ctl.exe" runservice -N "eventsentrydatabase96" -D "C:\Program Files (x86)\EventSentry\data96" -o "-p 5432"
commented Jun 25 by msimmons13 (600 points)
Hi,

I rebooted the server and now I receive the following (I've received about 150 in the past 12 hours):

      54321-WEB2         532     
       EventSentry              
       Application         6/25/2019 7:58:37 AM     
       Warning (Info)         3644703     
 
 
     The following errors or warnings occurred within the last 5 minutes while communicating with the database:

Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)
Primary Database: OdbcExpandError: [42703] ERROR: column "alert_isactive" of relation "esperformancemapping" does not exist;
Error while executing the query (7)

 
     If you have Extended Error Logging enabled, event ID 532 indicates the agent can connect to the database but cannot write data. Event 530 is enabled by default and indicates that the agent cannot connect to the database.
commented Jun 25 by Steven Flowers (2,320 points)
Hello,

In the EventSentry management console, if you click on your database action and then click "Initialize or Update Database", this should add the missing columns this error message is complaining about. If that doesn't resolve your issue and stop these errors, please let us know.

Thank you,
Steven
commented Jun 25 by msimmons13 (600 points)
That appears to have fixed it! Thank you very much!
Welcome to EventSentry Q&A, where you can ask questions and receive answers from other members of the community.
...