The other day I moved our EZProxy server application to the HP Proliant box described in an earlier post. EZProxy put such a small load on the machine I began looking for other work it could do…and quickly decided to make it one of my MySQL servers (for things like the campus staff directory, library’s database and e-journal listing services, etc. ).
Didn’t really think about it but MySQL uses port 3306…which is right in the range of “virtual” servers that EZProxy uses. With MySQL running, EZProxy complained about not being able to set up a server on that port.
Solution? Well, being a believer in the efficacy of talking directly to the developer, I sent Chris Zagar (creator of EZProxy) an email and he replied within a couple of hours.
Use the SkipPort directive in ezproxy.cfg (e.g., SkipPort 3306)
Then do a restart on EZProxy. You can use as many SkipPort directives as you need.
Like most of EZProxy, that seemed so logical and so obvious that I felt like an idiot–I surely missed it in the documentation. Knowing what to look for, I did find one mention of SkipPort on the EZProxy site but it is buried down in the release notes. So, I may still be an idiot but at least I wasn’t guilty of being lazy before bugging Chris.
Thanks Chris. Great product and great support.