- Article Type: General
- Product: Aleph
- Product Version: 15.2
We are sporadically getting the message "System is overloaded" when trying to access our Web OPAC
Just to add some experiences we're having - I tried again, accessed the WOPAC with no problem, using both IE and Firefox. When I refreshed the page once, I got the catalog again, but when I refreshed the page again, I got the System Overloaded message. I repeated these steps several times - one refresh I got the catalog but on the second refresh I got the message. Our webmaster thinks it's related to a licensing issue, but why would this arise now? We've been using Aleph for 2 years and as far as I know, our licensing hasn't changed recently.
Our license MAX-WEB-USERS is 030.
You suggest that there are times where you get the "System is overloaded message" but the Active user count is less than 30. I believe that this can not happen and that when this message appears the number of active z63's is always at the limit.
The following SQL shows that there are 461,982 Z63 Session records:
SQL-VIR01> select count(*) from z63;
**** Hit return to continue ****
This is a big number. It indicates that you are probably not running util a/11 (or clear_vir01) on any regular basis. You should be. But that is probably not connected to this problem.
The results of this query shows the most numerous ip-addresses:
SQL-VIR01> select Z63_CLIENT_ADDRESS, count(*) from z63 group by Z63_CLIENT_ADDRESS having count(*) > 1000;
22.214.171.124 /ms 1247
126.96.36.199 /ms 1368
188.8.131.52 /ms 1530
184.108.40.206 /ms 1673
220.127.116.11 /ms 1355
18.104.22.168 /ms 2134
22.214.171.124 /ms 2974
126.96.36.199 /ms 2440
188.8.131.52 IMo 6046
184.108.40.206 IMo 13471 <---
220.127.116.11 IMozi 10785
18.104.22.168 IMo 5297
22.214.171.124 IMo 4958
126.96.36.199 IMo 2889
188.8.131.52 IMoz 7727
Following the procedure described in KB 8192-483, I did "tracert 184.108.40.206". This shows that 220.127.116.11 is: "crawl.18.104.22.168.googlebot.com"
You need to do the anti-spider stuff under #5 at the end of KB 8192-481.
- Article last edited: 10/8/2013