similar to: Bug#395305: Unable to shutdown cleanly DomU when named more than 17 characters

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Hi, On system shutdown the 'xendomains' script appears to detect wrong guests: | Stopping libvirt management daemon: libvirtd. | Clearing ebtables rulesets: filter nat broute done. | Shutting down Xen domains: bev-d6x02(save).Error: Domain '1024' does not exist. | !(shut).Error: Domain '1024' does not exist. |

Hi all! I have installed xen on fc6 with kernel 2.6.18-1.2798.fc6xen with rpm package; i have create 3 guest os (fully virtualization) with virt-manager tool, installed on separated partition: 1 fc6 guest, 1 centos 4.4, 1 windows xp pro; all work pretty fine until this point, i have linked the configuration file of the guests machines to /etc/xen/auto for autostart/autostop, but when

Package: xen-utils-common Version: 3.0.3-0-2 Severity: normal Tags: patch When shutting down xen domains with '/etc/init.d/xendomains stop' most of the time not all domains are stopped when the script finishes. As it turns out the xendomains-script queries running domains by executing 'xm list', this command replies its usage info sometimes instead of giving proper output. I

Content-Type: multipart/mixed; boundary="===============0382030028==" MIME-Version: 1.0 From: Albert Dengg <a_d@gmx.at> To: Debian Bug Tracking System <395305@bugs.debian.org> Subject: xen-utils-common: here is a small patch to correctly handle long domU names in parseln Message-ID: <20070317182707.16837.48971.reportbug@audhumbla.dengg.priv.at> X-Mailer: reportbug 3.31

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This tripped me up recently too, but i found i needed a different patch: 0 aesop:~# diff -u /etc/init.d/xendomains{.orig,} - --- /etc/init.d/xendomains.orig 2007-04-18 12:04:04.000000000 -0400 +++ /etc/init.d/xendomains 2007-04-18 13:00:28.000000000 -0400 @@ -128,9 +128,9 @@ parseln() { - - name=`echo "$1" | cut -c0-17` +

Processing commands for control at bugs.debian.org: > merge 414294 395305 Bug#395305: Unable to shutdown cleanly DomU when named more than 17 characters Bug#414294: xen-utils-common: /etc/init.d/xendomains fail to save domains with "long" names Merged 395305 414294. > merge 413181 404533 Bug#404533: missing build deps on e2fslibs-dev and libreiserfs0.3-dev Bug#413181: xen-3.0:

Hi, I have a two instance mongrel cluster, running behind apache mod_proxy_balancer on a linux VPS. Mongrel_cluster is 1.01, mongrel is v1.02, rails 1.2.3, ruby 1.8.6. I seem to have enough memory. About 2 minutes after I start the cluster, one of my instances dies - it could be either one. The log file indicates that it received a TERM signal. The instance does die cleanly, removing its pid

> You''re running on a shared server and when you startup the second > mongrel more than likely the VPS system is sending the second Mongrel > a kill signal because you''ve gone over your resource allocation. > > ~Wayne Thanks - are there other resources that would be contentious other than memory? I believe I had about 60Meg still available (even w/ 2 mongrels

I installed Tomb Raider II under wine under linux; Since there have been some problems i need to uninstall it. But i'm unable to do that with the wine uninstaller. when i try to uninstall it through wine uninstaller i get the following error message: "the file c:\Program Files\Core Design\Uninst.isu is corrupted: fail to uninstall" so I have to do that manually; removing the

Should I be seeing messages like: Dec 14 12:06:59 nyx170 kernel: Lustre: MGS: haven''t heard from client dadccfac-8610-06e7-9c02-90e552694947 (at 141.212.30.185 at tcp) in 234 seconds. I think it''s dead, and I am evicting it. when the client was shut down cleanly? and the lustre file system is mounted via /etc/fstab ? The file system (i would hope) would be unmounted

Hi, the attached patch is relative to the current CVS content. It's needed to build and compile cleanly under Cygwin. The problem are the functions setrlimit/getrlimit. I have added checks for getrlimit, sysconf and setdtablesize to configure.in and appropriate checks in the source code. Corinna -- Corinna Vinschen Cygwin Developer Red Hat, Inc. mailto:vinschen at redhat.com

This refines the previous commit by shutting down the daemon cleanly at the end of the test (assuming the test was successful). It repurposes the 'internal_exit' API for this, which was previously used by the now defunct --enable-valgrind-daemon functionality. --- daemon/internal.c | 7 +------ generator/actions.ml | 3 ++- tests/daemon/captive-daemon.pm.in

Hi, I asked the question on stackexchange (http://unix.stackexchange.com/questions/264931/centos-7-unable-to-cleanly-umount-a-bind-mount-using-rbind-and-rslave) and CentOS 7 bug report (https://bugs.centos.org/view.php?id=10414) but didn't get any useful response, so I am thinking if I can get some help here. The problem arose when I tried to rbind mount /dev and /proc to a chroot sandbox

When decoding a FLAC file with bits per sample that is not a multiple of 8 and outputting in raw format, the decoder gets as far as the write callback before realising that it doesn't know how to write the data. It then fails with an unhelpful message (or trips an assert() in debug mode). The attached patch performs the check earlier, and gives a more helpful error message. Kind

From: Mukesh Rathor <mukesh.rathor@oracle.com> Use .ascii and .asciz to define xen feature string. Note, the PVH string must be in a single line (not multiple lines with \) to keep the assembler from putting null char after each string before \. Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> ---

Hello, I have a domain with three controllers (DC1/DC2/DC3). One is completely non-existent and offline (DC3). I am trying to remove the online controller completely from the domain. The Samba wiki is currently offline, but from recollection I did the following to remove DC2: - transferred all FSMO to DC1 - demoted DC2 The demotion part seems to have succeeded: --- root at dc2 ~# samba-tool

I connected to LDAP via Apache Directory Studio and it seems that the child node under the computer account is an RID set: ????????CN=RID Set,CN=DC2,CN=Computers,DC=ad,DC=home,DC=lan Is this an omission of the demotion process? Should this havfe been removed? Is it safe for me to delete this and try the "sambal-tool computer delete DC2" again?

On 29/05/2023 11:12, Alexandros Karypidis via samba wrote: > I connected to LDAP via Apache Directory Studio and it seems that the child node under the computer account is an RID set: > > ????????CN=RID Set,CN=DC2,CN=Computers,DC=ad,DC=home,DC=lan > > Is this an omission of the demotion process? Should this havfe been removed? Is it safe for me to delete this and try the

I used Apache Directory Studio to remove the "RID Set" node and after that a simple "samba-tool computer delete DC2" worked just fine. Perhaps the version of Samba in TurnKey Linux V16.1 has a bug (4.9.5-Debian)? Likely demotion should remove leaf nodes from domain controllers as part of the process. I have now recreated DC2 using TurnKey Linux V17.1 (4.17.6-Debian) and so

Hi Everyone! Just to let you know, I am very happy ext3 made it thorugh to linux kernel 2.4.15 We have installed ext3 on several machines here at jtrix.org (including two laptops) and everything seems to be working fine. Our only concern is for our two public servers. They run linux 2.2.19 for stability reasons. On one of the laptops (dual booting 2.2.19 and 2.4.14) kernel 2.2.19 failed to