[Bug 1532563] [NEW] package dnsutils 1:9.9.5.dfsg-3ubuntu0.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

2016-01-10 Thread Enrique Ortega Garcia
Public bug reported:

 vghcvgh

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: dnsutils 1:9.9.5.dfsg-3ubuntu0.6
ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
Uname: Linux 3.13.0-71-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
Date: Sat Jan  9 13:25:26 2016
DpkgHistoryLog:
 Start-Date: 2016-01-09  13:24:17
 Commandline: synaptic
 Upgrade: libisc95:i386 (9.9.5.dfsg-3ubuntu0.5, 9.9.5.dfsg-3ubuntu0.6), 
libbind9-90:i386 (9.9.5.dfsg-3ubuntu0.5, 9.9.5.dfsg-3ubuntu0.6), libdns100:i386 
(9.9.5.dfsg-3ubuntu0.5, 9.9.5.dfsg-3ubuntu0.6), liblwres90:i386 
(9.9.5.dfsg-3ubuntu0.5, 9.9.5.dfsg-3ubuntu0.6), libisccfg90:i386 
(9.9.5.dfsg-3ubuntu0.5, 9.9.5.dfsg-3ubuntu0.6)
 Remove: gnome-nettool:i386 (3.8.1-1), ubuntu-standard:i386 (1.325), 
dnsutils:i386 (9.9.5.dfsg-3ubuntu0.5), flashplugin-installer:i386 
(11.2.202.554ubuntu0.14.04.1)
DuplicateSignature: package:dnsutils:1:9.9.5.dfsg-3ubuntu0.6:package is in a 
very bad inconsistent state; you should  reinstall it before attempting a 
removal
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
InstallationDate: Installed on 2012-05-15 (1335 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.10
SourcePackage: bind9
Title: package dnsutils 1:9.9.5.dfsg-3ubuntu0.6 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting a removal
UpgradeStatus: Upgraded to trusty on 2014-10-10 (457 days ago)

** Affects: bind9 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check trusty

-- 
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/1532563

Title:
  package dnsutils 1:9.9.5.dfsg-3ubuntu0.6 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting a removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1532563/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1251654] [NEW] Remove /var/lib/mongodb/mongodb.lock trying to start mongodb service

2013-11-15 Thread Enrique Arizón Benito
Public bug reported:

After non-clean shutdown /var/lib/mongodb/mongodb.lock avoid mongodb to
start properly. Adding next line to /etc/init/mongodb.conf  (anywhere in
the script section before launching the daemon) fixes the problem:

ps -eo %u | grep -q ^mongodb$ || rm -f /var/lib/mongodb/mongod.lock


Explained:
-   ps -ef  %u   - print 
all uid for current processes.
-   grep -q ^mongodb   -  test if the 
mongo service is actually running. mongodb is the same value passed to 
start-stop-daemon  in the --chuid parameter.
-   || rm -f /var/lib/mongodb/mongod.lock   - Unconditionally remove the lock 
file if test failed.


Ex1:

script
  ENABLE_MONGODB=yes
  UID=mongodb # - Reuse value
  if [ -f /etc/default/mongodb ]; then . /etc/default/mongodb; fi
  ps -eo %u | grep -q ^${UID}$  || rm -f /var/lib/mongodb/mongod.lock
  if [ x$ENABLE_MONGODB = xyes ]; then exec start-stop-daemon --start 
--quiet --chuid ${UID} --exec  /usr/bin/mongod -- --config /etc/mongodb.conf; fi
end script

** Affects: mongodb (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1251654

Title:
  Remove /var/lib/mongodb/mongodb.lock trying to start mongodb service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1251654/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1080681] Re: debian guests get different IPv4 at every reboot

2012-11-28 Thread Enrique
I think that I found a workaround that solves part of the problem, editing the 
config file and adding the following line:
lxc.network.hwaddr = aa:aa:aa:aa:aa:aa

 In that way the ipv4 address is kept through reboots. However it is
still not the same one stated under lxc.network.ipv4.

-- 
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/1080681

Title:
  debian guests get different IPv4 at every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1080681/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1080681] [NEW] debian guests get different IPv4 at every reboot

2012-11-19 Thread Enrique
Public bug reported:


 Hi have several Ubuntu and Debian machines running in a host and for all the 
Ubuntu machines the IPv4 address they receive is always the same, and it is 
actually the one stated in the config file under lxc.network.ipv4.
 However, for the Debian machines, although the configuration file specifies a 
given lxc.network.ipv4, they get a different IPv4 address every time they 
reboot, ignoring the lxc.network.ipv4 property.

 To reproduce, just  create a Debian container using lxc-debian template:
 # SUITE=stable lxc-create -t debian -n my_debian

 Then, reboot the container several times, and each of them the IPv4
address will be different. Note that restarting networking in the guest
(/etc/init.d/networking restart) does indeed return the same address.

 I am using  lxc  0.7.5-3ubuntu65  under Ubuntu 12.04 as a host and both
Debian stable and testing guests show the problem.

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1080681

