* [gentoo-user] strange alarm signal
@ 2012-02-01 9:05 Thanasis
2012-02-01 21:21 ` Matthias Krebs
0 siblings, 1 reply; 3+ messages in thread
From: Thanasis @ 2012-02-01 9:05 UTC (permalink / raw
To: gentoo-user
Has anyone ever seen the following strange behaviour?
While updating the system with emerge, after each installation of a
package, before it starts emerging the next one, it pauses for a minute
or two, then displays "alarm signal" (without the quotes) on a new line,
and continues to emerging the next package.
Here is an example:
>>> Emerging (2 of 9) perl-core/IPC-Cmd-0.760.0
* IPC-Cmd-0.76.tar.gz RMD160 SHA1 SHA256 size ;-) ...
[ ok ]
>>> Unpacking source...
>>> Unpacking IPC-Cmd-0.76.tar.gz to
/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work
>>> Source unpacked in /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work
>>> Preparing source in
/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work/IPC-Cmd-0.76 ...
>>> Source prepared.
>>> Configuring source in
/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work/IPC-Cmd-0.76 ...
* Using ExtUtils::MakeMaker
* perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none
DESTDIR=/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/image/
Checking if your kit is complete...
Looks good
Writing Makefile for IPC::Cmd
Writing MYMETA.yml and MYMETA.json
>>> Source configured.
>>> Compiling source in
/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work/IPC-Cmd-0.76 ...
* emake OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed
make -j5 'OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed'
cp lib/IPC/Cmd.pm blib/lib/IPC/Cmd.pm
>>> Source compiled.
>>> Test phase [not enabled]: perl-core/IPC-Cmd-0.760.0
>>> Install IPC-Cmd-0.760.0 into
/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/image/ category perl-core
make -j5 pure_install
Installing
/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/image/usr/lib64/perl5/vendor_perl/5.12.4/IPC/Cmd.pm
>>> Completed installing IPC-Cmd-0.760.0 into
/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/image/
ecompressdir: bzip2 -9 /usr/share/doc
>>> Done.
>>> Installing (2 of 9) perl-core/IPC-Cmd-0.760.0
alarm signal
>>> Emerging (3 of 9) virtual/perl-IPC-Cmd-0.760.0
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/virtual/perl-IPC-Cmd-0.760.0/work
>>> Compiling source in
/var/tmp/portage/virtual/perl-IPC-Cmd-0.760.0/work ...
>>> Source compiled.
>>> Test phase [not enabled]: virtual/perl-IPC-Cmd-0.760.0
>>> Install perl-IPC-Cmd-0.760.0 into
/var/tmp/portage/virtual/perl-IPC-Cmd-0.760.0/image/ category virtual
>>> Completed installing perl-IPC-Cmd-0.760.0 into
/var/tmp/portage/virtual/perl-IPC-Cmd-0.760.0/image/
>>> Done.
>>> Installing (3 of 9) virtual/perl-IPC-Cmd-0.760.0
alarm signal
>>> Emerging (4 of 9) x11-libs/pixman-0.24.2
....
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [gentoo-user] strange alarm signal
2012-02-01 9:05 [gentoo-user] strange alarm signal Thanasis
@ 2012-02-01 21:21 ` Matthias Krebs
2012-02-01 22:03 ` Thanasis
0 siblings, 1 reply; 3+ messages in thread
From: Matthias Krebs @ 2012-02-01 21:21 UTC (permalink / raw
To: gentoo-user
On 02/01/2012 10:05 AM, Thanasis wrote:
> Has anyone ever seen the following strange behaviour?
> While updating the system with emerge, after each installation of a
> package, before it starts emerging the next one, it pauses for a minute
> or two, then displays "alarm signal" (without the quotes) on a new line,
> and continues to emerging the next package.
Hi Thanasis,
this message is from emerge /portage:
grep -r "alarm signal" /usr/lib64/portage/*
Binary file /usr/lib64/portage/pym/portage/exception.pyo matches
Binary file /usr/lib64/portage/pym/portage/exception.pyc matches
/usr/lib64/portage/pym/portage/exception.py: raise
AlarmSignal("alarm signal",
This one matches your one minute:
/usr/lib64/portage/pym/portage/elog/mod_mail_summary.py:
AlarmSignal.register(60)
Look like a timeout during mail sending to me. You have probably elog
mail sending configured in make.conf and your mailserver is borked.
HTH,
Matthias
> Here is an example:
>
>>>> Emerging (2 of 9) perl-core/IPC-Cmd-0.760.0
> * IPC-Cmd-0.76.tar.gz RMD160 SHA1 SHA256 size ;-) ...
>
> [ ok ]
>>>> Unpacking source...
>>>> Unpacking IPC-Cmd-0.76.tar.gz to
> /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work
>>>> Source unpacked in /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work
>>>> Preparing source in
> /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work/IPC-Cmd-0.76 ...
>>>> Source prepared.
>>>> Configuring source in
> /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work/IPC-Cmd-0.76 ...
> * Using ExtUtils::MakeMaker
> * perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none
> DESTDIR=/var/tmp/portage/perl-core/IPC-Cmd-0.760.0/image/
> Checking if your kit is complete...
> Looks good
> Writing Makefile for IPC::Cmd
> Writing MYMETA.yml and MYMETA.json
>>>> Source configured.
>>>> Compiling source in
> /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/work/IPC-Cmd-0.76 ...
> * emake OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed
> make -j5 'OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed'
> cp lib/IPC/Cmd.pm blib/lib/IPC/Cmd.pm
>>>> Source compiled.
>>>> Test phase [not enabled]: perl-core/IPC-Cmd-0.760.0
>>>> Install IPC-Cmd-0.760.0 into
> /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/image/ category perl-core
> make -j5 pure_install
> Installing
> /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/image/usr/lib64/perl5/vendor_perl/5.12.4/IPC/Cmd.pm
>>>> Completed installing IPC-Cmd-0.760.0 into
> /var/tmp/portage/perl-core/IPC-Cmd-0.760.0/image/
>
> ecompressdir: bzip2 -9 /usr/share/doc
>>>> Done.
>>>> Installing (2 of 9) perl-core/IPC-Cmd-0.760.0
> alarm signal
>
>>>> Emerging (3 of 9) virtual/perl-IPC-Cmd-0.760.0
>>>> Unpacking source...
>>>> Source unpacked in /var/tmp/portage/virtual/perl-IPC-Cmd-0.760.0/work
>>>> Compiling source in
> /var/tmp/portage/virtual/perl-IPC-Cmd-0.760.0/work ...
>>>> Source compiled.
>>>> Test phase [not enabled]: virtual/perl-IPC-Cmd-0.760.0
>>>> Install perl-IPC-Cmd-0.760.0 into
> /var/tmp/portage/virtual/perl-IPC-Cmd-0.760.0/image/ category virtual
>>>> Completed installing perl-IPC-Cmd-0.760.0 into
> /var/tmp/portage/virtual/perl-IPC-Cmd-0.760.0/image/
>
>>>> Done.
>>>> Installing (3 of 9) virtual/perl-IPC-Cmd-0.760.0
> alarm signal
>
>>>> Emerging (4 of 9) x11-libs/pixman-0.24.2
> ....
>
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [gentoo-user] strange alarm signal
2012-02-01 21:21 ` Matthias Krebs
@ 2012-02-01 22:03 ` Thanasis
0 siblings, 0 replies; 3+ messages in thread
From: Thanasis @ 2012-02-01 22:03 UTC (permalink / raw
To: gentoo-user
on 02/01/2012 11:21 PM Matthias Krebs wrote the following:
> On 02/01/2012 10:05 AM, Thanasis wrote:
>> Has anyone ever seen the following strange behaviour?
>> While updating the system with emerge, after each installation of a
>> package, before it starts emerging the next one, it pauses for a minute
>> or two, then displays "alarm signal" (without the quotes) on a new line,
>> and continues to emerging the next package.
> Hi Thanasis,
>
> this message is from emerge /portage:
> grep -r "alarm signal" /usr/lib64/portage/*
> Binary file /usr/lib64/portage/pym/portage/exception.pyo matches
> Binary file /usr/lib64/portage/pym/portage/exception.pyc matches
> /usr/lib64/portage/pym/portage/exception.py: raise
> AlarmSignal("alarm signal",
>
> This one matches your one minute:
> /usr/lib64/portage/pym/portage/elog/mod_mail_summary.py:
> AlarmSignal.register(60)
>
> Look like a timeout during mail sending to me. You have probably elog
> mail sending configured in make.conf and your mailserver is borked.
>
You were right. I hadn't configured the /etc/mail/aliases file.
Thanks !
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-02-01 22:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-01 9:05 [gentoo-user] strange alarm signal Thanasis
2012-02-01 21:21 ` Matthias Krebs
2012-02-01 22:03 ` Thanasis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox