Re: LogSPU "type of access"

"So this raises two questions.  I have removed orphaned hosts, but there 
are still many cases of !!! hosts in my Server Status list – not just 
oxfordjournals but many others, some of which have never been accessed.  
This is concerning.  How can I remove them if there is no option under 
Host Maintenance to do so?"

Easy - if there are databases with "!!!", then there should be an option 
under Host Maintenance in the .status page with a radio button next to 
the text "/Remove nnn orphaned host that has !!! database index 
(requires EZproxy restart)/" with a number instead of "nnn".  Click the 
radio button, clilck the "Process" button, then do a restart of the 
EZProxy service, and the "!!!" entries should go away.

If you have "!!!" listings and do not have that option in host 
maintenance, I suggest restarting the EZProxy service, clearing your 
browser caches, and looking again.  If still not there, contact OCLC for 
support :)

-Edward

-- 
Edward F Spodick, Head of IT and Services Infrastructure
Hong Kong University of Science & Technology Library
[email protected] tel:852-2358-6743 fax:852-2358-1043


On 28/11/2019 12:23 am, Hiller, Karl (hillerkj) wrote:
>
> Thanks to everyone who responded.
>
> As it turns out, the difference between the two journals is that one 
> (Gerontologist) exists as an orphaned host and therefore is proxying, 
> and the other (ILAR) is not in the host list and therefore is 
> resulting in a Needhost error.
>
> So this raises two questions.  I have removed orphaned hosts, but 
> there are still many cases of !!! hosts in my Server Status list – not 
> just oxfordjournals but many others, some of which have never been 
> accessed.  This is concerning.  How can I remove them if there is no 
> option under Host Maintenance to do so?
>
> I did previously have an IncludeFile for all of the oxfordjournals 
> hosts, but it got removed when the new stanza was released last 
> April.  Obviously this is why so many hosts were orphaned.  I think I 
> can fix this by restoring the old file – if I can find it (and thanks 
> to Laszlo Gercsov for sending me his version) --  but why is this no 
> longer part of the official stanza?  Were we supposed to take some 
> action to update all of our records to the new URL format?  (We are 
> not a hosted Ezproxy customer).
>
> thanks
>
> Karl
>
> *From:* Laurence Lockton [mailto:[email protected]]
> *Sent:* Monday, November 25, 2019 4:44 AM
> *To:* Hiller, Karl (hillerkj) <[email protected]>; 
> [email protected]
> *Subject:* RE: LogSPU "type of access"
>
> Hi Karl,
>
> It says on this page [1] for %{ezproxy-spuaccess}I
>
> When used with LogSPU, insert "proxy" if the remote user's access to 
> the URL will be proxied; "local" if being redirected due to ExcludeIP; 
> or "unknown" if the URL is not know to EZproxy and Option 
> RedirectUnknown appears in the config.txt
>
> Even if thereÂ’s no longer a stanza for oxfordjournals.org, there can 
> still be a virtual host gerontologist.oxfordjournals.org. If so itÂ’ll 
> be listed in the status page with !!! as the database index, and 
> there’s an option at the bottom of the page for removing “orphaned hosts.”
>
> Cheers,
>
> Laurence Lockton
>
> University of Bath
>
> UK
>
> [1] 
> https://help.oclc.org/Library_Management/EZproxy/Configure_resources/LogFormat
>
> *From:* EZproxy List <[email protected] 
> <mailto:[email protected]>> *On Behalf Of *Hiller, Karl (hillerkj)
> *Sent:* 22 November 2019 17:44
> *To:* [email protected] <mailto:[email protected]>
> *Subject:* [EZPROXY-L] LogSPU "type of access"
>
> In one of the examples on the documentation page for LogSPU, there is 
> a variable *%{ezproxy-spuaccess}i* that is called “type of access”, 
> and it appears to have the values ‘proxy’, ‘local’, or ‘unknown’.  
> These are unexplained.
>
> I have two resources, ilarjournal.oxfordjournals.org and 
> gerontologist.oxfordjournals.org.  There is no longer a stanza 
> containing “oxfordjournals.org” anywhere in config.txt, so both should 
> result in Needhost errors when used in starting point URLs.  However, 
> the Gerontologist SPU resolves to 
> https://academic.oup.com/gerontologist/issue 
> <https://academic.oup.com/gerontologist/issue> while Ilarjournal 
> results in a Needhost error.
>
> I donÂ’t see any difference between the two resources, how they resolve 
> to oup.com outside of Ezproxy, or the format of the SPUs within 
> Ezproxy.  However, I do notice that in the SPU log, “type of access” 
> for Gerontologist is ‘proxy’ while for Ilarjournal it is ‘unknown’.
>
> What would cause one resource to have ‘unknown’ as “type of access”?  
> What does that even mean?
>
> thanks for any advice,
>
> Karl
>
> --
> Karl Hiller
> Computer Info Analyst
> University of Cincinnati Libraries
> 513-556-6203
>
> ------------------------------------------------------------------------
>
> To unsubscribe from the EZPROXY-L list, click the following link:
> http://listserv.oclclists.org/scripts/wa.exe?SUBED1=EZPROXY-L&A=1
>
>
> ------------------------------------------------------------------------
>
> To unsubscribe from the EZPROXY-L list, click the following link:
> http://listserv.oclclists.org/scripts/wa.exe?SUBED1=EZPROXY-L&A=1
>


********************************************************************
If you wish to stop receiving messages from EZPROXY-L or otherwise amend your preferences,
you can do so <a href="https://www.oclc.org/forms/internet-subscription.en.html">here</a>.
Or email [email protected] including the relevant text below in the body of the email:
• To unsubscribe: "unsubscribe EZPROXY-L"
• To receive EZPROXY-L in digest form: "set EZPROXY-L digest"
• To set your options to no mail: "set EZPROXY-L nomail"
• To receive these messages in the future "set EZPROXY-L mail"
To contact the list owners directly please send your message to [email protected].
If you unsubscribe from EZPROXY-L, you will no longer be able to participate in any of its features, including the public forum.
To unsubscribe from all OCLC marketing email communications
(including all OCLC listervs, OCLC Connect emails, OCLC event notifications, product/service/cooperative updates and newsletters),
please email us at [email protected].