On Mon, Jun 27, 2016 at 11:03:36AM +0200, Sébastien Jodogne wrote: > > - I would not have guessed that adding --upgrade might have made > > a difference to a failure that tells me "stack smashing detected" > > at the console :-) > > Just to be sure: Is your issue an immediate crash with "stack smashing > detected", or is your issue a failure while executing the "--upgrade"?
Both are (were) issues for me. I have attempted to solve the upgrade issue by dropping/re-creating the database in PostgreSQL because the database did not hold production data. However, Orthanc-on-PG does not start anymore because the PG plugin now crashes with "stack smashing detected" so I cannot verify whether it would properly start with the new empty database ... > In the former case, couldn't it be possible that the > version of some shared library does not match its version of > the headers, maybe because of an unstable Debian? That is surely possible. That is why I offered to provide more information if told how to do so. > > Would you mind adding a line to the log indicating that > > --upgrade might be needed when Orthanc detects that situation > > at startup ? > > This is already the case; Here is a sample log of Orthanc 1.0.0 asking an > upgrade with the PostgreSQL plugins 2.0 (notice the line starting with "E"): I figured that out. It didn't have that line in the log when I first attempted the upgrade. Thanks, Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
