PS for POSTGRES crashes

Post Reply
nenadv
Posts: 11
Joined: 01 Jul 19 3:55

PS for POSTGRES crashes

Post by nenadv » 30 Oct 20 19:28

I am on the latest PS server edition. My postgres DB is version 11. I was able to create a DB, but nothing happens after I login with admin. I see the following in the event logs:

Faulting application name: IDimagerSU.exe, version: 5.6.0.3205, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.20246.1, time stamp: 0x207525e3
Exception code: 0xc0000005
Fault offset: 0x0000000000033c48
Faulting process id: 0x6b30
Faulting application start time: 0x01d6aee687ca844f
Faulting application path: C:\Program Files\IDimager Products\Photo Supreme 5 PostgreSQL\IDimagerSU.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 25c726b7-12d7-46bb-a3ec-6d0e59341b1c
Faulting package full name:
Faulting package-relative application ID:

If I start PS again I get a message "Another process is currently upgrading your database. ...", if I hi continue I get another fault in the event log.

Any idea?

Hert
Posts: 6435
Joined: 13 Sep 03 7:24

Re: PS for POSTGRES crashes

Post by Hert » 31 Oct 20 9:42

You're reporting a Windows message, but Windows error reports (unlike macOS reports) don't provide information. Is Photo Supreme perhaps giving an error before you get this Windows error?

Some obvious things to check:
1. Try to reinstall Photo Supreme
2. Make sure your firewall is not blocking the application from accessing the PostgreSQL database
3. Make sure that you have a physical connection to the same network used by the machine that database is installed on

If all positive;
1. Try to start PSU while keeping pressed the Ctrl+Alt+Win keys
2. Re-create that catalog
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

nenadv
Posts: 11
Joined: 01 Jul 19 3:55

Re: PS for POSTGRES crashes

Post by nenadv » 03 Nov 20 0:28

Hmm .. tried many things. You think that PS crashed because it got a bad response from the database.

I already tried ctrl-alt-win, uninstall, and install PS. And BTW, when you install again you are not prompted to create a new DB, it already knows about it, so something was left behind after uninstall. I was able to test the DB and able to create a user and DB for my use.

Why would I get this message about another process trying to update if there are no running PS processes (I restarted the machine and started PS again). At on point, I saw a progress bar of the DB update, bet it went away.

Any logging I can turn on?

Hert
Posts: 6435
Joined: 13 Sep 03 7:24

Re: PS for POSTGRES crashes

Post by Hert » 03 Nov 20 0:57

Are you getting an error from Photo Supreme when it crashes (not the windows event error). If so, can you share what that is? Thank you
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

nenadv
Posts: 11
Joined: 01 Jul 19 3:55

Re: PS for POSTGRES crashes

Post by nenadv » 03 Nov 20 1:57

I am able to create database, and click continue to login to it. The window with message:

Another process is currently upgrading your database, ...

If I click "ignore and continue" I eventually crash with an exception. Who is reporting this? It does not finish ever, why do I have to upgrade the DB I just created.

nenadv
Posts: 11
Joined: 01 Jul 19 3:55

Re: PS for POSTGRES crashes

Post by nenadv » 03 Nov 20 3:19

I cleaned up everything.

(1) uninstall PS server and standalone
(2) remove data under AppData
(3) cleaned up the registry as much as I could

I installed the server version. All went well until I connected to the new DB with admin and provided a password. A small window, progress bar, showed up for a couple of seconds with words of upgrading the database. It disappeared and app crashed. The last entries in the log for postgres:
2020-11-02 18:12:02.146 PST [107881] LOG: statement: CREATE VIEW v_AlbumVersion as SELECT v.* FROM v_ImageVersion v, v_AlbumDisplayVersionPlaceHolder ph WHERE ph.ItemGUID=v.GUID
2020-11-02 18:12:02.159 PST [107881] LOG: statement: COMMIT
2020-11-02 18:12:02.170 PST [107881] LOG: statement: BEGIN
2020-11-02 18:12:02.181 PST [107881] LOG: statement: CREATE VIEW v_CatalogItem as select i.*, ( select count(1) from idImageVersion v where v.MainImageGUID = i.GUID ) as idVersionCount, 0 as idMainVersion, i.GUID as MainGUID, fp.MediumType as MediumType, fp.MediumName as MediumName, fp.MediumSerial as MediumSerial, fp.FilePath || i.FileName as FullFileName, fp.FilePath as FilePath, ( select count(1) from idProp p, idCatalogItemDefinition d where p.GUID = d.GUID and d.CatalogItemGUID = i.GUID and p.PropValue <> 'A' ) as idPropCount from idCatalogItem i, idFilePath fp where fp.GUID = i.PathGUID
2020-11-02 18:12:02.198 PST [107881] LOG: statement: COMMIT
2020-11-02 18:12:02.209 PST [107881] LOG: statement: BEGIN
2020-11-02 18:12:02.221 PST [107881] LOG: statement: update idVersionInfo set VersionNr = 2843
2020-11-02 18:12:02.233 PST [107881] LOG: statement: COMMIT
2020-11-02 18:12:02.250 PST [107881] LOG: statement: prepare prepst10 as select GUID, PropName, idDescription, idSynonyms from idProp
2020-11-02 18:12:02.263 PST [107881] LOG: execute prepst10: prepare prepst10 as select GUID, PropName, idDescription, idSynonyms from idProp
2020-11-02 18:12:02.274 PST [107881] LOG: statement: prepare prepst11 as select GUID, CategoryName from idPropCategory
2020-11-02 18:12:02.286 PST [107881] LOG: execute prepst11: prepare prepst11 as select GUID, CategoryName from idPropCategory
2020-11-02 18:12:02.380 PST [107886] LOG: statement: prepare prepst0 as select * from idVersionInfo
2020-11-02 18:12:02.392 PST [107886] LOG: execute prepst0: prepare prepst0 as select * from idVersionInfo
2020-11-02 18:12:05.480 PST [107881] LOG: could not receive data from client: Connection reset by peer
2020-11-02 18:12:05.486 PST [107886] LOG: could not receive data from client: Connection reset by peer

