similar to: CEBA-2014:2004 CentOS 6 rsyslog BugFix Update

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi all, I know this comes from upstream (and most likely from the rsyslog project itself), but what's your opinion about Google Ads in system documentation files? > [peckel at mucnvjmppmtr01 ~]$ cat /etc/redhat-release > Red Hat Enterprise Linux Server release 6.7 (Santiago) > [peckel at mucnvjmppmtr01 ~]$ grep google /usr/share/doc/rsyslog-5.8.10/* >

CentOS Errata and Security Advisory 2012:0796 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0796.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ae69919d4970410464c2cf6f2754565ce793cada7db3f910e36fbdb1f5c82f37 rsyslog-5.8.10-2.el6.i686.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Bugfix Advisory 2013:1214 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1214.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 658fbf427d84c14563ba649a1f9f1d313aea812e2a8bf034a58fcb6efd1233e7 rsyslog-5.8.10-7.el6_4.i686.rpm

Peter Eckel wrote: > Hi all, > > I know this comes from upstream (and most likely from the rsyslog project itself), but what's your opinion about Google Ads in system documentation files? > >> [peckel at mucnvjmppmtr01 ~]$ cat /etc/redhat-release >> Red Hat Enterprise Linux Server release 6.7 (Santiago) >> [peckel at mucnvjmppmtr01 ~]$ grep google

On 10/29/2016 10:12 PM, Hadi Motamedi wrote: > I am using a centos server for cdr billing and mediation device on a remote > network. I am experiencing problem that I am suspicious it comes from main > supply power cut at the remote site. The power supply to the remote site > comes from battery charger that will be automatically switched in circuit > under main supply power cut but

Thank you very much for your reply . So you mean under the /var/log/messages it is distinguishable that which logs come from operator initiated reboot and which ones come from sudden power cut and then booting from scratch when power resumed ? Am I correct ? On Sat, Oct 29, 2016 at 11:44 PM, John R Pierce <pierce at hogranch.com> wrote: > On 10/29/2016 10:12 PM, Hadi Motamedi wrote:

And no sooner do I send the email than I spot the problem. Oops! Sorry about that. The sshd_config needed to contain a different internal-sftp line: Match User test-sftp-only ChrootDirectory /home/sftp/mcsosftp ForceCommand internal-sftp -f AUTHPRIV -l INFO PasswordAuthentication no AuthorizedKeysCommand /usr/local/bin/get_sftp_key That's gotten

Hello, I recently upgraded a server from CentOS 6.2 to 6.3 I found a change in the behavior of rsyslog's configuration file that I found particularly interesting. The "$PreserveFQDN on" directive was not being recognized as the config remained unchanged during the upgrade. This incorrect behavior caused the host to syslog with only the host name and not it's fully qualified

Hello everyone, We have some chrooted sftp-only users on a CentOS release 6.6 server. The server had been logging their actions, but after recent updates the logs have stopped. The server correctly logs non-chrooted users: Sep 14 17:47:24 vsecure4 sshd[1981]: Accepted publickey for jcours from 192.168.10.166 port 42545 ssh2 Sep 14 17:47:24 vsecure4 sshd[1981]: pam_unix(sshd:session):

centos 6.4, setup to be syslog server. Doing remote syslog using tcp works fine, so now want to add relp. I installed the rsyslog-relp package and told rsyslog.conf to use it: # RELP Syslog Server: $ModLoad imrelp # provides RELP syslog reception $InputRELPServerRun 20514 when I restart rsyslog I am told it does not like my InputRELPServerRun line: Oct 28 13:43:54 scan rsyslogd: [origin

Dear all? I install new version centos 6.4 64bit and everything is ok except it cannot reboot, below is the /var/messages information: May 20 10:08:07 ravi2 smbd[1712]: failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL May 20 10:22:24 ravi2 init: tty (/dev/tty1) main process (1727) killed by TERM signal May 20 10:22:24 ravi2 init: tty (/dev/tty2) main process (1729) killed by TERM

So I was having an issue with rsyslog in one of my centos 6.6 hosts: [root at scan ~]# /etc/init.d/rsyslog start Starting system logger: *** glibc detected *** /sbin/rsyslogd: double free or corruption (fasttop): 0x00007f80cc3da880 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x75e66)[0x7f80c9210e66] /usr/lib64/librelp.so.0(relpTcpDestruct+0x5f)[0x7f80c7f1a9bf]

Also, the last message in /var/log/messages before the crash was: ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

Hi there, Could someone please comment on the following hard-lock (*). Staring at the code, I see `nvkm_rd32` calls are enclosed in a timeout detection, except one. drivers/gpu/drm/nouveau/nvkm/engine/gr/g84.c#L171 ... nvkm_msec(device, 2000, if (!(nvkm_rd32(device, 0x100c80) & 0x00000001)) break; ); ... Would it make sense to also enclose this in the do/while loop ? Full ref: *

I have a server thats been running fine for a year or two lock up a few times recently, requiring power cycling. The /var/log/messages after a lockup last night is appended to this message. hardware is a pretty typical server, Supermicro X8DTE-F motherboard, dual Xeon X5650, 48GB ECC memory, LSI SAS 2008 for the boot disks, and LSI MegaRAID SAS 9261-8i for the data volume. Lots of 3TB

The following updates were released with the CentOS-6.5 Release Announcement. You can see the individual announcements by viewing the CentOS-CR-Announce Mailing List here: http://lists.centos.org/pipermail/centos-cr-announce/2013-November/thread.html If you want updates as fast as possible during CentOS point releases, please consider enabling the CentOS Continuous Release Repository:

Update me Richie, Meanwhile, I've booted the server in latest kernel, Its still not working for me. 2015-03-17 0:54 GMT+05:30 Thirumalai Nambi <thirumalai.sandy@gmail.com>: > > libtool-2.2.6-15.5.el6.x86_64 > upstart-0.6.5-13.el6_5.3.x86_64 > atmel-firmware-1.3-7.el6.noarch > redhat-rpm-config-9.0.3-42.el6.centos.noarch > plymouth-scripts-0.8.3-27.el6.centos.1.x86_64

libtool-2.2.6-15.5.el6.x86_64 upstart-0.6.5-13.el6_5.3.x86_64 atmel-firmware-1.3-7.el6.noarch redhat-rpm-config-9.0.3-42.el6.centos.noarch plymouth-scripts-0.8.3-27.el6.centos.1.x86_64 patchutils-0.3.1-3.1.el6.x86_64 bc-1.06.95-1.el6.x86_64 cscope-15.6-6.el6.x86_64 coreutils-8.4-37.el6.x86_64 ncurses-devel-5.7-3.20090208.el6.x86_64 libselinux-utils-2.0.94-5.8.el6.x86_64