Hello rolfschmidt,
thanks for the tip.
I renamed the file and the error from my first post is gone.
The system then reported that the PostgreSQL version is too low.
Version 10+ is required - installed and used 9.5.25.
################################################################
Using “pg_lsclusters” I was then able to see that new PostgreSQL versions were installed during the last update process.
9.5 main 5432 online postgres /var/lib/postgresql/9.5/main /var/log/postgresql/postgresql-9.5-main.log
10 main 5433 online postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
12 main 5434 online postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log
14 main 5435 online postgres /var/lib/postgresql/14/main /var/log/postgresql/postgresql-14-main.log
################################################################
“pg_upgrade” could not be performed
Performing consistency checks
Checking cluster versions ok
failure
Consult the last few lines of “pg_upgrade_server.log” for
the probable cause of the failure.
connection to server on socket “/var/lib/postgresql/.s.PGSQL.50432” failed: No such file or directory
Is the server running locally and accepting connections on that socket?
could not connect to source postmaster started with the command:
“/usr/lib/postgresql/9.5/bin/pg_ctl” -w -l “pg_upgrade_server.log” -D “/var/lib/postgresql/9.5/main” -o “-p 50432 -b -c listen_addresses=‘’ -c unix_socket_permissions=0700 -c unix_socket_directories=‘/var/lib/postgresql’” start
Failure, exiting
################################################################
After several attempts to specify the database version, I took a more radical approach
- Backup of the DB created
- All versions of PostgreSQL removed 9.5 / 10 / 12 / 14
- PostgreSQL installed version 17
- Recovery from DB backup
################################################################
Command “zammad run rails r “Setting.set(‘es_url’, ‘http://127.0.0.1:9200’)”” could now be executed
When I ran “zammad run rake searchindex:rebuild” I got the message:
rake aborted!
Don’t know how to build task ‘searchindex:rebuild’
web interface not accessible but the error changed to 500 Internal Server Errors.
All services are running Zammad => OK | Elasticsearch => OK | nginx => OK | Functional test nginx -t => OK
################################################################
I restarted the server – after that error 500 went away but “CSRF token verification failed!” when trying to log in
Changed the following values in zammad.conf
from => proxy_set_header X-Forwarded-Proto $scheme
to => proxy_set_header X-Forwarded-Proto https;
################################################################
After I restarted the nginx service, another error occurred which I unfortunately hadn’t noted down
With “zammad run rake searchindex:rebuild” I got the message => rake aborted! Don’t know how to build task ‘searchindex:rebuild’
“zammad run rake db:migrate” was possible - some data was also migrated
When I tried to log in, the error message that was no longer known was gone, but now you are logged out again immediately after logging in. Error message in the login mask “The session is no longer valid. Please log in again”
################################################################
What would be the next step?
PS: I’m only writing this in detail so that others might find it helpful 