[arch-general] pacman message: "too much happens::" ...
Hi, I'm updating the pacman database about once a day. For the last few days I always get this message: "too much happens:: Synchronizing package databases..." but everything works fine. I checked usr/bin/pacman, /usr/lib/libalpm.so.4 and usr/sbin/fcron using strings(1) for the text "much", but no hits. What's happening here? clemens
On Fri, Feb 5, 2010 at 4:08 PM, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
Hi,
I'm updating the pacman database about once a day. For the last few days I always get this message:
"too much happens:: Synchronizing package databases..."
but everything works fine. I checked usr/bin/pacman, /usr/lib/libalpm.so.4 and usr/sbin/fcron using strings(1) for the text "much", but no hits.
What's happening here?
Showing the command you are actually running might be a good first start... -Dan
Dan McGee wrote:
On Fri, Feb 5, 2010 at 4:08 PM, clemens fischer wrote:
I'm updating the pacman database about once a day. For the last few days I always get this message:
"too much happens:: Synchronizing package databases..."
but everything works fine. I checked usr/bin/pacman, /usr/lib/libalpm.so.4 and usr/sbin/fcron using strings(1) for the text "much", but no hits.
What's happening here?
Showing the command you are actually running might be a good first start...
Sorry. It's an fcrontab entry: { pacman --noprogressbar -Sy && pacman --noprogressbar -Qu || :; } 2>&1 clemens
On Fri, Feb 5, 2010 at 18:07, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
Sorry. It's an fcrontab entry:
{ pacman --noprogressbar -Sy && pacman --noprogressbar -Qu || :; } 2>&1
clemens
Try it with --debug for more info?
Daenyth Blank wrote:
On Fri, Feb 5, 2010 at 18:07, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
Sorry. It's an fcrontab entry:
{ pacman --noprogressbar -Sy && pacman --noprogressbar -Qu || :; } 2>&1
Try it with --debug for more info?
No chance. 'Cause it went away by itself. How about checking the servers? Does any component of them contain that string "too much happens"? I can imagine many people accessed the package servers due to the libpng* updates. clemens
On Sun, Feb 7, 2010 at 2:32 PM, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
Daenyth Blank wrote:
On Fri, Feb 5, 2010 at 18:07, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
Sorry. It's an fcrontab entry:
{ pacman --noprogressbar -Sy && pacman --noprogressbar -Qu || :; } 2>&1
Try it with --debug for more info?
No chance. 'Cause it went away by itself. How about checking the servers? Does any component of them contain that string "too much happens"? I can imagine many people accessed the package servers due to the libpng* updates.
Could it be a message from cron itself?
On Sun, Feb 7, 2010 at 11:00 PM, Aaron Griffin <aaronmgriffin@gmail.com>wrote:
On Sun, Feb 7, 2010 at 2:32 PM, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
Daenyth Blank wrote:
On Fri, Feb 5, 2010 at 18:07, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
Sorry. It's an fcrontab entry:
{ pacman --noprogressbar -Sy && pacman --noprogressbar -Qu || :; } 2>&1
Try it with --debug for more info?
No chance. 'Cause it went away by itself. How about checking the servers? Does any component of them contain that string "too much happens"? I can imagine many people accessed the package servers due to the libpng* updates.
Could it be a message from cron itself?
I did a quick grep on the pacman sources and it found no occurences of that string.
Aaron Griffin wrote:
Could it be a message from cron itself?
No, you might have read in my original post that I grepped for the string in fcron, pacman and libalpm, as well as the libc. clemens
On Sun, Feb 7, 2010 at 15:32, clemens fischer <ino-news@spotteswoode.dnsalias.org> wrote:
No chance. 'Cause it went away by itself. How about checking the servers? Does any component of them contain that string "too much happens"? I can imagine many people accessed the package servers due to the libpng* updates.
clemens
Maybe it's an error from your download agent if you're not using libfetch in pacman?
Daenyth Blank wrote:
Maybe it's an error from your download agent if you're not using libfetch in pacman?
Not that, either. I'm using no download agent. I wonder why it went away a few days ago. Does anybody else use "http://ftp.tu-chemnitz.de/pub/linux/archlinux/" or "http://ftp.uni-bayreuth.de/linux/" as pacman mirrors? Might well be that it is a message from their servers putting me off for overload. But its funny that everything worked, except for this message ... clemens
clemens fischer wrote:
"too much happens:: Synchronizing package databases..."
It was my fault after all. Maybe you'd have found it, if I had posted the entire fcrontab command: @mail(1),first(5) 8h ${tellit} "pacman sync"; \ { pacman --noprogressbar -Sy && pacman --noprogressbar -Qu || :; } 2>&1 and ${tellit} is: tellit="/root/bin/screen_backtick.sh -u root -b0" and screen_backtick.sh calls my very own eventlogger, which is a shell interface to mq_overview(7), the posix message queues. There are a number of writers in my systems sending status messages to be displayed in the screen/tmux status line. After switching to tmux, I increased the rate at which these messages are dequeued and displayed, so the queues filled up. There's resource limiter in eventlogger: if too many messages are queued, the STORM pseudo-message is shown to indicate an error. It so happens that STORM is set to "too much happens". I should have known better: If I am the only person with some problem, it just might be my fault ... clemens
clemens fischer wrote:
... After switching to tmux, I increased the rate at which these messages are dequeued and displayed, so the queues filled up.
Actually, I _decreased_ the dequeuing rate, and that's why they filled up. Sigh. clemens
participants (5)
-
Aaron Griffin
-
André Ramaciotti
-
clemens fischer
-
Daenyth Blank
-
Dan McGee