EZProxy

EZProxy Troubleshooting

EZProxy error: Segmentation fault (core dumped)

Error:

Segmentation fault (core dumped)

EZproxy does not offer any further information, making it difficult to diagnose. This happens when you have an IncludeFile entry, and that file does not exist or is not accessible to EZProxy due to incorrect file system permissions. To diagnose such errors, run ezproxy through strace:

# pwd
/usr/local/ezproxy
# strace ./ezproxy

Which yields the following output (preceding output removed):

...
open("journals.txt", O_RDONLY)          = -1 ENOENT (No such file or directory)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)

EZProxy error: No such file or directory

# pwd
/usr/local/ezproxy
# ./ezproxy
No such file or directory

This occurs when EZProxy (a 32-bit binary) is run on a 64-bit system. To fix this, install the following packages for Ubuntu:

# apt install lib32z1 libc6-i386 lib32gcc1 lib32stdc++6

Or the equivalent packages on other distributions.

EZProxy does not offer a 64-bit binary as of 2020.

EZProxy log analysis

Netdata supports web log analysis in real time, which can be useful in identifying issues with stanzas. To configure the Netdata web log plugin for use with the default EZProxy log format, use the following web_log.conf configuration (substitute your log filename accordingly):

ezproxy_log:
  name : 'ezproxy_log'
  path : '/usr/local/ezproxy/ezp2020.log'
  pattern : '(?P<vhost>[a-zA-Z\d.-_]+) (?P<port>\d+) (?P<address>[\da-f.:]+) \[.*\] "(?P<method>[A-Z]+)[^"]*" (?P[1-9]\d{2}) (?P<bytes_sent>\d+)'