Mailing List Archive

emerge-fetch.log not always updating
Howdy,

I was in the middle of a update and noticed the server I was connected
to was really slow.  I edited make.conf and removed that server.  I then
restarted emerge so it would try the next server and hopefully be a
better speed.  When I used tail to monitor emerge-fetch.log, it wasn't
updating the fetch progress.  It stopped right where I stopped the
previous attempt.  It looks like this:


root@fireball / # tail -f /var/log/emerge-fetch.log
166050K .......... .......... .......... .......... .......... 29% 66.1K
59m17s
166100K .......... .......... .......... .......... .......... 29% 81.6K
59m17s
166150K .......... .......... .......... .......... .......... 29% 76.2K
59m17s
166200K .......... .......... .......... .......... .......... 29% 63.7K
59m17s
166250K .......... .......... .......... .......... .......... 29% 29.3K
59m19s
166300K .......... .......... .......... .......... .......... 29% 31.7K
59m22s
166350K .......... .......... .......... .......... .......... 29% 44.7K
59m23s
166400K .......... .......... .......... .......... .......... 29% 73.7K
59m23s
166450K .......... .......... .......... .......... .......... 29% 22.6K
59m27s
166500K .......... .......... .......... .^C



It should show it connecting to the next server and resuming the
download but it doesn't.  I see the network activity on gkrellm but
nothing in the log.  It is downloading tho.  Gkrellm shows it is better
but why is the log not showing that?

Is this a bug or am I missing something?  It use some other file on
retries or something?

Thanks.

Dale

:-)  :-) 
Re: emerge-fetch.log not always updating [ In reply to ]
Can you reproduce by manually curling it?

On Sun, Aug 2, 2020, 18:41 Dale <rdalek1967@gmail.com> wrote:

> Howdy,
>
> I was in the middle of a update and noticed the server I was connected to
> was really slow. I edited make.conf and removed that server. I then
> restarted emerge so it would try the next server and hopefully be a better
> speed. When I used tail to monitor emerge-fetch.log, it wasn't updating
> the fetch progress. It stopped right where I stopped the previous
> attempt. It looks like this:
>
>
> root@fireball / # tail -f /var/log/emerge-fetch.log
> 166050K .......... .......... .......... .......... .......... 29% 66.1K
> 59m17s
> 166100K .......... .......... .......... .......... .......... 29% 81.6K
> 59m17s
> 166150K .......... .......... .......... .......... .......... 29% 76.2K
> 59m17s
> 166200K .......... .......... .......... .......... .......... 29% 63.7K
> 59m17s
> 166250K .......... .......... .......... .......... .......... 29% 29.3K
> 59m19s
> 166300K .......... .......... .......... .......... .......... 29% 31.7K
> 59m22s
> 166350K .......... .......... .......... .......... .......... 29% 44.7K
> 59m23s
> 166400K .......... .......... .......... .......... .......... 29% 73.7K
> 59m23s
> 166450K .......... .......... .......... .......... .......... 29% 22.6K
> 59m27s
> 166500K .......... .......... .......... .^C
>
>
>
> It should show it connecting to the next server and resuming the download
> but it doesn't. I see the network activity on gkrellm but nothing in the
> log. It is downloading tho. Gkrellm shows it is better but why is the log
> not showing that?
>
> Is this a bug or am I missing something? It use some other file on
> retries or something?
>
> Thanks.
>
> Dale
>
> :-) :-)
>
Re: emerge-fetch.log not always updating [ In reply to ]
Andrey F. wrote:
> Can you reproduce by manually curling it? 
>

I had to look up curl to see if I even have it installed.  I've seen it
mentioned but no idea what it is but it is installed here.  I'm not
worried about the server that was slow since I removed it.  I think it
was easylist or something.  Maybe it was having a bad day, something
slowing things down between me and it.  Either way, it doesn't matter. 
What I'm wondering, why doesn't the log file get updated when I have to
restart a fetch?  It fetches fine but emerge doesn't update the logs on
second attempts.  I've noticed this in the past but thought it was just
me hitting some sort of glitch.  Thing is, I noticed it not updating
several months ago and it still doesn't update on second attempts. 
There has to be more to this.  It seems emerge has developed a bug or
some nifty new feature that prevents logs from being updated.  ;-)

I might add, on occasion I have to switch servers.  They are fast and
work fine for sometimes years and then slow down or stop working
completely.  Me and the mirrorselect tool are pretty good friends.  I
even had to switch sync servers a while back.  It got to where it was
slow and then just plain stopped.  I think it stopped hosting Gentoo
stuff.  The site was up and all but nothing Gentoo anymore. 

Still curious about emerge-fetch.log not being updated on second
attempts tho. 

Dale

:-)  :-)