Re: [gentoo-user] syslog-ng: how to read the log files
On Sunday 22 February 2015 22:28:07 Dale wrote: Peter Humphrey wrote: On Sunday 22 February 2015 20:57:43 Dale wrote: I think you need this: app-admin/logrotate Then I think a cron package is needed to run that, set to daily here I think. It comes with logrotate: /etc/cron.daily/logrotate The script does but if you don't have a cron package installed, nothing will run to rotate the logs. Maybe my message wasn't worded correctly? It's been a long week. ;-) Ah, I see what you mean. My misread. -- Rgds Peter.
Re: [gentoo-user] syslog-ng: how to read the log files
On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] syslog-ng: how to read the log files
Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] logs in the browser?
As I see that syslog-thread ... I think of setting up something for apache that allows a client to browse and search through the postfix-logs for his domain. Any good hints what to use for that purpose? Stefan
Re: [gentoo-user] syslog-ng: how to read the log files
On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. Regards. https://github.com/balabit/syslog-ng/issues/314 -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
Re: [gentoo-user] syslog-ng: how to read the log files
Am Mon, 23 Feb 2015 12:10:18 -0600 schrieb Canek Peláez Valdés can...@gmail.com: On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. I remember getting a small number of messages like that, too, on my laptop. However, it's at the university, so I can't check now to see what types of messages were missed (if any; if I understand [1] correctly, those messages are most likely bogus?). But yeah, that's any idea, Covici: see what's in /var/log/messages, compare that to the journalctl output, and check if any messages were actually missed (diff -U might be of help here). And if/once you did that, what kinds of messages were missed, if any? If those messages really are bogus, you shouldn't see any differences between the two. Regards. https://github.com/balabit/syslog-ng/issues/314 Note that that fix would only be in the ~arch version of syslog-ng, the current stable version (3.4.8) is a few months too old. -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup pgp6f1D6dsAfM.pgp Description: Digitale
Re: [gentoo-user] syslog-ng: how to read the log files
Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 12:10:18 -0600 schrieb Canek Peláez Valdés can...@gmail.com: On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. I remember getting a small number of messages like that, too, on my laptop. However, it's at the university, so I can't check now to see what types of messages were missed (if any; if I understand [1] correctly, those messages are most likely bogus?). But yeah, that's any idea, Covici: see what's in /var/log/messages, compare that to the journalctl output, and check if any messages were actually missed (diff -U might be of help here). And if/once you did that, what kinds of messages were missed, if any? If those messages really are bogus, you shouldn't see any differences between the two. Regards. https://github.com/balabit/syslog-ng/issues/314 Note that that fix would only be in the ~arch version of syslog-ng, the current stable version (3.4.8) is a few
Re: [gentoo-user] mesa-10.3.7-r1 S3TC option
On 02/20/2015 07:10 PM, Mick wrote: Mick michaelkintzios at gmail.com writes: media-libs/mesa-10.3.7-r1: I have this installed too; with this video card : radeon VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] I mostly followed this guide, without any xorg customizations: http://wiki.gentoo.org/wiki/Radeon media-libs/libtxc_dxtn as well. This may be necessary to get nice I do not have this message anywhere in the logs. There is no dxtn or s3tc flag [1]. I have just discovered that elogviewer is not working currently; I have used it extensively in the past. I reinstalled it and the /var/log/portage/elog dir is setup correctly but empty. Strange; I'm not certain when my elogs quit working.. I'm not certain what is going on, as python is set to 3.4; running python updater now qutie a bit of breakage So I emerged media-libs/libtxc_dxtn manually. Yes, I am going to give this a whirl too. It's been a long time since I've looked into updating a radeon configuration. What card are you using? I have these flags set for mesa and maybe they are in need of updating? media-libs/mesa-10.3.7-r1 USE=bindist classic dri3 egl gallium gbm llvm nptl udev Any additional flags I could/should set for mesa and a radeon card? Any other helper packages? [1] http://www.gentoo.org/dyn/use-index.xml#doc_chap1
Re: [gentoo-user] syslog-ng: how to read the log files
Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. Regards. https://github.com/balabit/syslog-ng/issues/314 At the time when I did this there was no syslog-ng.service in /usr/lib/systemd/system, now there is, but my unit file is like this: [Unit] Description=System Logger Daemon Documentation=man:syslog-ng(8) [Service] Sockets=syslog.socket ExecStart=/usr/sbin/syslog-ng -F ExecReload=/bin/kill -HUP $MAINPID #Restart=on-failure [Install] WantedBy=multi-user.target Alias=syslog.service Is there a reason why this should not work? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] syslog-ng: how to read the log files
On Mon, Feb 23, 2015 at 1:31 PM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 12:10:18 -0600 schrieb Canek Peláez Valdés can...@gmail.com: On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. I remember getting a small number of messages like that, too, on my laptop. However, it's at the university, so I can't check now to see what types of messages were missed (if any; if I understand [1] correctly, those messages are most likely bogus?). But yeah, that's any idea, Covici: see what's in /var/log/messages, compare that to the journalctl output, and check if any messages were actually missed (diff -U might be of help here). And if/once you did that, what kinds of messages were missed, if any? If those messages really are bogus, you shouldn't see any differences between the two.
Re: [gentoo-user] mesa-10.3.7-r1 S3TC option
On Monday 23 Feb 2015 18:27:12 wirel...@tampabay.rr.com wrote: On 02/20/2015 07:10 PM, Mick wrote: Mick michaelkintzios at gmail.com writes: media-libs/mesa-10.3.7-r1: I have this installed too; with this video card : radeon VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] I mostly followed this guide, without any xorg customizations: http://wiki.gentoo.org/wiki/Radeon media-libs/libtxc_dxtn as well. This may be necessary to get nice I do not have this message anywhere in the logs. There is no dxtn or s3tc flag [1]. I have just discovered that elogviewer is not working currently; I have used it extensively in the past. I reinstalled it and the /var/log/portage/elog dir is setup correctly but empty. Strange; I'm not certain when my elogs quit working.. I'm not certain what is going on, as python is set to 3.4; running python updater now qutie a bit of breakage So I emerged media-libs/libtxc_dxtn manually. Yes, I am going to give this a whirl too. It's been a long time since I've looked into updating a radeon configuration. What card are you using? *-display description: VGA compatible controller product: RV730/M96-XT [Mobility Radeon HD 4670] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:02:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:29 memory:d000-dfff ioport:2000(size=256) memory:cfef-cfef memory:cfe0-cfe1 HOWEVER, I seem to recall the message in question showing up for a Kaveri APU, the A10-7850K, rather than the above card! I have these flags set for mesa and maybe they are in need of updating? media-libs/mesa-10.3.7-r1 USE=bindist classic dri3 egl gallium gbm llvm nptl udev Installed versions: 10.3.7-r1(20:18:24 02/19/15)(classic dri3 egl gallium gbm gles2 llvm nptl udev vdpau xvmc -bindist -debug -gles1 -opencl - openmax -openvg -osmesa -pax_kernel -pic -r600-llvm-compiler -selinux -wayland -xa ABI_MIPS=-n32 -n64 -o32 ABI_PPC=-32 -64 ABI_S390=-32 -64 ABI_X86=64 -32 -x32 KERNEL=linux -FreeBSD VIDEO_CARDS=r600 radeon -freedreno -i915 - i965 -ilo -intel -nouveau -r100 -r200 -r300 -radeonsi -vmware) Any additional flags I could/should set for mesa and a radeon card? Any other helper packages? [1] http://www.gentoo.org/dyn/use-index.xml#doc_chap1 I have these flags for x11-base/xorg-server-1.16.4: Installed versions: 1.16.4(10:37:19 02/20/15)(glamor ipv6 nptl suid udev xorg -dmx -doc -kdrive -minimal -selinux -static-libs -systemd -tslib -unwind -wayland -xnest -xvfb) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] syslog-ng: how to read the log files
Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 1:31 PM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 12:10:18 -0600 schrieb Canek Peláez Valdés can...@gmail.com: On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. I remember getting a small number of messages like that, too, on my laptop. However, it's at the university, so I can't check now to see what types of messages were missed (if any; if I understand [1] correctly, those messages are most likely bogus?). But yeah, that's any idea, Covici: see what's in /var/log/messages, compare that to the journalctl output, and check if any messages were actually
[gentoo-user] zfs io scheduler
Hi, is zfs setting the io scheduler to noop for the disks in the pool? I'm currently finding that the IO performance is horrible with a pool made from two mirrored disks ... -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
[gentoo-user] Re: [SOLVED] What happened to my 2nd eth0?
On Sun, Feb 22, 2015 at 09:01:47AM +, Mick wrote On Sunday 22 Feb 2015 04:52:34 Walter Dnes wrote: My DSL router modem is at 192.168.123.254. I have an HDHomerun network TV tuner that insists on coming up somewhere in the 169.254.X.Y block. Up until upgrading from 32 to 64 bits, I was able to see a 2nd eth0 (i.e. eth0:1) using the following /etc/conf.d/net setup... config_eth0= 192.168.123.251/29 broadcast 192.168.123.255 169.254.1.1/16 broadcast 169.254.255.255 Is there a reason you need to define a broadcast if you are using CIDR notation? I've always done it that way. At one time I had a router that could be made to send logs to a specified IP address. By setting their broadcast addresses to 192.168.123.255, and having the router log to that address, I could make both of my machines pick up the remote logs from the router. routes_eth0= default via 192.168.123.254 metric 20 192.168.123.248/29 via 192.168.123.254 metric 0 Isn't the above redundant if you have defined an identical default route? 169.254.0.0/16 via 169.254.1.1 metric 0 Another item that stopped working a while ago... I have a dialup connection for emergency backup use. Before the format of the /etc/conf.d/net file changed, I could simultaneously... * have eth0 as default route with expensive metric 20 * have ppp0 take over when dialup is active, with a cheaper metric * still be able to have my 2 machines talk to each other over eth0, even while the dialup connection ppp0 is active * have eth0 take over again as default route when ppp0 drops Unless you have set up: modules=!iproute2 netifrc will not use ifconfig. I've noticed iproute2 showing up recently in emerge. ***YES IT WORKS***. Thank you very much. I am now getting OTA TV to my desktop again. Slight modification. Using that search string in Google, I found http://www.michaeldolan.com/Tutorials/Downloads/conf.d/net My revised /etc/conf.d/net script is modules=( !iproute2 ) config_eth0= 192.168.123.251/29 broadcast 192.168.123.255 169.254.1.1/16 broadcast 169.254.255.255 routes_eth0= default via 192.168.123.254 metric 20 192.168.123.248/29 via 192.168.123.254 metric 0 169.254.0.0/16 via 169.254.1.1 metric 0 edit... I finally found the documentation (see below). I still have to fix up the metric and broadcast parameters. For now, I'm happy to have the TV signal coming to my desktop. ...and ifconfig returns... eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 192.168.123.251 netmask 255.255.255.248 broadcast 192.168.123.255 ether 00:1d:09:96:6c:1c txqueuelen 1000 (Ethernet) RX packets 1049019 bytes 1501104544 (1.3 GiB) RX errors 0 dropped 5 overruns 0 frame 0 TX packets 569447 bytes 45295143 (43.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xfdfc-fdfe eth0:1: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500 inet 169.254.1.1 netmask 255.255.0.0 broadcast 169.254.255.255 ether 00:1d:09:96:6c:1c txqueuelen 1000 (Ethernet) device interrupt 20 memory 0xfdfc-fdfe lo: flags=73UP,LOOPBACK,RUNNING mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 0 (Local Loopback) RX packets 8 bytes 480 (480.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8 bytes 480 (480.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 I would have appreciated a news item telling me that /etc/conf.d/net was going to change default behaviour, before it happened and caused breakage on my system. Or did it happen, and I missed it? CONFIG_IP_MULTIPLE_TABLES=y I do not have that option available it in my current kernel, or in the backup from before I switched from 32-bit to 64-bit mode. Not that it matters, now that I have things working. Given that iproute2 is now the default, I assume that ifconfig will be dropped sometime down the road. Documentation could be better. At the top of /etc/conf.d/net I see... # This blank configuration will automatically use DHCP for any net.* # scripts in /etc/init.d. To create a more complete configuration, # please review /etc/conf.d/net.example and save your configuration # in /etc/conf.d/net (this file :]!). # Actually /usr/share/doc/openrc-version/net.example is where to look # for example setup. Guess what... neither of those example files exist. It's actually /usr/share/doc/netifrc-version/net.example.bz2 (Where would I be without Google?) Also using Google, I found http://www.policyrouting.org/iproute2.doc.html which is quite complex. Looks like it's time to play around with the ip command and try to duplicate my current setup. Does anyone have a multi-route setup similar to mine configured with iproute2? The net.example file says # If you need more than one address, you can use something like this # NOTE: ifconfig
Re: [gentoo-user] syslog-ng: how to read the log files
Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. HTH -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup pgp64Eza5OoST.pgp Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] syslog-ng: how to read the log files
Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
[gentoo-user] NetworkManager-1.0.0 changed my wireless network behavior
My ~amd64 machine updated yesterday to NM-1.0.0 and this morning I noticed the bad behavior described here: https://bbs.archlinux.org/viewtopic.php?id=193660 The fix described there by ermo worked for me, but it took me a while to figure out how to get it done. The easy way is to right-click on the NetworkManager panel applet and choose the Edit Connections item to edit your wireless connection. In the editor window click on 'IPv6 Settings'. There is a drop-down menu labeled 'Method'. Click on 'Link- Local Only' and then Save. I'd never have figured this out on my own, so the Arch nerds bailed me out once again :) (BTW, my recent posts via gmane have been bouncing because of the recent change in the gentoo mailing-list email address. I hope the gmane guys will have it fixed soon. We'll see if this post makes it...)
Re: [gentoo-user] syslog-ng: how to read the log files
On Monday 23 February 2015 23:29:49 Neil Bothwick wrote: On Mon, 23 Feb 2015 18:18:36 -0500, cov...@ccs.covici.com wrote: I did change the unit file, but no joy, I still get messages like this: Feb 23 18:16:05 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 13 messages. I used to get messages like that. Sometimes substantial numbers of messages, 100+ was far from uncommon. But the last such message in my journal was on November 6th. That's on my laptop, my desktop doesn't have a single such message. Thank Goodness! Someone who knows enough to trim out the bits of the message he's not replying to. Why do you others make me page-down eight times to find what you've written in reply to the last three lines of the preceding message? -- Rgds Peter.
Re: [gentoo-user] logs in the browser?
On Mon, Feb 23, 2015 at 4:20 PM, Stefan G. Weichinger li...@xunil.at wrote: As I see that syslog-thread ... I think of setting up something for apache that allows a client to browse and search through the postfix-logs for his domain. Any good hints what to use for that purpose? Stefan, if you already have systemd (which I believe you do), why don't you compile in the support for microhttpd and use the journal? This is the exact scenario for which systemd-journal-gatewayd[1] was written. Regards. [1] http://www.freedesktop.org/software/systemd/man/systemd-journal-gatewayd.service.html -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
[gentoo-user] Report: Experience with f2fs
Some list members might be interested in how I've got on with f2fs (flash-friendly file system). According to genlop I first installed f2fs on my Atom mini-server box on 1/11/14 (that's November, for the benefit of transpondians), but I'm pretty sure it must have been several months before that. I installed a SanDisk SDSSDP-064G-G25 in late February last year and my admittedly fallible memory says I changed to f2fs not many months after that, as soon as I discovered it. Until two or three weeks ago I had no problems at all. Then while doing a routine backup tar started complaining about files having been moved before it could copy them. It seems I had a copy of an /etc directory from somewhere (perhaps a previous installation) under /root and some files when listed showed question marks in all fields except their names. I couldn't delete them, so I re-created the root partition and restored from a backup. So far so good, but then I started getting strange errors last week. For instance, dovecot started throwing symbol-not-found errors. Finally, after remerging whatever packages failed for a few days, /var/log/messages suddenly appeared as a binary file again, and I'm pretty sure that bug's been fixed. Time to ditch f2fs, I thought, so I created all partitions as ext4 and restored the oldest backup I still had, then ran emerge -e world and resumed normal operations. I didn't zero out the partitions with dd; perhaps I should have. I'll watch what happens, but unless the SSD has failed after only a year I shouldn't have any problems. An interesting experience. Why should f2fs work faultlessly for several months, then suffer repeated failures with no clear pattern? -- Rgds Peter.
Re: [gentoo-user] syslog-ng: how to read the log files
Am Tue, 24 Feb 2015 00:50:30 + schrieb Peter Humphrey pe...@prh.myzen.co.uk: On Monday 23 February 2015 23:29:49 Neil Bothwick wrote: On Mon, 23 Feb 2015 18:18:36 -0500, cov...@ccs.covici.com wrote: I did change the unit file, but no joy, I still get messages like this: Feb 23 18:16:05 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 13 messages. I used to get messages like that. Sometimes substantial numbers of messages, 100+ was far from uncommon. But the last such message in my journal was on November 6th. That's on my laptop, my desktop doesn't have a single such message. Thank Goodness! Someone who knows enough to trim out the bits of the message he's not replying to. Why do you others make me page-down eight times to find what you've written in reply to the last three lines of the preceding message? *Checks to see if he's guilty.* *Hangs head in shame.* -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup pgp7l3HzDsiJp.pgp Description: Digitale Signatur von OpenPGP
Re: [gentoo-user] Re: [SOLVED] What happened to my 2nd eth0?
On Monday 23 Feb 2015 08:39:42 Walter Dnes wrote: Looks like it's time to play around with the ip command and try to duplicate my current setup. Does anyone have a multi-route setup similar to mine configured with iproute2? The net.example file says # If you need more than one address, you can use something like this # NOTE: ifconfig creates an aliased device for each extra IPv4 address # (eth0:1, eth0:2, etc) # iproute2 does not do this as there is no need to # WARNING: You cannot mix multiple addresses on a line with other parameters! #config_eth0=192.168.0.2/24 192.168.0.3/24 192.168.0.4/24 # However, that only works with CIDR addresses, so you can't use # netmask. What exactly do they mean by... iproute2 does not do this as there is no need to There is no need to create virtual interfaces like eth0:1 to be able to have secondary IP addresses. The ip command adds them to the same eth0 interface. When I use VPN I can see that my interface has a secondary LAN address created by VPN, but it does not have an additional virtual NIC. The only thing is that if my primary IP address goes down temporarily, the secondary address becomes primary and stays there. I need to look at the VPN configuration to see how to define the VPN LAN as a secondary subnet, but this is not related to your question. PS. Did you look at setting your desired subnet rather than a local-link auto-configured address at your HDHomerun device? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] syslog-ng: how to read the log files
Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 1:31 PM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 12:10:18 -0600 schrieb Canek Peláez Valdés can...@gmail.com: On Mon, Feb 23, 2015 at 11:49 AM, cov...@ccs.covici.com wrote: Canek Peláez Valdés can...@gmail.com wrote: On Mon, Feb 23, 2015 at 3:41 AM, cov...@ccs.covici.com wrote: Marc Joliet mar...@gmx.de wrote: Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee l...@yagibdah.de: Neil Bothwick n...@digimed.co.uk writes: On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: I wonder if the OP is using systemd and trying to read the journal files? Nooo, I hate systemd ... What good are log files you can't read? You can't read syslog-ng log files without some reading software, usually a combination of cat, grep and less. systemd does it all with journalctl. There are good reasons to not use systemd, this isn't one of them. To me it is one of the good reasons, and an important one. Plain text can usually always be read without further ado, be it from rescue systems you booted or with software available on different operating systems. It can be also be processed with scripts and sent as email. You can probably even read it on your cell phone. You can still read log files that were created 20 years ago when they are plain text. Can you do all that with the binary files created by systemd? I can't even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the logs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a reason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. Except that I get lots of messages about the system journal missing messages when forwarding to syslog, so how can I make sure this does not happening? Could you please show those messages? systemd sends *everything* to the journal, and then the journal (optionally) can send it too to a regular syslog. In that sense, it's impossible for the journal to miss any message. The only way in which the journal could miss messages is at very early boot stages; but with a proper initramfs (like the ones generated with dracut), even those get caught. You get to put an instance of systemd and the journal inside the initramfs, and so it's available almost from the beginning. And if you use gummiboot, then you can even log from the moment the UEFI firmware comes to life. So, I get lots of messages in my regular syslog-ng /var/log/messages like the following: Feb 23 12:47:52 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 15 messages. So, I saw a post on Google to up the queue length, and I uped it to 200, but no joy, still get the messages like the one above. Are you using the unit file provided by syslog-ng (systemd-delta doesn't mention syslog)? Also, is /etc/systemd/system/syslog.service is a link to /usr/lib/systemd/system/syslog-ng.service? I do, and I don't get any of those messages. I use the default journal configuration. According to [1], this should be fixed. I remember getting a small number of messages like that, too, on my laptop. However, it's at the university, so I can't check now to see what types of messages were missed (if any; if I understand [1] correctly, those messages are most likely bogus?). But yeah, that's any idea, Covici: see what's in /var/log/messages, compare that to the journalctl output, and check if any messages were actually
Re: [gentoo-user] syslog-ng: how to read the log files
On Mon, 23 Feb 2015 18:18:36 -0500, cov...@ccs.covici.com wrote: I did change the unit file, but no joy, I still get messages like this: Feb 23 18:16:05 ccs.covici.com systemd-journal[715]: Forwarding to syslog missed 13 messages. I used to get messages like that. Sometimes substantial numbers of messages, 100+ was far from uncommon. But the last such message in my journal was on November 6th. That's on my laptop, my desktop doesn't have a single such message. -- Neil Bothwick Disinformation is not as good as datinformation. pgpkAJRo3OjyK.pgp Description: OpenPGP digital signature
