RHEL guest running on VMware rebooted unexpectedly. Looks like someone sent signal 15.

Solution Unverified - Updated -

Issue

  • RHEL guest running on VMware rebooted unexpectedly. Looking at /var/log/messsages file, it looks like someone sent kill -TERM signal.

    Jun 11 10:44:54 server1 init: tty (/dev/tty1) main process (2349) killed by TERM signal
Jun 11 10:44:54 server1 init: tty (/dev/tty2) main process (2351) killed by TERM signal
Jun 11 10:44:54 server1 init: tty (/dev/tty3) main process (2353) killed by TERM signal
Jun 11 10:44:54 server1 init: tty (/dev/tty4) main process (2355) killed by TERM signal
Jun 11 10:44:54 server1 init: tty (/dev/tty5) main process (2357) killed by TERM signal
Jun 11 10:44:54 server1 init: tty (/dev/tty6) main process (2359) killed by TERM signal
Jun 11 10:44:54 server1 kernel: Removing vmci device
Jun 11 10:44:54 server1 kernel: Resetting vmci device
Jun 11 10:44:54 server1 kernel: Unregistered vmci device.
Jun 11 10:44:54 server1 kernel: vmci 0000:00:07.7: PCI INT A disabled

Environment

  • Red Hat Enterprise Linux
  • RHEL guest virtual machine running on VMware ESXi server
  • VMware Tools installed

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.