search for: mxs

Greetings, All! I'm facing a problem with one particular directory in a mailbox. The exact error line is: Apr 7 12:00:21 mxs dovecot: imap(vera): Error: rename(/home/vera/.mail/INBOX/???? ??????????/new/1678353168.M710968P25673.mxs.ads.ccenter.lan,S=5442,W=5513:2,ST, /home/vera/.mail/INBOX/???? ??????????/cur/1678353168.M710968P25673.mxs.ads.ccenter.lan,S=5442,W=5513:2,ST) failed: Too many links The rest of the mailbox...

...ackup depository [backup] comment = Backup Repository force create mode = 0777 force directory mode = 6777 path = /mnt/data/backup browseable = no writable = yes valid users = NYC-14\backup, NYC-14\mcasale, NYC-14\administrator, NYC-14\sys_bak, NYC-14\PDS$, NYC-14\RDS$, NYC-14\MXS$, "NYC-14\Domain Admins" # bulk data storage for Development [bulk] browsable = no force create mode = 0777 force directory mode = 6777 path = /mnt/data/bulk writable = yes guest ok = yes # clients data [Clients] browsable = yes comment = Clients of Kn...

...y Mac, until I got an Ipad to test with - and never connected it to my Mac - and had the same time issue. It seems Mail.app uses the timestamp ('arrived date'?) on the mail file itself (Maildir here) to display the time. So.. I have dovecot 1.2.10 installed on top of vpopmail (multiple MXs, delivering to OpenSolaris NFS share via tcp), and it seems that deliver is using the GMT time when writing the Maildir file, and vdelivermail just uses the adjusted time.. Or maybe it just allows the OS to write the timestamp. Either way, is this a known issue with deliver - or is there a pat...

On 03/24/2016 02:26 AM, mxs kolo wrote: > use libvirt 1.3.2, it's more stable and never show negative values > for memory and swap inside container > The latest version available for CentOS/RHEL is version 1.2.17. What site are you using to get the rpm for version 1.3.2? Peter

...if anyone has any plugins for AV integration directly into dovecot. Our old pop servers have been scanning messges as they're moved from new->cur in the inbox and, at least where user's aren't poping every few seconds, there is occasionally enough time between scanning through the MXs to message retreval to snag a few more virues with updated definitions before they reach customers. Anyone doing anything similar? -- Kelsey Cummings - kgc at corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000...

Hi all After upgrade from Centos 7.5 to Centos 7.6, our test environment geted new version of libvirt 4.5.0 In which our old containers have broken config and can't start: 2018-12-05 10:38:32.634+0000: 18010: debug : virLXCControllerGetNICIndexes:368 : Getting nic indexes 2018-12-05 10:38:32.634+0000: 18010: error : virLXCControllerGetNICIndexes:400 : unsupported configuration: Unsupported

On 04/26/2016 07:44 AM, mxs kolo wrote: > Now reporduced with 100% > 1) create contrainer with memory limit 1Gb > 2) run inside simple memory test allocator: > #include <malloc.h> > #include <unistd.h> > #include <memory.h> > #define MB 1024 * 1024 > int main() { > int total = 0;...

Has anyone seen this issue? We're running containers under CentOS 7.2 and some of these containers are reporting incorrect memory allocation in /proc/meminfo. The output below comes from a system with 32G of memory and 84GB of swap. The values reported are completely wrong. # cat /proc/meminfo MemTotal: 9007199254740991 kB MemFree: 9007199224543267 kB MemAvailable: 12985680

Hi, Thanks for the reply. I guess RHEL choose v2.2.10 <http://dovecot.org/list/dovecot-news/2013-December/000268.html> as it is a good release with all the things working. My source of confusion are from 1) http://dovecot.org/oldnews.html I have gone through each release update news. Lots of work and bug fix after v2.2.10

On 04/08/2015 09:38 AM, mxs kolo wrote: > Hi all. > > I use LXC on Centos 7 x86-64, with libvirt version 1.2.6 and 1.2.12 > My container has bridged network: > # virsh dumpxml test1 > <domain type='lxc'> > <name>test1</name> > <uuid>518539ab-7491-45ab-bb1d-3d7f11bfb0...

Hi all. Has someone success story with using autofs + nfs inside libvirt LXC container ? In my case nfs client and server in lxc work just fine, but with autofs hang on system call state(). I use CE7_64 on nodes and inside container with libvirt 1.2.18 May be I must set some of capabilities in <feature> (http://man7.org/linux/man-pages/man7/capabilities.7.html) ? I try only CAP_SYS_ADMIN

On 03/24/2016 05:48 AM, Peter Steele wrote: > On 03/24/2016 02:26 AM, mxs kolo wrote: >> use libvirt 1.3.2, it's more stable and never show negative values >> for memory and swap inside container >> > The latest version available for CentOS/RHEL is version 1.2.17. What > site are you using to get the rpm for version 1.3.2? > > Peter &gt...

On 04/26/2016 10:01 AM, mxs kolo wrote: >> Cool, thanks for the info! Does this still affect libvirt 1.3.2 as well? You >> mentioned elsewhere that you weren't hitting this issue with that version > Sorry, I miss version and another details. > Test make on CentOS Linux release 7.2.1511 (Core) > and li...

On Wed, Dec 05, 2018 at 02:43:45PM +0300, mxs kolo wrote: > Hi all > > After upgrade from Centos 7.5 to Centos 7.6, our test environment > geted new version of libvirt 4.5.0 > In which our old containers have broken config and can't start: > 2018-12-05 10:38:32.634+0000: 18010: debug : > virLXCControllerGetNICIndexe...

https://bugzilla.redhat.com/show_bug.cgi?id=1681180 b.r. Maxim Kozin

On 08/26/2014 03:41 AM, mxs kolo wrote: > Hi all > > Centos 7.0.1406, 3.10.0-123.el7.x86_64 > Configure libvirt-1.2.7 as: > ./configure --prefix=/usr --with-xen=no --with-qemu=no > --with-openvz=no --with-vmware=no --with-esx=no --with-parallels=no > --with-bhyve=no --with-uml=no --with-vbox=no --with-...

On 08/26/2014 05:37 AM, mxs kolo wrote: >> Thanks for the report. That is disabling quite a lot of drivers (what >> is still left, lxc?), so it's a combination that has not gotten a lot of >> testing. I'll definitely look at fixing it before 1.2.8 is released, >> although it may miss release...

> So maybe we have a bug where the build depends on pre-installed files, > rather than building properly from the tarball. Good thing it's easy to > make a virgin VM to test this theory. Like I said, I'll try and > reproduce and fix this, but it may be a couple days. Some news. I get libvirt-1.2.8-rc1.tar.gz and successfully build it on my "problem" node, without

On 16.09.2014 17:40, mxs kolo wrote: > HI all > > Centos 7, 3.10.0-123.6.3.el7.x86_64 > libvirt 1.27, libvirt 1.2.8 builded from source with > ./configure --prefix=/usr > make && make install > LXC with direct network failed to start: > > Sep 16 19:19:38 node01 kernel: device br502 enter...

>> The latest version available for CentOS/RHEL is version 1.2.17. What >> site are you using to get the rpm for version 1.3.2? build from source rpm's > I found a download for this version and tried it out but we ran into a > different set of problems when running our software in containers under > this environment. Unfortunately we're out of time to address these