Core dump on boot during Yosemite installation

I have downloaded Yosemite from the App Store. All appears fine. When I run the installer, may MBP restarts for the installation but on rebooting it goes repeatedly into core dumps at the boot step. This can be interrupted using Cmd-R. When in Recovery Mode, resetting the Startup Disk will cure the failing reboots but then the installation has simply stopped and the computer boots into 10.9.5.
I have repeated this multiple times. I have 25 GB free disk space.
I expect that a clean install with cure this but I hate to have to do that.
Tim

I have the same problem.
After upgrading my MBpro from Lion to Yosemite installation finishes correctly and I can work in Yosemite.
But the next boot will result in repeated core dumps.
Restored Lion, deleted startup objects and 3rd Party drivers, tried again but the same problem.
Has the clean install helped ?

Similar Messages

  • Zfs core dumps in Solaris Zones after patchcluster installation

    Hi
    I've installed the recommended patch cluster for Solaris 10 (SPARC) on my T2000 Server.
    Now after the reboot all the Solaris Zones (got about 10 of them) instantly do zfs core dumps when their booted.
    Some Output:
    Dec 15 15:34:43 XXXXX genunix: NOTICE: core_log: zfs[1711] core dumped: /var/core/core_XXXXXX_zfs_0_0_1292423682_1711
    bash-3.00# svcs
    STATE STIME FMRI
    online 13:58:50 svc:/system/svc/restarter:default
    online 13:58:51 svc:/system/filesystem/root:default
    online 13:58:51 svc:/network/loopback:default
    online 13:58:53 svc:/network/pfil:default
    online 13:58:54 svc:/system/installupdates:default
    online 13:58:55 svc:/system/boot-archive:default
    online 13:58:56 svc:/network/physical:default
    online 13:58:57 svc:/system/filesystem/usr:default
    online 13:58:57 svc:/system/identity:node
    online 13:58:58 svc:/system/device/local:default
    online 13:58:58 svc:/system/keymap:default
    online 13:58:58 svc:/milestone/devices:default
    online 13:58:58 svc:/system/filesystem/minimal:default
    online 13:58:58 svc:/system/rmtmpfiles:default
    online 13:58:58 svc:/system/cryptosvc:default
    online 13:58:59 svc:/system/identity:domain
    online 13:58:59 svc:/system/name-service-cache:default
    online 13:58:59 svc:/system/coreadm:default
    online 13:58:59 svc:/network/ipsec/ipsecalgs:default
    online 13:58:59 svc:/application/print/ppd-cache-update:default
    online 13:58:59 svc:/network/ipsec/policy:default
    online 13:59:00 svc:/milestone/network:default
    online 13:59:00 svc:/network/initial:default
    online 13:59:00 svc:/system/manifest-import:default
    online 13:59:00 svc:/network/service:default
    online 13:59:00 svc:/milestone/single-user:default
    online 13:59:00 svc:/network/dns/client:default
    online 13:59:00 svc:/network/routing-setup:default
    online 13:59:00 svc:/milestone/name-services:default
    online 13:59:03 svc:/milestone/sysconfig:default
    online 13:59:03 svc:/system/utmp:default
    online 13:59:03 svc:/system/console-login:default
    offline 13:58:51 svc:/system/sysidtool:net
    offline 13:58:51 svc:/network/rpc/bind:default
    offline 13:58:51 svc:/system/sysidtool:system
    offline 13:58:52 svc:/network/nfs/status:default
    offline 13:58:52 svc:/network/nfs/nlockmgr:default
    offline 13:58:52 svc:/network/nfs/cbd:default
    offline 13:58:52 svc:/network/nfs/mapid:default
    offline 13:58:52 svc:/network/inetd:default
    offline 13:58:52 svc:/network/nfs/client:default
    offline 13:58:52 svc:/system/filesystem/autofs:default
    offline 13:58:53 svc:/system/system-log:default
    offline 13:58:53 svc:/network/smtp:sendmail
    offline 13:58:53 svc:/system/cron:default
    offline 13:58:53 svc:/milestone/multi-user:default
    offline 13:58:54 svc:/application/management/snmpdx:default
    offline 13:58:54 svc:/application/management/dmi:default
    offline 13:58:54 svc:/application/management/seaport:default
    offline 13:58:54 svc:/network/ssh:default
    offline 13:58:54 svc:/milestone/multi-user-server:default
    offline 13:58:54 svc:/application/font/fc-cache:default
    offline 13:58:55 svc:/application/management/sma:default
    offline 13:58:58 svc:/system/sac:default
    offline 13:59:00 svc:/network/shares/group:default
    offline 13:59:00 svc:/system/boot-archive-update:default
    maintenance 15:34:43 svc:/system/filesystem/local:default
    uninitialized 13:58:52 svc:/network/rpc/gss:default
    uninitialized 13:58:54 svc:/application/font/stfsloader:default
    uninitialized 13:58:55 svc:/network/rpc/rstat:default
    uninitialized 13:58:55 svc:/application/print/rfc1179:default
    uninitialized 13:58:55 svc:/application/x11/xfs:default
    uninitialized 13:58:55 svc:/network/finger:default
    uninitialized 13:58:55 svc:/network/ftp:default
    uninitialized 13:58:56 svc:/network/login:rlogin
    uninitialized 13:58:56 svc:/network/nfs/rquota:default
    uninitialized 13:58:56 svc:/network/rpc/rusers:default
    uninitialized 13:58:56 svc:/network/rpc/smserver:default
    uninitialized 13:58:57 svc:/network/security/ktkt_warn:default
    uninitialized 13:58:57 svc:/network/shell:default
    uninitialized 13:58:57 svc:/network/telnet:default
    uninitialized 13:58:58 svc:/network/rpc-100235_1/rpc_ticotsord:default
    uninitialized 13:58:58 svc:/network/rpc/cde-calendar-manager:default
    uninitialized 13:58:59 svc:/network/rpc/cde-ttdbserver:tcp
    bash-3.00# svcs -x
    svc:/system/filesystem/local:default (local file system mounts)
    State: maintenance since Wed Dec 15 15:34:43 2010
    Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
    See: http://sun.com/msg/SMF-8000-KS
    See: /var/svc/log/system-filesystem-local:default.log
    Impact: 24 dependent services are not running. (Use -v for list.)
    svc:/network/rpc/gss:default (Generic Security Service)
    State: uninitialized since Wed Dec 15 13:58:52 2010
    Reason: Restarter svc:/network/inetd:default is not running.
    See: http://sun.com/msg/SMF-8000-5H
    See: gssd(1M)
    Impact: 11 dependent services are not running. (Use -v for list.)
    svc:/network/rpc/rstat:default (kernel statistics server)
    State: uninitialized since Wed Dec 15 13:58:55 2010
    Reason: Restarter svc:/network/inetd:default is not running.
    See: http://sun.com/msg/SMF-8000-5H
    See: rpc.rstatd(1M)
    See: rstatd(1M)
    Impact: 1 dependent service is not running. (Use -v for list.)
    bash-3.00# cat /var/svc/log/system-filesystem-local:default.log
    [ Jul 10 03:41:35 Enabled. ]
    [ Jul 10 03:43:45 Rereading configuration. ]
    [ Jul 10 03:44:17 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 03:44:18 Method "start" exited with status 0 ]
    [ Jul 10 12:44:36 Enabled. ]
    [ Jul 10 12:44:45 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 12:44:45 Method "start" exited with status 0 ]
    [ Jul 10 12:45:03 Enabled. ]
    [ Jul 10 12:45:09 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 12:45:09 Method "start" exited with status 0 ]
    [ Jul 10 13:54:39 Enabled. ]
    [ Jul 10 13:54:46 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 10 13:54:46 Method "start" exited with status 0 ]
    [ Jul 18 12:34:19 Enabled. ]
    [ Jul 18 12:34:27 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 18 12:34:27 Method "start" exited with status 0 ]
    [ Jul 18 17:29:08 Enabled. ]
    [ Jul 18 17:29:15 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 18 17:29:15 Method "start" exited with status 0 ]
    [ Jul 19 11:13:34 Enabled. ]
    [ Jul 19 11:13:42 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:13:42 Method "start" exited with status 0 ]
    [ Jul 19 11:32:23 Enabled. ]
    [ Jul 19 11:32:30 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:32:31 Method "start" exited with status 0 ]
    [ Jul 19 11:57:06 Enabled. ]
    [ Jul 19 11:57:13 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 11:57:13 Method "start" exited with status 0 ]
    [ Jul 19 12:40:05 Enabled. ]
    [ Jul 19 12:40:12 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 19 12:40:12 Method "start" exited with status 0 ]
    [ Jul 20 15:51:46 Enabled. ]
    [ Jul 20 15:51:54 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 20 15:51:54 Method "start" exited with status 0 ]
    [ Jul 24 11:42:17 Enabled. ]
    [ Jul 24 11:42:25 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 24 11:42:25 Method "start" exited with status 0 ]
    [ Jul 27 12:05:06 Stopping because service disabled. ]
    [ Jul 27 12:05:07 Executing stop method (null) ]
    [ Jul 27 12:13:10 Enabled. ]
    [ Jul 27 12:13:17 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 27 12:13:17 Method "start" exited with status 0 ]
    [ Jul 27 13:10:26 Stopping because service disabled. ]
    [ Jul 27 13:10:26 Executing stop method (null) ]
    [ Jul 27 13:18:19 Enabled. ]
    [ Jul 27 13:18:26 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 27 13:18:26 Method "start" exited with status 0 ]
    [ Jul 31 10:12:31 Enabled. ]
    [ Jul 31 10:12:38 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jul 31 10:12:39 Method "start" exited with status 0 ]
    [ Aug  7 10:08:52 Stopping because service disabled. ]
    [ Aug  7 10:08:52 Executing stop method (null) ]
    [ Aug  7 10:34:50 Enabled. ]
    [ Aug  7 10:34:57 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  7 10:34:58 Method "start" exited with status 0 ]
    [ Aug  9 09:14:50 Stopping because service disabled. ]
    [ Aug  9 09:14:50 Executing stop method (null) ]
    [ Aug  9 09:55:03 Enabled. ]
    [ Aug  9 09:55:10 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  9 09:55:11 Method "start" exited with status 0 ]
    [ Aug 16 10:46:43 Enabled. ]
    [ Aug 16 10:46:50 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 10:46:50 Method "start" exited with status 0 ]
    [ Aug 16 12:06:56 Enabled. ]
    [ Aug 16 12:07:02 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 12:07:02 Method "start" exited with status 0 ]
    [ Aug 16 13:45:10 Enabled. ]
    [ Aug 16 13:45:16 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 13:45:16 Method "start" exited with status 0 ]
    [ Aug 16 14:36:59 Enabled. ]
    [ Aug 16 14:37:07 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 14:37:07 Method "start" exited with status 0 ]
    [ Aug 16 15:00:40 Enabled. ]
    [ Aug 16 15:00:47 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 16 15:00:47 Method "start" exited with status 0 ]
    [ Aug 22 16:00:13 Enabled. ]
    [ Aug 22 16:00:21 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 22 16:00:21 Method "start" exited with status 0 ]
    [ Aug 23 09:49:04 Enabled. ]
    [ Aug 23 09:49:10 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 09:49:11 Method "start" exited with status 0 ]
    [ Aug 23 09:49:23 Stopping because service disabled. ]
    [ Aug 23 09:49:23 Executing stop method (null) ]
    [ Aug 23 10:04:13 Enabled. ]
    [ Aug 23 10:04:20 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 10:04:20 Method "start" exited with status 0 ]
    [ Aug 23 10:06:57 Enabled. ]
    [ Aug 23 10:07:04 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 23 10:07:05 Method "start" exited with status 0 ]
    [ Oct 23 08:43:05 Enabled. ]
    [ Oct 23 08:43:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Oct 23 08:43:14 Method "start" exited with status 0 ]
    [ Nov 21 14:51:50 Enabled. ]
    [ Nov 21 14:51:58 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Nov 21 14:51:59 Method "start" exited with status 0 ]
    [ Nov 29 15:33:19 Enabled. ]
    [ Nov 29 15:33:26 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Nov 29 15:33:27 Method "start" exited with status 0 ]
    [ Dec 18 13:37:35 Enabled. ]
    [ Dec 18 13:37:42 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 18 13:37:42 Method "start" exited with status 0 ]
    [ Dec 19 08:48:07 Enabled. ]
    [ Dec 19 08:48:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:48:14 Method "start" exited with status 0 ]
    [ Dec 19 08:56:07 Enabled. ]
    [ Dec 19 08:56:14 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:56:14 Method "start" exited with status 0 ]
    [ Dec 19 08:57:41 Enabled. ]
    [ Dec 19 08:57:48 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Dec 19 08:57:48 Method "start" exited with status 0 ]
    [ Feb  1 10:39:48 Enabled. ]
    [ Feb  1 10:39:55 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb  1 10:39:56 Method "start" exited with status 0 ]
    [ Feb  8 11:12:50 Enabled. ]
    [ Feb  8 11:12:57 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb  8 11:12:57 Method "start" exited with status 0 ]
    [ Jun  6 10:08:34 Enabled. ]
    [ Jun  6 10:08:44 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Jun  6 10:08:46 Method "start" exited with status 0 ]
    [ Aug  8 09:45:48 Enabled. ]
    [ Aug  8 09:46:35 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug  8 09:46:36 Method "start" exited with status 0 ]
    [ Aug 14 17:53:59 Enabled. ]
    [ Aug 14 17:54:06 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 14 17:54:06 Method "start" exited with status 0 ]
    [ Aug 14 17:55:20 Enabled. ]
    [ Aug 14 17:55:27 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 14 17:55:27 Method "start" exited with status 0 ]
    [ Aug 18 15:19:17 Enabled. ]
    [ Aug 18 15:19:24 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 18 15:19:24 Method "start" exited with status 0 ]
    [ Aug 29 12:56:48 Enabled. ]
    [ Aug 29 12:56:55 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 29 12:56:55 Method "start" exited with status 0 ]
    [ Oct 13 11:59:43 Enabled. ]
    [ Oct 13 11:59:50 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Oct 13 11:59:51 Method "start" exited with status 0 ]
    [ Feb 26 16:47:00 Enabled. ]
    [ Feb 26 16:47:07 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Feb 26 16:47:07 Method "start" exited with status 0 ]
    [ Apr 14 15:54:17 Enabled. ]
    [ Apr 14 15:54:24 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Apr 14 15:54:25 Method "start" exited with status 0 ]
    [ Aug 28 08:49:58 Stopping because service disabled. ]
    [ Aug 28 08:49:58 Executing stop method (null) ]
    [ Aug 28 08:52:54 Enabled. ]
    [ Aug 28 08:53:01 Executing start method ("/lib/svc/method/fs-local") ]
    bootadm: this operation is not supported on sparc
    [ Aug 28 08:53:01 Method "start" exited with status 0 ]
    [ Aug 28 09:08:20 Stopping because service disabled. ]
    [ Aug 28 09:08:20 Executing stop method (null) ]
    [ Sep  1 16:05:36 Enabled. ]
    [ Sep  1 16:06:05 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 16:06:05 Method "start" exited with status 0 ]
    [ Sep  1 19:29:19 Enabled. ]
    [ Sep  1 19:29:27 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 19:29:27 Method "start" exited with status 0 ]
    [ Sep  1 23:04:00 Enabled. ]
    [ Sep  1 23:04:08 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  1 23:04:08 Method "start" exited with status 0 ]
    [ Sep  2 00:23:41 Stopping because service disabled. ]
    [ Sep  2 00:23:42 Executing stop method (null) ]
    [ Sep  2 00:46:46 Enabled. ]
    [ Sep  2 00:46:53 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep  2 00:46:54 Method "start" exited with status 0 ]
    [ Sep 26 12:04:34 Enabled. ]
    [ Sep 26 12:04:41 Executing start method ("/lib/svc/method/fs-local") ]
    [ Sep 26 12:04:42 Method "start" exited with status 0 ]
    [ Oct 20 13:05:09 Stopping because service disabled. ]
    [ Oct 20 13:05:10 Executing stop method (null) ]
    [ Oct 20 13:24:01 Enabled. ]
    [ Oct 20 13:24:08 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 20 13:24:09 Method "start" exited with status 0 ]
    [ Oct 21 16:30:59 Enabled. ]
    [ Oct 21 16:31:09 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 16:31:09 Method "start" exited with status 0 ]
    [ Oct 21 16:32:42 Stopping because service disabled. ]
    [ Oct 21 16:32:42 Executing stop method (null) ]
    [ Oct 21 16:42:05 Enabled. ]
    [ Oct 21 16:42:15 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 16:42:15 Method "start" exited with status 0 ]
    [ Oct 21 17:27:37 Enabled. ]
    [ Oct 21 17:27:47 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 21 17:27:47 Method "start" exited with status 0 ]
    [ Oct 22 11:08:34 Enabled. ]
    [ Oct 22 11:08:43 Executing start method ("/lib/svc/method/fs-local") ]
    [ Oct 22 11:08:43 Method "start" exited with status 0 ]
    [ Dec  9 09:17:33 Stopping because service disabled. ]
    [ Dec  9 09:17:33 Executing stop method (null) ]
    [ Dec 10 11:47:14 Enabled. ]
    [ Dec 10 11:47:24 Executing start method ("/lib/svc/method/fs-local") ]
    [ Dec 10 11:47:25 Method "start" exited with status 0 ]
    [ Dec 15 10:52:25 Stopping because service disabled. ]
    [ Dec 15 10:52:25 Executing stop method (null) ]
    [ Dec 15 12:42:16 Enabled. ]
    [ Dec 15 12:42:26 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 12:42:28 Method "start" exited with status 95 ]
    [ Dec 15 13:13:19 Enabled. ]
    [ Dec 15 13:13:28 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 13:13:30 Method "start" exited with status 95 ]
    [ Dec 15 13:58:51 Enabled. ]
    [ Dec 15 13:59:00 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 13:59:03 Method "start" exited with status 95 ]
    [ Dec 15 15:34:41 Leaving maintenance because clear requested. ]
    [ Dec 15 15:34:41 Enabled. ]
    [ Dec 15 15:34:41 Executing start method ("/lib/svc/method/fs-local") ]
    Abort - core dumped
    WARNING: /usr/sbin/zfs mount -a failed: exit status 134
    [ Dec 15 15:34:43 Method "start" exited with status 95 ]
    bash-3.00# /usr/sbin/zfs mount -a
    internal error: Unknown error
    Abort (core dumped)
    Before that I've installed the patch cluster with halted solaris zones which produced following output:
    Application of patches finished : 2010.12.15 12:08:43
    Following patches were applied :
    119254-77 119812-10 125719-31 140159-03 142911-01
    141588-04 119900-11 125731-05 142292-01 142933-02
    142251-02 119906-16 126206-05 141444-09 142909-17
    118666-28 120460-17 126363-08 141500-07 143140-04
    118667-28 121012-03 126365-16 141502-02 143502-01
    118777-16 121308-20 126868-04 141506-09 143506-01
    140860-02 122212-40 127724-02 141514-02 143615-02
    119059-56 122261-03 136998-09 141518-12 143731-01
    119213-23 122675-05 137000-07 141552-03 143733-01
    124628-10 123003-04 137080-05 141558-01 143977-01
    119252-29 123590-12 137147-06 141586-01 144053-04
    119280-23 123893-22 138195-04 141590-02 144106-01
    124188-03 124393-11 138822-07 141874-09 144254-01
    120199-15 124457-02 138826-07 141876-07 144488-04
    119534-19 124630-42 138880-02 142084-04 144492-01
    120272-28 125215-03 139099-04 142397-01 145124-01
    119757-18 125388-03 139620-01 142529-01 145796-01
    119783-15 125555-07
    Following patches were skipped :
    Patches already applied
    120900-04 119063-01 119810-05 123005-07 137093-01
    121133-02 119081-25 119986-03 124444-01 138866-03
    119317-01 119130-33 120061-02 124939-03 137137-09
    121296-01 123611-04 120201-05 124943-01 137871-02
    138215-01 140899-01 120292-02 124997-01 138181-01
    127884-01 122640-05 120329-02 125279-05 138361-01
    118712-23 126897-02 121975-01 125539-06 138373-02
    118918-24 127755-01 120719-02 125891-01 138647-01
    138217-01 125503-02 120830-06 126440-01 141016-01
    119578-30 125547-02 121095-02 126540-02 139555-08
    121453-02 140796-01 121606-04 127127-11 139967-01
    121453-02 120011-14 124171-07 136882-02 140455-01
    121118-16 139520-02 123630-03 137032-01 140563-01
    118833-36 119764-06
    Patches obsoleted by one or more patches already applied
    118731-01 124204-04 122660-10
    Patches not applicable to packages on the system
    121181-03 120410-33 121211-02 125533-15 143317-03
    119115-35 120412-11 122259-03 125541-06 143510-01
    119117-52 120414-27 122470-03 125952-20 143725-01
    119315-19 120543-21 122911-24 137004-08 143727-01
    119548-14 120739-06 122958-06 138387-01 143739-01
    119903-02 120811-09 123938-02 138824-07 144325-01
    120094-30 120849-04 125136-24 138876-01 145006-02
    120185-21 121104-11 125137-24 139986-01 145080-01
    119368-04 121136-02 125332-14 142244-02 145200-01
    120286-03
    Installation of patch set complete. PLEASE REBOOT THE SYSTEM.
    when i tried to reboot the system by init 6 the service iscsi hanged and produced syslog errors about a unkown iocall -> killed the process. System rebooted w/o errors.
    Does anyone have got an idea how to find out which patch or whatever do produce these errors?

    Hi,
    I'm having the same issue of diskmon core dumps after upgrading grid and database from 11.2.0.1 to 11.2.0.2 on Solaris 10 x86-64. Following this thread, I'm trying to deinstall the Oracle 11.2.0.1 grid home.
    I answered the following questions asked by the grid deinstall tool:
    1. ASM configuration was not detected in this Oracle home. Was ASM configured in this Oracle home (y|n): y
    2. Specify the ASM Diagnostic Destination: /db01/app/oracle/diag/asm/+ASM
    3. Specify the diskgroups that are managed by this ASM instance: DATA FRA
    4. De-configuring ASM will drop all the diskgroups at cleanup time. Do you want deconfig tool to drop the diskgroups:
    If I answer no to question 1, the tool exits with error.
    How do I answer question #4? (confused about this question of dropping diskgroups, it's already been upgraded)
    Deinstall of Oracle db Home 11.2.0.1 was successful.
    The +ASM instance has been upgraded and is running fine under 11.2.0.2 except for the excessive diskmon core dumps.
    Thanks,
    Lisa
    Edited by: user12018917 on Apr 19, 2011 10:21 AM

  • ORA-07445: exception encountered: core dump during database open

    Hi,
    after running OracleXE for 1 year on my notebook, I am running into a strange problem. During startup of the database ( opening the DB ) I get the following error:
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__VInfreq__kmmlrl+6329] [PC:0x2D7DF01] [ADDR:0x8] [UNABLE_TO_READ] []
    I then tried to reinstall the DB but the problem persists. I have no clues what influences this error.
    Any ideas welcome

    The machine is a notebook which is remotely administrated. The admin says there has not been a major software update.
    The notebook has 2 GB of main memory and 4 GB of free disk space.
    The database was up and running since 1 year. The first time I ran into this problem, was when I dropped a user from database. But that for sure was not the reason, as I totally removed oraclexe and reinstalled it from scratch and the problem persists.
    Interestingly the installation doesn't fail, but the final startup, so it might be one of the last packages being installed which produces the error.
    I'm looking forward to find some more details.

  • 13" late 2011 MacBook Pro has frozen after Yosemite installation. I can, however, boot from a clone of my MacBook Air that is on an external drive. Despite the fact that I can boot from the external, could it be the RAM that's the prob

    My daughter's 13" late 2011 MacBook Pro has frozen (null sign displays) after Yosemite installation. I can, however, boot from a clone of my MacBook Air that is on an external drive. I reinstalled Yosemite on the MBP HD, but it still hangs in mid install. Despite the fact that I can boot from the external, could it be the RAM that's the problem? I'd happily put 8 GB in if it seems probable that would solve the problem. I've tried all the suggested procedures that I've seen posted here. Disk Utility, and my older version of DiskWarrior indicate the HD is OK. I have DiskWarrior 5 on order.

    Boot the MBP with the OPTION key down.  If successful, you should see two HDD icons,  Select the recovery partition (on the right).
    From the 4 option menu select Disk Utility.
    Run Disk Utility>First Aid, Verify and Repair.
    If the disk cannot be repaired, it will have to be replaced.
    Ciao.

  • MDM installation on AIX 5.3 core dumps

    Hi all,
    We installed MDM 5.5 SP4 on AIX 5.3 ML 5 (and the latest patches were applied last week-end).
    The MDM Server, Import and Syndication daemons are started.
    Database is Oracle 10.2 (corresponding Oracle client is used), installed on the same server.
    MDM client software is in sync with the server level.
    Since the installation, we get core dumps of the mds daemon (even when trying to perform the most basic operations). Consider it to be completely unusable for testing anything. You look at it, it breaks. Sorry, but that is how it is.
    MDM Patches and hotfixes to the patches have been applied up to the latest level The problem is reported at SAP Support and they have core dumps, logfiles, trace files for studying.  So far, the only feedback we got was to install MDM on its own server (it is a trial installation on a server where other applications are running - though I can hardly see that as a cause for core dumps). 
    My questions :
    - are we unique in running MDM on this software paltform ?
    - are others (if they exist experiencing the same problems on AIX 5.3 ?
    To be honest : for the moment we are thinking about reinstalling on a Windows server.
    Thanks in advance for any feedback,
    Frank Van Overloop

    Hello,
    we have finally made some progress on this issue.
    Basically, we suffered from a combination of :
    - wrong usage of the product
    - probably shaky exception handling in the AIX version
    The cause was found by SAP MDM support after we reconstructed the problem while using a special debug-version of the mds executable. This produced a usable dump.
    --- extract from the SAP reply -
    The core dump shows a crash in recalculating the family tree after the
    import. Family tree is being used only to create printed catalogs (which require the publisher and an additional license).
    1) Do you have any value in the categories table?
    2) Does the MDM server crash if you cancel the automatic family tree
    recalculation in the import map, and answer "no" in the dialog box which asks to recalculate the family tree?
    3) Do you intend to create a printed catalog?
    If the answer to any of the questions is "no", then this asserts that
    the recalculation of the family tree should not take place at all. In
    this case the family table could/should be deleted. And this should not
    reoccur.
    end extract -
    After we deleted this family table,  the tests are running stable.
    It's a pity that the program does not 'die' in a more elegant way or gives some understandable indication on what is going wrong.
    It also looks like this exception is handled better on the Windows implementation. The same 'functional mistake' was made there and this produced no dumps at all. Could be a porting issue from one platform to another.
    Regards,
    Frank

  • SQL 2014 License mapping with physical cores during/after installation

    Hi,
    I have ESX Machine with 24 cores. I have to purchase SQL Server 2014 Enterprise physical core based license for 24 cores. so my question is- how SQL 2014 License will mapping/hosted/linked with physical cores during/after installation on ESX machine?
    Please help!!

    You are most welcome Satendra :-)
    Please close the thread, by marking the answer/s (the link under each response) and you can vote for responses as well (the link in the left of the response)
      Ronen Ariely
     [Personal Site]    [Blog]    [Facebook]

  • Hotspot core dumping during JVM garbage collection ?

    We have an application which calls a 3rd party supplied server API which has recently been upgraded to use Java 1.5
    We are getting the following error reported by our client application. The application is also now running Java 1.5 but references many classes in jar files which would have quite old code in.
    The supplier of the API has stated that the problem requires us to recompile all our jar files using v 1.5 ( including things like jconnect and jms ?!?!? ). This sounds like a bit of a cop-out to me, not to mention being impossible since we don't have the source for things like jconnect.
    I suspect that there is a garbage collection problem at the bottom of all this, but I'm not sure how I can "prove" this, nor do I currently have any real clue as to how to fix any GC problem that may exist.
    The application is supposed to wait for a message on a MQSeries queue and then transforms it via Xalan XSLT and sends it to a Server application. I've tried playing around with heap sizes etc but that just seems to make it worse. If I leave it at the settings that the previous version used then the client at least manages to process a couple of messages before core dumping. There doesn't seem to be a consistent trigger event to cause the core dump ( it's not a message arriving on a queue for example ) but it does seem to be fairly consistent timewise, i.e. after
    Any ideas gratefully accepted.
    Here's a logfile excerpt from my applications showing the Hotspot error message :
    =====================================================================================
    08-Jul-2008 10:01:05 Waiting for messages from COLT.BBFS
    08-Jul-2008 10:02:05 Waiting for messages from COLT.BBFS
    08-Jul-2008 10:03:05 Waiting for messages from COLT.BBFS
    405.815: [GC [PSYoungGen: 17331K->9244K(37632K)] 111702K->103615K(192128K), 0.1615910 secs]
    405.977: [Full GC#
    # An unexpected error has been detected by HotSpot Virtual Machine:
    #  SIGBUS (0xa) at pc=0xfe141348, pid=2600, tid=8
    # Java VM: Java HotSpot(TM) Server VM (1.5.0_03-b07 mixed mode)
    # Problematic frame:
    # V  [libjvm.so+0x141348]
    # An error report file with more information is saved as hs_err_pid2600.log
    # If you would like to submit a bug report, please visit:
    # http://java.sun.com/webapps/bugreport/crash.jsp
    =====================================================================================
    The logfile referred to in the error message contains the following.
    =====================================================================================
    # An unexpected error has been detected by HotSpot Virtual Machine:
    # SIGBUS (0xa) at pc=0xfe141348, pid=2600, tid=8
    # Java VM: Java HotSpot(TM) Server VM (1.5.0_03-b07 mixed mode)
    # Problematic frame:
    # V [libjvm.so+0x141348]
    --------------- T H R E A D ---------------
    Current thread (0x001484d8): VMThread [id=8]
    siginfo:si_signo=10, si_errno=0, si_code=1, si_addr=0x0000080f
    Registers:
    O0=0x00487588 O1=0xfe7d6454 O2=0x000079b0 O3=0x00007800
    O4=0x00008868 O5=0x00147d48 O6=0xf8781460 O7=0xfe0f7938
    G1=0xe52aaae8 G2=0x00000003 G3=0x00000003 G4=0x001484d8
    G5=0xf8781d98 G6=0x00000002 G7=0xf8781d98 Y=0x805683e2
    PC=0xfe141348 nPC=0xfe14134c
    Top of Stack: (sp=0xf8781460)
    0xf8781460: fe786000 00c6ba20 fe10013c e54bab68
    0xf8781470: 0000080f e54bab6c 0000080f 00000004
    0xf8781480: 00487588 00000134 e54bab6c 00000004
    0xf8781490: 00000001 00000000 f87814c0 fe17aef4
    0xf87814a0: fe6485b4 fe7d899c 001484d8 0011da40
    0xf87814b0: 00148988 00148c10 00148d7c f8781880
    0xf87814c0: 007c3389 007c3c0e 00000f87 00008868
    0xf87814d0: 00008800 00487588 fe141310 fe7d6454
    Instructions: (pc=0xfe141348)
    0xfe141338: ec 06 c0 1a 80 a5 a0 00 22 40 00 0a ba 07 60 01
    0xfe141348: f2 05 a0 00 ae 0e 60 03 80 a5 e0 03 22 40 00 05
    Stack: [0xf8702000,0xf8781d98), sp=0xf8781460, free space=509k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    V [libjvm.so+0x141348]
    V [libjvm.so+0x17aefc]
    V [libjvm.so+0x2d557c]
    V [libjvm.so+0x300ef8]
    V [libjvm.so+0x301e84]
    V [libjvm.so+0x2ff950]
    V [libjvm.so+0x29df30]
    V [libjvm.so+0x362b44]
    V [libjvm.so+0x6436f0]
    VM_Operation (0xe03012b0): parallel gc system gc, mode: safepoint, requested by thread 0x0031bca0
    --------------- P R O C E S S ---------------
    Java Threads: ( => current thread )
    0x00b2c028 JavaThread "Thread-4" [_thread_in_native, id=85]
    0x007f5048 JavaThread "Thread-0" [_thread_blocked, id=84]
    0x00c27cf0 JavaThread "Notification Delivery" [_thread_blocked, id=81]
    0x0026fa08 JavaThread "RMI LeaseChecker" daemon [_thread_blocked, id=73]
    0x00821048 JavaThread "RMI RenewClean-[162.11.2.32:44425]" daemon [_thread_blocked, id=70]
    0x0031bca0 JavaThread "GC Daemon" daemon [_thread_blocked, id=67]
    0x00cd5d28 JavaThread "RMI Reaper" [_thread_blocked, id=66]
    0x003c9300 JavaThread "Timer-0" daemon [_thread_blocked, id=65]
    0x00929fe0 JavaThread "RMI TCP Accept-0" daemon [_thread_in_native, id=64]
    0x0089bf18 JavaThread "SeedGenerator Thread" daemon [_thread_blocked, id=42]
    0x00c47248 JavaThread "Pool thread #7" daemon [_thread_blocked, id=38]
    0x00c466a0 JavaThread "Pool thread #6" daemon [_thread_blocked, id=37]
    0x00311850 JavaThread "Pool thread #5" daemon [_thread_blocked, id=36]
    0x00287a40 JavaThread "Pool thread #4" daemon [_thread_blocked, id=35]
    0x00286e98 JavaThread "Pool thread #3" daemon [_thread_blocked, id=34]
    0x00c134b0 JavaThread "Pool thread #2" daemon [_thread_blocked, id=33]
    0x00ad09e0 JavaThread "Pool thread #1" daemon [_thread_blocked, id=32]
    0x00286cd8 JavaThread "PoolThreadManager" daemon [_thread_blocked, id=31]
    0x00c129e0 JavaThread "Channel Reaper" daemon [_thread_blocked, id=30]
    0x00c669e8 JavaThread "ORB Daemon Thread" daemon [_thread_blocked, id=29]
    0x00b10170 JavaThread "Worker for ServerProtocol: (iiop) /0.0.0.0:20168" daemon [_thread_blocked, id=22]
    0x008a17e0 JavaThread "Syn~ Client" daemon [_thread_blocked, id=21]
    0x003dc378 JavaThread "PoolScavenger0" daemon [_thread_blocked, id=20]
    0x0015a928 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=15]
    0x00159880 JavaThread "CompilerThread1" daemon [_thread_blocked, id=14]
    0x00158a18 JavaThread "CompilerThread0" daemon [_thread_blocked, id=13]
    0x00157b98 JavaThread "AdapterThread" daemon [_thread_blocked, id=12]
    0x00156dc8 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=11]
    0x0014ccd8 JavaThread "Finalizer" daemon [_thread_blocked, id=10]
    0x0014ad90 JavaThread "Reference Handler" daemon [_thread_blocked, id=9]
    0x00038238 JavaThread "main" [_thread_in_native, id=1]
    Other Threads:
    =>0x001484d8 VMThread [id=8]
    0x0015c3b0 WatcherThread [id=16]
    VM state:at safepoint (normal execution)
    VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
    [0x00037728/0x00037758] Threads_lock - owner thread: 0x001484d8
    [0x00033650/0x00037ba8] Heap_lock - owner thread: 0x0031bca0
    Heap
    PSYoungGen total 37632K, used 9244K [0xf2eb0000, 0xf7ba0000, 0xf8400000)
    eden space 28352K, 0% used [0xf2eb0000,0xf2eb0000,0xf4a60000)
    from space 9280K, 99% used [0xf4a60000,0xf5367080,0xf5370000)
    to space 25216K, 0% used [0xf6300000,0xf6300000,0xf7ba0000)
    PSOldGen total 154496K, used 94371K [0xe8400000, 0xf1ae0000, 0xf2eb0000)
    object space 154496K, 61% used [0xe8400000,0xee028e78,0xf1ae0000)
    PSPermGen total 35584K, used 18260K [0xe4400000, 0xe66c0000, 0xe8400000)
    object space 35584K, 51% used [0xe4400000,0xe55d5158,0xe66c0000)
    Dynamic libraries:
    0x00010000      /dsdvlp/java/jvm/jdk1.5.0_03/bin/java
    0xff350000      /usr/lib/libthread.so.1
    0xff340000      /usr/lib/libdl.so.1
    0xff200000      /usr/lib/libc.so.1
    0xff390000      /usr/platform/SUNW,Sun-Fire-880/lib/libc_psr.so.1
    0xfe000000      /dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc/server/libjvm.so
    0xff1e0000      /usr/lib/libsocket.so.1
    0xff2d0000      /usr/lib/libsched.so.1
    0xff1b0000      /usr/lib/libCrun.so.1
    0xff160000      /usr/lib/libm.so.1
    0xff080000      /usr/lib/libnsl.so.1
    0xff060000      /usr/lib/libmp.so.2
    0xff030000      /dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc/native_threads/libhpi.so
    0xfdfc0000      /dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc/libverify.so
    0xfdf80000      /dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc/libjava.so
    0xfdf50000      /dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc/libzip.so
    0xfb7e0000      /usr/lib/locale/en_GB.ISO8859-1/en_GB.ISO8859-1.so.2
    0xe4190000      /dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc/libnet.so
    0xe3bd0000      /dsdvlp/lib/5/libSolarisNatives.so
    0xe3e90000      /dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc/librmi.so
    VM Arguments:
    jvm_args: -Djava.ext.dirs=/dsdvlp/java/tmijar/firs7/lib/cli:/dsdvlp/java/tmijar/firs7/lib/cli/ext:/dsdvlp/java/tmijar/firs7/lib/cmn/OpenORB:/dsdvlp/java/tmijar/firs7/lib/cmn/OpenORB/ext:/dsdvlp/java/tmijar/firs7/lib/cmn:/dsdvlp/java/tmijar/firs7/lib/cmn/ext:/dsdvlp/java/tmijar/firs7/daemonlib -Duser.dir=/dsdvlp/java/tmijar/firs7 -Dopenorb.config=file:/dsdvlp/java/tmijar/firs7/configs/OpenORB/config/SynOpenORB.xml -Dopenorb.home=file:/dsdvlp/java/tmijar/firs7/configs/OpenORB -Dcom.coexis.syn.general.orbbinding=com.coexis.syn.general.orbbinding.openorb.OpenORBBinding_1_4 -Dsun.rmi.dgc.client.gcInterval=360000 -Dsun.rmi.dgc.server.gcInterval=360000000 -Xms32m -Xmx256m -Dcom.coexis.syn.clientcommandsconfiglocation=file://localhost//dsdvlp/java/tmijar/firs7/configs/clientcommands.xml -Dcom.coexis.syn.clientconfiglocation=file://localhost//dsdvlp/java/tmijar/firs7/configs/fsbbtd_client.xml -XX:+PrintGCTimeStamps -XX:+PrintGCDetails
    java_command: com.coexis.syn.mqmessaging.daemon.RunDaemon -p /dsdvlp/bin/5/lndsfsd_fsbbtd.properties start
    Environment Variables:
    JAVA_HOME=/dsdvlp/java/jvm/jdk150
    CLASSPATH=.:/dsdvlp/java/jar/jconnect520.jar:/dsdvlp/java/jar/vbjapp340.jar:/dsdvlp/java/jar/vbjorb340.jar:/dsdvlp/java/jar/javax_jndi120.jar
    PATH=/usr/local/etc:/usr/lang:/usr/openwin/bin:/usr/ucb:/bin:/usr/etc:/usr/local/5/bin:/dsdvlp/bin/5:/dsdvlp/bin/4:/home/app/sybase/5/bin:/home/app/sybase/5/localscripts:/home/app/sybase/5/sqr:/home/app/lang:/home/app/lang/SC2.0.1:/usr/ccs/bin:/usr/local/opt/Acrobat3/bin:/dsdvlp/bin:.
    LD_LIBRARY_PATH=/dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc/server:/dsdvlp/java/jvm/jdk1.5.0_03/jre/lib/sparc:/dsdvlp/java/jvm/jdk1.5.0_03/jre/../lib/sparc:/usr/lib:/usr/openwin/lib:/usr/local/5/lib:/dsdvlp/lib/5:/dstest/lib/5:/home/app/sybase/5/lib:/dstest/cats/sun4/lib:/tmitest/Opus/opus/lib
    SHELL=/bin/csh
    DISPLAY=CLI00184.mfil.local:1.0
    OS=5
    --------------- S Y S T E M ---------------
    OS: Solaris 8 2/02 s28s_u7wos_08a SPARC
    Copyright 2002 Sun Microsystems, Inc. All Rights Reserved.
    Assembled 18 December 2001
    uname:SunOS 5.8 Generic_117350-20 sun4u (T1 libthread)
    rlimit: STACK 8192k, CORE 9216k, NOFILE 4096, AS infinity
    load average:2.24 2.67 2.68
    CPU:total 4 has_v8, has_v9, has_vis1, has_vis2, is_ultra3
    Memory: 8k page, physical 8388608k(166384k free)
    vm_info: Java HotSpot(TM) Server VM (1.5.0_03-b07) for solaris-sparc, built on Apr 13 2005 03:31:26 by unknown with unknown Workshop:0x550

    The very first suggestion I have is to move your VM to a more recent update of 1.5.0.
    It looks like you are crashing with 5.0u3, and I'm pretty sure 5.0u16 is available. You
    don't want to waste your time chasing a bug that's already been fixed.

  • I have a 2009 Macbook Pro with 1T hdd 8GB Ram and ran Maverick without problem...Yosemite installation has me completely frozen, nothing works but the spinning ball...I had to force shutdown last night, and haven't turned it on again...what do you ad

    I have a 2009 Macbook Pro with 1T hdd 8GB Ram and ran Maverick without problem...Yosemite installation has me completely frozen, nothing works but the spinning ball...I had to force shutdown last night, and haven't turned it on again...what do you advise?  During installation emptied cache, etc. Backed up using time machine, fortunately.

    Try these in order testing your system after each to see if it's back to normal:
    1. a. Resetting your Mac's PRAM and NVRAM
        b. Intel-based Macs: Resetting the System Management Controller (SMC)
    2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
    4. Reinstall Yosemite: Reboot from the Recovery HD. Select Reinstall OS X from the Utilities menu, and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
                because it is three times faster than wireless.
    5. Reinstall Yosemite from Scratch:
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    How to Clean Install OS X Yosemite
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
                because it is three times faster than wireless.

  • Cannot start BI server, cannot start cluster successfully, core dumped

    Hi
    I have the following configuration. The four machines are virtualized containers on solaris sparc
    machine 1 - PS, java host, web logic
    machine 2 - PS, java host, web logic
    machine 3 - bi server, primary cluster controller, scheduler
    machine 4 - bi server, secondary cluster controller, scheduler
    However i dont need the scheduler and i have not configured them completely
    I was able to successfully test on compete stack with no clustering and used only machines 1 and 3. I was able to login to the sample URL and see some graphs.
    The problem started once i was trying the clustering. I looked at the admin docs and the installation and deployment guides and followed the instructions and carefully did the configuration.
    I face multiple problems.
    In single stack some time the BI server was randoly stopping itself for no reason after starting it. it was very random that i used to feel happy if it does not stop.
    During clustering i was not able to start the cluster successfully at all. I did not want to worry about scheduler to start with and even the PS. I just wanted to connect to the BI server using the primary ccs and using the admin tool in the windows machine.
    Today morning i tried to start the BI server and then there was a core dump in both the machines and then i am not even able to start the server at all. There was nothing in the log files and i dont know what to do.
    The log files before the core dump as follows.
    server log file
    2009-07-30 18:18:47
    [36007] Loading repository /software/oraclebi/server/Repository/samplesales.rpd.
    2009-07-30 18:18:49
    [14055] Loading subject area: Sample Sales ...
    2009-07-30 18:18:49
    [14056] Finished loading subject area: Sample Sales.
    2009-07-30 18:18:49
    [58002] Query Cache loaded with 7 entries from saved cache files.
    2009-07-30 18:18:49
    [43030] : Oracle BI Server (64-bit) started. Version: 10.1.3.4.1.090414.1900.
    2009-07-30 18:19:11
    [43031] : Oracle BI Server shutdown.
    2009-07-30 18:19:12
    [58001] Query Cache Statistics -- Hits:0(0%), Qualified Misses:0(0%), Unqualified Misses:0(0%).
    2009-07-30 18:19:12
    [14058] Unloaded all subject areas.
    2009-07-30 18:25:25
    [36007] Loading repository /software/oraclebi/server/Repository/samplesales.rpd.
    2009-07-30 18:25:27
    [14055] Loading subject area: Sample Sales ...
    2009-07-30 18:25:27
    [14056] Finished loading subject area: Sample Sales.
    2009-07-30 18:25:27
    [58002] Query Cache loaded with 7 entries from saved cache files.
    2009-07-30 18:25:27
    [43030] : Oracle BI Server (64-bit) started. Version: 10.1.3.4.1.090414.1900.
    2009-07-30 18:26:25
    [43071] A connection with Cluster Controller maa-zone4:9706 was established.
    2009-07-30 18:30:08
    [nQSError: 12002] Socket communication error at call=recv: (Number=131) Connection reset by peer
    2009-07-30 18:30:08
    [nQSError: 12002] Socket communication error at call=recv: (Number=131) Connection reset by peer
    2009-07-30 20:57:24
    [36007] Loading repository /software/oraclebi/server/Repository/samplesales.rpd.
    2009-07-30 20:57:26
    [14055] Loading subject area: Sample Sales ...
    2009-07-30 20:57:26
    [14056] Finished loading subject area: Sample Sales.
    2009-07-30 20:57:26
    [58002] Query Cache loaded with 7 entries from saved cache files.
    2009-07-30 20:57:26
    [43030] : Oracle BI Server (64-bit) started. Version: 10.1.3.4.1.090414.1900.
    2009-07-30 20:58:39
    [43031] : Oracle BI Server shutdown.
    2009-07-30 20:58:39
    [58001] Query Cache Statistics -- Hits:0(0%), Qualified Misses:0(0%), Unqualified Misses:0(0%).
    2009-07-30 20:58:39
    [14058] Unloaded all subject areas.
    2009-07-30 21:01:40
    [36007] Loading repository /software/oraclebi/server/Repository/samplesales.rpd.
    2009-07-30 21:01:42
    [14055] Loading subject area: Sample Sales ...
    2009-07-30 21:01:42
    [14056] Finished loading subject area: Sample Sales.
    2009-07-30 21:01:42
    [58002] Query Cache loaded with 7 entries from saved cache files.
    2009-07-30 21:01:42
    [43030] : Oracle BI Server (64-bit) started. Version: 10.1.3.4.1.090414.1900.
    2009-07-30 21:08:51
    [43071] A connection with Cluster Controller maa-zone4:9706 was established.
    2009-07-30 21:10:31
    [43065] The connection with Cluster Controller maa-zone4:9706 was lost.
    2009-07-30 21:12:59
    [43071] A connection with Cluster Controller maa-zone4:9706 was established.
    :x
    $ ls
    cluster controller log file
    2009-07-30 21:12:59
    [71008] Cluster Controller started. Version: 10.1.3.4.1.090414.1900
    2009-07-30 21:12:59
    [71021] An attempt to establish a connection with Oracle BI Server maa-zone03:9703 failed.
    2009-07-30 21:12:59
    [71020] A connection with Oracle BI Server maa-zone4:9703 was established.
    2009-07-30 21:12:59
    [71010] Oracle BI Server maa-zone4:9703 has transitioned to ONLINE state.
    2009-07-30 21:13:14
    [71050] This Cluster Controller is promoted to Controlling because there has been no recent contact from
    the Primary Cluster Controller.
    2009-07-30 21:13:14
    [71071] An attempt to establish a connection with Oracle BI Scheduler maa-zone03:9705 failed.
    2009-07-30 21:13:14
    [71068] Oracle BI Scheduler maa-zone03:9705 has transitioned to OFFLINE state.
    2009-07-30 21:13:14
    [71071] An attempt to establish a connection with Oracle BI Scheduler maa-zone4:9705 failed.
    2009-07-30 21:13:14
    [71068] Oracle BI Scheduler maa-zone4:9705 has transitioned to OFFLINE state.
    2009-07-30 23:10:34
    [71019] The connection with Oracle BI Server maa-zone4:9703 was lost.
    2009-07-30 23:10:34
    [71011] Oracle BI Server maa-zone4:9703 has transitioned to OFFLINE state.
    2009-07-30 23:10:39
    [71021] An attempt to establish a connection with Oracle BI Server maa-zone4:9703 failed.
    your help is appreciated.
    thanks
    chaitanya kadaru

    all the four machines are four containers in a solaris server.
    The problem was with the hosts file, there were not entries matching the ipaddress and the hotname.
    After i fixed it now i have a stable BI servers and cluster controllers.
    Now i configured the presentation services to connect to the BI servers but i am getting the following exception.
    Type: Error
    Severity: 42
    Time: Thu Aug 6 13:04:02 2009
    File: project/webcomm/socket.cpp Line: 892
    Properties: ThreadID-6
    Location:
    saw.rpc.client.impl.verify
    saw.rpc.client.impl.initFixedRPC
    saw.rpc.client.cluster
    saw.threads
    An error occurred during execution of "connect". Connection refused [Socket:15]
    Any idea?
    thanks

  • WL 6.0sp2 + Syslog = core dump

    On Solaris 2.8, our startup class which calls Syslog.configure produces a
    core dump while starting the wl server.
    We're using jdk 1.3.0, Xalan 2.1 and the Xerces that comes with Xalan,
    jdom-b7 ( b6 also has the same resulte ) and the wl xml registry is set up
    to use external xalan / xerces rather than the internal versions. Xalan &
    Xerces are after the WL jars in the classpath during booting; we've also
    tried them before with the same results.
    This was working fine under Solaris 2.6, but no longer. Any ideas?

    On Solaris 2.8, our startup class which calls Syslog.configure produces a
    core dump while starting the wl server.
    We're using jdk 1.3.0, Xalan 2.1 and the Xerces that comes with Xalan,
    jdom-b7 ( b6 also has the same resulte ) and the wl xml registry is set up
    to use external xalan / xerces rather than the internal versions. Xalan &
    Xerces are after the WL jars in the classpath during booting; we've also
    tried them before with the same results.
    This was working fine under Solaris 2.6, but no longer. Any ideas?

  • Windows could not update the computer's boot configuration. Installation cannot proceed.

    HELP!!!
    Windows could not update the computer's boot configuration. Installation cannot proceed.
    The installation then it says "The installation was canceled" and "Any changes to your computer won't be saved.
    I have been trying to sort this out for over 15 hours.
    I have the MacBook Pro (Late 2011)
    Quad Core i7 (Clocked at 2.2GHz)
    4GB Ram
    Radeon Graphics (512mb graphics ram)
    Running OSX Yosemite (10.10.2)

    Did you have to modify Bootcamp Inof.plist to see the USB Installer option?
    Your USB device needs to be a USB2 device. Here is an example.

  • [Solved] Systemd: how to disable core dumps on application crashes?

    Hi,
    I'm sorry if this is the wrong forum, but I just couldn't find a place that's really suitable for such a question.
    I have a really annoying problem with systemd: I'm developing software, which sometimes crashes. And when it crashes, I sometimes want to examine core dumps.
    The problem is that systemd seems to force coredumps, but saves them in some kind of obscure internal storage, where I don't have a clue about how to extract them from.
    The only hint that I could find was http://lists.freedesktop.org/archives/s … 04643.html which isn't really helpful.
    The problem is that systemd installs its coredump handler on boot:
    [root@neptun ~]# cat /proc/sys/kernel/core_pattern
    |/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e
    Is there any way to disable this? I don't want core dumps to be generated unless I need them. Just clearing that file on boot seems too hackish for me, does anybody know if there is a systemd
    configuration option to turn coredumps off?
    Cheers,
    andr3as
    Last edited by andr3as (2012-12-15 01:42:24)

    The .conf file was recently renamed so the symlink must be called different as well. But I found it needs to contain something to actually overload systemd's default
    # echo kernel.core_pattern= > /etc/sysctl.d/50-coredump.conf
    # /lib/systemd/systemd-sysctl
    # cat /proc/sys/kernel/core_pattern # should be empty
    Last edited by Spider.007 (2013-07-13 10:06:41)

  • 13" Macbook is freezing during re-installation.

    Need of a little help here.  My book is freezing on the second disk during installation.  I am am re-installing due an issue on boot up trying to read the file System\Library\Caches\com.apple.kext.caches\Startup\Extensions.mkext.  I get a Read error0x7.  The disk utility from the start up reports that the disk appears to be healthy and all permsions are correct.  Any one have any ideas what could be goign on?  Can anyone tell me of any diagnostics I can run during the installation to see where the hang is? 

    The next time you have the problem, note the exact time: hour, minute, second.
    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Scroll back in the log to the time you noted above. Select any messages timestamped from then until the end of the episode. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Yosemite installer crashes

    On my i7 17 inch Powerbook, which has Mavericks 10.9.5, attempts to install Yosemite have failed.  When I downloaded the Yosemite installer the process got to the point where it said the machine will automatically restart but this never happened. So I went in and double clicked the Yosemite installer ap - it crashed within a few seconds. I have rebooted the machine, done a repair and permissions fix, started in Safe Mode, deleted and re-downloaded the installer app all with the same result - a crash at various times after the installer has been launched.
    The only console entry is that the system failed to make Yosemite Install the frontmost application. Sometimes it fails before I get any dialogs, sometimes it fails after a dialog or two has come up, sometimes it gets part way through the install dialog before it is to reboot and crashes.
    Any ideas or suggestions?

    Boot to the Recovery Volume (command - R on a restart or hold down the option key during a restart and select Recovery Volume). Run Disk Utility Verify/Repair and Repair Permissions until you get no errors.  Then re-install the OS.
    OS X Recovery
    OS X Recovery (2)

  • MSI P67A-C45 - Shutting down during OS installation

    I'll take a wild swing into cyber-space, hoping that someone out there have experienced this problem and found a solution.
    I've had a look around on these forums, trying to find a topic with the same problem as I've experienced, but couldn't find any.
    A friend of mine just bought the MSI P67A-C45 and it booted just fine. The problem occurs when trying to install Windows 7 Home premium 64bit version. It goes through the normal steps, re-booting once during the installation. But when trying to finalize the installation, the motherboard simply shuts down, and boots back up ~4-5 seconds later.
    I've tried booting with minimal components; Motherboard, GPU, SSD & DVD-ROM. I've also tried installing it on 2 other disks, 1 10k raptor and a normal 7200, but with the same result.
    Has anyone experienced this problem before? Or does anyone have any idea what could be causing it to shut down like this?
    Any ideas are welcome and appreciated.
    Spec of the PC:
    MSI P67A-C45
    Intel Core i7, 2600
    Corsair 8GB (2x4096MB) 1600MHz XMS3
    Gigabyte GeForce GTX 580 1536MB (Nvidia chipset)
    Corsair SSD Force Series 120GB
    FSP Everest 1010 , See spec below
    /Zanza

    Quote from: Stu on 12-April-11, 02:12:16
    Several members of this forum, myself included, have done our own tests and concluded that AHCI is of no benefit to SSD drives.
    That makes total sense because the only real benefit of AHCI for single drives is native command queuing which allows physical drive systems to sort the command queue in the way that best reduces head movement and revolutions (since data is placed all over the platters).  With an SSD, every memory location can be read at exactly the same speed so native command queuing would actually decrease performance by the few microseconds it takes to perform the useless command queue sorting operation.  
    - D

Maybe you are looking for