The main problem comes from the dataprotector (omniback) connection where xinetd writes German timestamps in the log file.
I have written a small xinetd test service which just runs the locale command on a specific port to check the output.
We have >200 linux systems which are backed up with dataprotector and only 2 systems that show the problem. One of them got rebooted and the problem was gone.
Thus it is not the client connection but a setting somewhere on the system.
I had done an apt-get remove xinetd and an apt-get install xinetd without success.
If I start a single xinetd the locale is OK but if I start xinetd from the service it still shows the wrong locale.
Please see the attached log.
The main problem comes from the dataprotector (omniback) connection where xinetd writes German timestamps in the log file.
I have written a small xinetd test service which just runs the locale command on a specific port to check the output.
We have >200 linux systems which are backed up with dataprotector and only 2 systems that show the problem. One of them got rebooted and the problem was gone.
Thus it is not the client connection but a setting somewhere on the system.
I had done an apt-get remove xinetd and an apt-get install xinetd without success.
If I start a single xinetd the locale is OK but if I start xinetd from the service it still shows the wrong locale.
Please see the attached log.