Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-09-12 17:44, Per Jessen wrote:

...

Carlos E. R. wrote:

...

When I fetch mail with fetchmail, I see this:

...

Your fetchmail is spewing a _lot_ of messages - looks like 30-50/sec?

Possibly. But not as fast as the network allows, only downloading about 10 KiB/S

...

...

The PID is that of fetchmail. How can avoid that?

Change the default rate limit:

$SystemLogRateLimitInterval [number] $SystemLogRateLimitBurst [number]

I don't know hat the default values would be, I have not that variable in my config file, which is the same as in 11.4 and there it worked fine.

http://www.rsyslog.com/tag/systemlogratelimitinterval/ -- Per Jessen, Zürich (13.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2012-09-12 at 21:49 +0200, Carlos E. R. wrote:

On Thursday, 2012-09-13 at 01:59 +0800, Otto Rodusek wrote:

...

add

$SystemLogRateLimitInterval 0 #$SystemLogRateLimitBurst 50 $SystemLogUsePIDFromSystem on

Ah, that means log all. Good.

It is not working... I still get complains from rsyslog: <5.6> 2012-09-13 22:45:09 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 22554 due to rate-limiting <5.6> 2012-09-13 22:45:10 Telcontar rsyslogd-2177 - - - imuxsock lost 6 messages from pid 22554 due to rate-limiting <5.6> 2012-09-13 22:45:36 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 7540 due to rate-limiting <5.6> 2012-09-13 22:45:40 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 22554 due to rate-limiting <5.6> 2012-09-13 22:45:41 Telcontar rsyslogd-2177 - - - imuxsock lost 6 messages from pid 22554 due to rate-limiting <5.6> 2012-09-13 22:45:44 Telcontar rsyslogd-2177 - - - imuxsock lost 10 messages from pid 7540 due to rate-limiting I'll try: $SystemLogRateLimitInterval 5 $SystemLogRateLimitBurst 2000 Or could it be because I did a rcsyslog reload instead of restart? - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlBSSMgACgkQtTMYHG2NR9VV0wCeJS+R1D8vHsjQaVNTtR6Vs50N 9N0AnA6qbNjHsLxo4P61M9RLpO5Ee6/i =Fton -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Otto Rodusek [09-14-12 04:56]:

Yep you're right - it worked for a while but now spewing out again. I'll be upgrading to 12.2 next week and see if the newer version of rsyslog will resolve the problem. I'm also playing around with the parameters to see if it has any effect.

I am on Tumbleweed and up to date. system is intel i7 w/12gb I got a *lot* of msg's: Aug 20 03:02:21 Crash rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable even filed a bug report but was asked to return to bare 12.1 from Tumbleweed and found the change too major compared to the discomfort. Did not close the bug: https://bugzilla.novell.com/show_bug.cgi?id=734672 on 05 Sept the err msg changed to: Sep 5 18:14:35 Crash rsyslogd-2177: imuxsock begins to drop messages from pid 5432 due to rate-limiting on 05 Sept after 22:32:11 GMT-5 the msgs stopped. On this date 12.2 was released and major package updates. on 08 Sept 08:15:37 GMT-5 they resumed but very reduced occurance. The only relevant change that I can see is: kernel-desktop-3.4.6-2.10.1 previous was: kernel-desktop-3.5.3-40.1 I have another machine which was receiving *many*, but frequency was much less than the above, of the "Resource temporarily unavailable" msgs which also changed to 3.4.6 kernel from 3.5.3, and err msgs have not resumed. I have a third machine which *doesn't* get the imuxsock err msgs. The 2nd (server) and 3rd (test) machines are x2 amds. I do not see a "pattern". -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [09-14-12 09:49]:

On 2012-09-14 13:59, Patrick Shanahan wrote:

...

even filed a bug report but was asked to return to bare 12.1 from Tumbleweed and found the change too major compared to the discomfort. Did not close the bug: https://bugzilla.novell.com/show_bug.cgi?id=734672

Well, you filed it against 12.1 in the product field; you need tumbleweed in there.

Yes, but couldn't find Tumbleweed at the time. And cannot now. Was told to use {current} when I filed it. ??? There *should* be a Tumbleweed version. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 09/14/12 17:41, Patrick Shanahan pecked at the keyboard and wrote:

