XML page cannot be displayed error

Post Reply
robert.vreeland
Posts: 12
Joined: Thu Mar 29, 2007 1:39 pm

XML page cannot be displayed error

Post by robert.vreeland »

I've had a few users report the following error when using the search engine on our site:
---
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

End element was missing the character '>'. Error processing resource 'http://search.replacements.com/xsl/PRrplimg.xsl'. Li...
<xsl:attribute name="SELECTED">SELECTED</x
---
I checked the XSL file and the element named in the message really is closed. It looks like maybe the browser isn't getting all of the XSL from the appliance.

The users report that they can rerun the same query and it will work, so the problem does not happen very often and is hard to duplicate. I'd say it happens on no more than 1% of searches.

Could the size of my XSL file be the problem? It's about 1050 lines.

Thanks,
Rob
User avatar
mark
Site Admin
Posts: 5513
Joined: Tue Apr 25, 2000 6:56 pm

XML page cannot be displayed error

Post by mark »

That size shouldn't be a problem. Does the page take a long time to load when that happens? Much longer than usual?
Is there anything in the error log or vortex log for the timeframe of that error?
You could try adding "dropXSL=html" to your url so that the rendering always occurs on the appliance instead of in the users browser.
robert.vreeland
Posts: 12
Joined: Thu Mar 29, 2007 1:39 pm

XML page cannot be displayed error

Post by robert.vreeland »

The users haven't reported any noticeable delay, but it's hard to say for sure since I haven't been able to duplicate the problem myself.

I pulled the entries from the error and vortex logs around the time of the last occurrence - does anything below stick out as an obvious problem?:

=====
FROM ERROR LOG:
Sat Aug 18 13:59:46 2007] (12973) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:55:42 2007] (12311) write(): Connection reset by peer
[Sat Aug 18 13:52:43 2007] (11812) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:51:57 2007] (11671) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:51:16 2007] (11583) write(): Connection reset by peer
[Sat Aug 18 13:51:05 2007] (11569) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:49:39 2007] (11252) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:48:38 2007] (11101) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:47:59 2007] (10948) write(): Connection reset by peer
[Sat Aug 18 13:47:50 2007] (10926) Remote connection 24.192.93.68 reset during file transfer
[Sat Aug 18 13:45:47 2007] (10556) cannot find file MSOffice/cltreq.asp: No such file or directory
[Sat Aug 18 13:45:46 2007] (10553) cannot find file _vti_bin/owssvr.dll: No such file or directory
[Sat Aug 18 13:42:01 2007] (9977) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:41:44 2007] (9883) Remote connection 71.113.112.216 reset during file transfer
[Sat Aug 18 13:41:43 2007] (9877) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:41:43 2007] (9878) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:41:19 2007] (9806) write(): Connection reset by peer
[Sat Aug 18 13:36:52 2007] (8105) 68.238.4.161 connection timed out
[Sat Aug 18 13:34:50 2007] (8517) write(): Connection reset by peer
[Sat Aug 18 13:32:06 2007] (8180) sub-process exiting due to SIGBUS (signal 7)
[Sat Aug 18 13:27:25 2007] (7442) write(): Connection reset by peer
[Sat Aug 18 13:23:34 2007] (6741) 005 Cannot read from 72.64.37.19:3041: Connection reset by peer in the function htbuf_read
[Sat Aug 18 13:21:18 2007] (6350) Unparsable If-Modified-Since time from 74.166.66.157: `Mozilla/4.0 (compatible; Windows XP 5.1)'

FROM VORTEX LOG:
006 2007-08-18 13:59:52 /search:2610: (12984) Stdout error to 98.194.229.107: Connection reset by peer; exiting
006 2007-08-18 13:59:24 /search:902: (12943) Stdout error to 24.41.60.15: Connection reset/closed?; exiting
006 2007-08-18 13:58:18 (12770) Can't write stdout: Connection reset by peer; exiting
000 2007-08-18 13:58:02 /search:4555: (12683) Terminated (signal 15)
000 2007-08-18 13:58:01 /search:4555: (12673) Terminated (signal 15)
006 2007-08-18 13:57:23 (12615) Stdout error to 63.99.4.26: Connection reset by peer; exiting
006 2007-08-18 13:56:59 /search:4555: (12492) Stdout error to 68.58.125.33: Connection reset/closed?; exiting
006 2007-08-18 13:56:19 (12230) Can't write stdout: Connection reset by peer; exiting
006 2007-08-18 13:56:13 /search:2934: (12431) Stdout error to 209.232.199.32: Connection reset/closed?; exiting
006 2007-08-18 13:55:36 (12297) Can't write stdout: Connection reset by peer; exiting
000 2007-08-18 13:53:14 /usr/local/morph3/texis/scripts/dowalk:2389: SQLPrepare() failed with -1 in the function prepntexis
100 2007-08-18 13:53:14 /usr/local/morph3/texis/scripts/dowalk:2389: Index /usr/local/morph3/texis/rpl.4303763c3/db1/xh_TiDsKyMtBy_ViMoDpPp appears to be being updated
000 2007-08-18 13:53:09 /search:3367: (11930) Terminated (signal 15)
006 2007-08-18 13:52:05 (11689) Can't write stdout: Connection reset by peer; exiting
006 2007-08-18 13:51:46 /search:4491: (11634) Stdout error to 71.210.133.179: Connection reset/closed?; exiting
006 2007-08-18 13:51:23 (11603) Can't write stdout: Connection reset by peer; exiting
000 2007-08-18 13:46:12 /search:3367: (10661) Terminated (signal 15)
000 2007-08-18 13:46:10 /search:3367: (10655) Terminated (signal 15)
000 2007-08-18 13:45:16 /search:3367: (10500) Terminated (signal 15)
000 2007-08-18 13:40:52 /search:3367: Timeout
006 2007-08-18 13:40:22 /search:3367: (9618) Stdout error to 207.200.116.67: Connection reset/closed?; exiting
000 2007-08-18 13:39:44 /search:1374: (9476) Terminated (signal 15)
006 2007-08-18 13:38:03 (9197) Can't write stdout: Connection reset by peer; exiting
000 2007-08-18 13:34:05 /search:663: (8473) Terminated (signal 15)
006 2007-08-18 13:33:04 (8332) Can't write stdout: Connection reset by peer; exiting
006 2007-08-18 13:32:44 (8238) Can't write stdout: Broken pipe; exiting
006 2007-08-18 13:32:29 (8210) Can't write stdout: Connection reset by peer; exiting
006 2007-08-18 13:32:04 (8178) Can't write stdout: Connection reset by peer; exiting
006 2007-08-18 13:28:35 (7600) Can't write stdout: Connection reset by peer; exiting
006 2007-08-18 13:28:00 /search:3367: (7480) Stdout error to 66.227.161.88: Connection reset/closed?; exiting
=====
User avatar
mark
Site Admin
Posts: 5513
Joined: Tue Apr 25, 2000 6:56 pm

XML page cannot be displayed error

Post by mark »

Those logs seem to indicate a lot of cases of the user hitting stop or such in the browser and some more mysterious terminations but it's hard to say if any are related to the reported problem without a tighter time frame.
Post Reply