Modify

Opened 6 years ago

Closed 6 years ago

Last modified 11 months ago

#2795 closed defect (fixed)

Pasted an email body which resulted in a ticket that was not viewable

Reported by: flakrat Owned by: pacopablo
Priority: normal Component: EmailProcessorMacro
Severity: normal Keywords:
Cc: mhanby@… Trac Release: 0.10

Description

I pasted an email (from MS Outlook) as a new comment on an existing ticket, I didn't press preview and went straight to Submit Change. The result was the error below whenever I attempted to view the ticket:

Oops…
Trac detected an internal error:

If you think this really should work and you can reproduce it, you should consider reporting this problem to the Trac team.

Go to http://trac.edgewall.org/ and create a new ticket where you describe the problem, how to reproduce it. Don't forget to include the Python traceback found below.

TracGuide — The Trac User and Administration Guide
Python Traceback

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 244, in dispatch
    req.display(template, content_type or 'text/html')
  File "/usr/lib/python2.3/site-packages/trac/web/api.py", line 358, in display
    data = self.hdf.render(template, form_token)
  File "/usr/lib/python2.3/site-packages/trac/web/clearsilver.py", line 296, in render
    injector.feed(template.render())
  File "/usr/lib64/python2.3/HTMLParser.py", line 108, in feed
    self.goahead(0)
  File "/usr/lib64/python2.3/HTMLParser.py", line 150, in goahead
    k = self.parse_endtag(i)
  File "/usr/lib64/python2.3/HTMLParser.py", line 327, in parse_endtag
    self.error("bad end tag: %s" % `rawdata[i:j]`)
  File "/usr/lib64/python2.3/HTMLParser.py", line 115, in error
    raise HTMLParseError(message, self.getpos())
HTMLParseError: bad end tag: '</Debug\n\narrayPrintSummary\nvdAll cfgUnit\nvdAll vdShow\nspmShow\nexcLogShow --- run this if your at firmware 6.1.xx -- otherwise it will\nnot produce any output ( This is the FA logs)\navtShow 1\nsvlShow 1\navtHostShow\ncfgUnitList\nmoduleList\ncfgPhyList\nghsList\nfcDevs 2\nfcDevs 4\nfcDevs 11\ngetObjectGraph_MT 8\nfcAll\nfc 10\nshowEnclosures\nfc 111\nhdd 5\nnetCfgShow\nmemShow (for a fastt 600 need to use -- memoryShow )\n\nThe following commands should be run when done collecting shell output:\n\nunld "Debug"\nexit\n\n(See attached file: putty.exerename)...........................\nHere is the putty program used for rlogin. You need to rename it to\nputty.exe (if needed)\n\n( If this is for an IBM CE the following list Part numbers of cables)\nthat may be needed)\nLaptop to rack power adapter cable .....45p5834\nEthernet Cross over cable 25\' ..................39X8924\n10\' ..................45P5860\nEthernet Straight Through 10\' ..................45P5861\nCommunication Kit ..................62H4857\n1 4 headed data set eliminator cable\n1 9 pin serial cable male / female\n1 9 pin female gender binder\nserial cable for  3542  (FAStT 200)   is p/n19K1179\n\n_________________________________________\nDASD Field Support Center\nIBM Global Services, Integrated Technology Services.\nNotes = DASD Field Support Center/Atlanta/Contr/ibm@ibmus\ninternet = dasdsupt@us.ibm.com\nhttp://www.ibm.com/servers/storage/support/disk/\n"This Mailbox is not monitored, please do not reply"</pre>', at line 415, column 4

I was able to recover the ticket by replacing the comment with an empty string

sqlite3 trac.db 'update ticket_change set newvalue="" where ticket=71 and field="comment" and oldvalue="9";'

This is the text that I attempted to wrap in the email block

{{{
#!email
Collecting Shell Commands (Non-Code Specific) 




NOTE: THESE COMMANDS NEED TO BE RUN ON BOTH CONTROLLERS AND OUTPUT SAVED IN SEPARATE FILES 
Please send files to dasdsupt@us.ibm.com

ITEMS NEEDED: 
1-Null-Modem Cable (This is a Serial Crossover Cable) 
2-Server, workstation, or laptop installed with Windows 95, 98, 2000, 

How to connect to the FAStT and capture output using PuTTY from Windows:

1) Launch PuTTY.exe
2) Type in the Controller IP address
3) Select the "Rlogin" protocol
4) Under Category: click "Logging"
5) Select "Log all session output"
6) Click the "Browse" button and navigate to a directory where you can e-mail from
7) Type the file name to include the controller you are connecting to. 
i.e. ctrl_A_shell_output.log
8) Click Save
9) Click Open

---------------------------------------------------------------------------------
How to connect to the FAStT and capture output using HyperTerminal:

Hyper Terminal Session Parameters:

