similar to: Empty /var/log/messages

Hi, My volume home is configured in replicate mode (version 3.12.4) with the bricks server1:/data/gluster/brick1 server2:/data/gluster/brick1 server2:/data/gluster/brick1 was corrupted, so I killed gluster daemon for that brick on server2, umounted it, reformated it, remounted it and did a > gluster volume reset-brick home server2:/data/gluster/brick1 server2:/data/gluster/brick1 commit

You do not need to reset brick if brick path does not change. Replace the brick format and mount, then gluster v start volname force. To start self heal just run gluster v heal volname full. On Thu, Feb 1, 2018 at 6:39 PM, Alessandro Ipe <Alessandro.Ipe at meteo.be> wrote: > Hi, > > > My volume home is configured in replicate mode (version 3.12.4) with the bricks >

On 2018-03-19 (13:19 MDT), Odhiambo Washington <odhiambo at gmail.com> wrote: > > Plus, if dovecot is able to write to a file owned by root:wheel, then there is a BIG problem right there!!! Logging is generally done by syslogd, not directly by the process. So no, dovecot is not writing to a file owned by root anymore than postfix is writing to mail.log which is also owned by root.

Hi, I simplified the config in my first email, but I actually have 2x4 servers in replicate-distribute with each 4 bricks for 6 of them and 2 bricks for the remaining 2. Full healing will just take ages... for a just single brick to resync ! > gluster v status home volume status home Status of volume: home Gluster process TCP Port RDMA Port Online Pid

On 2018-03-19 (14:20 MDT), Odhiambo Washington <odhiambo at gmail.com> wrote: > > I have been running FreeBSD since 1997, so I know quite a lot about it! > I know about /etc/syslog.conf, but you do realize now that you are conflicting yourself? No, I am not, I pointed out that dovecot does not writ ether logs, but that is a task generally managed by syslogd. then I said that in my

Hi, I have been trying to get the messages from iptables out of /var/log/messages with no luck. I tryied this settings: iptables -j LOG --log-level warn in /etc/syslog.conf kern.warn /var/log/critical kern.none;.... /var/log/messages # have no other call to kern o warn in syslog.conf service syslogd restart itpables -L -nv|grep LOG All seems ok, but the messages are still

Hello, I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115 connected by RS-232. I expected this setup to shut down before running out of battery power, but I either missed some important configuration or something else went wrong: The syslog says: Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line

/var/log/dovecot exists and has a lot of logging in it, but I get errors (in mail.log) on an always_bcc action in postfix: mail postfix/pipe[13015]: 401cvS0R8BzbSkL: to=<backup+073.kremels-kreme at doamin.tld>, relay=dovecot, delay=398058, delays=398045/13/0/0.04, dsn=4.3.0, status=deferred (temporary failure. Command output: Can't open log file /var/log/dovecot: Permission denied )

lspci shows MSI enabled for PCI device. PCI passthrough works fine. However, as soon as the MSI driver for card is insmodded, kernel panics. This is on xen-unstable. Tried the same with xen-3.3.0 which is supposed to have MSI passthrough, but the same guest shows MSI as disabled. Any else seen this bug, or know of a workaround ? Trace is as follows : ------------[ cut here ]------------

Hello, there are problems with quota dict when multiple dovecot deliver processes are launched in parallel. It can be reproduced by sending a mail with multiple different recipients - the mail is delivered OK to all recipients, but the quota are not updated correctly in sql. I looked at the code and it seems that the problem is somewhere in dict cache. If I configure in Postfix max number of

On Tue, Jan 26, 2016 at 1:51 PM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 26.01.2016 14:35, Andrei Perietanu wrote: > > On Tue, Jan 26, 2016 at 12:39 PM, Michal Privoznik <mprivozn@redhat.com> > > wrote: > > > >> On 26.01.2016 12:30, Andrei Perietanu wrote: > >>> Hi all, > >>> > >>> I am running KVM on a 3.18

changeset: 8830:fcc833cbaf82 tag: tip user: kaf24@firebug.cl.cam.ac.uk date: Mon Feb 13 10:41:23 2006 +0100 summary: Return real error code from Xen /dev/mem, not EAGAIN. x460: x86_32: Status: - dom0 boots fine - xend loads fine - single HVM domain loads fine - Multiple HVM domains load fine - destruction of any HVM domain causes dom0 to reboot Issues affecting

Hello, I'm seeing syslog messages "bleed" from the host and other LXC into the messages, maillog, secure logs of other LXCs. I'm using libvirt 1.0.0 on a host with systemd and kernel 3.9.10. Each LXC is running an older non-systemd linux distribution Is this a known issue? Is there a work around? Thank you for you time, Jim -- James R. Leu | Director of Technology | INOC

Hello, it seems that there is some bug in authentication cache code in dovecot version 1.1.alpha4 - after login attempt with wrong password the correct password also will fail. I can reproduce it very easy: $telnet 10.10.10.30 110 +OK Server. <861.2.46e6c679.jZ8QYpFmU8ZN6XIq7zPhkw==@server2> user testuser +OK pass pass +OK Logged in. quit +OK Logging out. Connection closed by foreign host.

Problem whith dnsupdate --> /etc/samba# samba_dnsupdate --all-names --fail-immediately Failed to get Kerberos credentials, falling back to samba-tool: kinit for DOMAIN-SERVER2$@POLICIA2.RIONEGRO.GOV.AR failed (Cannot contact any KDC for requested realm) ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') File

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

On Fri, 11 Sep 2015, Jason Welsh wrote: > ok, I have moved home out of the way and restarted automounter.. > and now I see the /home directory appear when autofs is started, but there is > still nothing there.. > > [root at server2 home]# cd /home > [root at server2 home]# ls > [root at server2 home]# cd jason > -bash: cd: jason: No such file or directory > [root at

I recently upgraded wine from 0.9.7 to 0.9.12 and while checking out that things were working I started up Google Earth but had the following error in terminal: Message from syslogd@TheVoid at Sun May 7 02:40:26 2006 ... TheVoid kernel: Bad page state at free_hot_cold_page (in process 'GoogleEarth.exe', page c125be60) Message from syslogd@TheVoid at Sun May 7 02:40:26 2006 ... TheVoid

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 Rowland, > Remove 'map untrusted to domain = Yes', it has been removed. > > Add 'domain logons = Yes' > > This gets it back to being a PDC: thanks for the hints! I did that, but it doesn't help. I guess the problem is not on the PDC server but on SERVER2. That's the one that got upgraded and stopped working (even with the non-pdc config of SERVER1). I