Bug 11254 - update_accelerator not working - Local cache is empty
Summary: update_accelerator not working - Local cache is empty
Status: CLOSED DEFERRED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: all All
: Will affect an average number of users Major Usability
Assignee: Bernhard Bitsch
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-04 12:06 UTC by Razvan Constantin
Modified: 2018-01-27 21:29 UTC (History)
3 users (show)

See Also:


Attachments
Cache maintenance (46.86 KB, image/png)
2016-11-04 12:06 UTC, Razvan Constantin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Razvan Constantin 2016-11-04 12:06:44 UTC
Created attachment 486 [details]
Cache maintenance

Problem started with IPFire update 106
Was working with update 105

Update Accelerator reports "Local cache is empty"
Nothing gets cached or delivered from cache.

SSH into machine and running /var/ipfire/updatexlrator/bin/lscache shows plenty of cached files BUT not all of them.
/var/updatecache has plenty of files cached

Running /var/ipfire/updatexlrator/bin/sources.pl throws the error:

Can't locate Regexp/Assemble.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.12.3/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.12.3 /usr/lib/perl5/5.12.3/x86_64-linux-thread-multi /usr/lib/perl5/5.12.3 .) at ./sources.pl line 31.
Comment 1 davidak 2017-10-01 00:31:27 UTC
Same here. I noticed after update from 109 to 113.

[root@ipfire ~]# /var/ipfire/updatexlrator/bin/lscache
No matching files found in cache

[root@ipfire ~]# du -h /var/updatecache
4.0K	/var/updatecache/download
4.0K	/var/updatecache/metadata
12K	/var/updatecache

Strange is also that the webinterface shows that 74 GB is used, but that is used on /var


Cache-Verzeichnis	Größe	Benutzt	Frei	Prozent
[/var/updatecache/]	107G	74G	29G	73%
Comment 2 Bernhard Bitsch 2018-01-27 17:51:24 UTC
Is this problem also with the current update ( 117 )?

BTW: sources.pl is part of my rewriting. A "normal" update should have put you back to standard accelerator.
Comment 3 davidak 2018-01-27 21:10:34 UTC
It works again in 117.
Comment 4 Bernhard Bitsch 2018-01-27 21:29:02 UTC
I close this bug.
Maybe it was a side effect of install of "new" update accelerator.
Correct display ( and storage of data ) will be worked on in rewrite.