* Carlos E. R. [09-14-12 09:49]:

...

On 2012-09-14 13:59, Patrick Shanahan wrote:

...

even filed a bug report but was asked to return to bare 12.1 from Tumbleweed and found the change too major compared to the discomfort. Did not close the bug: https://bugzilla.novell.com/show_bug.cgi?id=734672

Well, you filed it against 12.1 in the product field; you need tumbleweed in there.

Yes, but couldn't find Tumbleweed at the time. And cannot now. Was told to use {current} when I filed it. ???

There *should* be a Tumbleweed version.

You have just as much a chance of finding a Tumbleweed version as you would a Packman version. It is an addon repo just like Packman is. There is a tumbleweed forum for posting Tumbleweed problems. http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/ -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 14/9/12 6:51 PM, Bernhard Voelker wrote:

On 09/12/2012 05:14 PM, Carlos E. R. wrote:

...

When I fetch mail with fetchmail, I see this:

<5.6> 2012-09-12 17:09:03 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:07 Telcontar rsyslogd-2177 - - - imuxsock lost 187 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:09 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:13 Telcontar rsyslogd-2177 - - - imuxsock lost 226 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:15 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:19 Telcontar rsyslogd-2177 - - - imuxsock lost 144 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:21 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:25 Telcontar rsyslogd-2177 - - - imuxsock lost 248 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:27 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:31 Telcontar rsyslogd-2177 - - - imuxsock lost 196 messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:35 Telcontar rsyslogd-2177 - - - imuxsock begins to drop messages from pid 21238 due to rate-limiting <5.6> 2012-09-12 17:09:37 Telcontar rsyslogd-2177 - - - imuxsock lost 119 messages from pid 21238 due to rate-limiting

The PID is that of fetchmail. How can avoid that? Hi Carlos,

it's one point how to get rsyslogd to capture all messages, but instead of trying to tune rsyslogd like Per and Otto suggested, I'd try to find out why fetchmail is sending so much messages to the syslog. What are the actual messages?

Have a nice day, Berny Hi Berny,

Thanks for your good suggestion. In fact, that's exactly what I did in my case (not sure of Carlos situation) and changing to "$SystemLogRateLimitInterval 0" in /etc/rsyslog.conf got totally rid of the "imuxsock lost ??? messages from pid ????? due to rate-limiting" messages (none over the last 24 hrs or so) however I now get TONS of the following "rsyslogd: imuxsock: recvfrom UNIX: Resource temporarily unavailable" !! Changing params in /etc/rsyslog.conf doesn't seem to help solve this either. I'm thinking there may be some issue in the version of rsyslogd that I'm using in 12.1: # rsyslogd -v rsyslogd 5.8.5, compiled with: FEATURE_REGEXP: Yes FEATURE_LARGEFILE: No GSSAPI Kerberos 5 support: Yes FEATURE_DEBUG (debug build, slow code): No 32bit Atomic operations supported: Yes 64bit Atomic operations supported: No Runtime Instrumentation (slow code): No See http://www.rsyslog.com for more information. From the rsyslog.com website it seems this version (5.8.5) (my rpm is rsyslog-5.8.5-6.4.1.x86_64) is quite out of date. On my test server, 12.2 rsyslogd does not seem to exhibit these issues, so I will try to update my server to 12.2 (rsyslog-5.8.11-2.1.3.x86_64) next week and see if that resolves the issue. Doesn't seem serious, just irritating that logs fill up!!! Again thanks for any advice. Best regards. Otto. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-14 13:27, Otto Rodusek wrote:

This version has support for "64bit Atomic operations supported: Yes" whilst the 12.1 version does not - maybe that's where this issue lies as both my live and test servers are 64 bit, and hence I don't see the problem on the test server whilst I do on the live server. (It could also be because the load on the test server is minimal vs the live server - go figure!!)

You can use the command "logger" inside a loop in a script to send hundreds of messages and load it. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBTFd0ACgkQIvFNjefEBxpspACguss8OTi47qGi0RIzCcenbyOB 4UYAoJgrjQLENAccyZneDEQAV7SVPmy9 =IuDY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-09-14 13:32, Carlos E. R. wrote:

