search for: logservers

Hey guys, I am trying to set up a logging server using log4r ! When I try to run the server I get the following error message "LogServer not supported. ROMP is required (RuntimeError)" I installed romp the way its mentioned in some blog with similar issue. Any ideas about it ? Thanks. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails:

Hi, as seen the Eve online support improved in the last time. The problem with that is that these things are only workarounds atm. So the next step should be that these hacks get improved so they can become real patches which are accepted by AJ. The current patchfile can be found at http://elfe.mine.nu/eve/linux/ So basicly some facts about the current EVE status:

Hi I am using rsyslog to get logs to a central box and they are stored in the format of /<hostname>/<year>/<month>/<day>/<logfilename> I need a solution that can trawl through these directories and pick up exceptions like failed logons and sudo usage that sort of thing. Has anyone got any clues as to what might help to achieve this, i am looking into logsurfer but

I have multiple servers running stock CentOS 7 rsyslog 7.4.7-16.el7, which are configured to log locally and over TCP to a remote logserver, also running stock CentOS 7 rsyslog. The remote server uses imptcp to receive, and pretty basic rules to parse and commit to disk. I have several systems that log prolifically, but periodically, they stop soon after the remote log server HUPs (daily

Dear Group, I'm having a problem connecting Solaris 10 Server to a Redhat Enterprise Linux 5.4 and meanwhile pretty clueless on that issue. Hopefully I get at least a hint, from your group, where to look at. key-length is 2048, permissions are correct on .ssh-directory and the files itself, keygen is done manually. On the Linuxserver we're using openssh-4.3p2-36.el5, on Solaris the

I have this: class foo::foobar ($version) { } which is called like this: class facility::sanjose inherits facility::common { class { foo::foobar: version => "1.3.13" } } puppet complains with this on the client: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find parent resource type ''facility::sanjose'' of type hostclass in

Overview ======== This module implements the Center for Internet Security (CIS) Security Configuration Benchmark for Red Hat Enterprise Linux 6 v.1.1.0 (avilable at http://benchmarks.cisecurity.org). Each scored control has been implemented as a class or a custom fact. Installation ============ Please either: - Clone git repo from https://github.com/arildjensen/cis-puppet - Run "puppet

A new archive was announced for packages that have need for frequent changes [see below]. In theory, we should not have to update logcheck rules in Sarge, because we know that it's packages, with the exception of security updates will remain constant. This does not change the fact that we may wish to update the database on sarge <: Any thoughts? -Todd ----- Forwarded message from

Hi, This morning I discovered what seemed to be a deliberate crash in auth_worker: Jun 7 23:02:09 localhost dovecot: auth-worker: Error: #007Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2) Jun 7 23:02:09 localhost dovecot: auth-worker: Error: Fatal error in defaults handling. Program aborted Jun 7 23:02:09 localhost dovecot: auth-worker: Error: *** glibc detected ***

I'm not sure if this message ever made it to you, Jamie. I had a reverse DNS problem shortly after it was sent. ----- Forwarded message from Todd Troxell <ttroxell at debian.org> ----- Date: Wed, 1 Jun 2005 01:22:18 -0400 From: Todd Troxell <ttroxell at debian.org> To: "Jamie L. Penman-Smithson" <jamie at silverdream.org> Subject: Re: Logcheck rules from other

On 09/07/17 18:37, John Jasen wrote: > I have multiple servers running stock CentOS 7 rsyslog 7.4.7-16.el7, > which are configured to log locally and over TCP to a remote logserver, > also running stock CentOS 7 rsyslog. The remote server uses imptcp to > receive, and pretty basic rules to parse and commit to disk. > > I have several systems that log prolifically, but

I had my application running perfectly in the 1.8.2th version of ruby. Now I have updated the version of ruby to 1.8.6(through the one-click installer). I again installed the rails,uuid, and all other plugins. I am able to start the application of some applications. But for this application it is giving this error. Can some body help me................THANKS in advance. => Booting WEBrick...

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