I noticed qlop did not show latest merges, it printed only emerges completed before August 2021. While trying to understand why I used tail to cut last 5000 lines and created a new emerge.log from this. The old log was over 8.4 MB. With new smaller log I can see latest emerges. How to work around this? Or my log is just too big and I trimming it is the only way? Reproducible: Always
In another box the size of log is 17 MB and qlop works normally. Don't know what to think any more, what might be the limiting factor in my first box?
Can you share emerge --info from both boxes? Also, if you back up your log on the good box, can you read the bad log on it?
OK, I should have done it before filing here. Apparently the log is corrupted somehow. It won't read past Aug 2021 with qlop in another machine. I opened it in less and looking at this part of log I can't see anything weird, probably need to use hex mode to find the culprit. Anyhow, now I don't think it is a failure of qlop. Thanks for thinking with me.
(In reply to Saul Peebsen from comment #3) > OK, I should have done it before filing here. Apparently the log is > corrupted somehow. It won't read past Aug 2021 with qlop in another machine. > I opened it in less and looking at this part of log I can't see anything > weird, probably need to use hex mode to find the culprit. Anyhow, now I > don't think it is a failure of qlop. > Thanks for thinking with me. A pleasure. Just glad your issue is sorted!
(In reply to Sam James from comment #4) > (In reply to Saul Peebsen from comment #3) > > OK, I should have done it before filing here. Apparently the log is > > corrupted somehow. It won't read past Aug 2021 with qlop in another machine. > > I opened it in less and looking at this part of log I can't see anything > > weird, probably need to use hex mode to find the culprit. Anyhow, now I > > don't think it is a failure of qlop. > > Thanks for thinking with me. > > A pleasure. Just glad your issue is sorted! ... but if you do figure out hte character or something, let us know, because we might be able to fix the validation in qlop?
The problem likely is parallel merges. It's probably an interrupted (Ctrl-C-ed) merge that confuses the code. What you can do is grep for "*** emerge" and "*** terminating", that should match up, sort of.
The log in question is here: http://asclinux.com:8000/tmp/emerge.log.bz2
2021-09-03T14:40:16 >>> x11-libs/libXft: 2′10″ 2021-09-03T15:00:33 >>> x11-libs/pango: 9′06″ 2021-09-03T15:09:39 >>> x11-wm/openbox: 6′02″ 2021-09-03T15:27:39 >>> net-fs/nfs-utils: 8′04″ 2021-09-06T13:36:00 >>> dev-util/meson: 12′27″ 2055-09-06T15:27:17 >>> sys-process/htop: 3′52″ 2055-09-06T15:31:10 >>> dev-util/ccache: 10′28″ 2055-09-06T15:41:38 >>> x11-base/xorg-proto: 1′42″ 2055-09-06T15:43:20 >>> x11-libs/libXi: 3′26″ 2055-09-06T15:46:46 >>> app-vim/gentoo-syntax: 44s 2055-09-06T15:47:30 >>> net-misc/openssh: 15′48″ 2055-09-06T16:03:18 >>> sys-apps/man-pages: 12′22″ 2055-09-06T16:15:40 >>> app-misc/mc: 16′43″ 2055-09-06T16:32:23 >>> net-wireless/bluez: 16′31″ % grep bluez qlop-stopping-emerge.log | cut -d':' -f1 | sort -u | tail -n1 2703858534 % date -d@2703858534 6 September 2055 at 16:48:54 CET Did you experience a malfunction in your flux capacitor or something? qlop only goes forwards in time, so it's still stuck in 2055 in your case. I think your best move is to patch up your emerge.log...
Thank you! How did I miss that. Well, I could wait until September 2055 ... I live countryside, we have short power interruptions in windy days, must be one of those. This box is the only one without UPS.
