search for: syslogging

I just started messing with puppet, and i love it! I have used cfengine in the past, and were in process of planing to replace cfengine now. One thing thats stumped me this weekend and i know i read your working on virtal defines so i can''t do that, but how can i get arond this issue with the curretn setup. I think i am missing something fundamentally simple here. i have this

Yesterday, I switched our node structure from using node basenode, node nodetype inherits basenode, to using node classes per the changes discussed recently on this list and as defined in the wiki:GlossaryOfTerms. In the manifest, we have a syslog module which sets up all the components of syslog-ng we''re using. The ''syslog'' class is used by default on clients and then

So, this has always puzzled me a bit. By convention, init.pp contains one class, named the same as the module. However, what is the convention when the module may have multiple external access points? Say you have a module called ''syslog'' which provides both a client and a server class. I typically have used syslog::server and syslog::client. I''ve ended up using this

I''m trying to use environments and seem to be failing. Right now I have 4 defined environments: production, cat, development, beta They are defined as follows on my puppetmaster: cat /etc/puppet/puppet.conf [main] pluginsync = true vardir = /var/lib/puppet manifest = /etc/puppet/environments/production/site.pp modulepath = /etc/puppet/environments/production/modules [master] reports =

In case anyone is interested, I found the problem. I was running samba in a container that did not have any syslog service (rsyslogd or syslog-ng) running. By default, samba syslog only sends messages to the system's syslog socket and there was nothing listening on it so the messages just got dropped. I put rsyslogd in the container and configured it to listen on the syslog socket and am

If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? NOTIFYFLAG ONLINE SYSLOG NOTIFYFLAG ONBATT SYSLOG NOTIFYFLAG LOWBATT SYSLOG NOTIFYFLAG FSD SYSLOG NOTIFYFLAG COMMOK SYSLOG NOTIFYFLAG COMMBAD SYSLOG NOTIFYFLAG SHUTDOWN SYSLOG NOTIFYFLAG REPLBATT SYSLOG NOTIFYFLAG NOCOMM SYSLOG NOTIFYFLAG NOPARENT SYSLOG The 'wall'

Hi, I''m learning puppet as that is what they use at my current work, though that could change... Question 1: Last place of work, we wrote our own perl based system which was extremely simple and concise to drive - eg to distribute a file, we would put it in: <nfsdir>/noarch/dist/etc/syslog-ng/syslog-ng.conf/ # which means create a file /etc/syslog-ng/syslog-ng.conf on the

Trying to figure out if there's a way to get syslog.conf to direct remote logging from a wireless access point to log to a separate file instead of the main syslog and can't figure out how that could be done from man syslog.conf (or man 2/3 of syslog) this clearly doesn't work 192.168.1.251.* /var/log/WAP-2.log which according to the man page, makes

Thanks Simon,I think my question got a bit lost amongst all the grub issues - does anyone else have information about whether any references to syslog.target in systemd unit files can be removed?ChrisSent from Samsung Mobile on O2 -------- Original message -------- From: Simon Matter via CentOS <centos at centos.org> Date: 31/07/2020 10:02 (GMT+00:00) To: CentOS mailing list <centos

I have a 64bit centos 5.2 system. My router supports sending logs to a syslog server, so I was hoping to send them to my centos box so they are easier to keep an eye on. I've been googling for howto's etc, but I didn't think syslog would be that difficult. Do I need to use syslog-ng or can I use the syslog that's installed with centos 5.2? Any suggestions or guidance? Thanks,

On Feb 25, 2014, at 1:13 AM, Kris Jordan wrote: > If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? > > NOTIFYFLAG ONLINE SYSLOG > NOTIFYFLAG ONBATT SYSLOG > NOTIFYFLAG LOWBATT SYSLOG > NOTIFYFLAG FSD SYSLOG > NOTIFYFLAG COMMOK SYSLOG > NOTIFYFLAG COMMBAD SYSLOG > NOTIFYFLAG SHUTDOWN SYSLOG > NOTIFYFLAG

Hi All, I'm using a recent post 2.6.1 build provided by Fred (executables have modified date of 9th August) I have configured upsmon.conf with :- NOTIFYCMD C:\NUT\etc\NotifyCmd.bat and :- NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG LOWBATT SYSLOG+EXEC NOTIFYFLAG FSD SYSLOG+EXEC NOTIFYFLAG COMMOK SYSLOG+EXEC NOTIFYFLAG COMMBAD SYSLOG+EXEC

I have a simple mirror pool with 2 disks. I pulled out one disk to simulate a failed drive. zpool status shows that the pool is in DEGRADED state. I want syslog to log these type of ZFS errors. I have syslog running and logging all sorts of error to a log server. But this failed disk in ZFS pool did not generate any syslog messages. ZFS diagnosists engine are online as seen bleow. hrs1zgpprd1#

Hello Puppet Users, The following is the result of my first attempt to create a useful component definition of something I wanted Puppet to manage. Instead of just copying over "precompiled" syslog.conf files, I thought it would be more useful if I could specify the elements of the syslog.conf file. (Ultimately, I think this should be defined as a type.) I hit a few hurdles and I

I am thinking about writing some sort of deamon which signs syslog files with PGP. This should help dedecting unauthorised changes in the syslog files. What I have in mind works as follows: Whenever a new line is added to a syslog file the existing syslog file checked against the privious made signature. If the file passes this test, the new line(s) is/are added. Then a new signature is

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

file { "/var/log/syslog": target => "/var/log/messages" } generates the following error: err: //henson/stanford/syslog/file=/var/log/syslog: Failed to retrieve current state: undefined method `should'' for false:FalseClass

Hello guys Yesterday i started do configure my Mustek Powermust650 with nut using the megatec_usb driver. Everything works fine except for the mailing when something happens. My upsmon looks like this: MONITOR powermust650 at localhost 1 local controller master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /root/upsmailer POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15

I'm looking for suggestions as to a good general method of remote-logging services such as nginx or anything else which doesn't support syslog natively. I'm aware that there's an nginx patch, and we're evaluating this. It may be the way we fly. However there are other tools which may not have a patch for which remote logging would be useful. If there's a general soution

hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD