Displaying 20 results from an estimated 300 matches similar to: "Bug#687284: /usr/lib/xcp/bin/xe-reset-networking uses Fedora-specific paths"
2001 Sep 05
2
pam_limits and OpenSSH
Hi,
I have an account server with many users. It uses pam_limits module to
limit memory usage etc. The problem is that sometimes SSH rejects
connection after the password is entered. In syslog it prints something
like "fork: Resource temporary unavailable". After killing some root
processes it works perfectly.
Perhaps the daemon first sets process limits and then switches to
2009 Aug 25
1
Bug#543479: network-bridge doesn't handle secondary address of ${netdev}
Package: xen-utils-common
Version: 3.2.0-2
In network bridge, IP addresses of ${netdev} are correctly transferred
to ${tdev} which later is renamed to ${bridge} (by default = ${netdev}).
But then there is ifup ${bridge} which sets up again the network
configuration for ${bdrige}/${netdev} and aliases (e.g. eth0:1 defined
in /etc/network/interfaces) are loosed.
Regards,
Ognyan Kulev
2002 May 29
0
pam_limits module bug and its effects on pam applications
On 2001-10-26 at 13:35:50 Nicolas Williams <Nicolas.Williams at ubsw.com> wrote:
> On Fri, Oct 26, 2001 at 02:11:13PM +0200, Markus Friedl wrote:
> > On Fri, Oct 26, 2001 at 10:14:21AM +1000, Damien Miller wrote:
> > > On Thu, 25 Oct 2001, Ed Phillips wrote:
> > >
> > > > What is the reasoning behind this? Do we want to see a lastlog entry for
>
2012 Jul 06
1
Bug#680500: xcp-xe: Tab in autocomple of params for 'xe pif-list params=' erase some arguments
Package: xcp-xe
Version: 1.3.2-8
Severity: minor
When autocomplete for bash is activated following misbehavior happens:
xe pif-list params=device,m[Tab]
expected behavior:
autocomplete to xe pif-list params=device,management
actual behavior:
xe pif-list params=management
('device' removed)
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500,
2012 Sep 17
3
Bug#687936: xcp-xe: 'xe console' command undocumented
Package: xcp-xe
Version: 1.3.2-11
Severity: minor
xe did not prove help in autocomplete for xe console command.
Steps to reproduce:
xe console[tab]
Output (help) does not contains xe console command.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)
2013 Mar 05
1
Bug#702340: xe sr-create creates nested PV/VG
Package: xcp-xe
Version: 1.3.2-14
Severity: normal
I created an LV manually and ran the command:
xe sr-create type=ext name-label=myHostSr0 \
device-config:device=/dev/mapper/vg00-sr0
The SR was created, however, I found that it was created as a nested LV,
in other words, it appears xe did something like this:
pvcreate /dev/mapper/vg00-sr0
vgcreate sr_vg
lvcreate sr_vg sr0
2013 Dec 08
1
Bug#731718: after run: xe vm-import filename=... The VM could not be imported
Package: xcp-xe
Version: 1.3.2-15
after run: xe vm-import filename=debserv.ovf
i get messages:
The VM could not be imported.
msg: INTERNAL_ERROR: [ Failure("int_of_string") ]
In /var/log/xcp-xapi.log, i get the lines:
|5239 INET 127.0.0.1:80|VM import R:d700155bd1f0|import] Importing (as new VM)
|5239 INET 127.0.0.1:80|VM import R:d700155bd1f0|import] Reading XML
|5239 INET
2012 Jul 06
1
Bug#680511: xcp-xe: autocomplete for sr-probe type=nfs does not provide hints for device-config
Package: xcp-xe
Version: 1.3.2-8
Severity: minor
XCP 0.5,1.0 and 1.1 provides hints for device-config depends on type field in sr-probe, xcp-xapi (xcp-xe) does not.
Difference:
XCP 1.1 behavior:
xe sr-probe type=nfs device-config:[Tab]
device-config: device-config:serverpath=
device-config:server=
xcp-xe behavior:
xe sr-probe type=nfs device-config:[Tab]
(nothing)
Other arguments
2012 May 29
1
Bug#675052: xcp-xapi: xe vm-memory-target-set does not write target to xenstore
Package: xcp-xapi
Version: 1.3.2-6
Severity: important
Tags: upstream
xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning.
This breaks 'dynamic memory control' feature.
Steps to reproduce:
1) Setup any PV virtual machine with static-memory-min < static-memory-max
2)
2012 May 29
3
Bug#675055: xcp-xapi: xe-edit-bootloader does not compatible with new /dev/sm
Package: xcp-xapi
Version: 1.3.2-6
Severity: normal
Tags: upstream
/usr/lib/xcp/bin/xe-edit-bootloader failing with following message:
/usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138
Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787
Plugging VBD:
Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done
2005 Feb 27
1
Re: smb_proc_readX_data
/* Cc: samba list */
Vincent Marty wrote:
> Hi Ogi !
> Did you find a solution to the problem you described in a post in
> linux.samba in dec 2004 ?
> I get the same messages from Fedora Core 3 when accessing to a iMax
> under Mac Os 10.3.
Hi!
Since I started to use Debian kernel 2.6.10 (in unstable), the problem
disappeared. Fedora Core 3 uses 2.6.10 too so I don't know
2012 Nov 09
1
Bug#692841: xen-api: [INTL:ja] New Japanese translation
Package: xen-api
Version: 1.3.2-12
Severity: wishlist
Tags: patch l10n
Dear xen-api package maintainer,
Here's Japanese po-debconf template translation (ja.po) file that
reviewed by several Japanese Debian developers and users.
Could you apply it, please?
--
victory
http://userscripts.org/scripts/show/102724
-------------- next part --------------
A non-text attachment was
2013 Aug 06
1
Bug#718864: wrong default route
Package: xcp-xapi
Version: 1.3.2-15
Severity: important
New wheezy box
Follow the setup instructions for xcp-xapi, choosing openvswitch networking
Only loopback is defined in /etc/network/interfaces (the way it should
be for XCP)
IP address, router, DNS has been configured statically with
pif-reconfigure-ip
After reboot, the IP address is assigned correctly on the bridge
interface but some
2013 Dec 31
1
Bug#733694: please do not depend on module-init-tools
Package: xcp-networkd
Severity: important
Your package currently depends on the module-init-tools package,
which since March 2012 has become a dummy transitional package.
Please update your package to depend on kmod, because I want to
remove the transitional package.
You only need to replace "module-init-tools" with "kmod" in
debian/control.
--
ciao,
Marco
--------------
2013 Feb 24
1
Bug#701554: xcp-xapi: bashism in /bin/sh script
Package: xcp-xapi
Version: 1.3.2-14
Severity: important
User: debian-release at lists.debian.org
Usertags: goal-dash
Hello maintainer,
While performing an archive wide checkbashisms (from the 'devscripts'
package) check I've found your package containing a /bin/sh script making
use of a bashism.
checkbashisms' output:
>possible bashism in ./usr/lib/xcp/lib/host-restore line
2013 Jul 08
1
Bug#715333: IPv6 security risks with XCP dom0
Package: xcp-xapi
Version: 1.3.2-14
Severity: important
I understand that XCP version 1.3 doesn't support IPv6
This blog talks about enabling it in v1.6:
http://jeffloughridge.wordpress.com/2013/06/16/ipv6-in-xcp-1-6/
However, one observation that I have made is that the dom0 host, in a
default wheezy installation, has kernel IPv6 enabled and appears to have
a link-local address on every
2013 Oct 07
1
Bug#725676: resizing SR fails
Package: xcp-xapi
Version: 1.3.2-14
I've expanded the underlying volume for the SR
xe sr-scan doesn't seem to detect the new space
I've tried various things:
- using pvresize so that LVM detects the bigger partition
pvresize /dev/sda6
and the pvscan command now shows the correct space. running "xe
sr-scan uuid=$UUID" after this failed to detect the space
-
2013 Mar 06
1
Bug#702428: HVM fails to start with VIF / qemu-dm error
Package: xcp-xapi
Version: 1.3.2-14
Severity: important
I imported a HVM from a legacy xm environment.
It is attached to one vif, the xenapi management vif
It fails to start:
# xe vm-start uuid=f2ba4767-7b4f-b416-3da6-3fe059ebfc37
The server failed to handle your request, due to an internal error. The
given message may give details useful for debugging the problem.
message: device model
2012 Jul 06
1
Bug#680499: xcp-xapi: Http_client.Http_request_rejected during upgrade
Package: xcp-xapi
Version: 1.3.2-8
Severity: minor
During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host (upgrade was simulatanious on slave and master):
...
Setting up xcp-xapi (1.3.2-8) ...
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: INTERNAL_ERROR: [
2012 May 23
2
Bug#674137: xcp-xapi: default ports in xapi
Package: xcp-xapi
Severity: normal
Tags: upstream
Are there good reasons why xapi by default prefers to bidn to 80 and
443? This will lead to xapi installation/start failure on every server
machine that might (and will probably) have apache installed.
I know we can remove apache or change its port or change xapi's port
(But I've had a hard time to easily find out where to specify the