Unimus forum

Hello,

Running into an issue with Config Search functionality. We have ~300 devices backing up daily with 180 day retention, postgresql db - we can see all of the backups, but cannot seem to search configs quickly.

When we perform a config search the page just puts up the spinning circle/working icon for several minutes without ever returning results or presenting a failure message. Given enough time, we do receive results - but it has severely hampered the usefulness of the function.

I've upgraded from 2.6.0 to 2.6.3 and performed a full host restart as preliminary troubleshooting - we also don't seem to be getting anywhere near system resource limitations during a search (28%cpu, 25%memory). It doesn't seem to make a difference how tight a search or how wide either, (1 device vs. all devices).

Without an error message this is a bit hard to self diagnose - are there steps/procedures that can be provided to assist?

Thanks,
Alex

This sounds like an issue with the database or possibly storage.

I would first make certain that you have a current backup of your database before any more diagnostics. If the issue is a failing disk then you could be on a timer before data could be lost.

Here's a link to Postgres docs on backup: https://www.postgresql.org/docs/current/backup.html

I personally have only done SQL Dumps for my backups, https://www.postgresql.org/docs/current ... -dump.html, but this situation makes me think that a filesystem backup might be more appropriate especially since it requires you to shut down the DB first: https://www.postgresql.org/docs/current ... -dump.html

If you already have a backup, Unimus does have some pretty extensive logging which can help you to diagnose the issue.
https://wiki.unimus.net/display/UNPUB/L ... +Subsystem

Since the system seems to have extra memory available you probably can increase the memory allocation to the Unimus server which should help performance in general: https://wiki.unimus.net/display/UNPUB/C ... mory+usage
Do keep in mind that you do need to leave some memory for the Postgres DB.

My last thought is that is your database optimized for Unimus? You could also just be running into a bug if you are running an older Postgres version, so updating it might be helpful as well.
https://wiki.unimus.net/display/UNPUB/D ... quirements

If you have any questions or need some clarification, just ask. If none of this highlights/resolves the issue I will make certain to bring in the big guns for diagnostics.

Thanks Tommy,

This is on enterprise grade datacenter hardware, so I'm not worried at least about a failing physical disk.

I've bumped out the memory to 2G, even tried 4G without any performance improvement. 16 gigs assigned to the vm, I've still got 60+ gigs of disk available as well.

We're on postgresql 11, following the guidelines around requirements. Only difference I can think of is that we upgraded to 2.6.0 when it became available, but we didn't have this config search issue until relatively recently.

Let's get those big guns engaged please?

Hey,

So I chatted with the devs and they said we are releasing a new DB driver in 2.7.0 which revamps how we do Config Search in PostgreSQL. This should be released any day now and they that might be the solution to the problem.

That said, there are some questions about what logs Unimus is generating during the config search. Have you enabled logging and taken a look? If so, does anything stand out to you?

Following up, now that 2.7.0 has been released, have you had the opportunity to update and see if that resolves your issues?