Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Thanks for the answer, @MMB The only results for the code above, at the time, pointed to the built-in file for the ColorSync daemon, which confused me. A new log file appeared today and the results for the ps command this time returned: 208 ?? 0:00.06 /usr/libexec/usbd. Again, a built-in macOS file, not an application. How could macOS' own usb daemon cause a Java error?
    – PBear.SF
    Commented Feb 11, 2019 at 17:57
  • Puzzling. According the man pages, usbd arrived in 10.9 as a way for iOS devices to charge and send notifications.
    – MMB
    Commented Feb 12, 2019 at 21:18
  • Let's tackle this a different way. Given Apple's disdain for Java, let us assume the file isn't coming from Apple software. You also said the files are created around 2AM, which suggests something launched. Try the following command, which the results of which you might want to append to your original question: sudo launchctl list | cut -f3 | grep -v com.apple | sort
    – MMB
    Commented Feb 12, 2019 at 22:08
  • The above command will generate a list of services launched by third-party software that you have installed. Note that since the sudo command is issued, you'll need to enter your password.
    – MMB
    Commented Feb 12, 2019 at 22:32
  • Four Java crash logs later @MMB and one finally appeared today with a useful PID - revealing that there is indeed a JRE installed on my Mac, contained in the Serviio Media Server. I plan to uninstall Serviio, which should stop the Java error logs from appearing, but I am beginning to fear that these Java logs are just a symptom of my main problem and not the cause of what is making my computer crash at 2:10 AM every one to three days, during sleep mode. I have looked at many diverse crash logs now, in the Console, and every one that has a time stamp of 2:10 AM is in unreadable text or code.
    – PBear.SF
    Commented Feb 17, 2019 at 18:16