Volker Posted April 7, 2021 Report Share Posted April 7, 2021 Hi, after upgrading to the recent 7.0 I observe have these problems: closing a client takes up to a minutes when restarting the client apllication it takes several minutes until I can connect to the catalog again, because the maximum number of connections has been reached. Considering the new interface I would like to revert a previous version. Is there a way to do so? Best regards, Volker Quote Link to comment Share on other sites More sharing options...
Daria Kotilainen Posted April 7, 2021 Report Share Posted April 7, 2021 Hi Volker, Please restart Daminion server to drop the connections. You can also switch to the dark move via View menu. Please let em know if you created the backup of the catalog prior to the upgrade? In this case, yes, you can revert to the previous version without any issues. Daria Quote Link to comment Share on other sites More sharing options...
Volker Posted April 7, 2021 Author Report Share Posted April 7, 2021 Thank you for your reply, Daria. After restarting Daminion server the behaviour is unchanged: closing a client takes a very long time and starting the client doesn't work, because the connection limit has been reached. The dark view is working partially; just the thumbnail windows is affected. Volker Quote Link to comment Share on other sites More sharing options...
Volker Posted April 7, 2021 Author Report Share Posted April 7, 2021 Tha same behaviour occurs with 7.0.1.2427. Quote Link to comment Share on other sites More sharing options...
Volker Posted April 7, 2021 Author Report Share Posted April 7, 2021 When closing the client application I can see a very high CPU usage on the server with one or two of the Postgres processes. In the logs there are lots of syntax errors reported: ERROR 2021-04-07 21:51:08,175 FtsLoader.RecurrentTask [3] - Npgsql.PostgresException (0x80004005): 42601: Syntaxfehler bei »on« bei Npgsql.NpgsqlConnector.<>c__DisplayClass160_0.<<DoReadMessage>g__ReadMessageLong|0>d.MoveNext() --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() bei Npgsql.NpgsqlConnector.<>c__DisplayClass160_0.<<DoReadMessage>g__ReadMessageLong|0>d.MoveNext() --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei System.Threading.Tasks.ValueTask`1.get_Result() bei Npgsql.NpgsqlDataReader.<NextResult>d__44.MoveNext() --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei Npgsql.NpgsqlDataReader.NextResult() bei Npgsql.NpgsqlCommand.<ExecuteReaderAsync>d__102.MoveNext() --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei Npgsql.NpgsqlCommand.<ExecuteNonQuery>d__92.MoveNext() --- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde --- bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) bei Npgsql.NpgsqlCommand.ExecuteNonQuery() bei Dapper.SqlMapper.ExecuteCommand(IDbConnection cnn, CommandDefinition& command, Action`2 paramReader) in /_/Dapper/SqlMapper.cs:Zeile 2797. bei Dapper.SqlMapper.ExecuteImpl(IDbConnection cnn, CommandDefinition& command) in /_/Dapper/SqlMapper.cs:Zeile 568. bei FtsLoader.CatalogRepository.<>c__DisplayClass12_0.<SaveContent>b__0(IDbConnection connection) in C:\DaminionAutoGit\code\FtsLoader\src\FtsLoader\CatalogRepository.cs:Zeile 79. bei FtsLoader.Repository.UsingConnection[T](Func`2 func) in C:\DaminionAutoGit\code\FtsLoader\src\FtsLoader\Repository.cs:Zeile 20. bei FtsLoader.CatalogRepository.SaveContent(Int64 mediaItemId, String content) in C:\DaminionAutoGit\code\FtsLoader\src\FtsLoader\CatalogRepository.cs:Zeile 78. bei FtsLoader.RecurrentTask.RunAsync(ITask currentTask, IServiceProvider scopeServiceProvider, CancellationToken cancellationToken) in C:\DaminionAutoGit\code\FtsLoader\src\FtsLoader\RecurrentTask.cs:Zeile 72. Exception data: Severity: FEHLER SqlState: 42601 MessageText: Syntaxfehler bei »on« Position: 102 File: src\backend\parser\scan.l Line: 1002 Routine: scanner_yyerror Quote Link to comment Share on other sites More sharing options...
Katerina Karpenko Posted April 8, 2021 Report Share Posted April 8, 2021 Hello, If you use PostgreSQL lower than v. 10, please update it. To upgrade your PostgreSQL version, please follow these steps: - download PostgreSQL 10 or 12 (https://www.enterprisedb.com/downloads/postgres-postgresql-downloads) - Create backups of your catalogs in the Daminion server admin panel - Stop your current PostgreSQL and manually kill all residual processes if any (in TaskManager) - Run the installation of PostgreSQL and make sure it is being installed to the port 5432 - Once the installation is done, please double-check that only PostgreSQL is running - Go to Daminion server admin panel > Catalogs > select a catalog > Actions > Restore and restore the catalogs from the backups you created earlier. - Run Daminion server Let me know if you have any problems with the process. Kind regards, Kate Quote Link to comment Share on other sites More sharing options...
Volker Posted April 8, 2021 Author Report Share Posted April 8, 2021 Hi Kate, thank you very much for these detailed instructions. I was able upgrade PostgreSQL without any problems and now the Daminion clients are working flawlessly again 🙂 Is it safe to uninstall the previous database version now? Best regards, Volker 1 Quote Link to comment Share on other sites More sharing options...
Katerina Karpenko Posted April 8, 2021 Report Share Posted April 8, 2021 Yes, you can uninstall it if any other system doesn't use it. But for the Daminion catalogs, you should use only one version of PostgreSQL. Kind regards, Kate Quote Link to comment Share on other sites More sharing options...
WilfriedB Posted April 9, 2021 Report Share Posted April 9, 2021 On 4/8/2021 at 11:04 AM, Katerina Karpenko said: PostgreSQL 10 or 12 Kate, does this mean PostgreSQL is supported and was tested with Daminion? I remember a post where somebody claimed to have seen performance improvements after upgrading to PostgreSQL 12 (or 13?). Quote Link to comment Share on other sites More sharing options...
Katerina Karpenko Posted April 9, 2021 Report Share Posted April 9, 2021 Hi Wilfried, Yes, Daminion supports PostgreSQL 12. Some of our users have updated PostgreSQL since the 6.8 release. Unfortunately, Daminion does not support version 13 yet. Kind regards, Kate Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.