Hide Forgot
Description of problem: Please see this issue: https://github.com/varnishcache/varnish-cache/pull/1915 Version-Release number of selected component (if applicable): varnish-4.0.3-3.el7.x86_64
Hello, George. Thanks for reporting this. Can you please test with varnish-4.0.4-2.el7.x86_64, which should be in epel 7 testing now. If it has not trickled down to your local mirror yet, please try the bodhi update page at https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-ce7e643cb6 , or eventually the koji build at http://koji.fedoraproject.org/koji/buildinfo?buildID=822067 . If it works, please karma it up as a logged in fedora user, at the bodhi update page. If will enter stable faster with enough karma. Ingvar
Hi Ingvar, Thanks for your fast reply. I updated to varnish-4.0.4-2.el7.x86_64 from epel-testing. Before restarting the service, I ran: varnishlog -d There were no 'Log overrun' or 'Log reacquired' messages, which I assume is a good sign. Then I checked the timestamp of the first logged request with: varnishlog -d -c -I "TimeStamp:^Req" | head The first timestamp it returned was close to the time I updated the package. I'm not sure what I should assume by that. Shouldn't it return older requests as well? I have now restarted the service and will report back after one-two days (usually, this is the timeframe after which the issue occurred) and add karma to the bohdi page if everything works fine. Again, thanks for your work! George
Hi Ingvar, I had to test a new configuration and I reverted back to the stable release for a while. However, I plan to upgrade to the release from epel-testing very soon and send feedback about this issue. I'm sorry for the delay. George
Hi Ingvar, I had opened this bug report while using Varnish 4.0.3-3.el7.x86_64 under CentOS 7.2. After upgrading to CentOS 7.3.1611 and while still using the same Varnish version (4.0.3-3), I can no longer reproduce the problem. This tells me that the issue was caused by some other library which has been updated during the OS upgrade. So, I'm going to close this bug report. Thanks for your help. George