Hello Dimitri, I am very sorry that it broke your installation but it can be fixed in a minute.
We usually take extreme care to not break things on releases and this is the first time in the 3.x branch we decided to do so and I am pretty sure that there is almost no production deployment out there that is affected by this problem. When moving towards production we urgently suggest to review the authentication handler as the default setup comes with fixed passwords and "no auth" settings for testing! The authentication logic is described in detail in the configs in auth/ and on RTD: https://openxpki.readthedocs.io/en/latest/reference/configuration/realm.html#authentication For your actual problem - just open the file config.d/auth/stack.yaml and remove the authentication stacks you dont need or replace them with the config from the new upstream repository. Oliver Am 04.05.21 um 09:18 schrieb Dimitri TIMOCHENKO via OpenXPKI-users: > > Hello, > > When I was in the process of installing the v3.x version, automatic > update just came and corrupted the installation. > > The recently updated documentation addresses this broken (and > breaking) update with a recommendation to remove the whole > “/etc/openxpki folder created by the package and replace it with > a”manually downloaded directory. > > So, the only suggestion I see for now is to scrap your existing > installation and start over. If you had a production installation, it > would be killed either by the Debian package upgrade, or the manual > configuration replacement. I don’t see how to remediate this upgrade > issue, or how to preserve the existing configuration. > > > > When I was installing, I did not use sampleconfig.sh because I did > not want a demo configuration which “*never be used for > production”.*So, I don’t know, if I had a so-called “default” > configuration or not. Either way, my installation has become broken > with the same errors as yours. > > I do not have proxies nor sso systems, but the only place I find the > word “NoAuth” in the documentation is in the “Realm” section. But it > is unclear, how to remove these 2 handlers External and ClientSSO,in > which files/places, and how to help the existing system survive such > upgrades. In my case, as I could not yet install previous version, the > obvious way is to remove everything and start over. > > I am very sorry, but this is my sad feedback. > > > > *From:*Oliver Welter <[email protected]> > *Sent:* Monday, May 3, 2021 8:32 AM > *To:* [email protected] > *Subject:* Re: [OpenXPKI-users] Error after system update Debian 10 > > > > > > https://openxpki.readthedocs.io/en/latest/upgrading.html#release-v3-12 > <https://openxpki.readthedocs.io/en/latest/upgrading.html#release-v3-12> > > > > > > Am 03.05.21 um 05:55 schrieb Sandy Christiawan: > > Hello, > > > > I just built Openxpki with sampleconfig and it works fine for > experiment and stuff and learning about the basic functionality > with the RPC API. > > But then my Debian asked about OS updates and I thought that it > may not break everything. > > After updating and my VM restarted, i cannot run any openxpki > services like the Web give me this error: "Backend service is not > reachable or not responding" and the RPC api give me this error: > > { > "error": { > "message": "Unable to query OpenAPI specification from > OpenXPKI server", > "code": 50004, > "data": { > "pid": 1987 > } > } > } > > > > And when i try to do some command like openxpkictl start and also > other commands i got this same error message: > 2021/05/03 10:52:09 I18N_OPENXPKI_CLIENT_INIT_CONNECTION_FAILED; > __ERROR__ => Connection refused, __SOCKETFILE__ => > /var/openxpki/openxpki.socket > 2021/05/03 10:52:09 > > I18N_OPENXPKI_CLIENT_SEND_RECEIVE_SERVICE_MSG_ERROR_DURING_SEND_SERVICE_MSG; > __EVAL_ERROR__ => I18N_OPENXPKI_CLIENT_INIT_CONNECTION_FAILED; > __ERROR__ => Connection refused, __SOCKETFILE__ => > /var/openxpki/openxpki.socket > 2021/05/03 10:52:14 I18N_OPENXPKI_CLIENT_INIT_CONNECTION_FAILED; > __ERROR__ => Connection refused, __SOCKETFILE__ => > /var/openxpki/openxpki.socket > 2021/05/03 10:52:14 > > I18N_OPENXPKI_CLIENT_SEND_RECEIVE_SERVICE_MSG_ERROR_DURING_SEND_SERVICE_MSG; > __EVAL_ERROR__ => I18N_OPENXPKI_CLIENT_INIT_CONNECTION_FAILED; > __ERROR__ => Connection refused, __SOCKETFILE__ => > /var/openxpki/openxpki.socket > OpenXPKI server is not running or does not accept requests. > Status check failed. > > > > How should i fix it? > > Thankyou. > > > > Regards, > > Sandy Kristiawan. > > > > > _______________________________________________ > > OpenXPKI-users mailing list > > [email protected] > <mailto:[email protected]> > > https://lists.sourceforge.net/lists/listinfo/openxpki-users > <https://lists.sourceforge.net/lists/listinfo/openxpki-users> > > > > -- > Protect your environment - close windows and adopt a penguin! > > > _______________________________________________ > OpenXPKI-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openxpki-users -- Protect your environment - close windows and adopt a penguin!
_______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
