This has happened in the past and the workaround for it was as below:
ezproxy logs had filled the root filesystem and so authentication was unable to work.
E-resources not accessible
Request, Authorise and Publish
Requested by Qasim Afzal on 16-Nov-2017
Authorised by User Services
Publish to IS Website (Service Status and Alerts page):
Notes for future reference