Log of emerge readable output produced somewhere?

Message

nmbrthry · Post by **nmbrthry** » Fri Jun 02, 2006 5:03 pm

synss and I have a PyGTK program for more easily reading the elog files produced by Portage. See this topic for more information.

XenoTerraCide · Post by **XenoTerraCide** » Fri Jun 02, 2006 7:05 pm

is elog going to get a manpage? or become part of another one? I want to know exactly what the different levels are logging.

XenoTerraCide · Post by **XenoTerraCide** » Fri Jun 02, 2006 7:13 pm

how do you get it to log only the *green and *orange messages? I seem to be getting a lot of... things in the logs I don't want. like

Code: Select all

checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... i686-pc-linux-gnu-g++ -E
checking for i686-pc-linux-gnu-g77... i686-pc-linux-gnu-g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether i686-pc-linux-gnu-g77 accepts -g... yes
checking the maximum length of command line arguments..

frankly I don't care about any of that unless it breaks.

XenoTerraCide · Post by **XenoTerraCide** » Fri Jun 02, 2006 7:17 pm

can you limit or rotate the logs for elog? the only kind of documentation I find for it is make.conf.example and that's far from being very helpful.

dalek · Post by **dalek** » Sun Jun 25, 2006 6:41 am

XenoTerraCide wrote:can you limit or rotate the logs for elog? the only kind of documentation I find for it is make.conf.example and that's far from being very helpful.

I'm trying to figure mine out too. I use logrotate to keep down the size and age of my files. It works pretty well, does what it should for sure. Just wish it would rotate my dirty dishes to the dishwasher.

Aule · Post by **Aule** » Thu Jun 29, 2006 1:33 pm

dalek wrote:
XenoTerraCide wrote:can you limit or rotate the logs for elog? the only kind of documentation I find for it is make.conf.example and that's far from being very helpful.
I'm trying to figure mine out too. I use logrotate to keep down the size and age of my files. It works pretty well, does what it should for sure. Just wish it would rotate my dirty dishes to the dishwasher.

Could you please post your /etc/logrotate.d/[whatever]?

Aule

dalek · Post by **dalek** » Thu Jun 29, 2006 3:29 pm

Aule wrote:Could you please post your /etc/logrotate.d/[whatever]?

Aule

/etc/logrotate.d/emerge.log

Code: Select all

/var/log/emerge.log {
	size 1000k
	monthly
	rotate 5
	missingok
	copytruncate
	compress
}

Now if I could just get it to leave the last couple weeks worth instead of blanking it out.

It should compress it when it gets to 1MB or once a month, whichever comes first. It should also delete the old ones that are more than 5 months old. That's my theory anyway.

Hope that helps.

AndrewWilcox · Post by **AndrewWilcox** » Sun Jul 16, 2006 2:31 pm

I'm running Portage 2.1-r1, and following the instructions in /etc/make.conf.example I tried to set up emerge logging:

/etc/make.conf:

PORTAGE_ELOG_SYSTEM="save"
PORT_LOGDIR=/var/log/portage
PORTAGE_ELOG_CLASSES="error"

The settings appear to be being used:

# emerge --info --verbose | grep LOG
HUSHLOGIN="FALSE"
LOGNAME="root"
PORTAGE_ELOG_CLASSES="error"
PORTAGE_ELOG_MAILFROM="portage"
PORTAGE_ELOG_MAILSUBJECT="[portage] ebuild log for ${PACKAGE} on ${HOST}"
PORTAGE_ELOG_MAILURI="root"
PORTAGE_ELOG_SYSTEM="save"
PORT_LOGDIR="/var/log/portage"

However, in the log file produced I get all the output from the emerge, regardless of what I set PORTAGE_ELOG_CLASSES to.

I desperately need to see the important informational messages that an emerge produces, without the clutter of all the downloading, configuring, and compiling output.

Can you help?

Thank you,

Andrew

thoughtform · Post by **thoughtform** » Mon Aug 14, 2006 3:51 am