Hert
Posts: 6435
Joined: 13 Sep 03 7:24

Re: PS for POSTGRES crashes

Post by Hert » 03 Nov 20 10:01

From the PostgreSQL log, it seems that the connection is killed unexpected.
1. Do you have some virus scanner installed? If so, can you try to temporarily disable that?
2. Do you have a firewall installed? If so, can you try to temporarily disable that?

PS. You get the message that the database is being updated because during the upgrade of the database, a flag is set. When during the update of the database the application crashes then the flag is never reset. So you'll have to click the button that it's ok to reset the flag.
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

nenadv
Posts: 11
Joined: 01 Jul 19 3:55

Re: PS for POSTGRES crashes

Post by nenadv » 03 Nov 20 18:52

In the end, I got it working. I tried pg 9.4 with no success.

- installed pg12
- went on a different computer with no PS installed before
- somehow I noticed that you had a release on Nov 1 - I think you should add a version number and date for the release on the download page, as well as in the filename itself
- database was updated, but somewhere in the end it gave me a nice message that PG is missing some contribution module. Note that before, I would not get any message for PS about the DB, just a crash. This time it did not crash. And it was happening much earlier in Db update step.
- After fixing PG, I was able to complete DB update and run PS.
- Went to the old computer, installed new version, clicked on ignore for the update flag, and went into PS main screen

I am guessing that the combination of the new version and PG12 made a difference.

nenadv
Posts: 11
Joined: 01 Jul 19 3:55

Re: PS for POSTGRES crashes

Post by nenadv » 04 Nov 20 2:40

Well, I was able to install and work with the PS. But, it does crash from time to time:

- it crashed almost at the end of the folder import (2500 pics)
- when I restarted I had all the pictures there
- but then, it crashed a couple of more times while working on the folder pictures

It crashes at the same place as before.

I can run this under win debugger, but I'll need a symbol file to make sense of it.

Hert
Posts: 6435
Joined: 13 Sep 03 7:24

Re: PS for POSTGRES crashes

Post by Hert » 04 Nov 20 8:51

nenadv wrote:
04 Nov 20 2:40
somehow I noticed that you had a release on Nov 1 - I think you should add a version number and date for the release on the download page, as well as in the filename itself
You can always check the latest build here:
https://www.idimager.com/what-s-new-in-photo-supreme-v5

The application's EXE file includes debug symbols. If the application crashes you typically are presented with a dialog and an option to submit the exception. You can also click the option to see what will be sent first and check the debug call stack, even when not submitting the exception.

But here too, something appears to be wrong on that machine. Check if you also get exceptions when importing on that other computer that you used to upgrade the database. I'm pretty sure that the exact same reason why you couldn't upgrade the database is still the reason why you now get crashes.

Did you check the network connection between that machine and the DB server?
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

nenadv
Posts: 11
Joined: 01 Jul 19 3:55

Re: PS for POSTGRES crashes

Post by nenadv » 06 Nov 20 20:10

I did more experiments, on other Windows and Mac machines. They are working better than the original machine but witnessed two crashes, one on each. In both of them, I was presented with the exception window and was able to send a report to you. This is not happening on the original machine, probably as I am running a beta of Windows on it.

A network connection to DB is fine, I am able to connect with three computers, and log all the queries.

Hert
Posts: 6435
Joined: 13 Sep 03 7:24

Re: PS for POSTGRES crashes

Post by Hert » 06 Nov 20 21:07

I just checked the error log.
Execution of query failed (PostgreSQL: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
) (0)
That typically means that the connection between client and server is ended abnormally.
This is a PostgreSQL error. Googling the error gives lots of results. But this link gives an advise to add a config setting listen_addresses to your PostgreSQL.conf file.
https://stackoverflow.com/questions/159 ... xepectedly
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

Post Reply