Sshd core dump after logout
I've noticed that sshd has been producing core dumps. The core dumps aren't affecting anything and appear to be produced after the ssh session ends.
/var/adm/messages shows:
Jun 30 09:59:59 www1 sshd[15453]: [ID 800047 auth.info] Accepted publickey for webstats from 123.123.123.123 port 4935 ssh2
Jun 30 10:00:01 www1 genunix: [ID 603404 kern.notice] NOTICE: core_log: sshd[15453] core dumped: /var/core/core_www1_sshd_0_0_1151625600_15453
A core dump isn't produced every time but only appears to happen after ssh connections from windows systems running cygwin.
Running adb on a core dump shows:
core file = core_www1_sshd_0_0_1151390790_3514 -- program ``/usr/lib/ssh/sshd
'' on platform i86pc
SIGSYS: Bad System Call
Like I said, it doesn't appear to be causing any problems. Any ideas on how to stop it?
Forgot to mention. We are calling OCISessionEnd before rolling through OCIServerDetach.
/* STATIC */
static void logout()
printf ("\n\nFreeing statement handles..\n");
if(stmthp) OCIHandleFree ((dvoid *) stmthp, (ub4) OCI_HTYPE_STMT);
printf ("Logging off...\n");
if(authp) OCISessionEnd (svchp, errhp, authp, (ub4) 0);
Similar Messages
-
Hi,
We are continously getting dumps on our BW Central instance server after we did an Oracle patch upgrade from 9.2.0.6 to 9.2.0.8.
Following is our system environment
SAP Release.............. "640"
Application server....... "abci"
Operating system......... "SunOS"
Release.................. "5.10"
Hardware type............ "sun4v"
Database server.......... "abdb"
Database type............ "ORACLE"
Database name............ "ABP"
Database owner........... "SAPABP"
SAP kernel............... "640"
Database version......... "OCI_920 "
Patch level.............. "175"
Following below is the Core Dump that is generated for any process chains that we schedule on our BW server
Runtime Errors SYSTEM_CORE_DUMPED
Date and Time 14.04.2008 09:26:17
ShrtText
Process terminated by signal 11.
What happened?
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPMSSY2" had to be terminated because the ABAP
processor discovered an invalid system state.
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An SAP System process was terminated by an operating system signal.
Possible reasons for this are:
1. Internal SAP System error.
2. Process was terminated externally (by the system administrator).
Last error logged in SAP kernel
Component............ "Taskhandler"
Place................ "SAP-Server awci_ABP_00 on host awci (wp 5)"
Version.............. 1
Error code........... 11
Error text........... "ThSigHandler: signal"
Description.......... " "
System call.......... " "
Module............... "thxxhead.c"
Line................. 9780
How to correct the error
The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
contains a file called 'core'.
Save this file under another name.
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Kindly help.
Regards
Sachin
Edited by: Sachin N on Apr 14, 2008 12:26 PMNo. If the environment would be wrong the system wouldn´t start up.
Core dumps are in 99 % of the cases program errors (in the SAP kernel or in an interface (libdbora*)), misaligend accesses of data etc.
If you encounter such an error have a look in the C-Stack. If you can´t see where the error is happening opening an OSS call. Most of those errors are fixed by installing the latest patches for the kernel and the database interface.
Markus -
Memoy fault, core dump after import
Hi,
db is 9.2.0.7, os is hp-ux itanium 11.23
i have done schema level import, after import, i got the memory fault core dump at end of the import log file as last entry. I have seen core dump file created.
I did not see any errors in alert log file.
But Import has been done successfuly and can check that all objects are imported successfully.
why this memory cored dump error logged in import log file.Please post full error message what You got.
-
Large Core Dumps after DB Backup Control File
Hi All,
Server Specs (it is the test server having no functional modules):
Windows 2003 64bit
Oracle 10.2.0.4 (Patched from 10.2.0.2)
Netweaver 2004s
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
ORA-00279: change 21375038 generated at 09/21/2007 20:12:47 needed for thread 1
ORA-00289: suggestion : /export/pspp/oracle/dbs/xxx_example_xxx.dbf
ORA-00280: change 21375038 for thread 1 is in sequence #4
Specify log: {=suggested | filename | AUTO | CANCEL}
/OraRedo/RedoLogFiles/xxx_example_xxx.dbf
Log applied.
Media recovery complete.
I was facing Control file inconsistence issues against 2 partitions. Issue was resolved by using above commands and Netweaver started successfully. Im now facing another problem, im getting huge tracefiles in SAPTRACE\BACKGROUND folder since its recovery. I deleted those tracefiles which were of approx. 86GB.
Current Tracefiles sizes are:
<drive>:\oracle\TST\saptrace\background\tst_m000_5188.trc (7MB) and it is getting double by each generation.
Here are tracefiles of today (old ones deleted by me coz it was consuming a hell of space, e.g: 86GB as mentioned):
tst_m000_5188.trc (7 MB) Latest
tst_j000_5316.trc (4MB)
Here is Initial info from alert_tst.txt file contained in same folder:
Dump file f:\oracle\tst\saptrace\background\alert_tst.log
Thu Sep 02 13:55:34 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V5.2 Service Pack 1
CPU : 2 - type 8664, 1 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:2886M/4019M, Ph+PgF:19295M/20131M
Thu Sep 02 13:55:34 2010
Starting ORACLE instance (normal)
Thu Sep 02 13:55:35 2010
Specified value of sga_max_size is too small, bumping to 666894336
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 666894336
shared_pool_size = 318767104
shared_pool_reserved_size= 31598837
filesystemio_options = setall
control_files = E:\ORACLE\TST\ORIGLOGA\CNTRL\CNTLRTST.DBF, E:\ORACLE\TST\ORIGLOGB\CNTRL\CNTRLTST.DBF, F:\ORACLE\TST\SAPDATA1\CNTRL\CNTRLTST.DBF
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 318767104
compatible = 10.2.0
log_archive_dest = E:\oracle\TST\oraarch\TSTarch
log_buffer = 2061312
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = F:\ORACLE\TST\SAPTRACE\BACKGROUND
user_dump_dest = F:\ORACLE\TST\SAPTRACE\USERTRACE
core_dump_dest = F:\ORACLE\TST\SAPTRACE\BACKGROUND
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = TST
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 421317836
workarea_size_policy = AUTO
statistics_level = typical
MMAN started with pid=4, OS id=2760
PMON started with pid=2, OS id=2748
DBW0 started with pid=5, OS id=712
LGWR started with pid=6, OS id=604
CKPT started with pid=7, OS id=1088
SMON started with pid=8, OS id=1164
RECO started with pid=9, OS id=2680
CJQ0 started with pid=10, OS id=2972
MMON started with pid=11, OS id=1816
MMNL started with pid=12, OS id=2904
PSP0 started with pid=3, OS id=2692
Please Review,
Thanks in Advance.
Best Regards.All dispatchers and shared servers shutdown
Mon Jan 10 15:19:45 2011
ALTER DATABASE CLOSE NORMAL
Mon Jan 10 15:19:45 2011
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Jan 10 15:19:46 2011
Shutting down archive processes
Archiving is disabled
Mon Jan 10 15:19:51 2011
ARCH shutting down
ARC1: Archival stopped
Mon Jan 10 15:19:56 2011
ARCH shutting down
ARC0: Archival stopped
Mon Jan 10 15:19:57 2011
Thread 1 closed at log sequence 11
Successful close of redo thread 1
Mon Jan 10 15:19:59 2011
Completed: ALTER DATABASE CLOSE NORMAL
Mon Jan 10 15:19:59 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Shutting down Data Guard Broker processes
Mon Jan 10 15:20:00 2011
Completed: Data Guard Broker shutdown
Mon Jan 10 15:20:02 2011
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Jan 10 15:21:43 2011
Starting ORACLE instance (normal)
Mon Jan 10 15:21:43 2011
Specified value of sga_max_size is too small, bumping to 645922816
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 645922816
shared_pool_size = 318767104
__java_pool_size = 4194304
java_pool_size = 4194304
shared_pool_reserved_size= 31598837
filesystemio_options = setall
control_files = E:\ORACLE\TST\ORIGLOGA\CNTRL\CNTLRTST.DBF, E:\ORACLE\TST\ORIGLOGB\CNTRL\CNTRLTST.DBF, F:\ORACLE\TST\SAPDATA1\CNTRL\CNTRLTST.DBF
control_file_record_keep_time= 30
db_block_size = 8192
db_cache_size = 318767104
compatible = 10.2.0
log_archive_dest = E:\oracle\TST\oraarch\TSTarch
log_buffer = 2061312
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=TSTXDB)
job_queue_processes = 1
background_dump_dest = F:\ORACLE\TST\SAPTRACE\BACKGROUND
user_dump_dest = F:\ORACLE\TST\SAPTRACE\USERTRACE
core_dump_dest = F:\ORACLE\TST\SAPTRACE\BACKGROUND
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = TST
open_cursors = 800
optimpeek_user_binds = FALSE
pga_aggregate_target = 421317836
workarea_size_policy = AUTO
statistics_level = typical
dg_broker_start = TRUE
PMON started with pid=2, OS id=5108
PSP0 started with pid=3, OS id=3884
MMAN started with pid=4, OS id=3212
DBW0 started with pid=5, OS id=4508
LGWR started with pid=6, OS id=4124
CKPT started with pid=7, OS id=3684
SMON started with pid=8, OS id=3284
RECO started with pid=9, OS id=4360
CJQ0 started with pid=10, OS id=2128
MMON started with pid=11, OS id=3976
Mon Jan 10 15:21:43 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=3444
Mon Jan 10 15:21:43 2011
starting up 1 shared server(s) ...
DMON started with pid=15, OS id=4136
Mon Jan 10 15:21:43 2011
ALTER DATABASE MOUNT
Mon Jan 10 15:21:48 2011
Setting recovery target incarnation to 4
Mon Jan 10 15:21:48 2011
Successful mount of redo thread 1, with mount id 1881221383
Mon Jan 10 15:21:48 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Mon Jan 10 15:21:48 2011
ALTER DATABASE OPEN
Mon Jan 10 15:21:51 2011
Starting Data Guard Broker (DMON)
INSV started with pid=16, OS id=4264
Mon Jan 10 15:21:55 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=18, OS id=4768
Mon Jan 10 15:21:55 2011
ARC0: Archival started
Mon Jan 10 15:21:55 2011
ARC1: Archival started
ARC1 started with pid=19, OS id=5288
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 opened at log sequence 11
Current log# 3 seq# 11 mem# 0: E:\ORACLE\TST\ORIGLOGA\LOG_G13M1.DBF
Current log# 3 seq# 11 mem# 1: E:\ORACLE\TST\MIRRLOGA\LOG_G13M2.DBF
Successful open of redo thread 1
Mon Jan 10 15:21:57 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jan 10 15:21:57 2011
SMON: enabling cache recovery
Mon Jan 10 15:21:57 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Mon Jan 10 15:21:57 2011
ARC1: Becoming the heartbeat ARCH
Mon Jan 10 15:21:58 2011
Incremental checkpoint up to RBA [0xb.16b77.0], current log tail at RBA [0xb.16b77.0]
Mon Jan 10 15:21:59 2011
Successfully onlined Undo Tablespace 1.
Mon Jan 10 15:21:59 2011
SMON: enabling tx recovery
Mon Jan 10 15:21:59 2011
Database Characterset is UTF8
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 2
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=20, OS id=4156
Mon Jan 10 15:22:05 2011
Completed: ALTER DATABASE OPEN
Mon Jan 10 15:52:02 2011
Incremental checkpoint up to RBA [0xb.180ee.0], current log tail at RBA [0xb.1830a.0]
Mon Jan 10 15:52:16 2011
Shutting down instance: further logons disabled
Mon Jan 10 15:52:16 2011
Stopping background process CJQ0
Mon Jan 10 15:52:16 2011
Stopping background process QMNC
Mon Jan 10 15:52:17 2011
Background process QMNC not dead after 150 seconds
Mon Jan 10 15:52:17 2011
Stopping background process MMNL
Mon Jan 10 15:52:18 2011
Background process MMNL not dead after 10 seconds
Mon Jan 10 15:52:18 2011
Stopping background process MMON
Mon Jan 10 15:52:19 2011
Background process MMON not dead after 30 seconds
Mon Jan 10 15:52:19 2011
Shutting down instance (immediate)
License high water mark = 12
Mon Jan 10 15:52:19 2011
Stopping Job queue slave processes, flags = 7
Mon Jan 10 15:52:19 2011
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Mon Jan 10 15:52:24 2011
ALTER DATABASE CLOSE NORMAL
Mon Jan 10 15:52:24 2011
SMON: disabling tx recovery
SMON: disabling cache recovery
Mon Jan 10 15:52:25 2011
Shutting down archive processes
Archiving is disabled
Mon Jan 10 15:52:30 2011
ARCH shutting down
ARC1: Archival stopped
Mon Jan 10 15:52:35 2011
ARCH shutting down
ARC0: Archival stopped
Mon Jan 10 15:52:36 2011
Thread 1 closed at log sequence 11
Successful close of redo thread 1
Mon Jan 10 15:52:37 2011
Completed: ALTER DATABASE CLOSE NORMAL
Mon Jan 10 15:52:37 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Shutting down Data Guard Broker processes
Mon Jan 10 15:52:38 2011
Completed: Data Guard Broker shutdown
Mon Jan 10 15:52:40 2011
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Jan 10 15:53:28 2011
Starting ORACLE instance (normal)
Mon Jan 10 15:53:28 2011
Specified value of sga_max_size is too small, bumping to 645922816
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 645922816
__shared_pool_size = 318767104
shared_pool_size = 318767104
__java_pool_size = 4194304
java_pool_size = 4194304
shared_pool_reserved_size= 31598837
filesystemio_options = setall
control_files = E:\ORACLE\TST\ORIGLOGA\CNTRL\CNTLRTST.DBF, E:\ORACLE\TST\ORIGLOGB\CNTRL\CNTRLTST.DBF, F:\ORACLE\TST\SAPDATA1\CNTRL\CNTRLTST.DBF
control_file_record_keep_time= 30
db_block_size = 8192
__db_cache_size = 318767104
db_cache_size = 318767104
compatible = 10.2.0
log_archive_dest = E:\oracle\TST\oraarch\TSTarch
log_buffer = 2061312
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=TSTXDB)
job_queue_processes = 1
background_dump_dest = F:\ORACLE\TST\SAPTRACE\BACKGROUND
user_dump_dest = F:\ORACLE\TST\SAPTRACE\USERTRACE
core_dump_dest = F:\ORACLE\TST\SAPTRACE\BACKGROUND
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = TST
open_cursors = 800
optimpeek_user_binds = FALSE
pga_aggregate_target = 421317836
workarea_size_policy = AUTO
statistics_level = typical
dg_broker_start = TRUE
PMON started with pid=2, OS id=5296
PSP0 started with pid=3, OS id=4804
MMAN started with pid=4, OS id=3480
DBW0 started with pid=5, OS id=4312
LGWR started with pid=6, OS id=4036
CKPT started with pid=7, OS id=3372
SMON started with pid=8, OS id=5816
RECO started with pid=9, OS id=5240
CJQ0 started with pid=10, OS id=4524
MMON started with pid=11, OS id=6140
Mon Jan 10 15:53:28 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=5680
Mon Jan 10 15:53:28 2011
starting up 1 shared server(s) ...
DMON started with pid=15, OS id=5308
Mon Jan 10 15:53:28 2011
ALTER DATABASE MOUNT
Mon Jan 10 15:53:32 2011
Setting recovery target incarnation to 4
Mon Jan 10 15:53:33 2011
Successful mount of redo thread 1, with mount id 1881229688
Mon Jan 10 15:53:33 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Mon Jan 10 15:53:33 2011
ALTER DATABASE OPEN
Mon Jan 10 15:53:36 2011
Starting Data Guard Broker (DMON)
INSV started with pid=16, OS id=4536
Mon Jan 10 15:53:40 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=18, OS id=5552
Mon Jan 10 15:53:40 2011
ARC0: Archival started
ARC1: Archival started
ARC1 started with pid=19, OS id=5312
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 opened at log sequence 11
Current log# 3 seq# 11 mem# 0: E:\ORACLE\TST\ORIGLOGA\LOG_G13M1.DBF
Current log# 3 seq# 11 mem# 1: E:\ORACLE\TST\MIRRLOGA\LOG_G13M2.DBF
Successful open of redo thread 1
Mon Jan 10 15:53:41 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jan 10 15:53:41 2011
SMON: enabling cache recovery
Mon Jan 10 15:53:42 2011
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon Jan 10 15:53:42 2011
ARC0: Becoming the heartbeat ARCH
Mon Jan 10 15:53:43 2011
Incremental checkpoint up to RBA [0xb.18403.0], current log tail at RBA [0xb.18403.0]
Mon Jan 10 15:53:44 2011
Successfully onlined Undo Tablespace 1.
Mon Jan 10 15:53:44 2011
SMON: enabling tx recovery
Mon Jan 10 15:53:44 2011
Database Characterset is UTF8
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 2
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=20, OS id=5776
Mon Jan 10 15:53:50 2011
Completed: ALTER DATABASE OPEN
Mon Jan 10 15:55:46 2011
Starting ORACLE instance (normal)
Mon Jan 10 16:00:56 2011
Errors in file f:\oracle\tst\saptrace\background\tst_j000_3228.trc:
Mon Jan 10 16:01:26 2011
Beginning log switch checkpoint up to RBA [0xc.2.10], SCN: 16865686
Mon Jan 10 16:01:26 2011
Thread 1 advanced to log sequence 12 (LGWR switch)
Current log# 4 seq# 12 mem# 0: E:\ORACLE\TST\ORIGLOGB\LOG_G14M1.DBF
Current log# 4 seq# 12 mem# 1: E:\ORACLE\TST\MIRRLOGB\LOG_G14M2.DBF
Mon Jan 10 16:03:54 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_5396.trc:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], []
Mon Jan 10 16:04:01 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_5396.trc:
ORA-00600: internal error code, arguments: [kcbgcur_3], [61846], [9], [4], [0], [], [], []
Mon Jan 10 16:04:07 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_5396.trc:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], []
Mon Jan 10 16:06:30 2011
Completed checkpoint up to RBA [0xc.2.10], SCN: 16865686
Mon Jan 10 16:23:50 2011
Incremental checkpoint up to RBA [0xc.4e3a.0], current log tail at RBA [0xc.4f1f.0]
Mon Jan 10 16:53:57 2011
Incremental checkpoint up to RBA [0xc.55b9.0], current log tail at RBA [0xc.5726.0]
Mon Jan 10 17:00:01 2011
Errors in file f:\oracle\tst\saptrace\background\tst_j000_2516.trc:
Mon Jan 10 17:00:29 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_6048.trc:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], []
Mon Jan 10 17:00:33 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_6048.trc:
ORA-00600: internal error code, arguments: [kcbgcur_3], [61846], [9], [4], [0], [], [], []
Mon Jan 10 17:00:37 2011
Errors in file f:\oracle\tst\saptrace\background\tst_m000_6048.trc:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ], [0], [0], [1], [], [], [], []
Mon Jan 10 17:24:02 2011
Incremental checkpoint up to RBA [0xc.6125.0], current log tail at RBA [0xc.62ae.0] -
BDB core dumps after addition of 30MB data
Hi,
BDB dumps core after adding about 100000 items at regular intervals on HP-UX 64 bit environment.
Stack trace :
Program terminated with signal 6, Aborted.
#0 0xc00000000033cad0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
(gdb) bt
#0 0xc00000000033cad0:0 in kill+0x30 () from /usr/lib/hpux64/libc.so.1
#1 0xc000000000260cf0:0 in raise+0x30 () from /usr/lib/hpux64/libc.so.1
#2 0xc0000000002fe710:0 in abort+0x190 () from /usr/lib/hpux64/libc.so.1
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile db_err.o.
If NOT specified will behave as a non -g compiled binary.
#3 0xc000000038deb0f0:0 in __db_panic+0xc0 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile log_put.o.
If NOT specified will behave as a non -g compiled binary.
#4 0xc000000038e70ab0:0 in __log_flush_int+0x7e0 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
#5 0xc000000038e72d80:0 in __log_flush+0xa0 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile mp_bh.o.
If NOT specified will behave as a non -g compiled binary.
#6 0xc000000038e77fe0:0 in __memp_pgwrite+0x5f0 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
#7 0xc000000038e77460:0 in __memp_bhwrite+0x6a0 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile mp_alloc.o.
If NOT specified will behave as a non -g compiled binary.
#8 0xc000000038e76560:0 in __memp_alloc+0xb20 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile mp_fget.o.
If NOT specified will behave as a non -g compiled binary.
#9 0xc000000038e7a600:0 in __memp_fget+0xc60 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so---Type <return> to continue, or q <return> to quit---
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile bt_search.o.
If NOT specified will behave as a non -g compiled binary.
#10 0xc000000038d13720:0 in __bam_search+0x8d0 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile bt_cursor.o.
If NOT specified will behave as a non -g compiled binary.
#11 0xc000000038cf4e30:0 in __bam_c_search+0x590 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
#12 0xc000000038cf02c0:0 in __bam_c_get+0x640 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile db_cam.o.
If NOT specified will behave as a non -g compiled binary.
#13 0xc000000038de03d0:0 in __db_c_get+0x530 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile db_am.o.
If NOT specified will behave as a non -g compiled binary.
#14 0xc000000038dccf60:0 in __db_put+0x320 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile db_iface.o.
If NOT specified will behave as a non -g compiled binary.
#15 0xc000000038df37a0:0 in __db_put_pp+0x240 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
warning:
ERROR: Use the "objectdir" command to specify the search
path for objectfile cxx_db.o.
If NOT specified will behave as a non -g compiled binary.
#16 0xc000000038cbbc90:0 in Db::put(DbTxn*,Dbt*,Dbt*,unsigned int)+0x120 ()
from /integhome/jobin/B063_runEnv/service/sys/servicerun/bin/libdb_cxx-4.3.so
If some body as an idea about the cause for dump, pls reply.
Thanks,
SandhyaHi Sandhya,
This issue is already handled on your other thread:
BDB dumps core after adding approx 19MB of data
Please follow the suggestions provided there and try keeping one issue per thread when posting. The stack trace posted here is almost identical to the previous one you posted, and contains in addition only a couple of calls for memory pool file allocation and writing.
Thanks, regards,
Andrei -
JNI - core dump - internal error on linux after calling Java method
I'm getting a core dump after calling athe main statric method using JNNI.
On linux.
I can get the class id correcttly but when I attempt to call the method it craches with an internal error , anyone know why it would crash instead of just not work.
if(cls)
main_methodID = env->GetStaticMethodID(cls, "main", "([Ljava/lang/String;)V");
printf("Class Found Successfully\n");
else
printf ( "cls not found\n");
return 0;
if(main_methodID)
jstring first_str = env->NewStringUTF("The First String");//create string
jobjectArray args = (jobjectArray)env->NewObjectArray(1,env->FindClass("java/lang/String"), first_str);//new array with 2 elements
env->SetObjectArrayElement(args, 2, first_str);//insert the second string into index 1 of the array
jstring second_str = env->NewStringUTF("The Second String");//create string
env->SetObjectArrayElement(args, 1, second_str);//insert the second string into index 1 of the array
env->CallStaticVoidMethod(cls, main_methodID, args);//pass the array to the Java main method
The JAVA method is
public static void main(String[] args) {
System.out.println("Main method in Framework");
Framework framework = new Framework();
I see yere points but what I see on linux is it makes it to the constructor of the Java object and somewhere afterwards it bails out, the Java app does work alone. It appears to have problems initializing the JFrame, could there be a problem with the Java inheritance when a JVM is invoked throurgh native invocation??
Here's some of the Java stuff
public class Framework extends WindowAdapter {
public int numWindows = 0;
private Point lastLocation = null;
private int maxX = 500;
private int maxY = 500;
public Framework() {
System.out.println("JAVA Framework cnst");//GETTING HERE
makeNewWindow();
public void makeNewWindow() {
System.out.println("JAVA makeWindow"); //GETTING HERE
JFrame frame = new MyFrame(this); //NOT GETTING HERE!!!!!!!!!
numWindows++;
System.out.println("Number of windows: " + numWindows);
System.out.println("Frame location: " + lastLocation);
frame.setVisible(true);
System.out.println("Post Java set frame visible");
public static void main(String[] args) {
System.out.println("Main method in Framework");
Framework framework = new Framework();//GETTING HERE
class MyFrame extends JFrame {
protected Dimension defaultSize = new Dimension(200, 200);
protected Framework framework = null;
public MyFrame(Framework controller) {
super("New Frame");
System.out.println("MyFrame cnst ");//NOT GETTING HERE!!!!!!
framework = controller;
setDefaultCloseOperation(DISPOSE_ON_CLOSE);
addWindowListener(framework);
JMenu menu = new JMenu("Window");
menu.setMnemonic(KeyEvent.VK_W);
setSize(defaultSize);
} -
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 -
I'm having issues with the OCILogon2() API. The system is Solaris 8
running Oracle 9.0.1; the application is written in C. In normal
operation, the application functions with no issues: queries can be
made, etc, so this isn't an issue of getting it up and running; it
already works, but now a bug has been revealed.
The original thing which pointed out the problem is the fact that a
firewall in front of the Oracle database was timing out and dropping
the client connection after 60-minutes of inactivity. (Note that
the firewall problem is now a non-issue, but the error it uncovered
is a serious one, so I'd like to still find a solution to that in
case some other situation causes a similar problem.)
Eventually, the client would receive the ORA-03113 "end-of-file on
communication channel" error when calling OCILogon2() if attempting
to do a login/query after a period of inactivity because the firewall
had dropped the connection. The application is multi-threaded and is
using Connection Pooling, so if another thread attempted to login after
this error was received, the OCILogon2() API would core dump after the
initial OCILogon2() call had returned the error code.
Here is a stack trace of the exact errors (I wrote a smaller test
application which is stripped down and not multi-threaded and I
can duplicate this error at will):
--- begin stack trace ---
libclntsh.so.9.0`kpucpgetconn+0x27c(d7408, 54388, ffbef0f4, feef9804, 18, 0)
libclntsh.so.9.0`kpucpfnd+0x50(d7408, ffbef1a8, ffbef18c, ffbef0f4, 18, 0)
libclntsh.so.9.0`kpcpmap+0x94(4e28c, d7408, ffbef1a8, ffbef18c, ffbef1ac, 0)
libclntsh.so.9.0`kpuauthxa+0x720(1, 5449c, 5cea4, 1, 0, 0)
libclntsh.so.9.0`kpuauth+0x44(5d028, 5449c, 5cea4, 1, 0, fefcdb64)
libclntsh.so.9.0`kpulon2+0x37c(200, 1d, 54358, 7, 15e0, fefcdb64)
libclntsh.so.9.0`OCILogon2+0x130(200, 7, ffbef65c, 11cc8, 6, 11cd0)
--- end stack trace ---
What I'm curious about is why the OCILogon2() API does not return
an error code of some sorts whenever the connection is obviously
unavailable.
I'm not extremely knowledgeable about the OCI APIs, so is there
perhaps a way to verify the connection is active before attempting
a login call? (Whether that be OCILogon2() or OCIServerAttach(), etc.)
A 'ping' of sorts just to be sure? (Not that this would solve the
problem completely as the connection could be severed between the
ping and the login attempt.)
For other reasons, I already have a 'flag' which can be tripped to
tell the threads to not attempt Oracle queries (namely if the
environment initialization upfront failed). I could trip this flag upon
receiving an Oracle error like this, but that will not be a complete
solution to the problem due to timing issues -- another thread could be
attempting to login at the same time another thread is doing so
and before the flag can be set or checked, thus the second attempt is
going to cause a core dump, no exceptions. Or if all of the connection
pool links are currently busy, a thread could check the flag and see
that it is clear before attempting to login, so OCILogon2() is called
and the thread is now waiting for a connection to open in the pool;
the connection dies, one of the other threads throws ORA-03113
before leaving the pool and setting the flag, but now this other
"waiting" thread (who already checked the flag before trying to login)
grabs the open pool spot and immediately tries to complete its
OCILogon2() call. Core dump.
The ideal solution is, obviously, for the API to not core dump and
simply return a proper error code.
If anyone has any suggestions, I would greatly appreciate them.
If there is a workaround for this, such as being able to detect ahead
of time that the connection is down and then trying to reconnect, I'd
be interested in hearing about ways to do that as well.What if you don't have a support contract with Oracle, can you still contact them in a case like this (where I'm not asking someone to show me how to do something, but instead where it is clearly an issue with their product)?
Thanks for your reply. -
Core Dump on Solaris 10 (Signal 10 - Bus Error), but not on Solaris 8?
Hi,
We just moved our product from Solaris 8 to Solaris 10. It runs for months on Solaris 8 without any problems, while core dumped after running about 2 weeks on Solaris 10.
Any clue on what could be wrong is apprecaited.
pamHi Andrew,
Appreciate your answer very much. I am very new to Solaris and UNIX in general. Would you please let me know what kind of info would help diagnose the
problem? I have stack pointer, output of "where" from gdb. frme pointer, etc.
pam
===================
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.8"...(no debugging symbols found)
Core was generated by `./warnsrvr'.
Program terminated with signal 10, Bus error.
#0 0x001a3ca8 in __1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__ ()
(gdb) where
#0 0x001a3ca8 in __1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__ ()
#1 0x001a3ca8 in __1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__ ()
Previous frame identical to this frame (corrupt stack?)
======================================
(gdb) disassemble 0x001a3ca8
Dump of assembler code for function __1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__:
0x001a3c24 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+0>: cmp %o0, 1
0x001a3c28 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+4>: be,pn %icc, 0x1a3c38 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+20>
0x001a3c2c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+8>: sethi %hi(0x572000), %l6
0x001a3c30 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+12>: ret
0x001a3c34 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+16>: restore %g0, 0, %o0
0x001a3c38 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+20>: ld [ %l6 + 0x358 ], %l5
0x001a3c3c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+24>: cmp %l5, 0
0x001a3c40 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+28>: bne,pn %icc, 0x1a3c50 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+44>
0x001a3c44 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+32>: cmp %l5, 1
0x001a3c48 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+36>: ret
0x001a3c4c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+40>: restore %g0, 1, %o0
0x001a3c50 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+44>: bne,pn %icc, 0x1a3cb0 <__1cSWPReferenceManagerOInputIonoModel6MrknKIONO_MODEL_khki_nGRESULT__+4>
0x001a3c54 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+48>: sethi %hi(0x1a3c00), %l7
0x001a3c58 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+52>: mov -1, %i1
0x001a3c5c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+56>: sth %i1, [ %fp + -1864 ]
0x001a3c60 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+60>: add %fp, -1824, %o0
0x001a3c64 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+64>: ldd [ %l7 + 8 ], %f0
0x001a3c68 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+68>: call 0x1c87f0 <___const_seg_900001301+16>
0x001a3c6c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+72>: std %f0, [ %fp + -1856 ]
0x001a3c70 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+76>: call 0x1cf888 <__1cKIono2Ascii6FrknKIONO_MODEL_pcki_v_+100>
0x001a3c74 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+80>: add %fp, -1864, %o0
0x001a3c78 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+84>: sllx %i2, 0x30, %o1
0x001a3c7c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+88>: mov %i0, %o0
0x001a3c80 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+92>: srax %o1, 0x30, %o1
0x001a3c84 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+96>: call 0x182cb0 <__1cTGenReferenceManagerOGetCorrections6MrknKCLSGpsTime_rknICLSCoord_rnOCORRECTION_SET__nGRESULT__+3504>
0x001a3c88 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+100>: add %fp, -1864, %o2
0x001a3c8c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+104>: cmp %o0, 1
0x001a3c90 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+108>: be,pn %icc, 0x1a3ca0 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+124>
0x001a3c94 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+112>: mov %i0, %o0
0x001a3c98 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+116>: ret
0x001a3c9c <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+120>: restore %g0, 0, %o0
0x001a3ca0 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+124>: call 0x1a7068 <__1cSWPReferenceManagerPAdjustXTRATimes6MpnZCLSGnssSatellitePredictor_khrnKCLSGpsTime_rd_nGRESULT__+3584>
0x001a3ca4 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+128>: add %fp, -1864, %o1
0x001a3ca8 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+132>: ret
End of assembler dump.
=====================================
(gdb) info registers
g0 0x0 0
g1 0xfd77ecb8 -42472264
g2 0x11 17
g3 0xecf0 60656
g4 0xfd77e304 -42474748
g5 0xfc 252
g6 0x0 0
g7 0xfeda4200 -19250688
o0 0x1 1
o1 0x20 32
o2 0x693500 6894848
o3 0xecf0 60656
o4 0x6a21f0 6955504
o5 0x1 1
sp 0xfd77ec38 0xfd77ec38
o7 0x1a3ca0 1719456
l0 0x1b000021 452984865
l1 0x2ca2a40 46803520
l2 0x40173076 1075261558
l3 0x57d22e16 1473392150
l4 0x3fa80492 1067975826
l5 0x3c06fe49 1007091273
l6 0x4072b4a5 1081259173
l7 0x410d711d 1091399965
i0 0x421c0000 1109131264
i1 0xffffffff -1
i2 0x1d000018 486539288
i3 0x2ca2808 46802952
i4 0x40138e4a 1075023434
i5 0x8b122e16 -1961742826
fp 0xbfb17c3b 0xbfb17c3b
i7 0xa817f0db -1474826021
y 0x3 3
psr 0xfe401007 -29356025
wim 0x0 0
tbr 0x0 0
pc 0x1a3ca8 0x1a3ca8 <__1cSWPReferenceManagerMInputUtcInfo6MrknIUTC_INFO_khki_nGRESULT__+132>
npc 0x1a3cac 0x1a3cac <__1cSWPReferenceManagerOInputIonoModel6MrknKIONO_MODEL_khki_nGRESULT__>
fsr 0x400420 4195360
csr 0x0 0 -
Tomcat 4.0.5 and JDK 1.4.2 on HP-UX 11i giving core dump
Hi,
I am using Tomcat 4.0.5 web server for a high data volume web based project. I have changed the JDK from 1.3 to 1.4.2. The os is HP-UX 11i. After changing the JDK version, I am getting core dump after every 6 to 7 hours and Tomcat fails to continue.
Pls, tell me is it due to version mismatch or anything else.
Regards
Kousik MukherjeeHi,
If you have not already done so .. make sure that the latest patches that are required for 1.4.2 on HP-UX are installed (requires patch PHNE_29887 for HP-UX 11.11 (11i v1) PA-RISC. The patch solves socket problems that may cause hangs.) I think there may be some others as well ...
Good luck
LSH -
Setting up two machines for core dump
Hi, I'm trying to set up two Macs to collect a Core Dump after a Kernel Panic.
A MacBook Pro 3,1 triggers a kernel panic when Mavericks is installed, and either Ethernet or WiFi connections are changed. No diagnostic reports get generated at /Library/Logs/DiagnosticReports.
I have been reading on how to set up a core dump over FireWire, since Ethernet seems to be compromised. I'm able to do a core dump by triggering a kernel panic with DTrace. The Development Machine receives and stores the core dump correctly. However if a kernel panic occurs when WiFi is switched off, the Core Dump does not take place, and I don't know if it should work as the DTrace trigger does.
I have System 10.9.1 on both Target and Development machines. The machines are each other connected with a FireWire 800 cable and a ThuderBolt adapter, since Development machine lacks the FireWire port (It's a MacBook Pro retina).
- Target machine is connected to my WiFi network and is also connected to the Ethernet network. The FireWire 800 port is manually set to IP 10.0.1.127
- Development machine is connected to my WiFi network. The FireWire 800 cable coming from the Target machine connects to a ThunderBolt adapter and the port is manually set to IP 10.0.1.128
- On the Target machine (MacBook Pro 3,1) I've set
sudo nvram boot-args="debug=0xd46 _panicd_ip=10.0.1.128 kdp_match_name = firewire"
- On the Development machine (MacBook Pro retina)
sudo mkdir /PanicDumps
sudo chown root:wheel /PanicDumps
sudo chmod 1777 /PanicDumps
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.kdumpd.plist
- verified that the core dump server is working with
sudo launchctl list | grep kdump
- after connecting the FireWire cable to the Macs
run fwkdp
- and machine responds with:
FireWire KDP Tool (v1.6)
KDP Proxy and CoreDump-Receive dual mode active.
Use 'localhost' as the KDP target in gdb.
Ready.
As mentioned above, triggering a Core Dump with DTrace works just fine.
Turning WiFi Off causes a Kernel Panic, Target machine freezes immediatedly and nothing happens on Development machine.
Forcing power off on Target machine and restarting shows no logs on Console.
I've read very little on GDB and it seems hard to find information, at least on what I'm doing. I'm not trying to debug a kernel extension.
nvram -p dumps mostly jibberish on the terminal screen
I'm tempted on setting up the core dump with Ethernet, but hesitate since WiFi and Ethernet seem to block the system abruptly.
Can someone illuminate me please?
Thanks in advance and best regards,
GuidoThank you Ian, however, when I click this option, my library looses all of its preferences/user presets?? I am confused
They aren't lost, instead they have been left outside the catalog because they preceded the change.
You can drag the contents of your Lightroom presets folder into the Lightroom Settings folder within Lightroom catalog folder and the application will then see them after relaunch. This is by far the quickest and easiest way of copying existing presets to the central catalog. Follow these steps:
Step 1 - Open you original catalog
Step 2 - Open Lightroom Preferences and choose the Presets tab
Step 3 - Make sure that Store presets with catalog is unchecked
Step 4 - Hit the Show Lightroom Presets Folder... button.
The presets folder will see multiple sub-folders which contain your existing
Step 5 - Open the folder with the moved catalog (i.e. the version you put on the external disk)
Step 6 - Open the folder named Lightroom Settings
Step 7 - Delete it's contents
Step 8 - Drag the contents of the folder you opened in step 4 in to the Lightroom Settings folder that you opened in Step 6
Step 9 - Launch the moved catalog as described in my previous post (i.e. double click it)
If you did everything correctly the catalog will now have access to your presets -
Hi,
Had some problems connecting to my Wifi Network using core dump after installation. The problem was that the WPA_Supplicant was giving an ioctl [ SIOCSIWSSCAN ] error, saying resource temporarily unavailable.
All the details were correct in the wpa_supplicant and network profiles. So was rather confused, especially seeing as i had done a network install only minutes prior.
Tracked it down to a discrepancy in the driver versions used on the cd and that installed onto the system. The cd uses iwl3945 1.1.21 and the installed system 1.2.0ds.
Swapping the drivers over instantly solved the problem. This was on a Toshiba Satellite A200-1TO for reference.
Works perfectly now... Clearly
Just thought i'd mention this incase anyone has/or has had similar problems with the intel 3945 wireless adaptor. Was also wondering if anyone has a fix for this, as it'd surely be better to be using the later driver?Might be worth filing a bug report with the intel wireless devs, the ds part sounds like a beta or something.
-
High uptime (~2 years) Solaris 10 update 4 data ingest system just brought up to current patch level (~300 patches). Now, "format" command core dumps after selecting any disk unless NOINUSE_CHECK=1 is set. Call trace ends with the following -- any ideas?
1831/1: getmsg(7, 0x08045E10, 0x08045E1C, 0x08045E30) = 0
1831/1: getgroups(0, 0x00000000) = 11
1831/1: sysinfo(SI_HOSTNAME, "xxx.xxx.xxx.xxx", 255) = 24
1831/1: getuid() = 0 [0]
1831/1: getgid() = 0 [0]
1831/1: getgroups(11, 0x08045FD0) = 11
1831/1: Incurred fault #6, FLTBOUNDS %pc = 0xC4D961E1
1831/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x00756465
1831/1: Received signal #11, SIGSEGV [default]
1831/1: siginfo: SIGSEGV SEGV_MAPERR addr=0x00756465
It's clear we have a workaround, but anyone have an idea what's at the heart of the problem?After applying the most current recommended patch cluster it seems that patch 145900-06 causes format to dump core. Since this is an older patch (listed in MOS as 7 weeks old) I assume this is the result of a combination of patches (maybe the update 10 patch 144501-19?). I am still working with Oracle support to get this fixed. Stay tuned.
-
Why Mac Mountain Lion cannot use gdb to analzy kernel core dump??
I'm trying to use gdb debug a Core Dump after a Kernel Panic which I collected from two Macs,but when i use list command below i get some errs:
then get "can't find symblos for ****Hi Linc Davis:
thanks for your replay!
And could you tell me which "debug kernel available" shall i need to run,because i have seached all of Apple Developer site but found nothing useful infomation to be set?!
Below are the steps how i get Mac Mountain Lion(10.8.3 Build:12D78) kernel core dump from Apple Developer site:
1、Configuring the Server:
1)Creating the core dump directory:
server$ sudo mkdir /PanicDumps
Password:********
server$ sudo chown root:wheel /PanicDumps
server$ sudo chmod 1777 /PanicDumps
2)Activating the core dump server
server$ sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.kdumpd.plist
Password:********
3)Verifying the core dump server is active
server$ sudo launchctl list | grep kdump
Password:********
- 0 com.apple.kdumpd
2、Configuring a Client
client$ sudo nvram boot-args="debug=0xd44 _panicd_ip=10.***.***.***" (10.***.***.***
Password: ********
when i got client pc core dump,and use gdb analyze it ,i got some errs,eg,
/Volumes/KernelDebugKit?kgmacros:342:Error in sourced command file:
cannot access memory at address 0xffffff8000200004 -
Getting "Baseband Core dump in progress" and after that 3G doesn't work
My iPhone 4 told me several times that there is a Baseband Core dump in progress. After that my 3G connection doesn't work anymore. Only a reboot of the iPhone solves the damaged connection.
This behavior is going to make me angry. Can someone tell me how to solve this issue?
P.S: I'm not using any beta iOS Version.It's basically dumping a bunch of information from memory about the current state of the kernel and what not, so that it has a detailed error report to send to Apple. This data is uploaded to Apple when you sync with iTunes. Essentially an execution path of "core code". This is behavior typical of beta software, yet you state you're not running beta software on your phone...are you positive? If not, I've seen this with jailbroken phones.
Maybe you are looking for
-
ICC profiles for Epson R1800 and Lightroom - Mac Osx
Without trying to inflame an already heated discussion on prints that are too dark under my lightroom - printer - Mac Osx configuration. (Although I too am a sufferer of the darkness...!) I have recently downloaded the latest ICC profiles for the R18
-
Greetings, Perhaps someone can help me. I'm transcribing some of my written scores into logic. I have a score window open with the step input keyboard visible. I have assigned the number keys to pick the note values to mimic Sibelius and have keystro
-
NeST -stoppasswordserver -- how to restart?
How do we restart the passwordserver following a "NeST -stoppasswordserver"? We can't log in. We can't start passwordserver in single user mode. Anyone have any ideas on how to resurrect this machine?
-
Debit/credit not showing correctly
Dear All, I am making a report in which i have to show debit and credit of Actual General Ledger. I am using table FAGLFLEXA-TSL for showing debit and credit . Here I have to put debit in one column and credit in another column. So I wrote the code -
-
Balky, frozen mouse and keyboard
Since installing OS 10.4.6, my USB keyboard and mouse quickly bog down, coming to a halt altogether. The mouse starts out as responsive as usual, but soon stops tracking adequately. The feel is as if the mouse is "bogged down" with too many instructi