Andrew did you get an answer? I'm looking for this solution, too.
Thanks.

AndrewWilcox · Post by **AndrewWilcox** » Mon Aug 14, 2006 10:38 am

Scorpaen wrote:Andrew did you get an answer? I'm looking for this solution, too.
Thanks.

Not here, but in a Linux.com article (http://www.linux.com/article.pl?sid=06/08/07/1952207) I saw a link to a thread in these forums on graphical front ends to emerge logs (http://forums.gentoo.org/viewtopic-t-465493.html) Haven't had a chance to look at them yet.

Andrew

Genone · Post by **Genone** » Mon Aug 14, 2006 12:46 pm

If you don't want the full logs then don't set PORT_LOGDIR.
Anyway, the elog logfiles are in $PORT_LOGDIR/elog (/var/log/portage/elog if $PORT_LOGDIR is unset or empty)

stevit · Post by **stevit** » Thu Aug 17, 2006 3:23 am

I wrote a smal script for the elog custom command.
In my opinion those path applying infos are quite uninteresting, etc
but there is no way to deaktivate them and still get those infos what
you most likely shoukd do after merging your pakets.
So.... it's nothing big, some colours, filtering, piping, etc.
but the escaping of special chars took some time...
so perhaps someone finds it useful and don't have to build something like that on his own.

smals and simple emerge log summery on your ttys:

Code: Select all

PORTAGE_ELOG_CLASSES="warn error info"		# http://www.gentoo.de/main/de/portage-2.1.xml
PORTAGE_ELOG_SYSTEM="save custom"           # save, syslog, mail, custom

PORTAGE_ELOG_COMMAND= 				# some log-message formating... > /dev/tty11
   # if logfile exists....
   " if [ -f '\${LOGFILE}' ] ; then  
	   echo -e '\\n\\033[32m'`date '+%d %b - %T:'` '\\033[1;31m''\${PACKAGE}': '\\033[m' > /dev/tty11;
	   cat \${LOGFILE}  | egrep -v '(Running)|(Applying)|(INFO:)|(WARN:)|(^[:space:]*\$)' > /dev/tty11;
	   exit 0;	  
     fi" # exit with no errors... grep would "exit 1" on no matches

jorgepeixoto · Post by **jorgepeixoto** » Thu Aug 17, 2006 9:35 pm

My /var/log/portage is currently 253 MB. Is it ok/safe for me to delete some files in it (there are a couple of files that are really large) ?

stevit · Post by **stevit** » Thu Aug 17, 2006 10:22 pm

I delete the content of my /var/log/portage regulary.
So far nothing bad happend.

Perhaps try to avoid removing directories for e.g. /var/log/portage/elog or /var/log/portage itself.
All files within should be quite compensable (as long as there is no current emerge running).

Post by **kallamej** » Fri Aug 18, 2006 8:36 am

The full build logs are typically useful only when you want to debug a build afterwards, for instance if a build error is no longer in your scroll buffer.

juniper · Post by **juniper** » Sun Aug 20, 2006 3:35 pm

i made a post and it was locked saying that it was answered in this thread. well, i can't see the answer anywhere, so i will ask it again.

sometime when a package is emerged there is a little warning at the end, saying something like "run env-update". i think this information is stored in the ebuild as an "einfo".

is there a way to view this info with a command? like

<command> ebuild

and it pops out all the einfos?

Post by **kallamej** » Sun Aug 20, 2006 4:05 pm

The suggestion to run etc-update is displayed after every emerge if there are files under config protection to update. It has nothing to do with einfo. The e{info,warn,error,log} messages you see while emerging is often USE flag dependant and watching them all for an ebuild is not always relevant. Anyway,

Code: Select all

grep -E 'einfo|ewarn,eerror,elog' /path/to/ebuild

will show them all, albeit losing most context. Setup the elog framwork to your liking to see it after an emerge.

juniper · Post by **juniper** » Sun Aug 20, 2006 5:03 pm

i don't really want to see it after an emerge, i want to see it whenever i feel like it.

i thought that was maybe a command. i guess i will use grep.

rwf · Post by **rwf** » Fri Sep 15, 2006 11:35 pm

File names changed in /var/log/portage (PORT_LOGDIR)?

A snippet from my /var/log/portage directory (emacs dired)

Code: Select all

  -rw-r--r-- 1 root    portage   882 Sep 12 18:33 7137-portage-2.1.1.log
  -rw-r--r-- 1 root    portage     0 Sep 12 18:33 7138-portage-2.1-r2.log
  -rw-r--r-- 1 root    portage   534 Sep 12 18:33 7138-portage-2.1.1.log
  -rw-r--r-- 1 root    portage  123K Sep 14 10:46 app-admin:gnome-system-tools-2.14.0:20060914-173330.log
  -rw-r--r-- 1 root    portage   464 Sep 14 10:45 app-admin:gnome-system-tools-2.14.0:20060914-174527.log
  -rw-r--r-- 1 root    portage   14K Sep 14 10:47 app-admin:gnomesu-0.3.1:20060914-174633.log

The previous file format was date sequential. That way I could check the log's after a emerge --sync and emerge -avuDN world to see if any nice advisories were issused i.e.

Code: Select all

 * You must re-compile all packages that are linked against
 * OpenSSL 0.9.7 by using revdep-rebuild from gentoolkit:
 * # revdep-rebuild --library libssl.so.0.9.7
 * # revdep-rebuild --library libcrypto.so.0.9.7
 * After this, you can delete /usr/lib/libssl.so.0.9.7 
 * and /usr/lib/libcrypto.so.0.9.7

The 'new' format does not lend itself to scanning by date. Did I miss something?

Genone · Post by **Genone** » Sat Sep 16, 2006 3:48 am

You can still sort the files by date, just use the mtime as sort key (with ls -t for example).

rwf · Post by **rwf** » Sat Sep 16, 2006 6:22 am

Genone wrote:You can still sort the files by date, just use the mtime as sort key (with ls -t for example).

I knew that -- was just wondering why things changed. Somebody might want to update the /etc/make.config.example file which was included with the 2.1.1 portage update -- which caused the change/problem.

Code: Select all

# PORT_LOGDIR is the location where portage will store all the logs it
#     creates from each individual merge. They are stored as NNNN-$PF.log
#     in the directory specified. This is disabled until you enable it by
#     providing a directory. Permissions will be modified as needed IF the
#     directory exists, otherwise logging will be disabled. NNNN is the
#     increment at the time the log is created. Logs are thus sequential.
#PORT_LOGDIR=/var/log/portage

ruivilela · Post by **ruivilela** » Mon Oct 16, 2006 9:02 am

Is it currently possible to see emerge messages after an emerge world. I don't find much info on how to do this, but i know that this is/was planned.

yabbadabbadont · Post by **yabbadabbadont** » Mon Oct 16, 2006 9:08 am

Add "PORT_LOGDIR=/var/log/portage" to /etc/make.conf and all emerge output will be saved in the directory specified. You will need to clear it out manually on occasion.

Edit: That will save *all* output, including the compile. Read the portage man page and /etc/make.conf.example for information on how to only save the info and warning messages.

ruivilela · Post by **ruivilela** » Mon Oct 16, 2006 9:20 am

Thanks for tip. This will save me lot of time with post-install problems.

yabbadabbadont · Post by **yabbadabbadont** » Mon Oct 16, 2006 9:23 am

If you decide to save all output, you might search the forums for a tool called, portlog-info. It is just a shell script that scans through all the files in PORT_LOGDIR and displays the einfo and ewarn messages.

See http://forums.gentoo.org/viewtopic-t-13 ... ginfo.html for more information on this topic.

Log of emerge readable output produced somewhere?

How do I get PORTAGE_ELOG_CLASSES to actually do anything?

Is it ok to delete files in /var/log/portage?

Post-install messages ? [Solved]