I run the website and several services of my small company on a VPS (running CentOS 6.8) on which I have full administrative rights.
Due to trying to pinpoint a memory leak issue in PHP scripts, I've been monitoring the VPS for some time and I have once again looked at the logs. What I see is a long string of log messages, such as these:
I would like to solve whatever configuration problems cause these errors to "pollute" the system logs, because they make the logs unusable. Every 5 seconds, I get a batch of these:
Feb 17 12:43:03 vpsxxxxx init: tty (/dev/tty2) main process (1381) terminated with status 1 Feb 17 12:43:03 vpsxxxxx init: tty (/dev/tty2) main process ended, respawning Feb 17 12:43:03 vpsxxxxx init: tty (/dev/tty1) main process (1382) terminated with status 1 Feb 17 12:43:03 vpsxxxxx init: tty (/dev/tty1) main process ended, respawning Feb 17 12:43:03 vpsxxxxx /sbin/mingetty: tty2: no controlling tty: Operation not permitted Feb 17 12:43:03 vpsxxxxx /sbin/mingetty: tty1: no controlling tty: Operation not permitted
By the time the logs are rotated (on a weekly basis), I'm looking at over 60 MB in the log file, which brings nano to its knees.
I have no idea how necessary mingetty is to normal operation on the VPS (or to connecting via SSH). I'm the only one administering the server but I rarely use more than 2 simultaneous SSH connections.
Is there a solution to this amount of log messages related to mingetty?