Ticket #417 (closed defect: wontfix)
Images issue on site
Reported by: | laura | Owned by: | chris |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Live server | Keywords: | |
Cc: | jim | Estimated Number of Hours: | 0.0 |
Add Hours to Ticket: | 0 | Billable?: | yes |
Total Hours: | 0.1 |
Description (last modified by chris) (diff)
Not sure if a Chris or Jim one. At times over the past few months, images are not always displaying on the site. Seems to fix itself quite quickly usually. But has been more noticeable in occurance over past few weeks. Today though this is an ongoing issue and received loads of emails from staff, vols and users. The images are there in the html, just not showing to the end user. (popups working fine when clicked on).
I've just done a clear cache in settings/performance which seems to have helped.
Presume some sort of caching issue going on?
(also site quite sluggish for editing today too)
Change History
comment:1 Changed 4 years ago by chris
- Add Hours to Ticket changed from 0.0 to 0.1
- Total Hours changed from 0.0 to 0.1
comment:2 Changed 4 years ago by chris
Looking at the apache logs it looks like the current load spike is being caused by someone running SiteSucker?/2.3.6 against the server:
SiteSucker? is a Macintosh application that automatically downloads Web sites from the Internet.
comment:3 Changed 4 years ago by chris
- Status changed from new to closed
- Resolution set to wontfix
- Description modified (diff)
We are migrating to a new server, see wiki:PuffinServer and this will (probably) invalidate this issue, so closing this ticket.
The image issue will be due to caching, specifically which bit of the caching however I'm not sure without spending some time looking into it.
If the images show up with https and not http then I expect its the varnish cache -- there is no varnish caching for https.
There have been some big load spikes over the last few days -- this will be the reason for the sluggishness, see the munin stats:
https://kiwi.transitionnetwork.org/munin/webarch.net/quince.webarch.net/index.html
Specifically look at the general load spike:
https://kiwi.transitionnetwork.org/munin/webarch.net/quince.webarch.net/load.html
MySQL:
https://kiwi.transitionnetwork.org/munin/webarch.net/quince.webarch.net/mysql_queries.html
CPU:
https://kiwi.transitionnetwork.org/munin/webarch.net/quince.webarch.net/cpu.html
Memory:
https://kiwi.transitionnetwork.org/munin/webarch.net/quince.webarch.net/multimemory.html
Apache:
https://kiwi.transitionnetwork.org/munin/webarch.net/quince.webarch.net/apache_accesses.html
It appears to be that during the load spikes it's only the limit on the number of apache processes (25) that has stopped the machine being brought down by the traffic its getting, however I can't see a corresponding spike in traffic via piwik.