SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: Connection refused' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-11-21 01:40 MST

Project: All Projects ClearCenter ClearOS

Main | My View | View Issues | Change Log | Roadmap | Repositories

View Issue Details [ Jump to Notes ]				[ Issue History ] [ Print ]
ID	Project	Category	View Status	Date Submitted	Last Update
0001524	ClearOS	app-base - Base System	public	2014-01-21 08:25	2014-04-02 14:46
Reporter	user2
Assigned To	user2
Priority	normal	Severity	minor	Reproducibility	N/A
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version
Target Version	6.5.0 Updates	Fixed in Version	6.5.0 Updates
Summary	0001524: Yum cache is still problematic
Description	We still see reports of yum caching extremely old data. For example, a customer recently reported a cache that contained data that was at least 4 days old! In 6.5.0, the following parameter was added to yum.conf: http_caching=packages There's also the "metadata_expire" (defaults to 6 hours) and "mirrorlist_expire" parameters that might need to be shortened. That still doesn't explain the "4 days old" behavior. Perhaps it's related to skewed clocks at install time?
Tags	No tags attached.
Attached Files

Relationships

duplicate of  0001562 closed user2  Yum cache is still problematic

Relationships

Notes
(0001134) user2 2014-01-21 09:14	Confirmed the clock skew. 1) Set metadata_expire=60 2) Run "yum repolist" to grab repo data 3) Set clock back a day 4) Run "yum repolist" after a few minutes... the cache is never purged.

Notes

Issue History
Date Modified	Username	Field	Change
2014-01-21 08:25	user2	New Issue
2014-01-21 09:14	user2	Note Added: 0001134
2014-01-21 09:14	user2	Assigned To	=> user2
2014-01-21 09:14	user2	Status	new => confirmed
2014-02-07 13:15	user2	Status	confirmed => resolved
2014-02-07 13:15	user2	Fixed in Version	=> 6.5.0 Updates
2014-02-07 13:15	user2	Resolution	open => fixed
2014-02-13 09:45	user2	Issue cloned: 0001562
2014-02-13 09:45	user2	Relationship added	duplicate of 0001562
2014-04-02 14:46	user2	Status	resolved => closed

Issue History