Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About FredReitberger

  • Rank
  1. FredReitberger

    FMU Unexpectedly Quitting

    Passing this on: On OS X, this error can also happen if you are running our of vnodes (an internal system resource). You can check for this with the commands: sysctl kern.maxvnodes pstat -T The first command, sysctl, will display the maximum number of vnodes that the system can currently have. The second, pstat, will display a couple of bits of information. The one you want is the number of vnodes currently in use. If the number of vnodes currently in use is anywhere near the maximum you are probably having a problem with vnodes. A vnode is a block of memory in the kernel used to keep track of files on disk, and other several things, while they are in "active" use. When a program opens a file, the system requires a vnode for the file and one for the directory the file is in. Other things the kernel does also require vnodes. For example doing a DNS lookup takes a vnode. Whenever the operation is completed, the vnode is freed for reuse. When a program tries to open a file, and there are no vnodes available, the open will fail, even if everything else about the operation is fine. This will cause programs to fail when trying to open a log file, or writing a backup, or any of several other things. A few things other than opening files also require vnodes, such as DNS lookups. As virtual memory usage increases the system will use vnodes to keep track of the virtual memory. Many other steps can also require vnodes Certain system programs perform operations that must succeed in order for the system to continue functioning. When one of their internal operations fails, because there are no vnodes available, very bad things might happen. Although everything is supposed to check for that kind of thing, and try again, not everyone is that careful. Also there are a very few kernel operations that must have a vnode right now, and can not wait for one to be freed. If one of those happens and there isn't a vnode available, you will get a kernel panic. The solution is to tell the system to allocate space for more vnodes. The command: sudo sysctl -w kern.maxvnodes=20000 will raise the limit to 20000 till the next reboot. This must be run by an admin user and will prompt for a password. You should watch the output of: pstat -T to make sure that that is really enough. You want there to be a few thousand free when running all of the apps you are every planning to run. If not, raise the 20000 to something higher. Hope this helps

Important Information

By using this site, you agree to our Terms of Use.