Dell PowerVault 56F Dell PowerVault 51F 8-Port Fibre Channel Switch Insta - Page 146

A-2., MQ-QWRITE Error Example, Table A-3., Commands to Gather MQ-QWRITE, Error Information

Get Dell PowerVault 56F PDF manuals and user guides View all Dell PowerVault 56F manuals
Add to My Manuals
Save this manual to your list of manuals

Page 146 highlights

Dell_FC_Switch# 0x103fce60 (tTimers): Oct 14 11:07:43 Error MQ-QWRITE, 1, mqWrite failed, queue = 0x103d1d20, msg = 0x103fd3d0, errno = 0x3d0002 Traceback: _mqWrite+0x44 (0x10065864) _mPathAllShow+0x1158 (0x10078498) Figure A-2. MQ-QWRITE Error Example The most notable parameters are: • The ID of the task that attempted to send the message (tTimers in Figure A-2) • The queue ID (0x103d1d20 in Figure A-2) • The message pointer (0x103fd3d0 in Figure A-2) The following commands should be executed, and their output, together with the complete message log should be used when analyzing the error. NOTE: Some of these commands can only be run from the root account. Table A-3 describes MQ-QWRITE commands for gathering errors. Table A-3. Commands to Gather MQ-QWRITE Error Information Command Description i Lists all the current tasks in the system. Most tasks should be in "READY" or "PEND" state. If any task is in "SUSPEND" state, then a task trace of that task should be run using the tt command. tt Shows the stack trace of the task. show Shows information about the queue that overflowed. d ,2,4 Shows the content of the message. fspfShow Shows FSPF task's queue ID. portSemShow Shows tasks waiting on port semaphores. spy 5 Shows per-task microprocessor utilization. This command displays a report every five seconds. At least two reports should be printed, since the first one will indicate that all the microprocessor is used by the shell. A-8 Installation and Troubleshooting Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
A-8
Installation and Troubleshooting Guide
Figure A-2.
MQ-QWRITE Error Example
The most notable parameters are:
•
The ID of the task that attempted to send the message (
tTimers
in Figure A-2)
•
The queue ID (
0x103d1d20
in Figure A-2)
•
The message pointer (
0x103fd3d0
in Figure A-2)
The following commands should be executed, and their output, together with the
complete message log should be used when analyzing the error.
NOTE: Some of these commands can only be run from the root account.
Table A-3 describes MQ-QWRITE commands for gathering errors.
Dell_FC_Switch# 0x103fce60 (tTimers): Oct 14 11:07:43
Error MQ-QWRITE, 1, mqWrite failed,
queue = 0x103d1d20, msg = 0x103fd3d0,
errno = 0x3d0002
Traceback:
_mqWrite+0x44 (0x10065864)
_mPathAllShow+0x1158 (0x10078498)
Table A-3.
Commands to Gather MQ-QWRITE
Error Information
Command
Description
i
Lists all the current tasks in the system. Most tasks
should be in "READY" or "PEND" state. If any task is in
"SUSPEND" state, then a task trace of that task
should be run using the
tt
command.
tt <task name>
Shows the stack trace of the task.
show <queue ID>
Shows information about the queue that overflowed.
d <msg
pointer>,2,4
Shows the content of the message.
fspfShow
Shows FSPF task’s queue ID.
portSemShow
Shows tasks waiting on port semaphores.
spy 5
Shows per-task microprocessor utilization. This com-
mand displays a report every five seconds. At least
two reports should be printed, since the first one will
indicate that all the microprocessor is used by the
shell.