similar to: Bug#591456: Still a Debian bug

Displaying 20 results from an estimated 20000 matches similar to: "Bug#591456: Still a Debian bug"

2010 Aug 03
4
Bug#591456: xen-utils-common: The script hotplugpath.sh is missing in /etc/xen/scripts
Package: xen-utils-common Version: 4.0.0-1 Severity: important When Xen is configured in routed mode, restarting xend fails because the script hotplugpath.sh is missing. Please see below for more information. *** root at eliott:~# /etc/init.d/xend restart Restarting Xen daemons: xend/etc/xen/scripts/network-route: line 20: /etc/xen/scripts/hotplugpath.sh: No such file or directory
2010 Aug 03
0
Bug#591456:
I changed the suggested line in /etc/xen/xend-config.sxp configuration file, but the errors about the file hotplugpath.sh are still present. root at eliott:~# /etc/init.d/xend start Starting Xen daemons: xenstored xenconsoled xend/etc/xen/scripts/network-route: line 20: /etc/xen/scripts/hotplugpath.sh: No such file or directory /etc/xen/scripts/network-route: line 20:
2010 Nov 22
3
Bug#591456: xen-utils-common: The script hotplugpath.sh is missing in /etc/xen/scripts
Is there a fix for this in the works/coming for squeeze or do I have to patch the package myself? If so, how? Thanks, a grateful Debian user that hasn't patched packages yet! Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20101122/8433308c/attachment.htm>
2011 Feb 14
0
Bug#591456: Appologies
Me again I've downloaded the xen source from thexen.org and browsing for hotplugpath.sh give me no result, so I guess is not a Debian bug but rather xen bug.
2011 Mar 07
1
Bug 591456 - script hotplugpath.sh is missing
Hello List, why is the Bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591456 not fixed yet? It was already reported back in 2010 and a patch was already supplied, too. Is this a bigger deal? Thanks, Mario
2011 Feb 10
0
Bug#591456: Further effects of missing hotplugpath.sh [Re: squeeze: xen 4.0.1-2 + drbd8-utils: block-drbd script does no longer work?!]
FYI: This bug also breaks user supplied scripts (/etc/xen/scripts/block-*) that are needed to handle block device mounting other than "phy:" and "file:" disks. See attached email from debian-user mailing list. cheers -henrik -------------- next part -------------- An embedded message was scrubbed... From: Henrik Langos <hlangos-debian at innominate.com> Subject: Re:
2013 Apr 27
1
Bug#706283: xen-utils-common: Broken paths in /etc/xen/scripts/hotplugpath.sh
Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, While updating my xen package today, I was prompted with a config file conflict. --- /etc/xen/scripts/hotplugpath.sh 2013-04-28 01:51:20.899778510 +0800 +++ /etc/xen/scripts/hotplugpath.sh.dpkg-new 2013-04-19 19:39:55.000000000 +0800 @@ -1,12 +1,10 @@ SBINDIR="/usr/sbin" BINDIR="/usr/bin"
2012 Apr 05
0
Bug#588406: fix for missing XEN_SCRIPT_DIR
I had another look at this and found the source of the problem - the reason why XEN_SCRIPT_DIR is not set: The hotplugpath.sh file is missing in the package. In the "rules" file the "install" target includes this line: $(MAKE) -C $(BUILD_DIR)/tools/hotplug/Linux install-udev install-scripts UDEV_RULES_DIR=/lib/udev/rules.d The problem is that make is never run in the
2016 May 24
2
Xen4CentOS 6 64bit - domUs don't shutdown on dom0 after "yum upgrade" to 4.6.1
On Tue, May 24, 2016 at 3:23 PM, George Dunlap <dunlapg at umich.edu> wrote: > > The patches have been backported and are available in 4.6.1-9 from > virt-xen-testing. Please test it and report any problems here. > Thanks for the notice. It doesn't look like the fix went in. See below: # yum repolist | grep xen centos-virt-xen-testing CentOS-6 - xen - testing
2011 Oct 13
0
Re: The script hotplugpath.sh ismissingin/etc/xen/scripts
-----Original message----- From: Paul Muster paul@muster.dyndns.info Date: Thu, 13 Oct 2011 08:29:37 -0500 To: xen-users@lists.xensource.com Subject: Re: [Xen-users] The script hotplugpath.sh ismissing in/etc/xen/scripts > On 13.10.2011 01:52, Barry Kolts wrote: > > > What I did, following the instructions on the last page > > Paul referred to, is add "deb
2012 Apr 05
0
Processed: xen-utils-common unusable with DRBD
Processing commands for control at bugs.debian.org: > severity 588406 important Bug #588406 [xen-utils-common] xen-utils-common: /etc/xen/scripts/block not driving helper scripts; XEN_SCRIPT_DIR not properly set Severity set to 'important' from 'normal' > tags 588406 patch Bug #588406 [xen-utils-common] xen-utils-common: /etc/xen/scripts/block not driving helper scripts;
2016 May 25
0
Xen4CentOS 6 64bit - domUs don't shutdown on dom0 after "yum upgrade" to 4.6.1
On Tue, May 24, 2016 at 10:20 PM, exvito here <ex.vitorino at gmail.com> wrote: > On Tue, May 24, 2016 at 3:23 PM, George Dunlap <dunlapg at umich.edu> wrote: >> >> The patches have been backported and are available in 4.6.1-9 from >> virt-xen-testing. Please test it and report any problems here. >> > > Thanks for the notice. It doesn't look like
2011 Dec 12
0
[PATCH] flask: add tools/flask/utils/flask-label-pci to .hgignore
I have just committed the patch below. Ian. # HG changeset patch # User Ian Jackson <Ian.Jackson@eu.citrix.com> # Date 1323712783 0 # Node ID 7ca56cca09ade16645fb4806be2c5b2b0bc3332b # Parent 7e90178b8bbfd2f78e8f4c6d593a2fb233350f41 flask: add tools/flask/utils/flask-label-pci to .hgignore This was apparently forgotten in 24353:448c48326d6b Signed-off-by: Ian Jackson
2011 Feb 02
1
vif-route does not work
I am using Debian 6.0 "Squeeze", I applied that patch (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591456) to xen-common because of lack of hotplugpath.sh. network-route netdev=eth1 now does work, but vif-route gives me this error: root at xen-dom0:~# xm create /srv/xen/profiles/ca.cfg Using config file "/srv/xen/profiles/ca.cfg". Error: Device 0 (vif) could not be
2011 Feb 02
1
vif-route does not work
I am using Debian 6.0 "Squeeze", I applied that patch (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591456) to xen-common because of lack of hotplugpath.sh. network-route netdev=eth1 now does work, but vif-route gives me this error: root at xen-dom0:~# xm create /srv/xen/profiles/ca.cfg Using config file "/srv/xen/profiles/ca.cfg". Error: Device 0 (vif) could not be
2014 Mar 18
1
A record packet with illegal version was received.
Hello, I'm having a problem with using TLS in samba 4.1.4. When I try to connect to LDAP of samba 4 there is an error in the logs, which is: [2014/03/18 15:34:12.631262, 1] ../source4/lib/tls/tls_tstream.c:1338(tstream_tls_retry_handshake) TLS ../source4/lib/tls/tls_tstream.c:1338 - A record packet with illegal version was received. Here's the php script that tries to connect to
2007 Dec 06
1
smartd.conf get overridden
Yohoo! I have some issues with the smartd in CentOS5/x64 I edited the /etc/smartd.conf for my needs and restarted the smartd with "service smartd restart". But the start script is overriding my file. I checked it and saw the following lines: ---------------/etc/init.d/smartd------------ case "$1" in start | reload | restart) GEN_CONF="*SMARTD*AUTOGENERATED*" [ !
2013 Dec 12
2
Strategies for keeping autogenerated .Rd files out of a Git tree
Hi Quite a few R packages are now available on GitHub long before they appear on CRAN, installation is simple thanks to devtools::install_github(). However, it seems to be common practice to keep the .Rd files (and NAMESPACE and the Collate section in the DESCRIPTION) in the Git tree, and to manually update it, even if they are autogenerated from the R code by roxygen2. This requires extra
2017 Jun 17
2
LDAP ssl issue on port 636
Hello All, We have interesting issue. When application connect to PDC by port 389 (without ssl) everything works fine. When we try to use SSL by port 636 we have issue. ldapsearch -x -D "cn=user,ou=users,dc=dc,dc=local" -p 636 -h PDC -b "DC=dc,DC=local" -w pass output: ldap_result: Can't contact LDAP server (-1) ldapsearch -x -D
2019 Sep 18
2
LDAP bind to AD fails
Am 18.09.19 um 19:16 schrieb Kris Lou via samba: > More than likely, certificate issues. > > If you use the IP in pfsense, then the Samba certificate needs to have the > IP as the CN. So you suggest to contact the dc via hostname ... googled this query command: # openssl s_client -connect adc1:636 tells me ... CONNECTED(00000003) depth=0 O = Samba Administration, OU = Samba -