RE: Sid random crash with no clue in log files

iada: 2020/10/28 14:00:50 Para: debian-user@lists.debian.org Assunto: Re: Sid random crash with no clue in log files On Wed, Oct 28, 2020 at 04:09:33PM +0100, Sébastien Kalt wrote: > Hello, > > I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while > cop

Re: Sid random crash with no clue in log files

going nothing ... > > I can't manage to have a pattern for thoses craches. Today it craches 4 > times, the last week it didn't crash. > > I encoded a video with 100 % CPU charge during one hour and it didn't crash. > > When I look at the log files, I see nothi

Re: Sid random crash with no clue in log files

On Wed, 28 Oct 2020 16:09:33 +0100 Sébastien Kalt wrote: > I'm having random crashes on my ASUS PN50 mini PC : sometimes it's > while copying large files through network, sometimes when watching a > youtube video, sometimes juste using LibreOffice, or going nothing ... > Do you have any suggesti

Re: Sid random crash with no clue in log files

Sébastien Kalt writes: Hello, I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while [...] When it crashes, the system seems to be not responding, I can move the mouse, but it doesn't click, and then the screen becomes blank. I need to shut down the mini PC pushing th

Sid random crash with no clue in log files

es 4 times, the last week it didn't crash. I encoded a video with 100 % CPU charge during one hour and it didn't crash. When I look at the log files, I see nothing : syslog, messages, daemon.log, kern.log, Xorg.0.log.old, dmesg When it crashes, the system seems to be not responding, I c

Re: OT: the art of reviewing unix log files

On Mon, 1 Jun 2020, l0f...@tuta.io wrote: [dd] Having an appropriate tool helps a lot: https://lnav.org/ lnav - ncurses-based log file viewer The log file navigator, lnav, is an enhanced log file viewer that takes advantage of any semantic information that can be gleaned from the files b

Re: OT: the art of reviewing unix log files

Hi, 1 juin 2020 à 09:43 de david...@freevolt.org: > On the topic of reviewing unix log files, what have you read before > and found useful later? > Having an appropriate tool helps a lot: https://lnav.org/ Best regards, l0f4r0

OT: the art of reviewing unix log files

On the topic of reviewing unix log files, what have you read before and found useful later? -- https://news.ycombinator.com/item?id=12518471 alexk already addressed your concern: your keys, preferably issued by your org's CA (instead of being generated by you) should be short-lived, often

Re: Correlation between Log Files and Display Report?

Dear Sir, Prof. Greg Wooledge, Thank you very much for your kind reply. I have been aware of rsyslog and rsyslog.conf. The part that directs writing of the log files, such as, kern.log, syslog, user.log and so on, within /var/log/ folder. Now my Next Query: Have you been to, and perused, the

Re: Correlation between Log Files and Display Report?

f us have more experience in specific areas. > I had posted the following email to the two lists, boot and kernel, > with the query below. Kindly help me draw a correlation between error > display on the monitor and the log files, such as, kern.log, syslog, > user.log and so on, within

Correlation between Log Files and Display Report?

To, The Team Debian User, Debian.org Dear Sirs, our illustrious List Maintainers, I had posted the following email to the two lists, boot and kernel, with the query below. Kindly help me draw a correlation between error display on the monitor and the log files, such as, kern.log, syslog

Re: Suppress error message to log files

Hi, On Mon, Feb 04, 2019 at 02:42:51PM -0600, sel...@midwest.net wrote: > Play one game and > > This entry found in /var/log/{messages,syslog,user.log}: > Jan 26 00:55:23 debian quadrapassel[5542]: > ../../../../../gdk/x11/gdkwindow-x11.c:5611 > drawable is not a native X11 window […] >

Suppress error message to log files

(250K-13K) * 3 filling the log files per game. How do I suppress the posting of this "error".

Re: Log files: location and description

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 09, 2017 at 09:02:12AM -0400, Greg Wooledge wrote: > On Sun, Oct 08, 2017 at 02:38:21PM +0200, to...@tuxteam.de wrote: > > It's a shell feature: if you do "set -x" in a shell script, all the > > commands in the current shell get transcribed