1-COM Port = COM1
2-Baud Rate = 9600 or higher
3-Data Bits = 8
4-Stop Bits = 1
5-Parity = None
6-Flow Control = Xon/Xoff

1) Connect the appropriate serial cable to com port
2) Launch HyperTerminal in W2K it is located at:
-->Start-->Programs-->Accessories-->Communications-->HyperTerminal
3) In the Connection Description type FAStT
4) In the Connect To select the COM port that you are connected to. i.e. COM1
5) COM# Properties should be: 
Speed: 9600 or higher - default is 38400 (if doing firmware load select 115200)
Data bits: 8
Parity: None
Stop bits: 1
Flow control: Xon / Xoff
6) Select Transfer
7) Select Capture Text
8) Click the "Browse" button and navigate to a directory where you can e-mail from
9) Type the file name to include the controller you are connecting to. 
i.e. ctrl_A_shell_output.log
10) Click Save
11) Click Start

Note: HyperTerm will remember the file name of the capture file but will not automatically start capturing, so make sure that you redo steps 6-11 when you connect to the second controller.

---------------------------------------------------------------------------------
How to connect to the FAStT and capture output using RLOGIN on AIX:

1) Logon to the AIX box and get to a command prompt.
2) Issue the following command to start a script log that can later be downloaded and saved: script -a /tmp/fast_shellcmds_ctrlA.txt
3) Type rlogin ##.##.##.## --> where ## is the IP address of controller A
4) Enter password to get into the shell. Default password = infiniti -- older systems password = password
5) Issue all of the PD commands required
6) Type exit (this should take you out of the FAStT shell and back to the AIX console)
7) Type exit (this is to close the script log and save the file)
8) Issue the following command to start a script log that can later be downloaded and saved: script -a /tmp/fast_shellcmds_ctrlB.txt
9) Type rlogin ##.##.##.## --> where ## is the IP address of controller B
10) Enter password to get into the shell. Default password = infiniti -- older systems password = password
11) Issue all of the PD commands required
12) Type exit (this should take you out of the FAStT shell and back to the AIX console)
13) Type exit (this is to close the script log and save the file)


Initial Shell Access Procedure:

1-Press Ctrl+Break 3 time consecutively.

2-When you see "Press Space Bar Within 5 Seconds To Set Baudrate," press the Space Bar. 
Wait till you see that the Baudrate reports being set before going to step 3.

3-Press Ctrl+Break once.

4-When you see "Press Space Bar Within 5 Seconds To Set Baudrate, or Press ESC To Exit To Shell", press ESC.

5-You should see a login prompt. Key in the following password:

For 3526 , 3552 ,1742 ,3542 Fibre Controllers password is = "infiniti"



...........................


When a call is sent to next level for support the output of these commands should be run first and checked for failures before sending it up.  If you need assistance with decoding the output please let me know. 

Load This Command First 

ld </Debug

arrayPrintSummary 
vdAll cfgUnit 
vdAll vdShow 
spmShow 
excLogShow --- run this if your at firmware 6.1.xx -- otherwise it will not produce any output ( This is the FA logs)
avtShow 1
svlShow 1
avtHostShow 
cfgUnitList 
moduleList 
cfgPhyList 
ghsList 
fcDevs 2 
fcDevs 4
fcDevs 11 
getObjectGraph_MT 8 
fcAll
fc 10 
showEnclosures
fc 111
hdd 5
netCfgShow
memShow (for a fastt 600 need to use -- memoryShow )

The following commands should be run when done collecting shell output:

unld "Debug"
exit



(See attached file: putty.exerename)...........................
Here is the putty program used for rlogin. You need to rename it to putty.exe (if needed)


( If this is for an IBM CE the following list Part numbers of cables)
that may be needed)
Laptop to rack power adapter cable .....45p5834
Ethernet Cross over cable 25' ..................39X8924
10' ..................45P5860
Ethernet Straight Through 10' ..................45P5861
Communication Kit ..................62H4857
1 4 headed data set eliminator cable
1 9 pin serial cable male / female
1 9 pin female gender binder
serial cable for  3542  (FAStT 200)   is p/n19K1179   




_________________________________________
DASD Field Support Center
IBM Global Services, Integrated Technology Services.
Notes = DASD Field Support Center/Atlanta/Contr/ibm@ibmus
internet = dasdsupt@us.ibm.com
http://www.ibm.com/servers/storage/support/disk/
"This Mailbox is not monitored, please do not reply" 

}}}

Attachments (0)

Change History (2)

comment:1 Changed 6 years ago by pacopablo

  • Resolution set to fixed
  • Status changed from new to closed

(In [3716])
Added call to trac.html.escape for text of email in 0.10 version.
Closes #2795

comment:2 Changed 6 years ago by flakrat

Howdy, I just wanted to confirm that I have tested the latest version of emailprocessormacro and it did resolve the issue.

Thanks for the fix

Add Comment

Modify Ticket

Action
as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from pacopablo. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.