similar to: Application trying to use IPv6

Hi, I have problems with rsyslog on C7. In /etc/rsyslog.d/iptables.conf I have: # Log all iptables stuff separately :msg, contains, "iptables: " { action(type="omfile" file="/var/log/iptraf/info") stop } THis works fine. In /etc/rsyslog.d/mail.conf I have: # Log all the mail messages in one place. if ($syslogfacility-text == 'mail') then {

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

On 10/14/2015 01:56 PM, Jonathan Billings wrote: > lsof /dev/log Uhmm ... that is not what I expect: lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME systemd 1 root 27u unix 0xffff880250ea0f00 0t0 1436 /dev/log systemd-j 263 root 5u

Hi, My rsyslog is not working as expected. I have some thing in rsyslog.d that do well, like this: # Log all iptables stuff separately :msg, contains, "iptables: " { action(type="omfile" file="/var/log/iptraf/info") } No problems with that. Bu what's in /etc/rsyslog.conf like: mail.* /var/log/mail/info don't do anything at all. Rsyslogd -N1 is OK,

I''m pretty sure this is my fault but I need some help in fixing the system. It was installed at one point with snv_29 with the pre integration SUNWzfs package. I did a live upgrade to snv_42 but forgot to remove the old SUNWzfs before I did so. When the system booted up got complaints about kstat install because I still had an old zpool kernel module lying around. So I did pkgrm

TODO: Fix selinux :P --- Makefile.am | 1 + ovirt-node.spec.in | 3 ++ scripts/ovirt | 3 ++ scripts/ovirt-managed-rsyslog | 72 +++++++++++++++++++++++++++++++++++++++++ 4 files changed, 79 insertions(+), 0 deletions(-) create mode 100755 scripts/ovirt-managed-rsyslog diff --git a/Makefile.am b/Makefile.am index 0374f07..5201a79 100644

Author: ahl Repository: /hg/zfs-crypto/gate Revision: a2677fc0a5fb6895ed56fc4698646ece44978a48 Log message: 4970475 There should be a stackdepth equivalent for userland 5084954 value of dip can be incorrect in autovec 6181505 dtrace sysinfo:::modload probe does not fire when using ''modload'' 6265417 schedctl-yield isn''t listed in sdt_subr.c 6272558 gcc and dtrace

Adds rsyslog configaration module --- scripts/logging.py | 89 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 89 insertions(+), 0 deletions(-) create mode 100755 scripts/logging.py diff --git a/scripts/logging.py b/scripts/logging.py new file mode 100755 index 0000000..6a32b7a --- /dev/null +++ b/scripts/logging.py @@ -0,0 +1,89 @@ +#!/usr/bin/python +# +# Configures

On 10/14/2015 07:09 AM, C.L. Martinez wrote: > Uhmm ... that is not what I expect: > > lsof: WARNING: can't stat() fuse.gvfsd-fuse file system > /run/user/1000/gvfs > Output information may be incomplete. > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > systemd 1 root 27u unix 0xffff880250ea0f00 0t0 1436 /dev/log > systemd-j

This is a similar post to one I've made on the rsyslog list that has received no responses after four days, so I figured I'd try here since the problem seems to be CentOS specific. This is also my second attempt to send it to this list as the first seems to have never showed up. I am trying to test remote logging between two CentOS 6.3 systems and unable to get the client logs to show up

Nodes will use rsyslog to forward their logs to the server in /var/log/remote. --- installer/modules/ovirt/files/rsyslog.conf | 65 ++++++++++++++++++++ installer/modules/ovirt/manifests/ovirt.pp | 26 ++++++++ .../modules/ovirt/templates/ovirt-dns.conf.erb | 1 + ovirt-server.spec.in | 3 + scripts/ovirt-rsyslog-kerbsetup

On 10/14/2015 06:42 PM, Gordon Messmer wrote: > On 10/14/2015 07:09 AM, C.L. Martinez wrote: >> Uhmm ... that is not what I expect: >> >> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system >> /run/user/1000/gvfs >> Output information may be incomplete. >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> systemd

Hello All, Anyone out there using ISDN PRI from either MCI or XO/Allegiance? Gotta make the choice today and the difference per month is only about $25 in favor of MCI. Billing is pretty much the same between the two so I have pretty much no point of reference on which to choose. Any thoughts from anyone experienced with these two compnies would be greatly appreciated! Thanks, Wiley

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

I'm looking to acquire a few new core switches for our network which would be a major upgrade from the cheap unmanaged things we currently have. Basically, just users, servers, and other simple network devices will be plugged into them but I'd like to start doing some testing with iSCSI for various non-production reasons. I have no allegiance to a particular vendor although I do have a

I have several network appliances, and I want aggregate their syslog output for later analysis. Eventually I might think about a Splunk box, but for the interim I'm hoping to just build a CentOS 6 syslog server and have it aggregate everything on it for quick review. I installed rsyslog and am looking through the /etc/rsyslog.conf file for what I configure to (a) listen for syslog input from

Hello everyone, I am trying to set up a bare system to boot DOS over the network using PXE. My PXE server is a Windows XP system. I am following step by step in the instructions found at http://home.allegiance.tv/~joem298/. Everything seems to work at first, but at the end the error was the file 'pxelinux\default' configuration file could not be found. I am sure that all the files are

Peter- I am working on developing a system to perform network boot and automated system installs of many systems, and I would like to use PXE. New systems would boot via PXE, then directed to special images that partition, format and install the server. Upon reboot, the system would boot off of local disk. Do you know of any resources, or of anyone that has begun to develop an infrastructure

Hi unfortunately VirtualBox does not work yet in a Solaris Dom0: I installed VirtualBox beta and it runs fine on bare metal. Unfortunately the necessary driver does not load automatically in a xVM Dom0. It can be loaded manually but it looks like it does not work in a Dom0: bash-3.2# modinfo | grep vbox # this is a one time task: bash-3.2# cp /platform/i86pc/kernel/drv/amd64/vboxdrv

Hi everyone! I need some help with a page fault that occurs in Phantasy Star Online: Blue Burst. The annoying thing is that the page fault seems to cause the game to hang so the debug log is limited (I have to forcibly terminate the program with System Monitor). Here's what I do have: Code: fixme:imm:ImmDisableIME (0): stub fixme:imm:ImeHandleNotify