Timeline for How to recover MongoDB prompt from '>' to secondary node prompt?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2022 at 7:43 | answer | added | Wernfried Domscheit | timeline score: 0 | |
| Jul 17, 2022 at 0:45 | comment | added | user3637971 | I don't think it's wrong to connect to mongoDB node. I think it's considered like other way. On the other side, I made testing according to your advice, but when I start the primary node again the prompt changes to '>' on secondary node. Therefore, it happens the same. The easy way is exiting the shell and logging again on secondary node. I don't see in MongoDB shell a command where the prompt '>' was refreshed. | |
| Jul 15, 2022 at 14:54 | comment | added | Wernfried Domscheit | That's wrong, see linked documentation | |
| Jul 15, 2022 at 14:49 | comment | added | user3637971 | I connect by mongo -u "admin" -p --authenticationDatabase "admin" | |
| Jul 13, 2022 at 7:45 | comment | added | Wernfried Domscheit | How did you connect? If you connect properly to a Replica set (see Replica Set with Members on Different Machines) then a simple "ENTER" should restore your prompt. | |
| Jul 12, 2022 at 4:24 | answer | added | JJussi | timeline score: 0 | |
| Jul 11, 2022 at 15:45 | history | asked | user3637971 | CC BY-SA 4.0 |