01-09-2006
"Bad trap" usually means that kernel tried something impossible. Usually it is dereferencing a bad pointer. It could be hardware, but my first guess would be a kernel bug, most likely in some driver. However, that "cmd: sched" makes me suspect the scheduler in this case. Really, I would call place a service call with Sun for something like this. If that is not possible, I would make sure that I have the last patch cluster for the os. Did you recently add some hardware to your box? If so, check for patches to the driver it uses. Also there is prtdiag -v which might yield some clues.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
HELP is urgently required,
I run on SCO Unix 3 and this is the panic message that I get every time that I reboot 10U
k_trap - kernel mode trap type 0x0000000E
I have checked the swap already having the following results:
#swap -l
path dev swaplo blocks free... (3 Replies)
Discussion started by: alex_slb
3 Replies
2. UNIX for Dummies Questions & Answers
I have a system that upon boot, will declare a bad trap and reboot, whereupon it encounters the same bad trap and reboots in an endless cycle until I stop it. I can get to the ok prompt. An attempt to boot in single user mode left the box completely hung and required a power cycle to re-establish... (3 Replies)
Discussion started by: forbin24
3 Replies
3. UNIX for Dummies Questions & Answers
im ultra new at unix and was wondering if its possible to create aliases of the write command that send messeges to users using an ip address. i was thinking to use the '|awk' with the command finger but as i've said im a total newbie. thanks a lot in advance. (2 Replies)
Discussion started by: swag:þ
2 Replies
4. AIX
I am trying to map the information from the gensyms command, Its gives information about the various symbols info like symbol type, addr offset, and the main libraries addr starting point. My problem is , how do I map this 32 bit addr to a 64 bit addr, I am trying to extract Segment # information... (0 Replies)
Discussion started by: mrmeswani
0 Replies
5. Solaris
One of our Sun E450 machines crashed and has this message in the /var/adm/messages after it rebooted automatically. An extract of the log is below. I suspect it is memory, but I am not sure. Can anyone give me any ideas how to diagnose this correctly?
Thanks
Margaret Floyd
Apr 10 08:18:54... (1 Reply)
Discussion started by: floydm
1 Replies
6. Shell Programming and Scripting
Hi folks,
I have tried to add some trap detection in the below script....this script is used to monitor database activities...in a rather awkward way :rolleyes:....
The idea behind adding trap is that....this script creates lots of temporary files in the running folder to store the count... (1 Reply)
Discussion started by: frozensmilz
1 Replies
7. SCO
Hi, i'm another question:
I'm a directory /usr/data on my server sco unix 5.0.5:
# du /usr/data
4386948 /usr/data
I'm tried to connect to ftp directory /usr/data to this server and:
PANIC: k_trap - Kernel mode trap type 0x0000000E
Cannot dump 262040 pages to dumpdev hd(1/41):space... (3 Replies)
Discussion started by: sebpes
3 Replies
8. IP Networking
Hi All,
I know that getaddrinfo() return the multiple IP addresses (if present) for a hostname. But, I want to know how to get the TTL value for this list from DNS. I want to get this TTL value and cache this IP address list for that much time and then again go for DNS resolution if TTL expires.
... (2 Replies)
Discussion started by: softindia
2 Replies
9. Shell Programming and Scripting
In my Bash script I have an exit/cleanup function in a trap statement like:
trap exitCleanup 1 2 3 6 15 25
Is there anyway to capture which signal # has occurred to record in a log file. Please note I am trying to avoid something like:
trap 'mySignal=1; exitCleanup' 1
trap... (1 Reply)
Discussion started by: ckmehta
1 Replies
10. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
That is the last reply I received from my instructor, and I'm looking for some alternatives.
When using... (2 Replies)
Discussion started by: newuser45
2 Replies
LEARN ABOUT OPENSOLARIS
sunw.derby
SUNW.derby(5) Sun Cluster Miscellaneous SUNW.derby(5)
NAME
SUNW.derby, derby - resource type implementation of the Java DB database
DESCRIPTION
SUNW.derby is the failover resource type that enables you to use the Java DB database with Sun Cluster. The Java DB database is based on
the Derby database. For information about the database, see http://db.apache.org/derby/.
The extension properties associated with the SUNW.derby resource type are as follows:
Child_mon_level(integer)
Provides control over the processes that are monitored through the process monitor facility. This property denotes the level to which
the forked children processes are monitored. Omitting this property or setting this property to the default value is the same as omit-
ting the -C option for pmfadm(1M) (all children and their descendents are monitored).
Category Optional
Default -1
Tunable At creation
DB_path(string)
Specifies the location of the data file for the Java DB database.
The value for DB_path is a string specifying PATH. The specified path should be a path controlled by your chosen storage, for example
HAStoragePlus.
Category Mandatory
Default -1
Tunable At creation
DB_port(integer)
Specifies the port for the Java DB database.
Category Mandatory
Default 1527
Tunable At creation
DB_probe_port(integer)
Specifies the port that Sun Cluster uses to test the health of the server for the Java DB database.
Category Mandatory
Default 1528
Tunable At creation
Monitor_retry_count(integer)
Controls fault-monitor restarts. The property indicates the number of times that the process monitor facility restarts the fault moni-
tor. The property corresponds to the -n option passed to the pmfadm(1M) command. The Resource Group Manager (RGM) counts the number of
restarts in a specified time window (see Monitor_retry_interval). Note that Monitor_retry_count refers to the restarts of the fault
monitor itself, not of the SUNW.derby resource.
Category Optional
Default 2
Tunable Anytime
Monitor_retry_interval(integer)
Indicates the time window in minutes during which the RGM counts fault-monitor failures. The property corresponds to the -t option
passed to the pmfadm(1M) command. If the number of times that the fault monitor fails exceeds the value of the extension property Mon-
itor_retry_count, the process monitor facility does not restart the fault monitor.
Category Optional
Default 2 minutes
Tunable Anytime
Probe_timeout(integer)
Specifies the timeout value, in seconds, for the probe command.
Category Optional
Default 30 seconds
Tunable Anytime
SEE ALSO
pmfadm(1M)
Sun Cluster 3.2 12 Nov 2005 SUNW.derby(5)