similar to: Re: syslogd communication

There is a storage issue with the hoster. Things should get back to normal soon... hopefully! Arno (sent from my S3... please excuse my brevity) Le 8 oct. 2014 00:22, "Paul Kenyon" <pkenyon at advancedclustering.com> a ?crit : > Hello, > > I see you're a member of networkupstools on github. Do you have any > contact with the folks who manage the website? Getting

> > Second, why don''t you implement a "black box" log system ? > > That''s all log generated by all hosts on your network is forwarded > > to a seperate log machine called black box. Such computer grants > > no access to any body whatsoever except for user "root" loginning on > > the console. > > how to setup a

Hello, It's a bit off topic, but I'm hoping someone has seen this before. I'm running a couple of headless boxes, one is 4.7 release, the other is 4.8 release. Both have the same issue with newsyslog when I've got the serial port enabled for console management. (-h in boot.conf and a getty running on cuaa0 after the boot process) Logrotate tries to send an HUP to syslogd, but

Package: logcheck Version: 1.2.69 The inetutils-syslogd (2:1.5.dfsg.1-9) package provides a system logging daemon. syslogd periodically logs the following message: Dec 17 00:29:11 host syslogd (GNU inetutils 1.5): restart The following logcheck rulefile works to filter the messages from the "System Events" email: # cat inetutils-syslogd ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd

Hello! on my centos 4.4 i have enable selinux, but after this change syslogd can't no more run: # /etc/init.d/syslog restart Shutting down kernel logger: [ OK ] Shutting down system logger: [FAILED] Starting system logger: syslogd: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or

Hi all. Bug bin/8865 strikes again? I have a FreeBSD 4.8 Release machine. After sometime, the logs just aren't modified, syslogd just doesn't log. The last entry on /var/log/messages is from may 15. Could this be caused to use a serial console (-P on /boot.config, no keyboard attached) to access the machine? There was once a time that when i Control^D'ed on the serial console and

I made a quick change to syslogd(8) so that it can drop root privileges immediately after starting up. It opens up the log sockets (UNIX and network domains) and writes the PID files before dropping privs. It drops privs before openning log files and writing to users. Therefore, you would need to modify your log file permissions appropriately. As for writing to users, ttys generally are writeable

Yesterday I activated SELinux in targeted mode, then I rebooted and started receiving some error messages in the system services initialization: ====================================================================== audit(1156518721.252:2): avc: denied { read } for pid=2223 comm="syslogd" name="libc-2.3.4.so" dev=dm-0 ino=50441 scontext=user_u:system_r:syslogd_t

In response to my post regarding core-sdi's secure syslogd - ssyslogd. Sorry it has taken me so long to post this...been super busy... I didn't get a lot of responses back from the list regarding ssyslogd. Just a couple of people who said they were using it, and it was working. I grabbed the latest version (ssyslogd-1.22) from http://www.core-sdi.com/ssyslog/. I had a problem compiling

Hi all, I have installed a CentOS4.3 box and migrated some application from FC1 to the new box, everything else runs perfectly except syslogd/klogd. /etc/rc.d/init.d/syslog starts without any problem, but there is nothing logged into /var/log/messages, even I restart the service. However, I tried to shut the service down and run "syslogd -m 0 &" and "klogd -x &" as

Package: logcheck Version: 1.2.32 Severity: wishlist /etc/cron.daily/sysklogd restarts syslogd at the end of the script. This causes a daily log message, currently missed by logcheck: Jan 14 06:55:22 pyloric syslogd 1.4.1#16: restart (remote reception). I'm currently using this regex in ignore.server.d/local-syslogd: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd 1\.4\.1#16: restart \(remote

" Message from syslogd at localhost at Aug 27 08:57:53 ... kernel:Disabling IRQ #17" is the message I got on all my terminal windows at the time indicated. What is it complaining about? What should I do about it? I got some information from dmesg. It mentions IRQ 17, but the only error is from before the most recent hibernation. Here are some excerpts, in order from dmesg: SELinux:

Just updated our syslog server to 4.8-STABLE #0: Mon Apr 7 09:39:27 EDT 2003 In my rc.conf I have: # fgrep syslog /etc/rc.conf syslogd_program="/usr/local/sbin/syslog-ng" syslogd_flags="" Syslog-ng starts up appropriately; but syslogd also tries to start now. Since the port's already in use, rc hangs during boot until I ctrl-c at that point. Perhaps something's not

--------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: Denial of service attack in syslogd Advisory ID: RHSA-1999:055-01 Issue date: 1999-11-19 Updated on: 1999-11-19 Keywords: syslogd sysklogd stream socket Cross references: bugtraq id #809 --------------------------------------------------------------------- 1. Topic: A

One of our sites is currently testing Samba 3.0.21c as PDC on HP-UX 11.00 with openldap backend. >From time to time - about every two days - it suddenly becomes impossible for the clients (NT4 & XP) to save any more files to the samba shares. When the problems start occurring they simply stop and restart samba, and then everything works again for a couple of days. Please not that the samba

Hi, This advisory has a bit more than the Red Hat one.... Roger. ----- Forwarded message from Alfred Huger ----- >>From owner-bugtraq@SECURITYFOCUS.COM Mon Nov 22 18:49:41 1999 Approved-By: aleph1@SECURITYFOCUS.COM Message-ID: <Pine.GSO.4.10.9911220906250.11753-100000@www.securityfocus.com> Date: Mon, 22 Nov 1999 09:08:08 -0800 X-Reply-To: Alfred Huger

http://bugzilla.mindrot.org/show_bug.cgi?id=111 Summary: sshd syslogs raw untrusted data Product: Portable OpenSSH Version: -current Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

Hi, Our environment: HP-UX 11.00 server / Samba 3.0.21a as PDC / OpenLDAP backend We're developping a migration from AS/U to a Samba PDC. Currently we have following problem: logging onto an NT4 workstation is almost instantaneous, but when logging onto an XP workstation, this happens: (1) We type the user and password in Windows logon. (2) Windows logon immediately accepts user and

Hi guys, I was playing on vmware with btrfs on complete disks /dev/sd{b,c,d,e}. Next I decided to use partitions, so I created /dev/sd{b,c,d,e}1 and used those, worked fine! Afterward, I mistakenly re-ran an old command on the full disk ( mount -t btrfs -o subvol=. /dev/sdb /mnt/ ) notice this is sdb not sdb1, and I got this spectacular kernel freeze. Let me know if that''s some bug.

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Hi! the error suddenly appeared when rebooting one of the etch instances using xm reboot <name> on our etch server DEVIDE:~# DEVIDE kernel: ------------[ cut here ]------------ DEVIDE kernel: CPU: 3 DEVIDE:~# Message from syslogd@DEVIDE at Tue May 8 11:45:27 2007 ... Message from syslogd@DEVIDE at Tue May 8 11:45:27 2007