Poof crashes / instability

[acertain]

Well, I just started a scan on the rest of the folders (2011 - 2021) and just came back and it has crashed. Do you run with Postgres on a separate machine? Is it possible the database connection is timing out and killing the process?

[Hert]

I do run PostgreSQL on a stand alone machine. But on one machine also on the same machine. Connection timeouts should be no issue because PSU has connection recovery in case a connection is lost.

Did you also check the PostgreSQL logs?

[acertain]

Nothing in the logs at default logging levels.

[Hert]

If there's nothing in the PostgreSQL log then the database connection is fine.

Maybe you can start a new catalog and import your images to that and see if it's perhaps something in your current catalog that causes the crash. Start a new catalog from the Catalog menu in the hamburger menu. Start importing a smaller set first to see if there's a difference.

[acertain]

If I make sure everything is written out to the files, is there any other data or setting I need to save somewhere to make sure I don't lose anything?

[Hert]

You can create a PostgreSQL backup as described in the Maintenance manual.
But you can create a second catalog in your database with a different name so that the old one also stays available. But creating a backup of the catalog database is always recommended.

[acertain]

I have been super busy at work, so haven't gotten back here yet. I know about creating a backup of the catalog. But if I write everything out to the image files and then reimport them all to a new catalog, will all the information be preserved?

[Hert]

First make sure you have a backup.

PSU keeps a "last resort" backup in the metadata, called the ICS (IDimager Core Schema). By default PSU is configured to write the ICS.

If you want to rebuild a catalog from the ICS then make sure that after creating a new catalog that you enable ICS reading in the Sync settings. Try it with a few images first.

Please don't forget to switch ICS reading off after your import has completed. ICS writing should be kept switched ON, but ICS reading must be switched OFF for normal operation.

[G8DHE]

Does reading the ICS take precedence over the other metadata then Hert, or are any changes in the metadata included as well ?

[Hert]

ICS complements the standard metadata and contains the data that is not in other metadata (like version info, stacks, etc).

[acertain]

I just created a new catalog. And then tried to exit PSu. Instead, I got an exception.


So I killed PSu, restarted, opened the new, empty catalog, created another new one. And the same thing happened.

[acertain]

Well, back to verifying folders, and another poof crash. This one came with an exception report. Although unfortunately this looks like an after-effect of the crash rather than the cause. Looks like maybe heap corruption?

[acertain]

First make sure you have a backup.

PSU keeps a "last resort" backup in the metadata, called the ICS (IDimager Core Schema). By default PSU is configured to write the ICS.

If you want to rebuild a catalog from the ICS then make sure that after creating a new catalog that you enable ICS reading in the Sync settings. Try it with a few images first.

Please don't forget to switch ICS reading off after your import has completed. ICS writing should be kept switched ON, but ICS reading must be switched OFF for normal operation.

I have a backup. So can you explain how to do this? If I create a new catalog, won't it have an empty ICS? Can you give me step-by-step instructions? Because I've got 4 days left on my trial and right now, giving up seems like the best option.

Thanks.

Andrew

[acertain]

OK. So how does restore work at all? I have a backup from before all of this started happening. It's 50MB, so I think it is a real backup. But then when I create a new catalog and select restore, it just immediately pops up a window saying that restore is finished and that PSu will restart. Which it doesn't. I've tried restoring in on several computers, and with both the stand-alone and server editions and always get the same thing.

[Hert]

You can create a PostgreSQL backup as described in the Maintenance manual.

Restoring is also explained in the Maintenance manual.