Syslog filled with "init: console main process terminated with status 1" errors

Portal Home > Knowledgebase > Articles Database > Syslog filled with "init: console main process terminated with status 1" errors

Posted by jzukerman, 04-19-2014, 08:07 PM
A few days ago, my VPS became unresponsive and I opened a ticket with my provider. They rebooted the server (not sure if they mean the entire node or just my VPS) after they initially insisted there was no issue. Since the server came back up, I'm getting these errors repeating every few seconds in my /var/log/messages: I can see the processes running when I use ps aux: So I opened another ticket with my VPS provider and they claim the server is working fine. Yes it is working, but the syslogs are being filled with these errors. So there must be a way to stop the errors from happening. Any ideas?
Posted by Srv24x7, 04-23-2014, 01:35 AM
Hi, Open the file /etc/init/tty.conf and Comment out all the lines in it, and then reboot the VPS once. Check if the messages again to see if they still generates.
Posted by jzukerman, 04-23-2014, 09:13 AM
Seems to me that the file isn't used. My VPS provider finally got back to me a few days after my last response saying: Still not fixed.
Posted by Johnny Cache, 04-23-2014, 10:31 AM
Can you humor me an do a 'uname -a' please? If your VPS is OpenVZ I'm looking into a similar situation on my dev box/dev VPS', and I'm curious if they're using one of a couple different kernels I noticed this on just a few days back.
Posted by jzukerman, 04-23-2014, 05:04 PM
VPS is OpenVZ.
Posted by Johnny Cache, 04-23-2014, 05:31 PM
I'm a little shocked that your VPS provider hasn't upgraded to RHEL6 (vswap among other enhancements). I'd recommend asking your provider to migrate and convert your container over to an RHEL6 (CentOS6) node. You're not getting the most out of OpenVZ until then. Back to the issue at hand - I'm seeing this but under a completely different kernel, 2.6.32-042stab088.4. I'll have to go through their BugZilla and see if there's been anything reported, since it seems to have occurred after the most recent OpenVZ 2.6.18 and 2.6.32 branches.
Posted by UnfinishedSentenc, 04-23-2014, 05:35 PM
Agreed, CE6 based .32 kernel is a big improvement and solid as a rock. If they are still running .18 it must be pretty old hardware. Last edited by UnfinishedSentenc; 04-23-2014 at 05:48 PM.
Posted by jzukerman, 04-23-2014, 05:38 PM
I'm getting pretty tired of this host. I have another VPS with them that is down right now (heavy packet loss) or some type of network connectivity issue. Plus to get them to look into this syslog issue, it took 5 replies to the original ticket. The level1 or whatever level techs they use are useless. Canned responses just to get you to go away and close the ticket without checking anything.
Posted by Johnny Cache, 04-23-2014, 05:49 PM
Sounds like it may be time to look for another home. Most of the info the provider needs can be obtained with some tried-and-true troubleshooting. If it's related to the kernel, it's not something that can be "fixed soon" as it would be corrected in a future kernel (if applicable). Otherwise, you may have to hang in there until they can come up with a "fix, soon". Good luck.
Posted by jzukerman, 06-01-2014, 12:02 PM
This issue resolved itself. My VPS went down without warning a couple days ago (I assume the entire node/server itself crashed). I submitted a support ticket about my VPS being down and got the same canned responses. A little over 2 hours later it came back online, but without the massive console spam messages as mentioned in the original post. Still looking for a new provider. :-/ Last edited by jzukerman; 06-01-2014 at 12:10 PM.

Add to Favourites Print this Article