Re: Log files: location and description

On Sun, Oct 08, 2017 at 02:38:21PM +0200, to...@tuxteam.de wrote: > It's a shell feature: if you do "set -x" in a shell script, all the > commands in the current shell get transcribed (to stdout, I think). To stderr by default, but bash lets you set the BASH_XTRACEFD variable to send it elsewhere.

Debian-installer writes /dev/ references in grub.cfg, was Re: Log files: location and description

On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: > My current problem is finding the appropriate logs to document the > details behind my addendum to Bug 852323. Looking at the grub.cfg written by stretch's d-i RC3, it appears to write linux /boot/vmlinuz-4.9.0-2-686 root=

Re: Log files: location and description

D stuff, > >it might be worth pointing out that it has been reported here that > >a USB3 stick inserted at boot can demote the internal disk to > >/dev/sdb. No idea if that's relevant here unless you're using > >/dev/sdX without actually checking the by-id values that

Re: Log files: location and description

On 10/08/2017 09:40 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 08:58:11AM -0500, Richard Owlett wrote: On 10/08/2017 07:38 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 07:31:23AM -0500,

Re: Log files: location and description

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 08:58:11AM -0500, Richard Owlett wrote: > On 10/08/2017 07:38 AM, to...@tuxteam.de wrote: > >-BEGIN PGP SIGNED MESSAGE- > >Hash: SHA1 > > > >On Sun, Oct 08, 2017 at 07:31:23AM -0500, Richard Owlett wrote: [...] > >In a

Re: Log files: location and description

On 10/08/2017 07:38 AM, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 07:31:23AM -0500, Richard Owlett wrote: On 10/07/2017 03:01 PM, David Wright wrote: On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: [...] No idea about the oth

Re: Log files: location and description

On 10/07/2017 03:01 PM, David Wright wrote: On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: [snip] I have a hypothesis, but I need to have facts to back it up. Specifically: 1. During the installation process I need to inventory when and "as what" various USB devices are recogn

Re: Log files: location and description

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Oct 08, 2017 at 07:31:23AM -0500, Richard Owlett wrote: > On 10/07/2017 03:01 PM, David Wright wrote: > >On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: [...] No idea about the other things, but: > I don't understand. > Accordi

Re: Log files: location and description

ing the by-id values that d-i displays in the relevant places. I was suspecting something similar but instead of vainly attempting to describe it on my own I wanted to quote log files. My USB3 device is a WiFi Hotspot. IIRC it can initially be recognized as a memory device before it initializes. I

Re: HD device name assignments (was: Log files: location and description)

David Wright composed on 2017-10-07 15:01 (UTC-0500): > it might be worth pointing out that it has been reported here that > a USB3 stick inserted at boot can demote the internal disk to > /dev/sdb. It need not be v3 of USB, and it's one of the prime reasons alternatives to booting by device nam

Re: Log files: location and description

On Sat 07 Oct 2017 at 09:36:37 (-0500), Richard Owlett wrote: > I'm looking for a comprehensive catalog of log files giving > location, name, and one line description. I've Googled and found > bits and pieces that are too narrowly focused. To paraphrase my > situation, I

Log files: location and description

I'm looking for a comprehensive catalog of log files giving location, name, and one line description. I've Googled and found bits and pieces that are too narrowly focused. To paraphrase my situation, I'm not only not seeing the forest for the trees -- I'm also not seeing

Re: shell script removing log files.

On Lu, 22 dec 14, 10:51:26, pe...@easthope.ca wrote: > This command in a shell script removes unwanted log files. > > for i in $( echo *.Log ); do > /bin/rm $i; > echo "Removed $i." > done > > In the edge case of no matching files, rm complains. > /b

Re: shell script removing log files.

On Mon, Dec 22, 2014 at 10:51:26AM -0800, pe...@easthope.ca wrote: > This command in a shell script removes unwanted log files. > > for i in $( echo *.Log ); do > /bin/rm $i; > echo "Removed $i." > done > > In the edge case of no matching files, rm c

