Home → General →

Broken link report issues

• Edit

Thane Webb

07 Jun, 2016 08:29 PM

In the last several days a large number of links from the same site have started to appear in our broken link report and display as broken when submitting pages that include links to the site but none of them are broken. The reason for them appearing as broken is listed as (Response header too large). These pages are from our Catalog site which hasn't changed as far as I am aware of other than general content. Any thoughts on why all of the sudden the broken link report would be flagging this? Below is a link to an example page from our catalog. Also attached is a screenshot of a page containing numerous links to this site that show as broken in the link check.

http://aaunk.unk.edu/catalogs/current/crs/crsitec.asp#ITEC110

My first thought was that the catalog site had some sort of issue around 3:00 am when the broken link report ran but this has happened back to back days and every time a page is submitted that contains links to the catalog the links shows as broken in the link check.

• Screen_Shot_2016-06-07_at_3.23.06_PM.png 437 KB

1. Support Staff 1 Posted by Tim on 08 Jun, 2016 01:53 PM

   

   Hi Thane,

   Thanks for providing that screen shot. I copied a handful of these links into a local instance here and they aren't causing any problems, so I'm beginning to wonder if it might be related to the application server on your end. When you have a moment, can you take 3 or 4 of those links appearing in that list and see if you can curl them from the machine on which Cascade is running? For example:

   > curl -i aaunk.unk.edu/catalogs/current/crs/crsitec.asp#ITEC110
   

   If you're on a Windows machine, you won't have curl available to you by default. You could instead verify that you are able to do the following:

   • Open a web browser and browse directly to each URL without any errors
   • Open Windows Powershell and run a command similar to this, for example:

     Invoke-WebRequest aaunk.unk.edu/catalogs/current/crs/crsitec.asp#ITEC110 -OutFile c:\temp\itec110-test.txt
     

     After running this command, make sure that the temporary file generated contains the contents of that web page.

   Let me know what you find and we can go from there.

   Thanks

   • Edit

2. 2 Posted by Thane M. Webb on 08 Jun, 2016 02:36 PM

   

   I had Dylan Evans our IT person do what you asked and he said there were no issues going to those links. I sent him some more info and he is going to do more investigation.

   Thane Webb | Web services Coordinator

   Communications & Marketing
   308-865-8133 | [email blocked] | 1910 University Drive | Kearney, NE 68849

   • Edit

3. Support Staff 3 Posted by Tim on 08 Jun, 2016 02:46 PM

   

   Thanks for the update. While we're waiting to hear back from your IT folks, can you let me know what your External Link Check Timeout value is set to under System Menu -> Preferences -> General? I seem to recall one instance in the past where this message was being returned even though the actual problem was due to the link taking too long to respond. I'm just curious to see what value you all are currently using for this setting to see if that might be related.

   • Edit

4. 4 Posted by Thane M. Webb on 08 Jun, 2016 02:57 PM

   

   10000 milliseconds

   Thane Webb | Web services Coordinator

   Communications & Marketing
   308-865-8133 | [email blocked] | 1910 University Drive | Kearney, NE 68849

   • Edit

5. Support Staff 5 Posted by Tim on 08 Jun, 2016 03:01 PM

   

   Thanks. OK, that's more than enough time (at least it should be) so we can probably rule that out unless there is a good bit of network latency over there. Let me know after you hear back from IT and we can certainly investigate further.

   • Edit

6. 6 Posted by Thane M. Webb on 08 Jun, 2016 04:56 PM

   

   According to Dylan the links are working fine from the app server and web server. There are no latency issues and the links are loading in 1ms or less.

   Thane Webb | Web services Coordinator

   Communications & Marketing
   308-865-8133 | [email blocked] | 1910 University Drive | Kearney, NE 68849

   • Edit

7. Support Staff 7 Posted by Tim on 08 Jun, 2016 05:33 PM

   

   Can you confirm that this is still happening at the moment by editing/submitting the Page that you included a screen shot of in your initial description?

   I'll see if there is some additional logging we might be able to have you add to your instance to provide us with more clues.

   • Edit

8. Support Staff 8 Posted by Tim on 08 Jun, 2016 05:46 PM

   

   Hey Thane,

   I should have asked earlier, but can you tell me which version of the software you're running? I'm beginning to wonder if the total number of links on this page might be contributing to this behavior.

   • Edit

9. 9 Posted by Thane M. Webb on 08 Jun, 2016 06:29 PM

   

   We are running 7.14.2

   Thane Webb | Web services Coordinator

   Communications & Marketing
   308-865-8133 | [email blocked] | 1910 University Drive | Kearney, NE 68849

   • Edit

10. Support Staff 10 Posted by Tim on 08 Jun, 2016 06:43 PM

    

    Thanks, Thane. When you have a chance, let's go ahead and have you do the following:

    • Reproduce the issue (by editing/submitting the Page in your screen shot with the broken link check enabled).
    • Immediately attach your latest cascade.log file.
    • Edit

11. 11 Posted by Thane M. Webb on 09 Jun, 2016 07:43 PM

    

    Log file attached.

    Thane Webb | Web services Coordinator

    Communications & Marketing
    308-865-8133 | [email blocked] | 1910 University Drive | Kearney, NE 68849

    • cascade.log 51 KB
    • Edit

12. Support Staff 12 Posted by Tim on 10 Jun, 2016 05:53 PM

    

    Hi Thane,

    Unfortunately it doesn't look like that provided us with any useful logging. When you have a moment, let's try this:

    • Enable DEBUG logging for this class:

      com.hannonhill.cascade.model.link
      

    • Immediately edit/submit the Page in your screen shot (with the broken links check turned on) to replicate those link error messages
    • Go back to the logging screen and click Reset
    • Attach the latest cascade.log file once again

    Hopefully at that point we'll get some more detailed logging from this event.

    Thanks

    • Edit

13. 13 Posted by Thane M. Webb on 10 Jun, 2016 07:21 PM

    

    Cascade Log attached.

    Thane Webb | Web services Coordinator

    Communications & Marketing
    308-865-8133 | [email blocked] | 1910 University Drive | Kearney, NE 68849

    • cascade.log 300 KB
    • Edit

14. Support Staff 14 Posted by Tim on 28 Jun, 2016 02:52 PM

    

    Hi Thane,

    Is this behavior still occurring in your environment? It looks like our DEBUG logging isn't providing us with enough information to go off of in order to track down what may be happening on your server.

    Also, earlier in this discussion I had asked about Dylan running a couple of commands from the applications server itself (depending on which O/S the app is on). Can you have him do that again, and this time copy/paste the results of the command here?

    • Edit

15. 15 Posted by Thane M. Webb on 28 Jun, 2016 08:58 PM

    

    Yes it is still occurring. I will talk to Dylan and have him run this again and get back to you.

    Thane Webb | Web services Coordinator

    Communications & Marketing
    308-865-8133 | [email blocked] | 1910 University Drive | Kearney, NE 68849

    • Edit