Hello Horacio, thank you for taking the time to file this bug report.
Configurando mysql-server-5.1 (5.1.41-3ubuntu12.10) ...
mysql stop/post-start, (post-start) process 26238
frontend: Fatal IO error 9 (Descriptor de fichero erróneo) on X server :0.0.
dpkg: error al procesar mysql-server-5.1
** Tags added: upstream
** Changed in: apache2 (Ubuntu)
Status: New = Triaged
** Changed in: apache2 (Ubuntu)
Importance: Undecided = Low
** Also affects: apache2 via
http://issues.apache.org/bugzilla/show_bug.cgi?id=43502
Importance: Unknown
Status: Unknown
--
You
Public bug reported:
minicom, while connected to for example /dev/ttyUSB0 - displays
incoming data.
*no* keystrokes are sent out.
When closing minicom - some data is sent (a TX led will flash shortly)
- the same hardware works fine with sercom, cutecom etc - but I miss minicom.
-Reproduced this
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in Ubuntu.
https://bugs.launchpad.net/bugs/938485
Title:
No keystrokes are sent - no outgoing serial
To manage notifications about this bug go to:
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/902339
Title:
samba(7) references missing programs
To manage notifications about this bug go to:
** Also affects: genshi (Ubuntu Precise)
Importance: High
Status: Confirmed
** Changed in: genshi (Ubuntu Precise)
Milestone: None = ubuntu-12.04-beta-1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. There have been many changes in Ubuntu since that time
you reported the bug and your problem may have been fixed with some of
the updates. It would help us a lot if you could test it on a currently
supported Ubuntu
As no-one replied for almost 2 years, I am assuming the problem is gone.
Therefore, I'll close this report.
** Changed in: samba (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. There have been many changes in Ubuntu since that time
you reported the bug and your problem may have been fixed with some of
the updates. It would help us a lot if you could test it on a currently
supported Ubuntu
Fixed in 3.1.19.
** Changed in: squid3 (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/937987
Title:
squid is loosing cache data when
It says fixed but I don't think it's fixed. I'm using Ubuntu 11.10 with
Puppet 2.7.10 and still having this problem.
I also filed Puppet bug #12773: Service Status detection does not always
work properly on Ubuntu in https://projects.puppetlabs.com/issues/12773
See also forum thread: puppet
An easy fix:
In /etc/init.d/amavis:
replace the line
STOP=--stop --quiet --pidfile $PIDFILE --name ${DAEMONNAME}
with
STOP=--stop --quiet --pidfile $PIDFILE
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: keepalived (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
I just hit the same situation. The solution described (with getent -s
compat passwd) wouldn't work there because they actually have passwd:
compat in /etc/nsswitch.conf and a +:: line in /etc/passwd. The
smbpasswd was already 2MiB large as I killed the import process.
Can you please
Re-opening - this bug is still open upstream, and while there have been
changes in this area of the code I'm pretty sure none of them have
affected the rewriting of fields in SWAT.
** Changed in: samba (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because
Public bug reported:
Error updating Squid 3 from 3.0/18 STABLE to any of the newer versions.
Tried 3 updated versions.
All give this error:
Errors were encountered while processing:
squid3
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error
code (1)
*** The
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/938612
Title:
Squid3 3.1.11-1ubuntu0.1 failed to install/upgrade: ErrorMessage:
subprocess installed post-installation script
You have been subscribed to a public bug:
I passed an invalid option to euca-describe-instances and it printed a
stack dump. That seems a bit excessive -- a few lines of exception
handling would improve this experience a lot.
Observe:
$ euca-describe-instances --user admin
Traceback (most
** Project changed: nova = euca2ools (Ubuntu)
** Changed in: euca2ools (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in Ubuntu.
https://bugs.launchpad.net/bugs/938215
Title:
Public bug reported:
This morning I upgraded my Openstack hosts to the latest packaged
version of the nova packages. After the upgrade some of the compute node
machines were rather unresponsive.
After investigation it became apparent that nova-compute was nearly
exhausting the node's memory. I
Public bug reported:
After upgrading the Openstack packages in Precise this morning to the
latest version, I have found that nova-manage doesn't support the
fixed (fixed-ip) catagory.
The traceback:
$ sudo nova-manage fixed list
No handlers could be found for logger nova.virt.libvirt.firewall
Blueprint changed by James Page:
Whiteboard changed:
Status 20122501
Dev packages avaliable for hadoop, hive, pig, hbase and hadoop-zookeeper
in http://launchpad.net/~hadoop-ubuntu/+archive/dev
sudo add-apt-repository ppa:hadoop-ubuntu/dev
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/938752
Title:
Lucid containers don't have sudo set up
To manage notifications about this bug go to:
Public bug reported:
With the latest ubuntu template change, the ubuntu user in the Lucid
containers no longer have sudo access and needs to be manually added.
There's a temporary workaround (from outside your container): chroot
/var/lib/lxc/container/rootfs passwd
ProblemType: Bug
Public bug reported:
After upgrading nova-compute this morning to the latest nova-compute
package in Precise I have noticed a non-fatal traceback in /var/log/nova
/nova-compute.log.
Traceback:
2012-02-22 15:04:28,413 ERROR nova.manager [-] Error during
ComputeManager._sync_power_states: 'dict'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/938765
Title:
Container will no longer start under 12.04
To manage notifications about this bug go to:
Public bug reported:
beuno@beuno-laptop:~/canonical/ubunet/trunk$ sudo lxc-start -n u1-server-lp
lxc-start: failed to create the command service point
lxc-start: failed to add command handler to mainloop
lxc-start: mainloop exited with an error
Debug log: http://paste.ubuntu.com/852806/
An SRU has been uploaded to Ubuntu 11.10 fixing some timing issues at
boot time.
Can you make sure your system is fully up to date including bridge-utils
at version 1.5-2ubuntu1.1?
If the problem still happens after that, the following would probably be useful:
- ls -l /run/network/
- initctl
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: lxc (Ubuntu)
Status: New = Triaged
** Summary changed:
- Container will no longer start under 12.04
+ Lxc-start should warn if a container is already running
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
This bug was fixed in the package lxc - 0.7.5-3ubuntu30
---
lxc (0.7.5-3ubuntu30) precise; urgency=low
[ Serge Hallyn ]
* 0048-warn-if-container-started: If container startup fails because the
container is already running, give an error message to that effect.
(LP:
This bug was fixed in the package lxc - 0.7.5-3ubuntu30
---
lxc (0.7.5-3ubuntu30) precise; urgency=low
[ Serge Hallyn ]
* 0048-warn-if-container-started: If container startup fails because the
container is already running, give an error message to that effect.
(LP:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
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/938699
b1, what version of Ubuntu did you dist-upgrade from? I think this may
be a problem when upgrading from a version where upstart does not
control squid (likely 8.04 (hardy) or 9.10 (karmic)). The packaging
needs to remove these symlinks before installing the new upstart-
compatibility symlink in
Marking as confirmed as I've run into this last week when deploying to
the CI lab. I've only hit it once and was unable to reproduce during
subsequent deployments. nova-compute was exhausting all memory and
eventually being killed off by OOM killer.
** Also affects: nova
Importance:
** Bug watch added: Debian Bug tracker #660903
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660903
** Also affects: munin (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660903
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: mysql-5.1 (Ubuntu Precise)
Milestone: precise-alpha-1 = ubuntu-12.04-beta-1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/880339
Title:
AppArmor profile needs
** Changed in: munin (Ubuntu)
Status: Incomplete = Triaged
** Summary changed:
- snmp__if plugin does not work
+ snmp__if plugin does not work if server only supports 32 bit counters
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: nova (Ubuntu)
Status: New = Confirmed
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in
Thomas, thanks for the update. I'll close the bug then as Fix Released.
** Changed in: apache2 (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Hi rahul. Can you make sure your hostname is resolvable?
try
ping `hostname`
RabbitMQ will refuse to start up if your hostname is not resolvable.
From your error message, it looks like your hostname is 'openstack-Chef-
Server'. Newer versions of rabbitmq handle this a bit more gracefully
btw.
Fix proposed to branch: master
Review: https://review.openstack.org/4404
** Changed in: nova
Status: Confirmed = In Progress
** Changed in: nova
Assignee: (unassigned) = Adam Gandelman (gandelman-a)
--
You received this bug notification because you are a member of Ubuntu
Server
Thomas, thanks for the updates. I think you have a pretty complicated
setup, and we can't necessarily cater to such a setup in the packaging
given the number of options dnsmasq has. There's a path for other users
with a similar setup to yours, and that is --listen-interface.
Closing this as
No response for almost 18 months. Closing as Invalid.
** Changed in: setserial (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to setserial in Ubuntu.
https://bugs.launchpad.net/bugs/46994
Ken, is this still an issue in natty or any later release?
Thanks!
** Changed in: squid3 (Ubuntu)
Assignee: Amos Jeffries (yadi) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
No response on this bug for almost 18 months. Closing as Invalid.
** Changed in: dhcp3 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in Ubuntu.
https://bugs.launchpad.net/bugs/26949
** Also affects: nova
Importance: Undecided
Status: New
--
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/938763
Title:
nova compute manager traceback during _sync_power_states
Hi Andrew, thanks for the report. To be clear, was this an upgrade from
the Oneiric/Diablo to Preicse/Essex, or an upgrade between version of
Essex? Also, is it correct to assume that, at the time of the upgrade,
there were instances running on the compute node? Thanks
--
You received this
Hi Shane, the error is here:
Starting rabbitmq-server: FAILED - check /var/log/rabbitmq/startup_{log, _err}
rabbitmq-server.
invoke-rc.d: initscript rabbitmq-server, action start failed.
dpkg: error processing rabbitmq-server (--configure):
subprocess installed post-installation script returned
As there haven't been any duplicates since February, 2010, 2 years now,
I am closing this as Invalid in postfix. I believe the debconf task is
valid, but low priority.
** Changed in: postfix (Ubuntu)
Status: Incomplete = Invalid
** Changed in: debconf (Ubuntu)
Importance: Undecided =
** Changed in: munin (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/851625
Title:
snmp__if plugin does not work if server only supports 32
I think I traced this down to the usb tablet option in
nova/virt/libvirt/connection.py
--
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/938699
Title:
nova-compute runaway memory
Chuck: nice find. Turning that option off fixes this for me.
--
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/938699
Title:
nova-compute runaway memory allocation
To manage
Verified using test case on oneiric.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/922645
Title:
ubuntu template
** Changed in: nova
Status: New = Confirmed
** Changed in: nova
Importance: Undecided = High
--
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/938699
Title:
nova-compute
This bug was fixed in the package lxc - 0.7.5-0ubuntu8.4
---
lxc (0.7.5-0ubuntu8.4) oneiric-proposed; urgency=low
* 0022-fix-lxc-destroy-bugs.patch:
- don't delete a running container
- handle case where rootfs is not specififed in config (or config is
corrupt or has
Hello Serge, or anyone else affected,
Accepted lxc into oneiric-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
Hello Gary, or anyone else affected,
Accepted lxc into oneiric-proposed. The package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
**
I dist-upgraded from an ubuntu 10.04.2 LTS. But this problem also occurs
with a normal upgrade.
sudo lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.2 LTS
Release:10.04
Codename: lucid
I have a VM-Snapshot of the system before the
Actually, I take that back. I think I got lucky ... it didn't fix the
problem for me. I may not be having the same problem, though.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
** Branch linked: lp:ubuntu/oneiric-proposed/lxc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/927883
Title:
lxc-execute fails due to missing /dev/shm
To manage notifications about
** Branch linked: lp:ubuntu/oneiric-proposed/lxc
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/924337
Title:
lxc on precise is not working with lucid containers (container does
not
This may be fixed by the patch that went in for bug 934575. Can you
give that a try?
--
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/938699
Title:
nova-compute runaway memory
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: nova
Assignee: (unassigned) = Mike Milner (milner)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
This no longer applies since we switched over to nova-rootwrapper.
** Changed in: nova (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Fix proposed to branch: master
Review: https://review.openstack.org/4430
** Changed in: nova
Status: Triaged = In Progress
** Changed in: nova
Assignee: (unassigned) = Chuck Short (zulcss)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
This is fixed in precise.
** Changed in: nova (Ubuntu)
Status: Confirmed = Fix Released
--
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/912701
Title:
Openstack Compute with Xen
Blueprint changed by Clint Byrum:
Whiteboard changed:
Status: cursory review shows all dependencies of glusterfs to be in main
already. Should be a straight forward MIR process.
Work Items:
- MIR glusterfs: TODO
+ MIR glusterfs: POSTPONED
No discussion need, we just need to review
Blueprint changed by Clint Byrum:
Whiteboard changed:
Status: spec needed, place-holder work items added to get a better
handle on the scope of work.
Work Items:
[clint-fewbar] write spec for charm testing facility: DONE
implement specified testing framework: TODO
deploy testing
Blueprint changed by Clint Byrum:
Whiteboard changed:
Work Items:
- [canonical-kernel-team] investigate large xattr support patch from Ted T'so
in ext4: POSTPONE
- [canonical-kernel-team] potentially help push large xattr support to ext4:
POSTPONE
- confer with kernel-team to decide on which
Blueprint changed by Clint Byrum:
Whiteboard changed:
Work Items:
[canonical-kernel-team] investigate large xattr support patch from Ted T'so
in ext4: POSTPONED
[canonical-kernel-team] potentially help push large xattr support to ext4:
POSTPONED
confer with kernel-team to decide on
Blueprint changed by Clint Byrum:
Whiteboard changed:
Status: all txaws patches were accepted upstream and uploaded, so the
universe dependencies have been cut significantly. Zookeeper MIR should
be able to proceed.
Work Items:
MIR txaws: DONE
MIR txzookeeper: DONE
- MIR zookeeper:
** Changed in: bind9 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/930280
Title:
AppArmor profile for named prevents reading of samba4
** Changed in: quota (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to quota in Ubuntu.
https://bugs.launchpad.net/bugs/930551
Title:
System with quota enabled hangs after upgrade to 11.10
To
Marking confirmed based on debian report.
** Bug watch added: Debian Bug tracker #652026
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652026
** Also affects: amavisd-new (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652026
Importance: Unknown
Status: Unknown
*** This bug is a duplicate of bug 913809 ***
https://bugs.launchpad.net/bugs/913809
This looks very similar to http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=526325 .
** Changed in: samba (Ubuntu)
Importance: Undecided = High
** Bug watch added: Debian Bug tracker #526325
Hi,
the terminal log contains:
* Checking quotas... [72G quotacheck: lstat Cannot stat
`//home/carlos/.gvfs': Permission denied
Guess you'd better run fsck first !
exiting...
[66G[ OK ]
* Turning on quotas... [72G quotaon: Cannot find quota file on
** Changed in: euca2ools (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in Ubuntu.
https://bugs.launchpad.net/bugs/933656
Title:
euca-describe-instances --ipv4 does not include
Thanks for reporting this bug. Reproduced in precise.
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
** Changed in: vm-builder (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: keystone (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/930255
Title:
Keystone's precise dbconfig uses incorrect case for
I suspect this is a duplicate of bug 921489.
** Changed in: openldap (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/937613
Title:
** Changed in: squid3 (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/938612
Title:
Squid3 3.1.11-1ubuntu0.1 failed to install/upgrade:
Current git trunk is no problem, libvirt.template.xml in
https://wiki.ubuntu.com/Testing/EnableProposed needs to be fixed. if anyone
has a problem, check below.
[ before ]
!-- The order is significant here. File must be defined first --
serial type=pipe
source
** Changed in: nova (Ubuntu)
Importance: Undecided = Medium
--
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/934118
Title:
Floating ips not available to instances after upgrade
To
I should probably have mentioned, nova checks these roles in a case
sensitive manor.
Using the wrong case means the roles simply will not work..
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
** Changed in: minicom (Ubuntu)
Importance: Undecided = Medium
** Changed in: minicom (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to minicom in Ubuntu.
https://bugs.launchpad.net/bugs/938485
** Changed in: python-novaclient (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-novaclient in Ubuntu.
https://bugs.launchpad.net/bugs/934515
Title:
--meta key=value cannot accept
Thanks for reporting this bug. The upgrade log shows:
==
Erro de Configuração: Esperado um texto, encontrado T_EOL: =
: linha 236, coluna 12 do arquivo /etc/bacula/bacula-
dir.conf
dbname = ; DB Address = ; dbuser = ; dbpassword =
Thanks for taking the time to report this bug.
Looking at precise and lucid versions, it looks like the dovecot-common
ufw rules were shipped by older ufw-common packages, whereas newer
packages ship it in dovecot-core.
** Changed in: dovecot (Ubuntu)
Importance: Undecided = Low
** Changed
sqlalchemy.exc.OperationalError: (OperationalError) table user_roles already
exists u'\nCREATE TABLE user_roles (\n\ttenant_id INTEGER, \n\tuser_id INTEGER,
\n\tid INTEGER NOT NULL, \n\trole_id INTEGER, \n\tPRIMARY KEY (id), \n\tUNIQUE
(user_id, role_id, tenant_id)\n)\n\n' ()
dpkg: error al
Thanks for reporting this bug.
The error message you pointed to:
chown: invalid user: `proxy\r:winbindd_priv\r'
suggests that if you edit /etc/squid3/squid.conf you should find lines
without a trailing newline. Adding newlines should solve this problem.
Could you post your
Thxs for your help; I gave up and reinstalled the server; no more problems;
Thxs again
Carlos
--
Sent from my iOffice
On 2012-02-22, at 5:40 PM, Serge Hallyn 931...@bugs.launchpad.net wrote:
Hi,
the terminal log contains:
* Checking quotas... [72G
Note I can't reproduce this on precise.
Marking priority medium.
** Changed in: euca2ools (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in Ubuntu.
Hi,
I reinstalled the latest build and the rabbitmq error has gone away.
Seems that upgrading from 11.10 on a daily build is not the best thing
to do.
Thanks for your time.
Shane
Sent from my iPad
On 22 Feb 2012, at 19:14, Clint Byrum cl...@fewbar.com wrote:
Hi Shane, the error is here:
** Changed in: nova (Ubuntu)
Importance: Undecided = Medium
--
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/938763
Title:
nova compute manager traceback during _sync_power_states
** Also affects: nova
Importance: Undecided
Status: New
--
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/934118
Title:
Floating ips not available to instances after upgrade
** Changed in: amavisd-new (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to amavisd-new in Ubuntu.
https://bugs.launchpad.net/bugs/930916
Title:
amavis start-stop script fails to stop
Thank you Clint. I actually upgraded by Ubuntu 11.04 to ubuntu11.10 and
now that problem is resolved. But your comment would be a good help for
others if they are also facing the same issue.
Thanks a lot for your kind help.
Regards
Rahul Sharma
--
You received this bug notification because you
1 - 100 of 2817 matches
Mail list logo
