Issue s-nail: -s: normalizing away invalid ASCII NL / CR bytes

[jola]

Server operating system version

Centos 7.9 ELS

Plesk version and microupdate number

18.0.66

When I login via ssh to my Plesk server I now get the following error message displayed:

s-nail: -s: normalizing away invalid ASCII NL / CR bytes

I recently upgraded to Obsidian 18.0.66 and this is on an Centos 7 ELS server.

Anyone have any clue what might be causing this error message? The server seems to work well, and if I just ignore the error message everything seems to work as normal when I am logged in via ssh.

Thanks for any hints!

 

[Vladimir C.]

Hello! I was not able to reproduce such behavior in the test environment. Could you please let me know where do you see this message? In the SSH terminal right after you connected to the server?

I've checked out internal database and did not find any cases related to such issue. According to internet research this normalization is not necessarily an error but a warning indicating s-nail corrected an issue. If the email behaves as expected, you may not need to take further action.

However, it would be good to know more details about the issue. I would recommend contact Plesk technical support team to investigate it further.

 

[jola]

Hello! I was not able to reproduce such behavior in the test environment. Could you please let me know where do you see this message? In the SSH terminal right after you connected to the server?

I've checked out internal database and did not find any cases related to such issue. According to internet research this normalization is not necessarily an error but a warning indicating s-nail corrected an issue. If the email behaves as expected, you may not need to take further action.

However, it would be good to know more details about the issue. I would recommend contact Plesk technical support team to investigate it further.

 

[jola]

Thanks for your quick reply. I have found the problem. It was an error message shown directly in the ssh terminal after I logged in.

For many years I have had this small section in my root .bashrc file which sends a small email to the server admin with a warning that someone logged in as root, giving the IP and domain name of the login source. I'm not 100% sure why this all of a sudden started to give these error messages, it has been working well for many years, but after playing a bit with the small details in the bash script that sends these warning emails it now works without any error.

 

[scsa20]

For many years I have had this small section in my root .bashrc file which sends a small email to the server admin with a warning that someone logged in as root, giving the IP and domain name of the login source. I'm not 100% sure why this all of a sudden started to give these error messages, it has been working well for many years, but after playing a bit with the small details in the bash script that sends these warning emails it now works without any error.

It's more likely because of the updated packages over time changed how the command is done within the bash script. Just a theory though. Good to hear it's fixed though!