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

Question

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.

Answer 1

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.

Comments

>Please open "Services" on this host and locate the "EventSentry Database" service - is the service running?
It is not. If I start it manually, I receive a popup saying the service started and then stopped.

>Please note that EventSentry does not install a MySQL database, the database which ships with EventSentry is a PostgreSQL-based database.
Sorry, I misspoke I meant PostgreSQL. Was mostly attempting to state that I was using the "built in" database.

>In regards to the Heartbeat service not updating, in the management console please click on "Heartbeat" and then click the "Update ..." button
That worked and I no longer receive the "Version Information" popup. I noticed on the "home page" the "Collector" was showing a lower version number so I did the manual update there too and that is now correct.


>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.

I agree. Something went wrong with this patch session for both of my servers (same behavior on both) and it is still not running. My thought is that I need to simply uninstall & reinstall, but I will wait if that helps improve the product.

---

Hello,

If you double-click on the EventSentry Database v9.6 service, what is the path to executable? Is it:

"C:\Program Files (x86)\EventSentry\postgresql96\bin\pg_ctl.exe" runservice -N "eventsentrydatabase96" -D "C:\Program Files (x86)\EventSentry\data96" -o "-p 5432"

Is the "pg_ctl.exe" in the correct location? Is the database in the correct directory? If the file/database folders are in the correct location and it's still not starting, please contact support so that one of our representatives can do an online meeting with you.

Steven

---

>If you double-click on the EventSentry Database v9.6 service, what is the path to executable? Is it
Yes, it matches what you said.

>Is the "pg_ctl.exe" in the correct location?
yes.

>Is the database in the correct directory?
yes.

>please contact support so that one of our representatives can do an online meeting with you.
How do I go about doing that?

---

Hello,

If you email support@netikus.net and reference this forum post, someone should be able to help you out and provide you with a link to schedule a meeting.

Thank you.

---

All corrected now, marked as answer and updating for future reference. The issue was multiple versions of postgres.exe running from EventSentry's "rollback" folder.

Thanks for the assistance!

---

Thank you for confirming, this is the first time we've observed this issue. We'll keep an eye out for this in case another user runs into this issue.

---

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?

---

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"