Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Nothing is getting written to the access.log #338

Closed
RodBruce opened this issue Dec 10, 2019 · 3 comments
Closed

Nothing is getting written to the access.log #338

RodBruce opened this issue Dec 10, 2019 · 3 comments
Labels
bug
Milestone
5.0

Comments

@RodBruce
Copy link

RodBruce commented Dec 10, 2019 •
edited
Loading

I upgraded from 4.0.3 to 4.1.4. I copied the cantaloupe.properties file and made the recommended changes from the UPGRADING.md. Nothing changed in my LOGGING section. The application log and error log are both getting written to as expected but nothing is getting written to the access.log. This is happening on both servers that I have upgraded. I double checked and there are no permission issues. I'm including the Logging section of my properties file.

Thanks

cantaloupe.properties.logging.txt
adolski pushed a commit that referenced this issue Dec 13, 2019
Add a CustomRequestLog to the Server (#338)
f1571f3
@adolski adolski added the bug label Dec 13, 2019
@adolski adolski added this to the 4.1.5 milestone Dec 13, 2019
@adolski
Copy link
Contributor

adolski commented Dec 13, 2019

Thanks for reporting this, @RodBruce. It looks like the access log was broken by a Jetty upgrade some time ago. This has been fixed in the release/4.1 branch for inclusion in 4.1.5.

@adolski adolski closed this as completed Dec 13, 2019
adolski referenced this issue Dec 18, 2019
Merge branch 'release/4.1' into develop
00689c8 
# Conflicts:
#	pom.xml
#	src/test/java/edu/illinois/library/cantaloupe/resource/LandingResourceTest.java
@adolski adolski reopened this Dec 18, 2019
@adolski adolski mentioned this issue Dec 18, 2019
Closed
adolski pushed a commit that referenced this issue Dec 18, 2019
Revert most of f1571f3 (#338)
00debb3
@adolski adolski removed this from the 4.1.5 milestone Dec 18, 2019
@adolski
Copy link
Contributor

adolski commented Dec 18, 2019

This isn't fixed after all, and it will probably remain broken in the 4.1.x series (see #339 for background).

@adolski adolski added this to the 5.0 milestone Jul 8, 2020
@adolski
Copy link
Contributor

adolski commented Jul 8, 2020

Fixed by aab2b90

@adolski adolski closed this as completed Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
5.0
Development

No branches or pull requests
2 participants
@adolski @RodBruce