Re: shell script removing log files.

On 22/12/14 19:51, pe...@easthope.ca wrote: > This command in a shell script removes unwanted log files. > > for i in $( echo *.Log ); do > /bin/rm $i; > echo "Removed $i." > done > > In the edge case of no matching files, rm complains. > /bin/rm: c

Re: shell script removing log files.

On 12/22/2014 at 01:51 PM, pe...@easthope.ca wrote: > This command in a shell script removes unwanted log files. > > for i in $( echo *.Log ); do > /bin/rm $i; > echo "Removed $i." > done > > In the edge case of no matching files, rm complains. > /b

shell script removing log files.

This command in a shell script removes unwanted log files. for i in $( echo *.Log ); do /bin/rm $i; echo "Removed $i." done In the edge case of no matching files, rm complains. /bin/rm: cannot remove `*.Log': No such file or directory If echo is replaced with ls, it compl

Re: Vanished log files after reboot

On Du, 26 oct 14, 13:04:39, mad wrote: > Hi! > > After a reboot of a virtual machine *all* old log files in /var/log and > directories under that are gone (.1, .2.gz, ...). Please post the output of 'df -hf' from inside the VM. Kind regards, Andrei -- http://wiki.debian.

Vanished log files after reboot

Hi! After a reboot of a virtual machine *all* old log files in /var/log and directories under that are gone (.1, .2.gz, ...). Does anyone know how that might happen? I already checked the VM for root kits and I certainly can't remember configuring something like that. TIA mad -

Re: logrotate cannot rotate some log files

On 15/06/2014 10:49 AM, André Nunes Batista wrote: > # logrotate -f -v /etc/logrotate.d/ 2> logrotate.txt > > # cat logrotate.txt | grep syslog > reading config file rsyslog > rotating pattern: /var/log/syslog > considering log /var/log/syslog > rotating log /var/log/syslog, log->rotateCount is 7

Re: logrotate cannot rotate some log files

On Sat, 14 Jun 2014 21:49:35 -0300 André Nunes Batista wrote: > 0 -rw-r- 1 root adm 0 Feb 9 07:35 /var/log/syslog.1.gz Move out syslog* to another place and restart syslog (looks like you have a hole in file numbering). If that doesn't work, try to reinstall logrotate and rsyslog (or switc

logrotate cannot rotate some log files

Hello debianers! I recently noticed that some log files on a wheezy box are not being rotated anymore and are getting rather large. I went through logrotate.conf and logrotate.d and did not spot anything wrong. When I run logrotate -f -v /etc/logrotate.conf, some error messages are shown, but

Re: Postfix not writing to mail log files on wheezy system.

peter green wrote: While attempting to look into a mail issue on one of my machines I noticed that /var/log/mail/mail.log did not appear to have been updated since december. I belive that this may have been triggered by an upgrade from squeeze to wheezy but I don't remember exactly when I upg

Postfix not writing to mail log files on wheezy system.

While attempting to look into a mail issue on one of my machines I noticed that /var/log/mail/mail.log did not appear to have been updated since december. I belive that this may have been triggered by an upgrade from squeeze to wheezy but I don't remember exactly when I upgraded the machine.

tor-arm - unable to read tor log files

arm gives the following error: [ARM_WARN] Unable to read tor's log file: /var/log/tor/log [1 duplicate hidden] I created the tor-arm user as suggested. The log file dir /var/log/tor is ownership debian-tor.debian-tor The log files /var/log/tor/log are ownership debian-tor.adm Am I suppos

Re: gibberish in log files

On Wed, 2012-12-26 at 23:52 +0100, Sven Hartge wrote: > Ross Boylan wrote: > > > *Dec 15 23:35:43 corn kernel: sf omt"."wt tnadjunl<>2851760]RieF:d-4 sn ree > > aamd > > *Dec 15 23:35:43 corn kernel: 5[544.113 esrS m4:junlprm:dvc m4,sz 12 ora is > > lc 8 a rn e 04 a ac 0,mxcmi g 0 a rn g 0<>285

Re: gibberish in log files

Ross Boylan wrote: > *Dec 15 23:35:43 corn kernel: sf omt"."wt tnadjunl<>2851760]RieF:d-4 sn ree > aamd > *Dec 15 23:35:43 corn kernel: 5[544.113 esrS m4:junlprm:dvc m4,sz 12 ora is > lc 8 a rn e 04 a ac 0,mxcmi g 0 a rn g 0<>2851773]RieF:d-4 hcigtascinlg(m4)nr > aht otnms<5>[2584541.845130] R

gibberish in log files

For awhile, maybe a month, my logs sometimes contain garbage like this (lines with * in front): Dec 15 23:35:42 corn kernel: [2584540.069530] ext3_orphan_cleanup: deleting unreferenced inode 79901 Dec 15 23:35:42 corn kernel: [2584540.069530] EXT3-fs: dm-43: 43 orphan inodes deleted Dec 15 23:35:

Re: Rotation of Xorg log files

On 2012-06-17 17:42:07 +0100, Alan Chandler wrote: > On 17/06/12 12:53, Camaleón wrote: > >On Sun, 17 Jun 2012 06:23:44 +0100, Alan Chandler wrote: > > > >>Can anyone tell me what is supposed to be rotating (and cleaning Xorg > >>log files). I've just notice

Re: Rotation of Xorg log files

On 17/06/12 12:53, Camaleón wrote: On Sun, 17 Jun 2012 06:23:44 +0100, Alan Chandler wrote: Can anyone tell me what is supposed to be rotating (and cleaning Xorg log files). I've just noticed /var/log contains about 540 versions of the log I experienced something similar in my Wheezy s

Re: Rotation of Xorg log files

On Sun, 17 Jun 2012 06:23:44 +0100, Alan Chandler wrote: > Can anyone tell me what is supposed to be rotating (and cleaning Xorg > log files). I've just noticed /var/log contains about 540 versions of > the log I experienced something similar in my Wheezy system... IIRC it happen

Re: Rotation of Xorg log files

On Sun, 2012-06-17 at 08:07 +0100, Alan Chandler wrote: > [snip] (II) intel: Driver for Intel Integrated Graphics Chipsets: > [snip] Fatal server error: > [ 32068.412] xf86OpenConsole: Cannot find a free VT > [snip] Did you read one of the Google hits regarding to "Cannot find a free VT" that unf

Re: Rotation of Xorg log files

Hello Excerpt from Ralf Mardorf: > On Sun, 2012-06-17 at 06:23 +0100, Alan Chandler wrote: >> Can anyone tell me what is supposed to be rotating (and cleaning Xorg >> log files). I've just noticed /var/log contains about 540 versions of >> the log > > Wow,

Re: Rotation of Xorg log files

On 17/06/12 06:36, Ralf Mardorf wrote: On Sun, 2012-06-17 at 06:23 +0100, Alan Chandler wrote: Can anyone tell me what is supposed to be rotating (and cleaning Xorg log files). I've just noticed /var/log contains about 540 versions of the log Wow, fortunately my X logs for Debian are li

Re: Rotation of Xorg log files

On Sun, 2012-06-17 at 06:23 +0100, Alan Chandler wrote: > Can anyone tell me what is supposed to be rotating (and cleaning Xorg > log files). I've just noticed /var/log contains about 540 versions of > the log Wow, fortunately my X logs for Debian are limited to spinymouse

Rotation of Xorg log files

Can anyone tell me what is supposed to be rotating (and cleaning Xorg log files). I've just noticed /var/log contains about 540 versions of the log -- Alan Chandler http://www.chandlerfamily.org.uk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subje

Re: How to read log files

> I just came across a page that might help you with the subject. > > > > I was looking for something else and stumbled across this. > Thanks, Wayne! That page has already been read and bookmarked long ago! -- Dotan Cohen http://bido.com http://what-is-

Re: How to read log files

Dotan Cohen wrote: Mar 28 09:14:19 sfd kernel: [ Â Â 0.00] Linux version 2.6.31-20-generic (bui...@palmer) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010 (Ubuntu 2.6.31-20.58-generic) Doesn't look like Debian to me... Ubuntu is a Debian derivativ

Re: How to read log files

>>> xgrep () { grep -i "$1" $(echo $PATH | tr ":" " ") ; } >>> >> Nice. I'm having a hard time understanding that last one, but I will >> figure it out. Thanks! >> > It looks like it takes the PATH environment variable and splits it into > multiple tokens (directories), and grep will search in *eve

Re: How to read log files

On 2.4.2010 1:45, Dotan Cohen wrote: >> etcgrep () { grep -ir "$1" /etc/* ; } >> sgrep () { grep -ir "$1" /usr/src/linux ; } >> xgrep () { grep -i "$1" $(echo $PATH | tr ":" " ") ; } >> > > Nice. I'm having a hard time understanding that last one, but I will > figure it out. Thanks! > > It look

Re: How to read log files

> etcgrep () { grep -ir "$1" /etc/* ; } > sgrep () { grep -ir "$1" /usr/src/linux ; } > xgrep () { grep -i "$1" $(echo $PATH | tr ":" " ") ; } > Nice. I'm having a hard time understanding that last one, but I will figure it out. Thanks! -- Dotan Cohen http://bido.com http://what-is-what.com

Re: How to read log files

On Wed, Mar 31, 2010 at 08:00:18PM +0300, Dotan Cohen wrote: > > That was quite what I asked: where could I read more on the subject? > Dead trees are fine! > Hi Dotan, These are trivial but handy for chasing down where messages come from: etcgrep () { grep -ir "$1" /etc/* ; } sgrep () { gre

Re: How to read log files

On 28.3.2010 19:33, Jari Fredriksson wrote: > On 28.3.2010 19:11, Dotan Cohen wrote: >> Is there a good resource for learning to read log files such as the >> kernel log, messages, dmesg, and such? I have been googling but found >> nothing really comprehensive yet unders

Re: How to read log files

> Sure, a very efficient way to do some bug hunting is just to copy-paste > the error in google's search, after removing some locale file names that > are probably not unique. Usually that gives you a "this is wrong, and > this is what you can do about is". When it doesn't is when the fun begins...

Re: How to read log files

Debian-based systems, specifically how to parse log files for errors". > My answer is  Google is your friend.  I am not about to do your research > for you.  This is a Help List but it is expected that the person asking for > help has already tried other sources before asking for help

Re: How to read log files

Jochen Schulz schreef: > Camaleón: >> Then he could use a serial port and instruct kernel (at boot time) to log >> out there. I've done that one time, with a VM machine and another linux >> (openSUSE). >> >> What are the recommended steps to achieve this in Debian? > > /etc/inittab contains exam

Re: How to read log files

Wayne schreef: > Dotan Cohen wrote: >>> As a last resort buy a book on linux that covers the subject you want >>> answered. >>> >> >> That was quite what I asked: where could I read more on the subject? >> Dead trees are fine! >> > > Based on your previous posts, I take that to mean > > Tell me w

Re: How to read log files

Dotan Cohen wrote: As a last resort buy a book on linux that covers the subject you want answered. That was quite what I asked: where could I read more on the subject? Dead trees are fine! Based on your previous posts, I take that to mean Tell me what book I should get to teach me how to f

Re: How to read log files

On Wed, 31 Mar 2010 13:00:18 -0400 (EDT), Dotan Cohen wrote > Wayne wrote: >> As a last resort buy a book on linux that covers the subject you want >> answered. >> > > That was quite what I asked: where could I read more on the subject? > Dead trees are fine! I think I understand Dotan's point.

Re: How to read log files

> As a last resort buy a book on linux that covers the subject you want > answered. > That was quite what I asked: where could I read more on the subject? Dead trees are fine! -- Dotan Cohen http://bido.com http://what-is-what.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.

Re: How to read log files

Camaleón: > > Then he could use a serial port and instruct kernel (at boot time) to log > out there. I've done that one time, with a VM machine and another linux > (openSUSE). > > What are the recommended steps to achieve this in Debian? /etc/inittab contains examples. (Legacy) Grub can be con

Re: How to read log files

On Tue, 30 Mar 2010 23:19:29 +0200, Jochen Schulz wrote: > Camaleón: >>> The machine is locking up and the keyboard leds flash. >> >> When the machine locks, try to access it via ssh. > > That won't work when the keyboard LEDs are flashing. That's a clear sign > for a kernel panic. We just have

Re: How to read log files

Camaleón: > On Tue, 30 Mar 2010 23:20:59 +0300, Dotan Cohen wrote: > >>> I cannot see any "panic" or "kernel oops" in that log. >>> >>> What is the exact behaviour are you seeing? >>> >> The machine is locking up and the keyboard leds flash. > > When the machine locks, try to access it via ssh.

Re: How to read log files

Dotan Cohen wrote: My 2 cents: read and understand log messages when you are in trouble, if system is working well, you don't need understand these logs. But in that case I would not be able to identify the faulty lines in the log. I need to know what a healthy log looks like, to diagnose a si

Re: How to read log files

On Tue, 30 Mar 2010 23:20:59 +0300, Dotan Cohen wrote: >> I cannot see any "panic" or "kernel oops" in that log. >> >> What is the exact behaviour are you seeing? >> >> > The machine is locking up and the keyboard leds flash. When the machine locks, try to access it via ssh. >> I think you shou

Re: How to read log files

> I cannot see any "panic" or "kernel oops" in that log. > > What is the exact behaviour are you seeing? > The machine is locking up and the keyboard leds flash. > I think you should be a little more verbose so people can understand the > big picture and make any suggestion. > I was asking in t

Re: How to read log files

> My 2 cents: read and understand log messages when you are in trouble, > if system is working well, you don't need understand these logs. > But in that case I would not be able to identify the faulty lines in the log. I need to know what a healthy log looks like, to diagnose a sick one. > googl

Re: How to read log files

> Mar 28 09:14:19 sfd kernel: [    0.00] Linux version > 2.6.31-20-generic (bui...@palmer) (gcc version 4.4.1 (Ubuntu > 4.4.1-4ubuntu8) ) #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC 2010 (Ubuntu > 2.6.31-20.58-generic) > > Doesn't look like Debian to me... > Ubuntu is a Debian derivative, Jordan. I

Re: [OT] teenage slang. was: Re: [OT] Help for non-Debian distributions (was How to read log files)

On Monday 29 March 2010 21:12:59 Neal Hogan wrote: > > But, as you say, this is way OT. > > Certainly, more OT than any ubuntu/debian question ;-) Quite :-) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia

Re: [OT] teenage slang. was: Re: [OT] Help for non-Debian distributions (was How to read log files)

On Mon, Mar 29, 2010 at 3:09 PM, Lisi wrote: > On Monday 29 March 2010 18:44:29 Stephen Powell wrote: >> On Mon, 29 Mar 2010 12:51:08 -0400 (EDT), Lisi wrote: >> > As for KKL, I needed a translation. >> >> This is *really* off-topic, but perhaps this is it: >> >> http://www.urbandictionary.com/def

Re: [OT] teenage slang. was: Re: [OT] Help for non-Debian distributions (was How to read log files)

On Monday 29 March 2010 18:44:29 Stephen Powell wrote: > On Mon, 29 Mar 2010 12:51:08 -0400 (EDT), Lisi wrote: > > As for KKL, I needed a translation. > > This is *really* off-topic, but perhaps this is it: > > http://www.urbandictionary.com/define.php?term=KKL > > It showed up in an internet searc

Re: How to read log files

On Mon, Mar 29, 2010 at 5:29 PM, Celejar wrote: > On Mon, 29 Mar 2010 13:38:14 +0200 > Javier Barroso wrote: > >> On Mon, Mar 29, 2010 at 9:06 AM, Dotan Cohen wrote: >> >> Why don't you just post what you've got? You will most probably find >> >> someone who can explain not only where the proble

Re: [WOT] Help for non-Debian distributions (was How to read log files)

On Mon, Mar 29, 2010 at 01:44:29PM -0400, Stephen Powell wrote: > On Mon, 29 Mar 2010 12:51:08 -0400 (EDT), Lisi wrote: > > As for KKL, I needed a translation. > > This is *really* off-topic, but perhaps this is it: > > http://www.urbandictionary.com/define.php?term=KKL > Eew. -- Kind Regards

Re: [OT] Help for non-Debian distributions (was How to read log files)

On Mon, 29 Mar 2010 12:51:08 -0400 (EDT), Lisi wrote: > As for KKL, I needed a translation. This is *really* off-topic, but perhaps this is it: http://www.urbandictionary.com/define.php?term=KKL It showed up in an internet search, but I can't access the site right now because my employer has tha

Re: [OT] Help for non-Debian distributions (was How to read log files)

On Monday 29 March 2010 17:29:26 Jordan Metzmeier wrote: > While I agree that this particular issue is very general > to Linux itself, That is really the point that I was making. > people still need to learn to seek help from the > appropriate communities. I actually agree in general. Asking

Re: [OT] Help for non-Debian distributions (was How to read log files)

> I have certainly benefitted from the question and its answers.  And Debian is > my distro of choice. > > I would take semantic exception to the questions about "we" supporting him; > since Jordan is most certainly not supporting Dotan, and the first person is > therefore inaccurate and inappropri

Re: [OT] Help for non-Debian distributions (was How to read log files)

On Mon, 29 Mar 2010 12:08:52 -0400 (EDT), Camaleón wrote: > On Mon, 29 Mar 2010 11:47:30 -0400, Stephen Powell wrote: >> If Camaleón wants to help him, we can't stop him; ... > Thanks for your understanding. BTW, I'm "her" :-) Oops! Sorry. With non-English names, I can't always tell. (Actually,

Re: How to read log files

On Monday 29 March 2010 16:18:12 Camaleón wrote: > On Mon, 29 Mar 2010 11:10:34 -0400, Jordan Metzmeier wrote: > > On Mon, Mar 29, 2010 at 10:39 AM, Camaleón wrote: > >> I support the person and his question, he seems to be an active (and > >> productive) Debian user. > >> > >> Anyway, Debian and U

Re: [OT] Help for non-Debian distributions (was How to read log files)

On Mon, 29 Mar 2010 11:47:30 -0400, Stephen Powell wrote: > On Mon, 29 Mar 2010 11:10:34 -0400 (EDT), Jordan Metzmeier wrote: (...) >> Do we support all of them here on debian-users list? > > That's not even an exhaustive list. According to DistroWatch.com, there > are, at the time of this wri

[OT] Help for non-Debian distributions (was How to read log files)

On Mon, 29 Mar 2010 11:10:34 -0400 (EDT), Jordan Metzmeier wrote: > On Mon, Mar 29, 2010 at 10:39 AM, Camaleón wrote: >> On Mon, 29 Mar 2010 09:54:40 -0400, Jordan Metzmeier wrote: >>> >>> We are still supporting this guy, even though it appears he is not >>> running Debian? >> >> I support the pe

Re: How to read log files

On Mon, 29 Mar 2010 13:38:14 +0200 Javier Barroso wrote: > On Mon, Mar 29, 2010 at 9:06 AM, Dotan Cohen wrote: > >> Why don't you just post what you've got? You will most probably find > >> someone who can explain not only where the problem is but how to read > >> it, too. > >> > > > > In the ge

Re: How to read log files

On Mon, 29 Mar 2010 11:10:34 -0400, Jordan Metzmeier wrote: > On Mon, Mar 29, 2010 at 10:39 AM, Camaleón wrote: >> I support the person and his question, he seems to be an active (and >> productive) Debian user. >> >> Anyway, Debian and Ubuntu share almost the same source. >> >> >> > You don't th

Re: How to read log files

On Mon, Mar 29, 2010 at 10:39 AM, Camaleón wrote: > On Mon, 29 Mar 2010 09:54:40 -0400, Jordan Metzmeier wrote: > >> We are still supporting this guy, even though it appears he is not >> running Debian? > > I support the person and his question, he seems to be an active (and > productive) Debian u

Re: How to read log files

On Mon, 29 Mar 2010 09:54:40 -0400, Jordan Metzmeier wrote: > We are still supporting this guy, even though it appears he is not > running Debian? I support the person and his question, he seems to be an active (and productive) Debian user. Anyway, Debian and Ubuntu share almost the same source

Re: How to read log files

On 28.3.2010 19:11, Dotan Cohen wrote: > Is there a good resource for learning to read log files such as the > kernel log, messages, dmesg, and such? I have been googling but found > nothing really comprehensive yet understandable for a newbie. Where > should I start? > As has be

Re: How to read log files

On Mon, Mar 29, 2010 at 9:50 AM, ceduardo wrote: > 2010/3/28 Dotan Cohen : >> Is there a good resource for learning to read log files such as the >> kernel log, messages, dmesg, and such? I have been googling but found >> nothing really comprehensive yet understandabl

Re: How to read log files

2010/3/28 Dotan Cohen : > Is there a good resource for learning to read log files such as the > kernel log, messages, dmesg, and such? I have been googling but found > nothing really comprehensive yet understandable for a newbie. Where > should I start? > > Thanks! > You c

Re: How to read log files

On Mon, 29 Mar 2010 10:06:46 +0300, Dotan Cohen wrote: >> Why don't you just post what you've got? You will most probably find >> someone who can explain not only where the problem is but how to read >> it, too. >> >> > In the general sense my intention was to learn and not lazy-web the > list. Bu

Re: How to read log files

On Mon, Mar 29, 2010 at 9:06 AM, Dotan Cohen wrote: >> Why don't you just post what you've got? You will most probably find >> someone who can explain not only where the problem is but how to read >> it, too. >> > > In the general sense my intention was to learn and not lazy-web the > list. But yo

Re: How to read log files

On Mon, Mar 29, 2010 at 3:06 AM, Dotan Cohen wrote: >> Why don't you just post what you've got? You will most probably find >> someone who can explain not only where the problem is but how to read >> it, too. >> > > In the general sense my intention was to learn and not lazy-web the > list. But yo

Re: How to read log files

> Why don't you just post what you've got? You will most probably find > someone who can explain not only where the problem is but how to read > it, too. > In the general sense my intention was to learn and not lazy-web the list. But you are right, attached is /var/log/messages. -- Dotan Cohen

Re: How to read log files

On Sunday 28 March 2010 19:26:19 Jari Fredriksson wrote: > Maybe you are not entitled to use a computer in the first place? I hope that this was a semantic/language error, and not an unpleasant comment. But it reads more like a very unpleasant comment. Lisi -- To UNSUBSCRIBE, email to debian-

Re: How to read log files

On 2010-03-28 14:24, Dotan Cohen wrote: On 28 March 2010 21:26, Jari Fredriksson wrote: I have no problem reading log files. But I have 25 years behind of reading those. Excellent. I hope to have a similar thing to say in the year 2035. Maybe you are not entitled to use a computer in the

Re: How to read log files

Thierry Chatelet writes: > So even if linux was born the very same year; 1991 + 25 = 2016 Log files have been around for just a _little_ bit longer than Linux has. -- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe&q

Re: How to read log files

Dotan Cohen: > > Actually, I am interested in Kernel logs and messages at the moment. > For individual software such as Apache, TFM is usually rather > adequate. But where is TFM for the kernel? Why don't you just post what you've got? You will most probably find someone who can explain not only

Re: How to read log files

On Sunday 28 March 2010 20:26:19 Jari Fredriksson wrote: Out of space man!!! Here is an extract from wikipedia: In 1991 while attending the University of Helsinki, Torvalds began to work on a non-commercial replacement for MINIX,[19] which eventually became the Linux kernel. So even if linux was

  1   2   3   >