Score:0

Ssh messages do not output to a pipe configured in syslog.conf

tv flag

I have configured a pipe in syslog.conf for auth.* to capture the ssh syslog error and status messages. I have then a python script that processes this pipe's input and I check that we receive something by writing the content of the pipe to a file.

When running a "ssh [email protected]" command (IP does not exist on network) I expect to see the ssh error in the file but it's empty. This used to work but it's not working anymore. What might of happened?

HBruijn avatar
in flag
I would expect that typically only the ssh *daemon* messages get forwarded to syslog, not (error) messages from the ssh *client*.
A Mere avatar
tv flag
Is there a way to generate such a daemon message for testing purposes?
HBruijn avatar
in flag
The [`logger`](https://man7.org/linux/man-pages/man1/logger.1.html) command line utility can be used to send messages to a syslog daemon
Score:0
cu flag

Check that the syslog.conf is up to date, and if so, replace the python script with the 'tee' utility to see if there is a problem in the syslog

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.