Error Messages Troubleshooting

[pervect]

I'm currently getting the following error messages:

Warning: file_get_contents(http://www.sciam.com/xml/sciam.xml) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /includes/init.php(319) : eval()'d code on line 218

Warning: file_get_contents(http://www.sciam.com/xml/sciam.xml) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /includes/init.php(319) : eval()'d code on line 218

Warning: file_get_contents(http://www.sciam.com/xml/sciam.xml) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /includes/init.php(319) : eval()'d code on line 218

Warning: file_get_contents(http://www.sciam.com/xml/sciam.xml) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /includes/init.php(319) : eval()'d code on line 218

 

[NeoDevin]

you're not the only one

 

[Astronuc]

I received the same or similar messages yesterday, which slowed the loading of the main page. I posted about a main page problem.

 

[ZapperZ]

Yup. This has occurred at least on 3 different days for the past week.

Zz.

 

[ZapperZ]

BTW, this is a hint.

The only problem when this occurs is that it takes FOREVER to display the PF main page. You actually don't need to get to that to navigate around PF. Once you are in (after waiting FOREVER), to go from one forum to the other without going through the PF main page is quick and easy. Just scroll to the bottom of the page and click on the drop-down Forum Jump box. This will allow you to go to any part of PF while bypassing the main page.

Zz.

 

[-Job-]

This happens when loading the RSS data from Scientific American to display the Scientific American headlines. If the Scientific American site is down or overloaded then the main PF page (which waits for these headlines) will be very slow.

To avoid this PF can cache the Scientific American RSS locally on its server, then every X hours check for a new version of the RSS file.
Or implement an RSS timeout.