[gentoo-user] PORTAGE_ELOG

[gentoo-user] PORTAGE_ELOG

[Daniel Iliev]

Hi, everyone!

I decided to activate the portage ELOG system. I can't make portage send
mail or write in the syslog. "save" appears to be the only working
"PORTAGE_ELOG_SYSTEM" - it saves log files in /var/log/portage for the
emerge activities. The settings relevant to ELOG in my make.conf are:

PORT_LOGDIR=/var/log/portage
PORTAGE_ELOG_CLASSES="info warn error log"
PORTAGE_ELOG_SYSTEM="syslog save mail"
PORTAGE_ELOG_MAILURI="root@localhost localhost"
PORTAGE_ELOG_MAILFROM="portage@localhost"
PORTAGE_ELOG_MAILSUBJECT="\${PACKAGE}"

Please, advise.

Ah! One more thing: I use postfix and syslog-ng. Both of them seem to be
working properly.


-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] PORTAGE_ELOG

[Arnau Bria]

On Mon, 30 Oct 2006 22:28:45 +0200
Daniel Iliev wrote:

> Hi, everyone!
Hi,
I have little to offer to you...
 
> I decided to activate the portage ELOG system. I can't make portage
> send mail or write in the syslog. "save" appears to be the only
> working "PORTAGE_ELOG_SYSTEM" - it saves log files
> in /var/log/portage for the emerge activities. The settings relevant
> to ELOG in my make.conf are: 
> PORT_LOGDIR=/var/log/portage
> PORTAGE_ELOG_CLASSES="info warn error log"
> PORTAGE_ELOG_SYSTEM="syslog save mail"
> PORTAGE_ELOG_MAILURI="root@localhost localhost"
> PORTAGE_ELOG_MAILFROM="portage@localhost"
> PORTAGE_ELOG_MAILSUBJECT="\${PACKAGE}"
> 
> Please, advise.

I have been having problems with same, but using a "real" mail server
(for your root@localhost I assume you're using default postfix install,
am I right?)

I saw the error when a package finished its emerge, then portage told
me that there was a problem with AUTH...
Please, take a look after a package is compiled (not installed) to look
for any special message.
And also, take a look into postfix log file...

> Ah! One more thing: I use postfix and syslog-ng. Both of them seem to
> be working properly.

Cheers!

-- 
Arnau Bria
http://blog.emergetux.net
Wiggum: Dispara a las ruedas Lou.
Lou: eee, es un tanque jefe.
Wiggum: Me tienes hartito con todas tus excusas.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] PORTAGE_ELOG

[Daniel Iliev]

Arnau Bria wrote:
> Hi,
> I have little to offer to you...
>
> I have been having problems with same, but using a "real" mail server
> (for your root@localhost I assume you're using default postfix install,
> am I right?)
>   

Thank you for you response.

1) About the "real" server: Well, "echo test | sendmail -t
root@localhost" works. I assume it should be enough, but I also tried
with "root@realdomain.com realdomain.com" - no change.
2) Yes, it is postfix from the portage. Installed and configured as
described in the official documentation found at:
http://www.gentoo.org/doc/en/mailfilter-guide.xml

> I saw the error when a package finished its emerge, then portage told
> me that there was a problem with AUTH...
> Please, take a look after a package is compiled (not installed) to look
> for any special message.
> And also, take a look into postfix log file...
>   

I see no errors. Neither while emerging, neither in the logs. No problem
with AUTH, because I use IP based policy for email relaying without
authentication.

Now. The things got even more weird and unexplainable for me. I did
"emerge -DuNav world" and there were some font packages to be rebuild
because of a change in the USE flags. After emerge finished I got emails
for the those packages but not a single message in the syslog. Another
thing I noticed is that packages emerged by "emerge -DuNav world" put
their logs in "/var/log/portage/elog/" while all other packages put
their logs in "/var/log/portage/".

Strange. I think I'm missing something simple but important. Any ideas?

-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] PORTAGE_ELOG

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 272 bytes --]

On Tuesday 31 October 2006 15:06, Daniel Iliev wrote:
> 1) About the "real" server: Well, "echo test | sendmail -t
> root@localhost" works.

So why don't you just take advantage of that?

PORTAGE_ELOG_MAILURI="root@localhost /usr/sbin/sendmail"

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] PORTAGE_ELOG

[Daniel Iliev]

Bo Ørsted Andresen wrote:
> On Tuesday 31 October 2006 15:06, Daniel Iliev wrote:
>   
>> 1) About the "real" server: Well, "echo test | sendmail -t
>> root@localhost" works.
>>     
>
> So why don't you just take advantage of that?
>
> PORTAGE_ELOG_MAILURI="root@localhost /usr/sbin/sendmail"
>
>   