...

On 2012-09-14 13:27, Otto Rodusek wrote:

...

This version has support for "64bit Atomic operations supported: Yes" whilst the 12.1 version does not - maybe that's where this issue lies as both my live and test servers are 64 bit, and hence I don't see the problem on the test server whilst I do on the live server. (It could also be because the load on the test server is minimal vs the live server - go figure!!)

You can use the command "logger" inside a loop in a script to send hundreds of messages and load it.

#!/bin/bash

for((i=0;i<5000;i++)) do /bin/logger -p local3.debug -t testlog "Message test $i" done

Then run "time testlog". 5000 messages in 4 seconds. My limit is currently:

$SystemLogRateLimitInterval 5 $SystemLogRateLimitBurst 2000

so it should trigger, and it doesn't :-?

Probably because each call to /bin/logger is a new process. -- Per Jessen, Zürich (14.7°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sat, 15 Sep 2012 01:47:19 Carlos E. R. wrote:

On 2012-09-14 13:59, Per Jessen wrote:

...

...

so it should trigger, and it doesn't :-?

Probably because each call to /bin/logger is a new process.

Yes... I'm thinking that way, too.

You could use python which has a simple syslog interface: --- snip --- import syslog syslog.syslog('Processing started') for i in range(100): syslog.syslog(syslog.LOG_ERR, 'Python test %i' % i) --- snip --- See http://docs.python.org/library/syslog.html for options (example at bottom of page). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-16 07:06, Cristian Rodríguez wrote:

On 14/09/12 08:45, Carlos E. R. wrote:

see also systemd-cat(1)

cer@Telcontar:~/tmp> man systemd-cat No manual entry for systemd-cat cer@Telcontar:~/tmp> - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBVvQoACgkQIvFNjefEBxpXUQCgiqA9cNyVrydAWMnoaKIBbTMw GpoAoNksTAFbvYZsmh3uxbgYHNxQJ6/S =9AIE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-16 14:22, Per Jessen wrote:

Carlos E. R. wrote:

...

...

see also systemd-cat(1)

cer@Telcontar:~/tmp> man systemd-cat No manual entry for systemd-cat cer@Telcontar:~/tmp>

Weird - I have it on a brandnew 12.2 system.

Look again at my signature. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBVx/wACgkQIvFNjefEBxpZHgCfbG1m33KEVQH/gx5gvmSfDMwX i5kAnAvazzqeoMtzwFuShXvrS+NxEUPW =WIAm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2012-09-16 at 14:41 +0200, Carlos E. R. wrote:

...

I'm waiting to have a bunch of at least a hundred emails to fetch before running fetchmail again and see.

I did, and it worked... rsyslog did not complain this time. With this setting:

$SystemLogRateLimitInterval 5 $SystemLogRateLimitBurst 2000

There is an update of rsyslog to version 5.10.0 that addresses precissely this issue: +++··············· openSUSE-2012-648 - rsyslog: Updated to 5.10.0 This update fixes the following issues for rsyslog: - Updated to 5.10.0 [V5-stable] (bnc#753077, bnc#778769), the actual rsyslog v5-stable series, incorporating all fixes the 5.8.x [EOL V5-stable] and changes from 5.9.x series. It turns off rate limiting on unix socket by default (caused problems) ···············++- - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlBjbPsACgkQtTMYHG2NR9W2DQCfXK2E6zhB8jEvC/fIMs9phyYv +5UAn0gp2S3d2AtCe+5Fv8+EFDfsuuot =4wrE -----END PGP SIGNATURE-----

On 27/9/12 7:05 AM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-09-26 23:00, Carlos E. R. wrote:

...

On Sunday, 2012-09-16 at 14:41 +0200, Carlos E. R. wrote:

...

...

I'm waiting to have a bunch of at least a hundred emails to fetch before running fetchmail again and see. I did, and it worked... rsyslog did not complain this time. With this setting: $SystemLogRateLimitInterval 5 $SystemLogRateLimitBurst 2000 There is an update of rsyslog to version 5.10.0 that addresses precissely this issue:

+++··············· openSUSE-2012-648 - rsyslog: Updated to 5.10.0

This update fixes the following issues for rsyslog: - Updated to 5.10.0 [V5-stable] (bnc#753077, bnc#778769), the actual rsyslog v5-stable series, incorporating all fixes the 5.8.x [EOL V5-stable] and changes from 5.9.x series. It turns off rate limiting on unix socket by default (caused problems) ···············++-

And after the update, syslog is truncating messages :-(

<5.4> 2012-09-27 00:06:36 Telcontar router - - - rent IP= 79.144.178.252

The real message is "Logging the current IP=..."

and there are many more:

<4.5> 2012-09-26 23:02:36 Telcontar su - - - er on none <4.5> 2012-09-26 23:02:36 Telcontar su - - - er on none <3.6> 2012-09-26 23:12:53 Telcontar smartd 4414 - - b [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 115 to 116 <3.6> 2012-09-26 23:12:53 Telcontar smartd 4414 - - c [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 106 to 107

- -- Cheers / Saludos,

Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBjijsACgkQIvFNjefEBxquxwCgvM5qbb4V7txPGZ014H3ezwfN 0rAAn28zV8QD60ktRj24wUKp09460FAq =v0SZ -----END PGP SIGNATURE-----

Hi Carlos, Yep, I just updated to rsyslog 5.10.0 from 5.8.5 and indeed all the messages are truncated - very irritating!! Did you by any chance get a reply or possibly find a solution short of downgrading to 5.8.5 (system is Opensuse 12.2 x86_64)? Thanks. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 3/10/12 5:06 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 2012-10-02 17:10, Otto Rodusek wrote:

...

Hi Carlos,

Yep, I just updated to rsyslog 5.10.0 from 5.8.5 and indeed all the messages are truncated - very irritating!! Did you by any chance get a reply or possibly find a solution short of downgrading to 5.8.5 (system is Opensuse 12.2 x86_64)? No, no reply. And I downgraded, of course. Please, please, add your comment to https://bugzilla.novell.com/show_bug.cgi?id=783177, else they will think that it is me alone and do nothing.

- -- Cheers / Saludos,

Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBsAC4ACgkQIvFNjefEBxqcQwCgjllRRY9oHTppIMLk5rPHP4WZ AMAAn3ak2hI+Ox7iO50a6IvLTaBAhv/S =p6xo -----END PGP SIGNATURE----- Hi Carlos,

Okie done! Posted comment at https://bugzilla.novell.com/show_bug.cgi?id=783177, hopefully something will get done about this soon - some of my scripts that analyses and reports on the logs are failing as a result. BTW systemd-journalctl does report all the entries correctly without any truncation. Best regards. Otto. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [09-26-12 19:09]: ...

And after the update, syslog is truncating messages :-(

<5.4> 2012-09-27 00:06:36 Telcontar router - - - rent IP= 79.144.178.252

The real message is "Logging the current IP=..."

and there are many more:

<4.5> 2012-09-26 23:02:36 Telcontar su - - - er on none <4.5> 2012-09-26 23:02:36 Telcontar su - - - er on none <3.6> 2012-09-26 23:12:53 Telcontar smartd 4414 - - b [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 115 to 116 <3.6> 2012-09-26 23:12:53 Telcontar smartd 4414 - - c [SAT], SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 106 to 107

I wonder if you have a local problem. I have rsyslog-5.10.0-2.4.1.x86_64 and do not see truncated entries in /var/log/messages ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Otto Rodusek [10-03-12 07:43]: ...

Hmm...that's interesting...in fact it's not just my /var/log/messages but all my logs (/var/log/mail, /var/log/warn, etc etc).

I cited /var/log/messages but I see no noticable abnormality in any of my log files.

However, as I pointed out to Carlos, systemd-journalctl reports all the messages correctly without truncation.

I see this also

Any idea what the "local problem" may be or where to look? Interesting enough, I have another system that is also 12.2 x86_64, just updated via yast2 to rsyslog 5.10.0 yesterday, also exhibits the same truncation problem now. The systems are located in completely different areas and are not linked.

No, I do not. But I have three boxes, 2 with Tumbleweed and 1 with 12.2 upgraded from 12.1, which do *not* show truncation.

As with Carlos, if I revert back to rsyslog 5.8.5 problem goes away!! I re-install rsyslog 5.10.0 and the truncation problem returns!!

Thanks for shedding any light on this issue!!

I would guess some kind of race condition but believe there is no relation to rsyslog and journald and that it appears the *same* chars are dropped from similar logs. Is it possibly a locale problem? I have LC_CTYPE=en_US.UTF-8. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-10-03 13:34, Patrick Shanahan wrote:

* Carlos E. R. <> [09-26-12 19:09]:

I wonder if you have a local problem. I have rsyslog-5.10.0-2.4.1.x86_64 and do not see truncated entries in /var/log/messages ???

Well, there are now two people with the same problem, so I don't think so. However, I repeatedly installed the old version of rsyslog and the new one, and it was consistent: the new one failed with the same configuration. If there is some new needed setting that should be enabled on the new version, they should say so somewhere, I suppose. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBsJO0ACgkQIvFNjefEBxqMMACeLvqVdQ0pWCuOhT3C/pW8dxG6 nfsAoIOARc7RuTWgo6XNmrykkgpFpj78 =bBiJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-10-03 14:11, Patrick Shanahan wrote:

* Carlos E. R. <> [10-03-12 07:46]:

I noticed "it appears" the same chars are dropped from similar looking log entries ????

That means that the failure is consistent. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBsLUUACgkQIvFNjefEBxpISgCffDFsQ4ENwND/IAErXOwtqOSt nM0AoNDKY74Gajky+V1kfiIqb3dj9GQO =QliN -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-10-03 14:37, Otto Rodusek wrote:

PS: Hmm...both are production systems so they are never re-booted. I wonder if I reboot the system whether the problem goes away????

No, I tried that yesterday. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBsUmQACgkQIvFNjefEBxr4gACggVlQB9Wmdqxho1fTuF+qW+JS wIoAoLRShbxbDdwk+7eviEcGskYADw8o =dGJO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 4/10/12 12:49 AM, Anton Aylward wrote:

Take a look at what's in the config file in

/etc/rsyslog.d/listen.conf

On my Fedora system it has

$SystemLogSocketName /run/systemd/journal/syslog

That might explain a lot!

I'm holding off on the 12.x series for now, waiting until I get the new laptop :-)

Hi Anton, Thanks for helping out - however, I'm not sure what you mean. Could you possibly elaborate your answer? Also why would this affect rsyslog-5.10.0-2.4.1.x86_64 and not rsyslog-5.8.11-2.1.3.x86_64. There is no /etc/rsyslog.d/listen.conf in Opensuse 12.2, however there is a syslog socket in /run/systemd/journal/ so looks like it is defined somewhere. Thanks and best regards. Otto. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-10-03 18:49, Anton Aylward wrote:

Take a look at what's in the config file in

/etc/rsyslog.d/listen.conf

On my Fedora system it has

$SystemLogSocketName /run/systemd/journal/syslog

No such file in my 12.1 with the problem. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBsijMACgkQIvFNjefEBxokFACfY7Lw0/hfnjGoul5zXtEIUTAw ZzMAn1J5rFe9Dxk6tMnxHgKXJtPQNYgN =0wQn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hi, I tired the same logger command Carlos specified in bugzilla on both 12.1 (with sysvinit) and 12.2 with systemd. In both cases the full text has been added to /var/log/messages, no truncation observed Both systems have rsyslog 5.10.0 and are clean installs with no tweaking of syslog parameters (only local logging). Regards, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-14 12:51, Bernhard Voelker wrote:

On 09/12/2012 05:14 PM, Carlos E. R. wrote:

Hi Carlos,

it's one point how to get rsyslogd to capture all messages, but instead of trying to tune rsyslogd like Per and Otto suggested, I'd try to find out why fetchmail is sending so much messages to the syslog. What are the actual messages?

Well, it is the verbose log of fetchmail, and I want it. I can delete it later when I do not need it further. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBTFSYACgkQIvFNjefEBxpfmQCaA0NNN4vJFHBabQH5aYFpeYFy /rQAn21VU8ks3vs0abDjKFQRSxoRXfaB =gs+4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org