search for: log_outputs

Hello list. I have just a generic question. Exim delivers fine to dovecot-lda. My problems are the logfiles. Whenever I recieve a message Exim writes to dovecot.log as the user who recieves the mail. This forces me to have that logfile world writeable. I don't really like that. How do you guys deal with that? Here my transport: dovecot_delivery: driver = pipe # You may or may not

Hi all, I am not 100% sure if this is a -dev or a -user topic, but I am leaning towards the former. Feel free to cuss at me and tell me to ask -user, instead. I used to run a patchset that allowed full logs of everything taking place via OpenSSH. This also allowed me to replay any session, live or after the fact. I am fully aware of the security implications of logging everything, especially

I think, i had the same problem as you. When dovecot runs lmtp, no user is logged in, so there is no user from which you can get groups. So i think, my solution is (not really sure, if this is right, it's a long time ago, i played around) this transport in exim for local delivery dovecot_delivery:????????????? ? debug_print = "T: dovecot_delivery_pipe for $local_part@$domain translates

> On 28/08/2019 21:01 R.N.S. via dovecot <dovecot at dovecot.org> wrote: > > > > Am 28.08.2019 um 19:46 schrieb Jakobus Sch?rz via dovecot <dovecot at dovecot.org>: > > > > I think, i had the same problem as you. > > > > When dovecot runs lmtp, no user is logged in, so there is no user from > > which you can get groups. So i think, my

Using libvirt under openstack I encounter a problem when launching a VM with multiple partitions (2 G image) , While a single partition can be launched successfully . The launch is done with Openstack. We are using in libvirtd.conf log_level=1 and log_outputs="1:file:/var/log/libvirt/libvirtd.log" we can see that in /var/log/libvirt/libvirtd.log appear the following error message and the VM is finally shutdown : 2014-06-11 14:47:26.166+0000: 12971: error : qemuMonitorIO:614 : internal error End of file from monitor ( file attached be...

Hi, I am using virConnectOpen(const char *uri) to connect to the local hypervisor. When uri is set to "lxc:///", an error gets logged in /var/log/messages about failed connection. But I do not see any error for "xen:///". The machine does not have these drivers installed, and I am using libvirt 0.6.3. My questions are - 1. Why I see error in /var/log/messages for container

Hi, recently i had some domains stopped without any obvious reason for me. Unfortunately i didn't find the cause. I'd like to log information about the domains that i have more information the next time this will happen. In /etc/libvirt/libvirtd.conf i have: log_level = 3 log_outputs="3:file:/var/log/libvirt/libvirtd.log" which creates enormous log files, but with logrotate and xz i can manage that. But i think this is just related to libvirtd. The logs for the domains under /var/log/libvirt/qemu are poor and very small, nearly no information. Is there a way to be mor...

With libvirt 6.9.0, qemu 5.1.0, and following configurations: libvirt: key_file = "/etc/ssl/libvirt/server.lan.key" cert_file = "/etc/ssl/libvirt/server.lan.crt" ca_file = "/etc/ssl/libvirt/ca.crt" log_filters="3:remote 4:event 3:util.json 3:rpc 1:*" log_outputs="1:file:/var/log/libvirt/libvirtd.log" qemu: default_tls_x509_cert_dir = "/etc/ssl/qemu" default_tls_x509_verify = 1 migration with tls: virsh # migrate vm1 qemu+tls://server2.lan/system --persistent --undefinesource --copy-storage-all --verbose --tls never succeeds. Progress...

...need to reboot the box to reinstate it is there any known issue with libvirt/lxc on fedora 31 ? ***** here?s the little that I?ve been able to figure out so far by myself * I have turned on debugging of libvirtd as per the docs log_filters="3:remote 4:event 3:util.json 3:rpc 1:*" log_outputs="1:file:/var/log/libvirt/libvirtd.log? and am digging in that log file, as well as the system journal, and the containers journals, to try and find some correlation; * I have seen an error message saying this > virNetSocketReadWire:1850 : End of file while reading data: Input/output er...

hi all, i've exim 4.53RC2 + dovecot-cvs on OSX 10.4.2. i'm working on implementing recipient-delimiters for delivery from exim to a user's imap store using dovecot's cvs-lda. reading on the wiki (Jakob's latest comments?): " ... the part after the delimiter is passed to the lda as an additional parameter. so dovecot-lda should handle that parameter and leave the

So as to make sure that Dovecot Sieve's vacation system works Exim has to be forced to generate a "Reply-To:" header in the message (which it doesn't do by default). The current example for using the Dovecot LDA with Exim doesn't do this. Here is a replacement example for the local_delivery transport:- local_delivery: driver = pipe command =

I've just started using Dovecot, and can't seem to get the LDA to work. I get the following error: Mar 4 00:47:19 thebighonker dovecot: lda(ler): Error: user ler: Initialization failed: namespace configuration error: Duplicate namespace prefix: "" Mar 4 00:47:19 thebighonker dovecot: lda(ler): Fatal: Invalid user settings. Refer to server log for more information. Mar 4

> On 28/08/2019 21:07 R.N.S. via dovecot <dovecot at dovecot.org> wrote: > > > > Am 28.08.2019 um 20:02 schrieb Aki Tuomi via dovecot <dovecot at dovecot.org>: > > > > > >> On 28/08/2019 21:01 R.N.S. via dovecot <dovecot at dovecot.org> wrote: > >> > >> > >>> Am 28.08.2019 um 19:46 schrieb Jakobus Sch?rz via

hi All, I'm new to this list and also not a professional libvirt user:) I'm trying to use it for running a container. This is my config: <domain type='lxc'> <name>test</name> <uuid>d3667da2-061a-7b20-a29c-3afc798a257e</uuid> <memory>500000</memory> <currentMemory>500000</currentMemory> <vcpu>1</vcpu> <os>

...ubitzky wrote: > Using libvirt under openstack I encounter a problem when launching a VM > with multiple partitions (2 G image) , >While a single partition can be launched successfully . The launch is >done with Openstack. > >We are using in libvirtd.conf log_level=1 and >log_outputs="1:file:/var/log/libvirt/libvirtd.log" > we can see that in /var/log/libvirt/libvirtd.log appear the following >error message and the VM is finally shutdown : > Do you have some filters applied? If not, the file should have more messages. Actually, it should get so big it...

On 29.8.2019 12.18, R.N.S. via dovecot wrote: > >> Am 28.08.2019 um 20:02 schrieb Aki Tuomi via dovecot <dovecot at dovecot.org>: >> >> >>> On 28/08/2019 21:01 R.N.S. via dovecot <dovecot at dovecot.org> wrote: >>> >>> >>>> Am 28.08.2019 um 19:46 schrieb Jakobus Sch?rz via dovecot <dovecot at dovecot.org>:

...> >"rpm -aV" didn't turn up anything obvious: > >S.5....T. c /etc/libvirt/libvirtd.conf was modified for logging: ># diff libvirtd.conf libvirtd.conf.rpmnew >1,4d0 >< log_level = 1 >< log_filters="1:remote 1:event 1:json 1:rpc 1:qemu" >< log_outputs="1:file:/var/log/libvirt/libvirtd.log" >< # ># > >>> Is there a "how to" similar to [1] that lets one qemu to log that it was >>> invoked and how far it got? >>> >>> I removed qemu (dnf remote qemu; sudo dnf remove qemu-common) &gt...

On 29.8.2019 12.30, R.N.S. via dovecot wrote: > >> Am 29.08.2019 um 11:23 schrieb Aki Tuomi via dovecot <dovecot at dovecot.org>: >> >> >> On 29.8.2019 12.18, R.N.S. via dovecot wrote: >>>> Am 28.08.2019 um 20:02 schrieb Aki Tuomi via dovecot <dovecot at dovecot.org>: >>>> >>>> >>>>> On 28/08/2019 21:01

...ously attempting to use balance-rr and 802.3ad bonding modes on my host. However, I just changed to using "active-backup" and the problem remains. I have in /etc/libvirt/libvirtd.conf the following three lines (the rest is stock, i.e. all comments): log_level = 2 log_filters="" log_outputs="1:file:/var/log/libvirt/libvirt.log" Below I posted the contents of the libvirt log file after doing a "service libvirt start". Anyone ever fought this before? Thanks! [1] http://wiki.centos.org/HowTos/KVM [2] http://lists.centos.org/pipermail/centos-virt/2014-March/003722....

I have installed OVS from sources using the installation steps mentioned on this link: http://docs.openvswitch.org/en/latest/intro/install/general/ I had installed libvrt, KVM, QEMU and all the necessary packages using apt-get. My KVM-QEMU hypervisor has been running well. To add a VM with the port attached to OVS bridge I changed the XML domain file as per the instructions on this page: