|
|
Address by this work also 0010970 or report if there are (still) issues. |
|
|
Fix title: Backend version is, btw, v1.3.1 (what you see invoking taler-merchant-httpd --verision) and backoffice SPA version already is v1.3.4 (which can be seen in the merchant web interface or on the system here: /usr/share/taler-merchant/spa/version.txt) : I got this wrong first, thought versioning between both components was harmonized. |
|
|
I tried first to upgrade TOPS/CHF test platform taler.hacktivism.ch from v1.3.0 of the backend to v1.3.1, given stage is already installed with v1.3.1. Given that between v1.2.6 and 1.3.0 I didn't experience any issues on the hacktivism platform, I did assume jumping in production from v1.2.6 to v1.3.1 should also work. Only thing I realized is that DB scheme changed from v1.3.0 to v1.3.1 (between v1.2.6 and v1.3.0 it didn't change), such that taler-merchant-dbinit needed to be run as $USER in order to be able to start the services again, this being taler-merchant-httpd on all instance involved. The Operator's Manual suggests to anyhow always run this command, such as to avoid critical-looking errors with DB connection errors, even though if such errors appear it's also made clear in the error logs that taler-merchant-dbinit should be run, which is also documented to always do: https://docs.taler.net/taler-merchant-manual.html#upgrade-procedure The following steps do the job and should always work to upgrade a merchant; as root: systemctl stop taler-merchant.target # Safer to stop the taler-merchant-* server components. ... psql backups were done by psql_dump and psql_dumpall (under clean circumstances redundant, but easier for a raw import should other tables exist) ... apt-get update apt-get upgrade # Confirming then to upgrade taler-merchant package and dependencies As $USER for the backend, this being taler-merchant-httpd, these steps were required: # From root su - taler-merchant-httpd -s /bin/bash # Being root, with no login shell defined by default for taler-merchant-httpd / $USER. taler-merchant-dbinit # No output is good. # Again as root exit # Assuming being user taler-merchant-httpd systemctl start taler-merchant.target # Check status of taler-merchant-httpd(.service); as root systemctl status taler-merchant-httpd should show the service running again. # Check journalctl for unit taler-merchant-httpd(.service); as root journalctl -u taler-merchant-httpd # Try an instance to make sure things are most probably sane I was already logged in to talersticker, which is used for public wallet testing and couldn't see any obvious issues, as for what concerns data availability. |
|
|
Make title clearer, as it was not immediately clear of which prod system we're talking about. |
|
|
Reassign to me, vanished before by mistake. |
|
|
(Re-)Logins and actual CHF test payments on TOPS/CHF test platform taler.hacktivism.ch and my.taler-ops.ch (this first), now both running merchant version v1.3.1 and backoffice SPA v1.3.4 underway... make sure core functionality works for sure! |
|
|
Good, also relogin w/ either email or SMS. Same applies for taler.hacktivism.ch which is still used to show-case Taler payments to interested folks. |
- Anonymous
