similar to: DomU stalls, no CPU activity

I started my AD-member server with the DC not being present. Afterwards, I executed the "good practice" sequence from the howtos for testing a installation: "testparm ..." "nmblookup -d ..." "nmblookup -M ..." "nmblookup __SAMBA__ ..." "smbclient -L ..." And some domain tests: "net ads testjoin" "net ads lookup"

I?m receiving the following error(s) messages when trying reloading dovecot (Debian wheezy). doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 73: Unknown setting: socket doveconf: Error: managesieve-login: dump-capability process returned 89 Configuration file /etc/dovecot/dovecot.conf : # If you only want to use dovecot-auth, you can set this to "none".

I have successfully joined a domain with Samba 3.0.30 But after approx. one or two hours, winbind looses connection to the domain controller and users are not allowed to connect shares. After a 'killall winbindd' and restarting of winbind, the users can connect to the shares again. How can I work around this bug? Configuration looks like this: [global] dos charset = ISO-8859-1

Starting with version 3.0.31, it is not possible to access shares on a Windows Server 2000 SP4, even though it is possible to join the domain controlled by that Server. The same configuration worked "fine" (for one hour) with 3.0.30. What has changed? What do I need to configure or compile differently to get back to 3.0.2x behaviour? The commands #> wbinfo -u #> wbinfo -g #>

On Mon, 2014-04-21 at 15:43 +0200, Sjors Gielen wrote: > Package: xen-utils-4.1 > Version: 4.1.4-3+deb7u1 > Severity: important > > When an LVM LV that serves as the root disk for a Xen DomU contains a boot > loader (or possibly other data) in its volume boot record, pygrub fails to boot > it, printing "Error: boot loader didn't return any data" before exiting.

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When an LVM LV that serves as the root disk for a Xen DomU contains a boot loader (or possibly other data) in its volume boot record, pygrub fails to boot it, printing "Error: boot loader didn't return any data" before exiting. I think this is because of the function "is_disk_image" on line 45 of

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important Tags: security patch When you use xl toolstack, you can't reboot domUs. When you switch back to xm toolstack, than reboot works again. I think the problem with the debian packaged version is the same as in this thread: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html I also think it's a security issue,

On 2 July 2013 09:58, Martin Kletzander <mkletzan@redhat.com> wrote: > I'd say this is a problem with sasl, nothing else. "No mechanism found" > may mean that libraries for configured mechanism aren't found or unknown > mechanism is being requested. I doubt that access to those libraries > would be a permisison problem, but you might be missing some >

Package: xcp-xapi Version: 1.3.2-15 Severity: normal I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log [20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1 [20130829T19:29:18.012Z|debug|sriov1|314 UNIX

On 07/02/2013 10:13 AM, Maciej Gałkiewicz wrote: > On 2 July 2013 09:58, Martin Kletzander <mkletzan@redhat.com> wrote: > >> I'd say this is a problem with sasl, nothing else. "No mechanism found" >> may mean that libraries for configured mechanism aren't found or unknown >> mechanism is being requested. I doubt that access to those libraries

Package: libxen-dev Version: 4.1.4-3+deb7u1 Severity: wishlist Dear Maintainer, I want to make some fine monitoring of my xen machines and the xentop utility does not exactly fits my needs I saw in the sources that it uses some kind of library named libxenstat wich seems very acurate. This library is already built to make the xentop utility but the debian package does not makes it available as

Hi I am running following asterisk installed with apt on Debian 7.1. dpkg -l |grep asterisk ii asterisk 1:1.8.13.1~dfsg-3+deb7u1 amd64 Open Source Private Branch Exchange (PBX) ii asterisk-config 1:1.8.13.1~dfsg-3+deb7u1 all Configuration files for Asterisk ii asterisk-core-sounds-en-gsm 1.4.22-1 all asterisk PBX

> Hi > > I am running following asterisk installed with apt on Debian 7.1. > > dpkg -l |grep asterisk > ii asterisk 1:1.8.13.1~dfsg-3+deb7u1 > amd64 Open Source Private Branch Exchange (PBX) > ii asterisk-config 1:1.8.13.1~dfsg-3+deb7u1 > all Configuration files for Asterisk > ii

Hello, Since recently (not sure when), dsync stopped working. dsync -u klink mirror XXXX dsync-local(klink): Error: remote: dsync-server: invalid option -- 'l' dsync-local(klink): Error: remote: doveadm dsync-server [-u <user>|-A] [-S <socket_path>] dsync-local(klink): Error: read() from worker server failed: EOF I did not change anything on my setup but dovecot was

Package: xen-system-amd64 Version: 4.1.4-3+deb7u1 Severity: normal The xen kernel detects 3GB of memory instead of the full 4GB. When using the "normal" kernel 4GB is detected. On boot the 4GB is detected: root at ams-tc1-xen27:~# dmesg |grep Mem [ 0.000000] Memory: 3226132k/4980736k available (3426k kernel code, 788180k absent, 966424k reserved, 3312k data, 576k init) But only

Processing commands for control at bugs.debian.org: > reassign 745419 src:xen 4.1.4-3+deb7u1 Bug #745419 [xen-utils-4.1] xen-utils-4.1: Pygrub fails to boot from LVM LV when something installed in the volume boot record Bug reassigned from package 'xen-utils-4.1' to 'src:xen'. No longer marked as found in versions xen/4.1.4-3+deb7u1. Ignoring request to alter fixed versions of

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

Hello, I have problems running Xen (from Debian 7, i386 userspace) on Asus P3-AE5 system (M2V-TVM board) with Athlon 64 3000+ CPU (AM2, 1.8GHz). In short, Xen is not accessible from amd64 Linux kernels but works fine with 686 kernels. Long version: xen-system-i386 (4.1.4-3+deb7u1) works fine with linux-image-3.2.0-4-686-pae xen-system-amd64 (4.1.4-3+deb7u1) works fine with

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Severity: important Dear Maintainer, Just upgraded a Supermicro server (X9SCM-F motherboard) from Squeeze to Wheezy. And now the IPMI serial console no longer work as it used to. It hangs like this: [...] (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) ENABLING IO-APIC IRQs (XEN) -> Using old ACK method (XEN) Platform timer

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Package: xen-linux-system-amd64 Version: 3.2+46 Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Package: xenwatch Version: 0.5.4-3 Package: xenstore-utils Version: 4.1.4-3+deb7u1 Package: xen-tools Version: 4.3.1-1 I installed Debian 7 (amd64) in a HX5 blade server (IBM Bladecenter H) 32 GB RAM, 2 Intel Xeon SixCore 2.Ghz, Internal