Thanks, Bo!

Already tried - no effect.
My guess is that I miss something about the conditions *when* portage
sends mails. I mean how come that all the packages I use to test "ELOG"
with *emerge -C package ; emerge package* write logs in
*/var/log/portage* and only those that are re-emerged with *emerge
-DuNav world* write logs in */var/log/portage/elog* ?



-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] PORTAGE_ELOG

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

On Tue, 31 Oct 2006 16:06:01 +0200, Daniel Iliev wrote:

> Now. The things got even more weird and unexplainable for me. I did
> "emerge -DuNav world" and there were some font packages to be rebuild
> because of a change in the USE flags. After emerge finished I got emails
> for the those packages but not a single message in the syslog. Another
> thing I noticed is that packages emerged by "emerge -DuNav world" put
> their logs in "/var/log/portage/elog/" while all other packages put
> their logs in "/var/log/portage/".

All logs go into $PORT_LOGDIR (usually /var/log/portage) if it is
defined. These are the full output of each emerge command, plus another
file containing the elog/ewarn/einfo/error output. The ELOG files contain
only the e-messages you specify and go in $PORT_LOGDIR/elog. So you
should be seeing logfiles in both if everything is working correctly.

Note that not all ebuilds output e-messages, so you won't get ELOG info
for every package you emerge.


-- 
Neil Bothwick

- We are but packets in the internet of Life-

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] drift: cron, emerge and mail

[Daniel Iliev]

Neil Bothwick wrote:
>
> All logs go into $PORT_LOGDIR (usually /var/log/portage) if it is
> defined. These are the full output of each emerge command, plus another
> file containing the elog/ewarn/einfo/error output. The ELOG files contain
> only the e-messages you specify and go in $PORT_LOGDIR/elog. So you
> should be seeing logfiles in both if everything is working correctly.
>
> Note that not all ebuilds output e-messages, so you won't get ELOG info
> for every package you emerge.
>
>
>   

That was it! Thanks, Neil!

I was testing with "emerge -C tcpdump ; emerge tcpdump". After your mail
i tried "emerge -1 media-fonts/font-adobe-100dpi" and I got mail.

Now here goes my next question: is there a way to get via email the
portage output for all packages?

Let me explain what I'm trying to do. I want to automate "emerge --sync
&& emerge -DuNv world" with a cron job and to receive mails for the
portage activities. I really don't need all the gcc output. I only need
the portage "info warn error" messages in order to know if I have to do
"dispatch-conf", if some package has failed and if there is some
important note about changes in the structure/functionality of a given
package.
Is there a "gentoo way" to achieve this functionality or I have to do it
"my way"?

-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] drift: cron, emerge and mail

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

On Tue, 31 Oct 2006 17:18:03 +0200, Daniel Iliev wrote:

> Let me explain what I'm trying to do. I want to automate "emerge --sync
> && emerge -DuNv world" with a cron job

I'm not sure automating emerge -u world is  good idea. I have a cron task
that does

emerge --sync
emerge -upvDN world | mail
emerge -ufDN world

Then I read the mail and decide on the updates before anything is merged.

> and to receive mails for the
> portage activities. I really don't need all the gcc output. I only need
> the portage "info warn error" messages

PORTAGE_ELOG will do this for you.

> in order to know if I have to do "dispatch-conf",

It won't do this, but "find $(portageq config_protect) -name '._cfg*'"
will. Or you could put it in a script with

if [ "$(find $(portageq config_protect) -name '._cfg*' | wc -l)" != "0" ]
then
	echo "Run dispatch-conf"
fi
 
> if some package has failed and if there is some
> important note about changes in the structure/functionality of a given
> package.

PORTAGE_ELOG will tell you that.


-- 
Neil Bothwick

Madness takes its toll. Exact change, please.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] [SOLVED] drift: cron, emerge and mail

[Daniel Iliev]

Neil Bothwick wrote:
> On Tue, 31 Oct 2006 17:18:03 +0200, Daniel Iliev wrote:
>
>   
>> Let me explain what I'm trying to do. I want to automate "emerge --sync
>> && emerge -DuNv world" with a cron job
>>     
>
> I'm not sure automating emerge -u world is  good idea. I have a cron task
> that does
>
> emerge --sync
> emerge -upvDN world | mail
> emerge -ufDN world
>
> Then I read the mail and decide on the updates before anything is merged.
>   
> --SNIP--
>
>   


Thank you very much, Neil!

I'm going to follow 100% of your advice. It never crossed my stupid mind
that I can automate only reporting and fetching the pending updates
without actually merging them. I also prefer updates to take place in my
presence.


-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list