Timeline for Failed to get D-Bus connection: Connection refused
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2022 at 10:29 | comment | added | Ben | Nothing worked for me, until I login as target user via ssh. anything (login included) started with "su"/"sudo" -u etc will not work at all. then I just loginctl enable-linger $newuser. luckily It works after reboot, It seems just one-time login is enough. | |
| Oct 29, 2020 at 20:36 | comment | added | CodeMed | Just added additional updates to the OP. Do you have more suggestions? | |
| Oct 28, 2020 at 22:26 | comment | added | CodeMed | We just added the results of your suggestion to the OP. We are happy to use a user with remote login abilities per your suggestion, but this still leaves the problem shown above. What else should we try? | |
| Oct 24, 2020 at 0:48 | comment | added | CodeMed | $XDG_RUNTIME_DIR is not defined for my-host in the EC2 instance in question. Since Ansible is being used to create my-host, it may take a little time to get remote login set up for my-host. Our model was for Ansible to login as user and then change to become my-host. I will be able to work on this Monday and get back to you with more results. Thank you. | |
| Oct 23, 2020 at 7:48 | history | edited | Stewart | CC BY-SA 4.0 | added 275 characters in body |
| Oct 23, 2020 at 7:23 | history | edited | Stewart | CC BY-SA 4.0 | added 84 characters in body |
| Oct 23, 2020 at 7:16 | history | answered | Stewart | CC BY-SA 4.0 |