Timeline for answer to Redis not starting with systemctl by Viraj Wadate
Current License: CC BY-SA 4.0
Post Revisions
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2019 at 14:07 | comment | added | Kalyan Raghu |
journalctl -u redis gave info about the error in my case *** FATAL CONFIG FILE ERROR *** Reading the configuration file, at line 147 >>> 'supervised systemd #signal systemd' Bad directive or wrong number of arguments which was to remove the commented out part after systemd
|
|
| Mar 25, 2019 at 13:29 | comment | added | Viraj Wadate | Yes journalctl -u service-name also gives output. | |
| S Mar 25, 2019 at 13:22 | history | suggested | AndreasM | CC BY-SA 4.0 |
clarity of the answer improved.
|
| Mar 25, 2019 at 13:10 | comment | added | AndreasM | The journal output already gives hints on what the problem may be: " NOTIFY_SOCKET not found" Do you have further info on this Redis problem? | |
| Mar 25, 2019 at 13:08 | review | Suggested edits | |||
| S Mar 25, 2019 at 13:22 | |||||
| Mar 25, 2019 at 12:05 | review | First posts | |||
| Mar 25, 2019 at 13:10 | |||||
| Mar 25, 2019 at 12:01 | history | answered | Viraj Wadate | CC BY-SA 4.0 |