[Yazlist] [Zebralist] Zebra / Yazproxy -- ``Present request out of range'' messages'' when system under load

Adam Dickmeiss adam at indexdata.dk
Thu Sep 18 21:12:10 CEST 2008


Richard MAHONEY wrote:
> [Apologies for cross posting (I'm uncertain whether this is an issue
> with YAZ or Zebra)]
>
> Readers,
>
> Of late I've begun to notice a tendency in my Zebra / Yazproxy
> installation to return ``Present request out of range'' messages. It
> would appear that this occurs when the system is being crawled by
> Google, though I wouldn't have thought that this in itself should have
> caused any issues (the maximum number of pages crawled per day is only
> a little over 12,000).
>
>   
You have provided a lot information. But I don't see how the 'out of 
range' should occur. Clearly some error in a Z39.50 client can cause it 
.. It could also be caused by an error in yazproxy .. if that (being a 
Z39.50) make a bad present request.. You should dig in the log files and 
see when it occurs for yazproxy7zebra and the corresponding URLs used 
for the user interface .. Presumably somebody (google bot) is going 
there.. You need to find an example of it occurring etc..

Hope this helps.

/ Adam
> The system is as follows:
>
> yazproxy-1.2.1/yazpp-1.0.0/yaz-2.1.18
>
> idzebra-2.0.32/yaz-3.0.32
>
> php-5.2.6/apache-2.2.9/current PHP/YAZ
>
> OS: SunOS 5.11 snv_62 i86pc i386 i86pc (OpenSolaris)
>
> URL: http://scholia.indica-et-buddhica.org/search/interface/
>
>
> Yazproxy is invoked with the following command:
>
> # yazproxyctl.sh (with ARGS="")
>
> Though a config.xml such as the following was tried without resolving
> the ``Present request out of range'' issue:
>
> ***********************
> <?xml version="1.0"?>
> <proxy xmlns="http://indexdata.dk/yazproxy/schema/0.9/"
> xmlns:xi="http://www.w3.org/2001/XInclude"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>  
> xsi:schemaLocation="http://indexdata.dk/yazproxy/schema/0.9/yazproxy.xsd">
>   <target name="localhost" default="1">
>     <url>localhost:port</url>
>     <target-timeout>30</target-timeout>
>     <client-timeout>60</client-timeout>
>  <!--   <max-sockets>8</max-sockets> -->
>     <keepalive>
>       <bandwidth>1000000</bandwidth>
>       <pdu>1000</pdu>
>     </keepalive>
>     <limit>
>       <bandwidth>5000000</bandwidth>
>       <pdu>500</pdu>
>       <retrieve>10000</retrieve>
>       <search>250</search>
>     </limit>
>   </target>
>   <target name="*">
>     <target-timeout>60</target-timeout>
>     <client-timeout>30</client-timeout>
> <!--    <max-sockets>8</max-sockets> -->
>     <keepalive>
>       <bandwidth>1000000</bandwidth>
>       <pdu>1000</pdu>
>     </keepalive>
>     <limit>
>       <bandwidth>5000000</bandwidth>
>       <pdu>500</pdu>
>       <retrieve>10000</retrieve>
>       <search>250</search>
>     </limit>
>   </target>
>   <max-clients>150</max-clients>
> <!--  <max-connect>30</max-connect> -->
> <!--  <period-connect>10</period-connect> -->
> <!--  <limit-connect>15</limit-connect> -->
> </proxy>
> *********************
>
> Zebra is started with the following:
>
> # zebrasrv -T -w /path/to/zebra/databases -c
> /path/to/zebra/databases/zebra.cfg \
>  -u username -D tcp:localhost:port
>
> zebra.cfg contains the following:
>
> ************************
> profilePath: ./:/path/to/share/idzebra-2.0/tab
> modulePath: /path/to/lib/idzebra-2.0/modules
>
> dbname.recordType: alvis.filter_alvis_conf.xml
> dbname.storeData: 1
> dbname.database: dbname
>
> attset: bib1.att
> attset: explain.att
>
> register: register01:300M register02:300M register03:300M
> shadow: shadow01:300M shadow02:300M shadow03:300M
> lockDir: lock
> setTmpDir: tmp
> keyTmpDir: tmp
>
> staticrank: 1
> rank: rank-1
>
> memMax: 32
> ***************************
>
>
> I would appreciate any suggestions. Thanking you in advance ...
>
>
> Best regards,
>
>  Richard MAHONEY
>
>
>
>   




More information about the Yazlist mailing list