08-10-2019
Trying a time machine restore for the second time (after checking the external hard disk, my backup disk, again) ....
Let's see what happens.
LOL, next time I'll clean the dirty screen before taking a photo ... hahaha (embarrassing) ... was in my luggage just back from a road trip.
Note: I thought this (before) was a Catalina Beta issue; but now upgrading Mojave give the same darn "installation" crash!
10 More Discussions You Might Find Interesting
1. Solaris
How can I make analysis for catalina.out (2 Replies)
Discussion started by: Burhan
2 Replies
2. Solaris
Hey!
I compiled TUN 1.1 driver on my Solaris 10 64bit, and everything was working fine, all the commands for installation were successfull (add_drv, devfsadm -i tun ... etc.)
and the driver was working fine as I got OpenVPN server up and running with successful clients attached. My only problem... (2 Replies)
Discussion started by: TomSu
2 Replies
3. Solaris
Hi,
Recently i received a request to rotate logs of catalina.out (tomcat). The file size was about 807 MB. I used logadm to truncate the log ( -c ) and zip (-z 0) it.
Everything worked fine, catalina.out.0.gz was created (22 MB) and the size of original catalina.out became 0kb.
After... (2 Replies)
Discussion started by: Mack1982
2 Replies
4. Shell Programming and Scripting
Hi,
I need to monitor the tomcat log file called "Catalina.out" for any errors like out of memory,JDBC exceptions,broken pipe any other errors and exceptions
The script should monitor this file and send a mail instantly and create a text file with errors day to day.
Iam using Solaris... (3 Replies)
Discussion started by: chaithanyaa
3 Replies
5. OS X (Apple)
Interestingly Apple has decided to switch the default shell for new users from bash to zsh in MacOS Catalina (10.15)
Use zsh as the default shell on your Mac - Apple Support
Another interesting fact is that Catalina also comes with /bin/dash (5 Replies)
Discussion started by: Scrutinizer
5 Replies
6. Programming
On the NI-VISA boards there has been some frustration where folks cannot get NI-VISA to work on macOS Catalina because Catalina (macOS 10.15.x) is "not supported" by NI-VISA (for many months, it seems). Currently, the README shows:
NI-VISA 19.0 for macOS supports the following platforms:
... (10 Replies)
Discussion started by: Neo
10 Replies
7. Windows & DOS: Issues & Discussions
Just a quick note for macOS users.
I just installed (and removed) Parallels Desktop 15 Edition on my MacPro (2013) with 64GB memory and 12-cores, which is running the latest version of macOS Catalina as of this post. The reason for this install was to test some RIGOL test gear software which... (6 Replies)
Discussion started by: Neo
6 Replies
8. OS X (Apple)
WARNING!
Just upgraded my MacPro (2013) from Catalina 10.15.2 to 10.15.3.
After the routine download and restart for upgrade installation, the Mac would not boot. Totally crashed.
Now, I'm in the process of a 15 hour restore from my last time machine backup.
I'm not very happy with... (3 Replies)
Discussion started by: Neo
3 Replies
9. Programming
Currently have two ESP8266 modules testing some Blynk apps, whereI'm not so happy with the Blynk business model for developers, but that's another story.
So, with two of my ESP8266s currently "busy", I decided to work on the ESP32, and in particular the ESPWROOM32.
I installed the... (0 Replies)
Discussion started by: Neo
0 Replies
10. OS X (Apple)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT OSX
reportcrash
ReportCrash(8) BSD System Manager's Manual ReportCrash(8)
NAME
ReportCrash -- Generates crash reports
SYNOPSIS
ReportCrash
DESCRIPTION
ReportCrash analyzes crashing processes and saves a crash report to disk. A crash report contains information that can help a developer
diagnose the cause of a crash. ReportCrash also records the identity of the crashing process and the location of the saved crash report in
the system.log and the ASL log database.
ReportCrash is invoked automatically by launchd when a crash is detected. For applications and other processes running in the per-user
launchd context, ReportCrash runs as a LaunchAgent and saves crash reports in the user's ~/Library/Logs/DiagnosticReports/ directory. For
daemons, other processes running in the system launchd context and other privileged processes, ReportCrash runs as a LaunchDaemon and saves
crash reports in the system's /Library/Logs/DiagnosticReports directory where they are only readable by admin users. If there are too many
crash reports saved for a particular process, older reports will automatically be removed in order to conserve disk space.
launchtl can be used to disable and re-enable crash reporting. To disable crash reporting:
launchctl unload -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
To re-enable crash reporting:
launchctl load -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
For application crashes (but not background process crashes) ReportCrash will display a dialog notifying the user that the application unex-
pectedly quit and offering to reopen the application or send the report to Apple. For developers, the behavior of this dialog can be
adjusted using /Developer/Applications/Utilities/CrashReporterPrefs.app which is installed as part of the developer tools.
Crash reports which are sent to Apple are submitted anonymously by the SubmitDiagInfo process. The reports are used by Apple to improve its
products. Users who need support should use http://www.apple.com/support or other authorized support channels. Developers who are ADC mem-
bers should report bugs using http://bugreporter.apple.com in order to allow for two way communication between Apple and the bug reporter.
More information about interpreting the contents of crash reports can be found in Technote 2123: http://developer.apple.com/tech-
notes/tn2004/tn2123.html
SEE ALSO
launchd(8), launchd.plist(8), launchctl(8), spindump(8), SubmitDiagInfo(8)
Mac OS June 1, 2019 Mac OS