I can also confirm this problem. As can I confirm that "/etc/init.d/ssh
restart" is a valid (but time consuming and probably proportional in
time to number of processes) workaround. When I noticed this problem
(after about 15 hours of uptime), there were something in the region of
3000 defunct ssh
Public bug reported:
Binary package hint: nmap
steps to reproduce:
no...@neo:~/tmp/c$cat foo && cat bar
1
2
no...@neo:~/tmp/c$ndiff foo bar
Traceback (most recent call last):
File "/usr/bin/ndiff", line 1036, in
main()
File "/usr/bin/ndiff", line 1024, in main
scan_a.load_from_file(f
** Attachment added: "ndiff.patch"
http://launchpadlibrarian.net/36350506/ndiff.patch
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36350507/Dependencies.txt
--
ndiff crashes when its called with not nmap files
https://bugs.launchpad.net/bugs/491623
You received th
i made a mistake with the file ndiff.patch. its just the diff file.
the path is this attachment now.
** Attachment added: "ndiff.patch"
http://launchpadlibrarian.net/36350932/ndiff.patch
** Attachment removed: "ndiff.patch"
http://launchpadlibrarian.net/36350506/ndiff.patch
--
ndiff crash
I know this is an old bug, but I'm pretty confident now that the problem
isn't in db_pool, just that the increased concurrency exposed bugs in
nova. This was complicated by bugs in SQLAlchemy (since fixed) and in
MySQLdb (which I've opened up a bug report and supplied a patch) that
masked the real
** Summary changed:
- nova-compute stops processing compute.$HOSTNAME occasionally
+ nova-compute stops processing compute.$HOSTNAME occasionally on libvirt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.l
There has not been any fix released in Mantis, so the status in mantis
in incorrect. It should be confirmed.
There is a fix for mantis in the unreleased development branch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubu
Public bug reported:
the useradd command reproducibly fails: Setting up openssh-server
(1:5.8p1-1ubuntu1) ...
useradd: cannot lock /etc/group; try again later.
adduser: `/usr/sbin/useradd -d /var/run/sshd -g nogroup -s /usr/sbin/nologin -u
113 sshd' returned error code 10. Exiting.
dpkg: error p
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
https://bugs.launchpad.net/bugs/725018
Title:
package openssh-server 1:5.8p1-1ubuntu1 failed to install/upgrade:
Unterprozess installiertes post-installation-Skript
*** This bug is a duplicate of bug 514053 ***
https://bugs.launchpad.net/bugs/514053
I found that there was a file /etc/group.lock. After deleting it, it
worked. So this is possibly a bug in adduser.
** This bug has been marked a duplicate of bug 514053
cant add groups using groupadd get
*** This bug is a duplicate of bug 514053 ***
https://bugs.launchpad.net/bugs/514053
The point is that this was repoducible. Somehow the lock file was left
there and would persist through reboots until I manually got rid of it.
--
You received this bug notification because you are a member o
Is the bug that 1.0 doesn't route anywhere or that 1.0 is in the list in
the first place? I can't find any documentation on what a 1.0 API should
be.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad
The reason why I ask is because I don't even see a 1.0 EC2 API doc
anywhere. It's not listed here:
http://aws.amazon.com/archives/Amazon-EC2
and the latest version isn't 1.0. All of the versions fit -mm-dd
format so 1.0 seems like it's a mistake not supposed to be in the list.
I'm not an exp
Ok, I missed that you testes EC2 itself and saw 1.0 on there
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/948595
Title:
Default api-paste.ini does not properly route metadata request
Will Dapper ever have php > 5.1.2 ?
Bug is marked as "Fix released", but I still only see php version 5.1.2.
Please but PHP 5.1.3 or 5.1.4 in backports.
--
Upgrade to PHP 5.1.4 for dapper (security fixes)
https://bugs.launchpad.net/bugs/42562
You received this bug notification because you are a
To bad... I will have to make the upgrade my self then.
Maybe the topic of this bug should be changes to reflect was has been fixed !?
Or status changed to "Wont fix"?
--
Upgrade to PHP 5.1.4 for dapper (security fixes)
https://bugs.launchpad.net/bugs/42562
You received this bug notification bec
** Visibility changed to: Public
--
Security flaw in openSSH prior to 5.2
https://bugs.launchpad.net/bugs/379329
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lis
Annoying bug still present at fresh Hardy-server installation!
Easily fixed by changing ownership of /var/lib/dhcp3 to 'dhcp'.
** Summary changed:
- (Dapper) can't create /var/lib/dhcp3/dhclient.eth0.leases: Permission denied
+ (Dapper, Hardy) can't create /var/lib/dhcp3/dhclient.eth0.leases: Pe
i guess it has something to do with intel cpus - i installed recently a
kvm-vm with windows server 2008 on my "amd athlon 64"-based jaunty
server with no problems at all...
on my notebook, i still got problems booting non-virtio based vms from
harddisk using virt-manager/libvirtd. a linux-vm with
What I found out is: there's no x64 driver for both AC'97 and ES1370 for
Windows. 64bit Chipsets would have no AC'97, so there is only the
Realtek driver which doesn't work well. And ES1370 is a very, very old
audio chip which is probably only supported for legacy reasons but only
in the 32bit vers
20 matches
Mail list logo