Title:
  debian guests get different IPv4 at every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1080681/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1052972] Re: lxc-debian cannot create a testing release container

2012-11-15 Thread Enrique
I tested the latest package in precise and it works fine. Thank you!
 Enrique

-- 
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/1052972

Title:
  lxc-debian cannot create a testing release container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1052972/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1052972] Re: lxc-debian cannot create a testing release container

2012-10-31 Thread Enrique
I have tested successfully the proposed update. Thank you!

** 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/1052972

Title:
  lxc-debian cannot create a testing release container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1052972/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1052973] [NEW] align lxc-debian and lxc-ubuntu options

2012-09-19 Thread Enrique
Public bug reported:


 It would be desirable to align the options of lxc-debian and lxc-ubuntu 
templates. For instance -r for release and -a for architecture like in 
lxc-ubuntu.

 I am using lxc 0.7.5-3ubuntu62

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1052973

Title:
  align lxc-debian and lxc-ubuntu options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1052973/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1052972] [NEW] lxc-debian cannot create a testing release container

2012-09-19 Thread Enrique
Public bug reported:


 I have tried to create a debian container which uses the testing release with 
the following command:

SUITE=testing lxc-create -t debian -n debian-testing-amd64

 However it fails at some point with this messages:

E: Couldn't find these debs: dhcp3-client
Failed to download the rootfs, aborting.
Failed to download 'debian base'
failed to install debian
failed to execute template 'debian'
aborted


 If I use stable with SUITE=stable then it works fine.

 I am using lxc version 0.7.5-3ubuntu62 in Ubuntu 12.04

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1052972

Title:
  lxc-debian cannot create a testing release container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1052972/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 753605] [NEW] removing mysql with apt doesn't delete user mysql

2011-04-07 Thread Enrique
Public bug reported:

 I installed mysql-5.1 and later on I wanted to remove it. When I purged
it, the mysql user is still in my /etc/passwd. I think that the user has
to be removed, to leave the system in the same status as before.

 It can be reproduced with the following commands:
apt-get install mysql-server
apt-get purge libdbd-mysql-perl libdbi-perl libhtml-template-perl 
libnet-daemon-perl  libplrpc-perl mysql-client-5.1 mysql-server mysql-server-5.1

 After that, the user mysql appears at the end of /etc/passwd, which shouldn't.
 Also, the group mysql should be removed, if contains no other users.
I am using Ubuntu 10.04 TLS

 Regards

** Affects: mysql-5.1 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/753605

Title:
  removing mysql with apt doesn't delete user mysql

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 731324] [NEW] apt-get purge exim4 doesn't delete Debian-exim4 account

2011-03-08 Thread Enrique
Public bug reported:

Binary package hint: exim4


 I was uninstalling the exim4 package using command:
apt-get purge exim4 exim4-base exim4-config exim4-daemon-light

 I expected the Debian-exim account and group to be automatically deleted, but 
it is not the case. Apparently there is no error message.
 I am using Ubuntu 10.04.2 LTS.

** Affects: exim4 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in ubuntu.
https://bugs.launchpad.net/bugs/731324

Title:
  apt-get purge exim4 doesn't delete Debian-exim4 account

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 700812] Re: dpkg-reconfigure slapd doesn't ask for domain or admin pasword

2011-02-19 Thread Enrique
Hi, 
 yes, that help page was helpful to properly setup slapd. I would suggest that 
the server guide and the online community help are kept in sync.
 Thank you!
 Enrique

-- 
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/700812

Title:
  dpkg-reconfigure slapd doesn't ask for domain or admin pasword

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 700812] [NEW] dpkg-reconfigure slapd doesn't ask for domain or admin pasword

2011-01-09 Thread Enrique
Public bug reported:


  I tried to configure a OpenLDAP server using the instructions in 
https://help.ubuntu.com/community/OpenLDAPServer.
 However, it seems that debconf doesn't ask anymore for the domain and admin 
password. These makes it harder to configure properly the server.
 Also, it would be very useful if the wiki page is updated.

 I am using Ubuntu Server 10.04.1.

** Affects: openldap (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/700812

Title:
  dpkg-reconfigure slapd doesn't ask for domain or admin pasword

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 619947] Re: initialization of autofs is erratic (no nis maps available)

2010-08-26 Thread Enrique

 I discovered the reason why nis wasn't starting. I had the name of the server 
instead of the IP address (sorry, I overlooked the instructions about the IP 
address in yp.conf).
 Now ypbind always starts. And autofs seems to read auto.master from the NIS 
server properly. I have rebooted about 10 times and in all of them autofs 
works. So probably the bug can be closed as mistaken.
 Thank you very much for the support and sorry for the mistake.
 Regards,
 Enrique

-- 
initialization of autofs is erratic (no nis maps available)
https://bugs.launchpad.net/bugs/619947
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 510171] Re: connection from windows clients only works using IP, not using hostname

2010-02-19 Thread Enrique Belarte
I have exactly the same problem on 9.10.

-- 
connection from windows clients only works using IP, not using hostname
https://bugs.launchpad.net/bugs/510171
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs