Difference between revisions of "EZProxy"

From Libopedia
Jump to navigation Jump to search
(Created page with "== EZProxy Troubleshooting == === EZProxy error: Segmentation fault (core dumped) === Error: Segmentation fault (core dumped) EZproxy does not offer any further informatio...")
 
Line 11: Line 11:
 
  # strace ./ezproxy
 
  # strace ./ezproxy
 
Which yields the following output (preceding output removed):
 
Which yields the following output (preceding output removed):
<nowiki>...
+
<nowiki>...
 
open("journals.txt", O_RDONLY)          = -1 ENOENT (No such file or directory)
 
open("journals.txt", O_RDONLY)          = -1 ENOENT (No such file or directory)
 
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
 
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
 
+++ killed by SIGSEGV (core dumped) +++
 
+++ killed by SIGSEGV (core dumped) +++
 
Segmentation fault (core dumped)</nowiki>
 
Segmentation fault (core dumped)</nowiki>

Revision as of 09:48, 5 July 2018

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)