This page is (hopefully) the beginning of a page to help resolve various technical difficulties with accessing or editing Wikipedia Pages. == Cache problems with Internet Explorer == A problem commonly reported by Internet Explorer users relates to Wikipedia content that seems to be out-of-date. The problem usually manifests as disappearing page edits or days-old current events. This problem is almost always caused by Wikipedia:Clear_your_cache. Almost all Web browsers temporarily store a copy of viewed Web pages on the user's computer, and almost all browsers are configured by default to display the cached copy if the user revisits the same page and it can be determined that the page has not been updated since his last visit. Usually, this process works as expected; however, some versions of Internet Explorer fail to always correctly re-download a page when it has become outdated (which may be a software bug). (The Internet Explorer problem is not unique to Wikipedia; if you incorrectly see cached data here, you are likely seeing out-of-date pages on other sites too.) There are three simple workarounds you should try if you encounter this problem. #Click the Refresh button in the toolbar or activate the Refresh keyboard shortcut (on Microsoft Windows computers, either F5 or Ctrl-R). #If that doesn't work, try Ctrl-F5 (i.e. hold down the Control key and then press F5); this shortcut is documented as always refreshing the page from the Internet, regardless of what is in the cache. #If neither method of refreshing works, you can manually delete all files in your cache. To do this, select "Internet Options" from the Internet Explorer "Tools" menu and then click the "Delete Files..." button. (Note that this last process may take some time if the cache has not been recently cleared.) Finally, you might simply consider trying a different Web browser. Mozilla Firefox, Netscape Navigator, and Opera (browser) are three popular alternatives available for a variety of operating systems. Internet Explorer has been singled-out in this troubleshooting section because the majority of cache-related problems are reported by Internet Explorer users, but similar issues could be found in other browsers in the future. For more information about Wikipedia page caching and caching in general, see Wikipedia:Clear your cache. == Firewall / Privacy Issues == Symptoms: Images don't show up correctly, or the 'Wikipedia' logo graphic appears instead of referenced images; log-in does not 'stick', and the user's ip keeps appearing at the top right of pages instead of the user name. Apparently, Wikipedia must make use of some more advanced cookie features. Make sure that any Firewall or Privacy settings (e.g., ZoneAlarm, IE privacy settings, etc.) let Wikipedia have more freedom to set cookies as it desires; in particular, for ZoneAlarm settings, you must allow cookies with private header information. == Too-Many Connections Problem == Symptoms: Some contributors occasionally see error messages like the following instead of the page they requested: Warning: open(/tmp/sess_e3b9b5e8f5afa9cce2aa0066fca4a143, O_RDWR) failed: Too many open files in system (23) in /usr/local/apache/htdocs/w/wiki.phtml on line 7 Warning: Failed opening 'Setup.php' for inclusion (include_path='.:/usr/local/lib/php') in /usr/local/apache/htdocs/w/wiki.phtml on line 12 Fatal error: Undefined class name 'outputpage' in /usr/local/apache/htdocs/w/wiki.phtml on line 14 Warning: open(/tmp/sess_e3b9b5e8f5afa9cce2aa0066fca4a143, O_RDWR) failed: Too many open files in system (23) in Unknown on line 0 Warning: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0 This is caused by the existence of a limit on the number of files which can be open at once, and at times too many users have been connected at once (essentially, this is Wikipedia becoming a victim of its own success). The limit has recently been increased to avoid this error occurring so frequently. However, some people's systems may have cached versions of the error message and so be continually redisplaying it; see "Cache Problems with IE" above. == Firefox doesn't display images == The Mozilla Firefox browser allows you to control whether Web pages can load images from outside the Web site you are viewing. If you enable this feature, images will not be displayed in Wikipedia pages, because images are loaded from commons.wikipedia.org rather than the en.wikipedia.org site you are viewing. Solution: # Tools - Options - Web Features # Set the "Load Images" checkbox # Clear the "for the originating web site only" checkbox ==History problems== Lately (as of 2005), with [http://wikipedia.sourceforge.net/ MediaWiki 1.4rc1], it sometimes happens that viewing the history of an article that was edited when the system was very busy shows that several of the most-recent edits aren't listed any more. If that happens, selecting either a different history length (e.g. "last 20" instead of the default 50) will cause the correct history to be shown. It seems to be a caching problem, not some problem with the database. == Other Problems == I have a new problem that is not on this list. What should I do? Post your question on the Wikipedia:Village pump or ask one of the Wikipedia Wikipedia:Administrators or Wikipedia:Developers. Administrator and Developer User:Lee Daniel Crocker can probably answer most of your troubleshooting questions. See also Wikipedia:Browser notes. Wikipedia FAQ
== Reloading cached pages == I am unable to access the following areas: *Clermont County, Ohio *List of Montana counties *The main page of www.wikipedia.org I get various errors, all php related. Some are missing files, others are too many files open, and the like. The Clermont County one has been like this for days. What is happening here? -- User:Ram-Man This is probably due to general heavy traffic loads from readers and ''very'' heavy edit load from me and especially you. ;) --User:Maveric149 Shouldn't this clear out? Why has it been hours or days (in the case of Ohio) like this? -- Ram-Man Clear your browser cache, hit reload, try again. Especially if you're using Internet Explorer, which seems to jealously preserve failed page loads. --User:Brion VIBBER 03:18 Sep 29, 2002 (UTC) I concur. Although I am using a Netscape version rather than Explorer, I too find that the error messages comes back if I go to the same page again, but then disappears when I hit 'Reload'. User:Andre Engels Clearing the cache fixed my problem. Thanks! -- User:Ram-Man ''Incidentally, one way to force Infernal Exploder to refresh is to hold down the Ctrl key while clicking the refresh icon. Which reminds me of a joke: "Only women refresh; men reload." -- User:Netesq 20:10 Sep 29, 2002 (UTC)'' If 'reload' also doesn't work, try to manually change the URL from www.wikipedia.org to www.wikipedia.com; rest unchanged. That should get around any caches that just keep acting on reload.User:Andre Engels 23:25 Oct 2, 2002 (UTC) Perhaps the problem here is that, although we normally send pages set to expire immediately, so that there will be no caching, perhaps no such expiration is set when we send errors. Well, we generate the errors here on our server, so surely we can send such expiration commands then too? Programmers: Am I right? — User:Toby Bartels 05:26 Sep 30, 2002 (UTC) If you're getting one of the errors described above, our script probably isn't even getting a chance to run; if it does, the error messages usually come up before we have a chance to output the custom headers, and you can't output headers after content has started. So, um, prolly not. --User:Brion VIBBER 05:31 Sep 30, 2002 (UTC) == Saving Changes Weirdness == Weirdness is afoot. I can't save changes in Konqueror at all and Mozilla tries, seems to fail, displays an error message saying there is no data in the page but then I see the saved edit in RC. --User:Maveric149 : same here. Chimera mac os. -- User:Tarquin :Same with me with IE. It gives me an error saying it can't find the page, but the editing is done anyway, according to Recent Changes. -- User:Zoe : same here with NC4.6 changes are added, but with message no data in page. User:TeunSpaans Better now? I was about to restart the web & database servers when it suddenly started working smoothly a few minutes ago. (Lee, did you do something?) --User:Brion VIBBER 22:59 Oct 21, 2002 (UTC) :Hmm, well I can read pages but I do get the error on saving. Weird. --User:Brion VIBBER 23:00 Oct 21, 2002 (UTC) ::I ''think'' I got it; when it doubt, clear the PHP script cache. --Brion Brion, I just installed your patch and upgraded PHP to 4.2.3 while I was there. The process may have been a bit bumpy... --User:66.216.68.43
wat is the difference between the lan and wan ad man :LAN, Metropolitan area network and WAN. ;) --User:TheParanoidOne 19:29, 16 Apr 2005 (UTC)
Troubleshooting is a form of problem solving. It is the systematic search for the source of a problem so that it can be solved. Troubleshooting is used in many fields such as system administration and electronics. Normally a process of elimination is used to isolate possible causes of problems. Usually troubleshooting is applied to something that has suddenly stopped working, so the first focus, or concentration of attention, should be on what has changed. However, care must be used to not jump to false conclusions of causality - correlation does not always mean cause. A basic principle in troubleshooting is to start from the simplest and most probability possible problems first. This is illustrated by the old saying "When you see hoof prints, look for horses, not zebras", or to use another maxim (saying), use the KISS principle. This principle results in the common complaint about help desks or manuals, that they sometimes first ask: "Is it plugged in?", but this should not be taken as an affront, rather it should serve as a reminder or conditioning to always check the simple things first before calling for help. Further steps in troubleshooting are to check each component in a system one by one, and to substitute known good components for any suspect ones. A cognitive walkthrough is also a good thing to try. Comprehensive documentation produced by proficient technical writers is very helpful, especially if it provides a theory of operation for the subject device or system. ==See also== *Root cause analysis *Scientific method *Trial and error
See other meanings of words starting from letter:
Words begining with Troubleshooting:
Troubleshooting
Troubleshooting
Troubleshooting
Troubleshooting
Troubleshooting_Wikipedia
Troubleshooting_Wikipedia
Troubleshooting
This page is (hopefully) the beginning of a page to help resolve various technical difficulties with accessing or editing Wikipedia Pages. == Cache problems with Internet Explorer == A problem commonly reported by Internet Explorer users relates to Wikipedia content that seems to be out-of-date. The problem usually manifests as disappearing page edits or days-old current events. This problem is almost always caused by Wikipedia:Clear_your_cache. Almost all Web browsers temporarily store a copy of viewed Web pages on the user's computer, and almost all browsers are configured by default to display the cached copy if the user revisits the same page and it can be determined that the page has not been updated since his last visit. Usually, this process works as expected; however, some versions of Internet Explorer fail to always correctly re-download a page when it has become outdated (which may be a software bug). (The Internet Explorer problem is not unique to Wikipedia; if you incorrectly see cached data here, you are likely seeing out-of-date pages on other sites too.) There are three simple workarounds you should try if you encounter this problem. #Click the Refresh button in the toolbar or activate the Refresh keyboard shortcut (on Microsoft Windows computers, either F5 or Ctrl-R). #If that doesn't work, try Ctrl-F5 (i.e. hold down the Control key and then press F5); this shortcut is documented as always refreshing the page from the Internet, regardless of what is in the cache. #If neither method of refreshing works, you can manually delete all files in your cache. To do this, select "Internet Options" from the Internet Explorer "Tools" menu and then click the "Delete Files..." button. (Note that this last process may take some time if the cache has not been recently cleared.) Finally, you might simply consider trying a different Web browser. Mozilla Firefox, Netscape Navigator, and Opera (browser) are three popular alternatives available for a variety of operating systems. Internet Explorer has been singled-out in this troubleshooting section because the majority of cache-related problems are reported by Internet Explorer users, but similar issues could be found in other browsers in the future. For more information about Wikipedia page caching and caching in general, see Wikipedia:Clear your cache. == Firewall / Privacy Issues == Symptoms: Images don't show up correctly, or the 'Wikipedia' logo graphic appears instead of referenced images; log-in does not 'stick', and the user's ip keeps appearing at the top right of pages instead of the user name. Apparently, Wikipedia must make use of some more advanced cookie features. Make sure that any Firewall or Privacy settings (e.g., ZoneAlarm, IE privacy settings, etc.) let Wikipedia have more freedom to set cookies as it desires; in particular, for ZoneAlarm settings, you must allow cookies with private header information. == Too-Many Connections Problem == Symptoms: Some contributors occasionally see error messages like the following instead of the page they requested: Warning: open(/tmp/sess_e3b9b5e8f5afa9cce2aa0066fca4a143, O_RDWR) failed: Too many open files in system (23) in /usr/local/apache/htdocs/w/wiki.phtml on line 7 Warning: Failed opening 'Setup.php' for inclusion (include_path='.:/usr/local/lib/php') in /usr/local/apache/htdocs/w/wiki.phtml on line 12 Fatal error: Undefined class name 'outputpage' in /usr/local/apache/htdocs/w/wiki.phtml on line 14 Warning: open(/tmp/sess_e3b9b5e8f5afa9cce2aa0066fca4a143, O_RDWR) failed: Too many open files in system (23) in Unknown on line 0 Warning: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0 This is caused by the existence of a limit on the number of files which can be open at once, and at times too many users have been connected at once (essentially, this is Wikipedia becoming a victim of its own success). The limit has recently been increased to avoid this error occurring so frequently. However, some people's systems may have cached versions of the error message and so be continually redisplaying it; see "Cache Problems with IE" above. == Firefox doesn't display images == The Mozilla Firefox browser allows you to control whether Web pages can load images from outside the Web site you are viewing. If you enable this feature, images will not be displayed in Wikipedia pages, because images are loaded from commons.wikipedia.org rather than the en.wikipedia.org site you are viewing. Solution: # Tools - Options - Web Features # Set the "Load Images" checkbox # Clear the "for the originating web site only" checkbox ==History problems== Lately (as of 2005), with [http://wikipedia.sourceforge.net/ MediaWiki 1.4rc1], it sometimes happens that viewing the history of an article that was edited when the system was very busy shows that several of the most-recent edits aren't listed any more. If that happens, selecting either a different history length (e.g. "last 20" instead of the default 50) will cause the correct history to be shown. It seems to be a caching problem, not some problem with the database. == Other Problems == I have a new problem that is not on this list. What should I do? Post your question on the Wikipedia:Village pump or ask one of the Wikipedia Wikipedia:Administrators or Wikipedia:Developers. Administrator and Developer User:Lee Daniel Crocker can probably answer most of your troubleshooting questions. See also Wikipedia:Browser notes. Wikipedia FAQ
Troubleshooting
== Reloading cached pages == I am unable to access the following areas: *Clermont County, Ohio *List of Montana counties *The main page of www.wikipedia.org I get various errors, all php related. Some are missing files, others are too many files open, and the like. The Clermont County one has been like this for days. What is happening here? -- User:Ram-Man This is probably due to general heavy traffic loads from readers and ''very'' heavy edit load from me and especially you. ;) --User:Maveric149 Shouldn't this clear out? Why has it been hours or days (in the case of Ohio) like this? -- Ram-Man Clear your browser cache, hit reload, try again. Especially if you're using Internet Explorer, which seems to jealously preserve failed page loads. --User:Brion VIBBER 03:18 Sep 29, 2002 (UTC) I concur. Although I am using a Netscape version rather than Explorer, I too find that the error messages comes back if I go to the same page again, but then disappears when I hit 'Reload'. User:Andre Engels Clearing the cache fixed my problem. Thanks! -- User:Ram-Man ''Incidentally, one way to force Infernal Exploder to refresh is to hold down the Ctrl key while clicking the refresh icon. Which reminds me of a joke: "Only women refresh; men reload." -- User:Netesq 20:10 Sep 29, 2002 (UTC)'' If 'reload' also doesn't work, try to manually change the URL from www.wikipedia.org to www.wikipedia.com; rest unchanged. That should get around any caches that just keep acting on reload.User:Andre Engels 23:25 Oct 2, 2002 (UTC) Perhaps the problem here is that, although we normally send pages set to expire immediately, so that there will be no caching, perhaps no such expiration is set when we send errors. Well, we generate the errors here on our server, so surely we can send such expiration commands then too? Programmers: Am I right? — User:Toby Bartels 05:26 Sep 30, 2002 (UTC) If you're getting one of the errors described above, our script probably isn't even getting a chance to run; if it does, the error messages usually come up before we have a chance to output the custom headers, and you can't output headers after content has started. So, um, prolly not. --User:Brion VIBBER 05:31 Sep 30, 2002 (UTC) == Saving Changes Weirdness == Weirdness is afoot. I can't save changes in Konqueror at all and Mozilla tries, seems to fail, displays an error message saying there is no data in the page but then I see the saved edit in RC. --User:Maveric149 : same here. Chimera mac os. -- User:Tarquin :Same with me with IE. It gives me an error saying it can't find the page, but the editing is done anyway, according to Recent Changes. -- User:Zoe : same here with NC4.6 changes are added, but with message no data in page. User:TeunSpaans Better now? I was about to restart the web & database servers when it suddenly started working smoothly a few minutes ago. (Lee, did you do something?) --User:Brion VIBBER 22:59 Oct 21, 2002 (UTC) :Hmm, well I can read pages but I do get the error on saving. Weird. --User:Brion VIBBER 23:00 Oct 21, 2002 (UTC) ::I ''think'' I got it; when it doubt, clear the PHP script cache. --Brion Brion, I just installed your patch and upgraded PHP to 4.2.3 while I was there. The process may have been a bit bumpy... --User:66.216.68.43
Troubleshooting
wat is the difference between the lan and wan ad man :LAN, Metropolitan area network and WAN. ;) --User:TheParanoidOne 19:29, 16 Apr 2005 (UTC)
Troubleshooting
Troubleshooting is a form of problem solving. It is the systematic search for the source of a problem so that it can be solved. Troubleshooting is used in many fields such as system administration and electronics. Normally a process of elimination is used to isolate possible causes of problems. Usually troubleshooting is applied to something that has suddenly stopped working, so the first focus, or concentration of attention, should be on what has changed. However, care must be used to not jump to false conclusions of causality - correlation does not always mean cause. A basic principle in troubleshooting is to start from the simplest and most probability possible problems first. This is illustrated by the old saying "When you see hoof prints, look for horses, not zebras", or to use another maxim (saying), use the KISS principle. This principle results in the common complaint about help desks or manuals, that they sometimes first ask: "Is it plugged in?", but this should not be taken as an affront, rather it should serve as a reminder or conditioning to always check the simple things first before calling for help. Further steps in troubleshooting are to check each component in a system one by one, and to substitute known good components for any suspect ones. A cognitive walkthrough is also a good thing to try. Comprehensive documentation produced by proficient technical writers is very helpful, especially if it provides a theory of operation for the subject device or system. ==See also== *Root cause analysis *Scientific method *Trial and error
See other meanings of words starting from letter:
T
TA | TB | TC | TD | TE | TF | TG | TH | TI | TJ | TK | TL | TŁ | TM | TN | TO | TP | TR | TS | TU | TW | TX | TY | TZ |Words begining with Troubleshooting:
Troubleshooting
Troubleshooting
Troubleshooting
Troubleshooting
Troubleshooting_Wikipedia
Troubleshooting_Wikipedia
These materials are based on Wikipedia and licensed under the GNU FDL
YouTube.com videos better site than Turbo Tax 2007
