My `messages.txt` file is being flooded with error messages. What can I do to address this issue?
If your `messages.txt` file is constantly being populated with error messages similar to the following:
2023-06-15 15:13:25 getaddrinfo error some.domain.com -2
2023-06-15 15:13:25 UUConnect host 'some.domain.com' not found in DoTranslate
2023-06-15 15:13:25 Host not found: some.domain.com
Where the date, time, and the domain `some.domain.com` may vary, you're encountering UUConnect errors. These errors occur when EZproxy fails to connect
to a domain that cannot be found.
This issue often arises when a resource provider discontinues a domain, but references to it still exist on their website.
Each time this non-existent domain is accessed, EZproxy records a UUConnect error in the manner described above. As these failed attempts accumulate, your
`messages.txt` file becomes cluttered with hundreds or thousands of entries.
How can I prevent these UUConnect errors from overloading my `messages.txt` file?
To manage the influx of UUConnect errors in your `messages.txt` file, follow these steps:
1. First, ascertain whether the domain in question truly doesn't exist or if it's temporarily unavailable. If the domain is experiencing temporary downtime,
suppressing the errors may lead to problems once the site is operational again.
2. Utilize a command line to perform an nslookup on the domain mentioned in the UUConnect error. For instance: ` nslookup some.domain.com `
3. If the response resembles: ` *** ddiv0001sac1.saa.domain.org can't find some.domain.com: Non-existent domain ` , the key phrase to note is 'non-existent
domain'. In such cases, it's appropriate to suppress the errors as there's no solution for this issue.
How can I use the NeverProxy directive to prevent UUConnect errors from being recorded in `messages.txt`?
To stop UUConnect errors from cluttering your `messages.txt` file, follow these steps:
1. Implement the NeverProxy directive as shown: ` NeverProxy some.domain.com ` .
2. Keep in mind that NeverProxy directives are not limited to database stanzas; they can be placed anywhere within the ` config.txt ` file.
For more detailed guidance on employing the NeverProxy directive, consult this
By incorporating NeverProxy directives into your configuration, you can effectively reduce the number of UUConnect errors recorded in your `messages.txt`
If you continue encountering UUConnect errors within your `messages.txt` file even after implementing NeverProxy, reach out to OCLC Support for assistance.
Ensure you include copies of your `config.txt` and `messages.txt` files when seeking support.