Skip to content

Instantly share code, notes, and snippets.

@lfender6445

lfender6445/gist:b7949bbd127bf88e2d0c

Last active August 29, 2015 14:02
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lfender6445/b7949bbd127bf88e2d0c to your computer and use it in GitHub Desktop.
Save lfender6445/b7949bbd127bf88e2d0c to your computer and use it in GitHub Desktop.
Download ZIP
syslogd out of control - memory leak, osx fix
Raw
gistfile1.md

Syslogd memory leak, osx fix

syslogd out of control?

syslogd is a daemon/background process that logs and generates messages from the system. if this is eating up your CPU, you can find the offending process and kill it.

  1. Open up terminal and run tail -f /var/log/system.log. You may see some output like this, but it will be very different for you machine:

    Jun 12 11:17:08 lfender-mbp kernel[0]: *** kernel exceeded 500 log message per second limit  -  remaining messages this     second discarded ***
Jun 12 11:17:09 lfender-mbp kernel[0]: Data/Stack execution not permitted: ruby[pid 72771] at virtual address 0x7fbd9c078000, protections were read-write

  2. Kill the offending process id (pid), in this case see above output as an example - ruby[pid 72771]

  3. kill -15 72771

  4. If that doesn't work, try kill -9 72771

See http://scofaq.aplawrence.com/FAQ_scotec6killminus9.html for more on killing processes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment