[Bug 996968] [NEW] Samba needs to be stopped and restarted in order to work
Public bug reported: 1- I setup samba in order to have my server act as Domain Controller (I have NO windows server) 2- after each reboot of my server (Internity), smbd and nmbd are running, but I am unable to connect to it (see first screen capture) 3- stopping and restarting smbd and nmbd fixes this. It seems that on the first start, either smb did not uses the right smb.conf file, or that an early startup of samba make it miss some files or ressources. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: samba 2:3.6.3-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 09:36:18 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: samba UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/996968 Title: Samba needs to be stopped and restarted in order to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+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 996968] Re: Samba needs to be stopped and restarted in order to work
** Attachment added: screen capture 1 https://bugs.launchpad.net/bugs/996968/+attachment/3138058/+files/Capture%20du%202012-05-09%2009%3A33%3A59.png -- 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/996968 Title: Samba needs to be stopped and restarted in order to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+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 996968] Re: Samba needs to be stopped and restarted in order to work
** Attachment added: screen capture 2 https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+attachment/3138061/+files/Capture%20du%202012-05-09%2009%3A35%3A40.png -- 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/996968 Title: Samba needs to be stopped and restarted in order to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+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 996968] Re: Samba needs to be stopped and restarted in order to work
** Attachment added: smb.conf https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+attachment/3138062/+files/smb.conf -- 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/996968 Title: Samba needs to be stopped and restarted in order to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+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 996968] Re: Samba needs to be stopped and restarted in order to work
This behaviour was observed in Ubuntu 11.10 too. -- 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/996968 Title: Samba needs to be stopped and restarted in order to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/996968/+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 995956] Re: cgconfig upstart job should start earlier and mount all available cgroup types by default
I see you. The critical issue is point 1, while point 2 is more a configuration issue. Now after your explanation I agree with your opinion about point 2. A better way is to add mount points (cpuset,blkio) to the default configuration file. What should I do for it then? Well, I'm not against changing the title if it's needed. The main purpose for me is to run daemons with limits. Upstart doesn't handle cgroups and cgroup limits at the moment, so the final optimal way I found is: a) use cgconfig.conf to set limits b) use service.override and cgexec to run daemon in the special cgroup. cups example: exec cgexec -g cpuset:daemon-cups /usr/sbin/cupsd -F cgred could also be used, but if you use lxc on the same machine it affects all lxc container's daemons (cups) too and I don't need such limits. Anyway point 1 of this bug report is needed for this method to work too (cgconfig should start before cups). Could you give me a link about libcgroup+libvirt problems? Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/995956 Title: cgconfig upstart job should start earlier and mount all available cgroup types by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/995956/+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 997029] [NEW] package libkrb5-3 1.9.1+dfsg-1ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-deb --control returned error exit status 2
Public bug reported: during upgrading one of the syste m from 11.10, i encountered this problem ProblemType: Package DistroRelease: Ubuntu 11.10 Package: libkrb5-3 1.9.1+dfsg-1ubuntu2.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Wed May 9 15:21:44 2012 ErrorMessage: ErrorMessage: subprocess dpkg-deb --control returned error exit status 2 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) SourcePackage: krb5 Title: package libkrb5-3 1.9.1+dfsg-1ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-deb --control returned error exit status 2 UpgradeStatus: Upgraded to oneiric on 2012-05-09 (0 days ago) ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 oneiric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/997029 Title: package libkrb5-3 1.9.1+dfsg-1ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-deb --control returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/997029/+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 997029] Re: package libkrb5-3 1.9.1+dfsg-1ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-deb --control returned error exit status 2
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/997029 Title: package libkrb5-3 1.9.1+dfsg-1ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-deb --control returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/997029/+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 878597] Re: rabbitmq-server fails to uninstall
** Changed in: rabbitmq-server (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in Ubuntu. https://bugs.launchpad.net/bugs/878597 Title: rabbitmq-server fails to uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/878597/+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 997029] Re: package libkrb5-3 1.9.1+dfsg-1ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-deb --control returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: not-debian-format ** Changed in: krb5 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/997029 Title: package libkrb5-3 1.9.1+dfsg-1ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess dpkg-deb --control returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/997029/+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 988520] Re: After failed auth, subsequent auths in same context fail
** Changed in: krb5 (Debian) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/988520 Title: After failed auth, subsequent auths in same context fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/988520/+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 995079] Re: Internal server error when accessing nova/instances_and_volumes/ via horizon
Same problem here! I was using the hastexo guide to configure keystone, using a file catalog. So, I was having some problems. I dropped the databases, rebuild all them, including the keystone. Now, I'm using the guide from docs.openstack.org. I followed it step by step, creating the tenant, all services and endpoints. Keystone is running (I can see with netstat). I've tested exporting the OS_ variables and/or SERVICE_ENDPOINT and SERVICE_TOKEN=ADMIN. Not working. When I run $ keystone --token token --endpoint http://10.129.10.44:35357/v2.0 service-list it works. When I try to boot an instance I get: ERROR: Invalid key_name provided. (HTTP 400) I think it is something wrong with keystone! And, the is NO log on keystone.log. When running in debug mode, just that when trying to access via dashboard: /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/webob/dec.py:142: DeprecationWarning: Response.request and Response.environ are deprecated req.response.request = req /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:639: SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen(). Pool.__init__(self, creator, **kw) /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:145: SADeprecationWarning: Pool.add_listener is deprecated. Use event.listen() self.add_listener(l) PS.: keystone produces the same log entries when a cmd call is made. And, finally, apache log just says: [error] No handlers could be found for logger openstack_dashboard Thanks! -- 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/995079 Title: Internal server error when accessing nova/instances_and_volumes/ via horizon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/995079/+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 994781] Re: removing a node when it has failed commissioning is not possible from the UI
** Changed in: maas Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/994781 Title: removing a node when it has failed commissioning is not possible from the UI To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994781/+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 795673] Re: init.d restart operation can fail without proper notice if the memcached process takes a long time ( 1s) to shut down
** Changed in: memcached (Debian) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to memcached in Ubuntu. https://bugs.launchpad.net/bugs/795673 Title: init.d restart operation can fail without proper notice if the memcached process takes a long time ( 1s) to shut down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/795673/+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 551544] Re: puppet in lucid does not support upstart status
Hi, I've the same problem on Lucid Ec2 hosts: ssh service does not restart correctly using hasstatus = true, even expliciting upstart as provider I'm using Puppet version 2.7.14 from skettler's PPA -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/551544 Title: puppet in lucid does not support upstart status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/551544/+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 551544] Re: puppet in lucid does not support upstart status
Hi Lorello, In the puppet source code at github you can see how the status is checked via upstart: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb The is a search for 'start' on the status output. So if ssh is running and status ssh gives the following output 'ssh start/running, process x' then puppet should know the service is running. Also you can check https://projects.puppetlabs.com/issues/12773 since it has some more information on this as well. How exactly can we reproduce your problem? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/551544 Title: puppet in lucid does not support upstart status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/551544/+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 997159] [NEW] package samba 2:3.6.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 12.04 Package: samba 2:3.6.3-2ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu6 AptOrdering: dante-server: Purge samba: Configure Architecture: amd64 Date: Wed May 9 19:09:31 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111011) SourcePackage: samba Title: package samba 2:3.6.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-04-29 (9 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- 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/997159 Title: package samba 2:3.6.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/997159/+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 997159] Re: package samba 2:3.6.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- 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/997159 Title: package samba 2:3.6.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/997159/+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 997159] Re: package samba 2:3.6.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/997159 Title: package samba 2:3.6.3-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/997159/+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 488696] Re: syntax error in nsswitch config near [ syntax error ]
automount[2274]: lookup_init:136: lookup(yp): map auto.master: Local domain name not set type sudo hostname computername to fix. found answer here http://askubuntu.com/questions/40977/setting-up-nfs-client-shows-local-domain-name-not-set-error this just happened to me, scary thing was it was after a power failure (i might have installed some updates, not sure?) and left the computer broken. serious issue. Ubuntu 10.10 with .38 kernel and most updates applied. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/488696 Title: syntax error in nsswitch config near [ syntax error ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/488696/+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 997217] [NEW] salsauthd maxes cpu
Public bug reported:
sasl2-bin version 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu contains a bug
that causes heavy cpu utilization, impacting normal operation of one of
our mail servers following an upgrade to Ubuntu 12.04.
We are running the daemon with the following options:
/usr/sbin/saslauthd -a rimap -O our.imap.server -r -m
/var/spool/postfix/var/run/saslauthd -n 5
We noticed that users were unable to send mail and that the saslauthd processes
were using approximately 100% of each cpu core. An strace of one of the runaway
process showed that it was stuck in the following behaviour:
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, , 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, , 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, , 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, , 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, , 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, , 940)= 0
select(9, [8], NULL, NULL, {0, 0}) = 1 (in [8], left {0, 0})
read(8, , 940)= 0
.
with further inspection showing that the file descriptor in question was a
socket connected to our imap server in CLOSE_WAIT.
Browsing saslauthd/auth_rimap.c in the source package for sasl2-bin, we
came across the following code, repeated in two locations:
while( select (fds, perm, NULL, NULL, timeout ) 0 ) {
if ( FD_ISSET(s, perm) ) {
ret = read(s, rbuf+rc, sizeof(rbuf)-rc);
if ( ret0 ) {
rc = ret;
break;
} else {
rc += ret;
}
}
}
It looks like this loop is expected to run until a read error is encountered or
the timeout of 1 second is reached. There is no test to check that 0 bytes were
read, indicating that the connection was closed by the remote peer. Since
select() will immediately return the size of the set of the partially closed
descriptor (1, which is 0), and calls to read() will always yield 0 bytes,
there's the potential for execution to get stuck in this non blocking loop and
I'm presuming that that's what's happening here.
We've not performed any further analysis to prove that this is really
what's happening but if my intuition is correct then our IMAP server (an
nginx imap proxy) most liklely closes the connection at an unexpected
time under as yet undetermined conditions.
** Affects: cyrus-sasl2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/997217
Title:
salsauthd maxes cpu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/997217/+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 997222] Re: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- 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/997222 Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/997222/+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
[Blueprint servercloud-q-chef] Getting Chef Back Into Ubuntu
Blueprint changed by Clint Byrum: Whiteboard changed: Discussion Topics: What issues lead to the packages being removed from precise? How do we ensure that these don't re-occur to ensure the long term viability of chef as part of Ubuntu? + - Maintaining chef in Debian will help with this. + - Recommending users of Ubuntu and Debian to use the packages (instead of gem installing) will also help. -- Getting Chef Back Into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-chef -- 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 997222] Re: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/997222 Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/997222/+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
Re: [Bug 522509] Re: [FFE] tftpd-hpa doesn't start on boot
Also why does service say it is running when it isn't? Yeah, I saw the same thing. Didn't investigate it enough to make any comments. Anything else I can try to make tftpd-hpa work from boot? Maybe starting tftpd as an up line on the interface definition (/etc/network/interface, man interfaces for more info). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/522509 Title: [FFE] tftpd-hpa doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/522509/+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 994779] Re: changing the IP address of the maas server requires a reinstall
** Changed in: maas (Ubuntu) Assignee: (unassigned) = Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/994779 Title: changing the IP address of the maas server requires a reinstall To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994779/+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 997261] [NEW] package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
Public bug reported: Just for your information. Keep up the good work. /Johan ProblemType: Package DistroRelease: Ubuntu 10.04 Package: slapd 2.4.21-0ubuntu5.7 ProcVersionSignature: Ubuntu 3.0.0-13.22~lucid1-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 Architecture: i386 Date: Wed May 9 20:21:21 2012 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu-Server 10.04.3 LTS Lucid Lynx - Release i386 (20110719.2) SourcePackage: openldap Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- 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/997261 Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/997261/+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 997261] Re: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
-- 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/997261 Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/997261/+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 987963] Re: purging maas\* leaves /var/lib/cobbler and /etc/cobbler populated
** Changed in: maas (Ubuntu) Assignee: (unassigned) = Andres Rodriguez (andreserl) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/987963 Title: purging maas\* leaves /var/lib/cobbler and /etc/cobbler populated To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/987963/+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 997269] [NEW] dovecot imap broken by apparmor policy
Public bug reported: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor=ALLOWED operation=getattr parent=10922 profile=/usr/sbin/dovecot//null-107 //null-10b//null-118 name=/home/foobar/Maildir/.foobar/dovecot.index.log pid=10937 comm=imap requested_mask=r denied_mask=r fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has flags=(complain), but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the usr.lib.dovecot.imap policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in complain mode. What are these //null-NNN/ strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/997269/+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 997269] Re: dovecot imap broken by apparmor policy
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/997269/+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 907197] Re: ip address can't be injected into the instance when using lxc
Unable to reproduce and no response from original reporter - marking 'Invalid' ** Changed in: nova (Ubuntu) Status: Incomplete = Invalid -- 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/907197 Title: ip address can't be injected into the instance when using lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/907197/+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 820696] Re: sheepdog will be stopped but not restarted on transition from runlevel 1 to 2
** Changed in: sheepdog (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to sheepdog in Ubuntu. https://bugs.launchpad.net/bugs/820696 Title: sheepdog will be stopped but not restarted on transition from runlevel 1 to 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sheepdog/+bug/820696/+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 974509] Re: Issues resolving ubuntu archives.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/974509 Title: Issues resolving ubuntu archives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/974509/+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 924002] Re: build system strips binaries, so no debug symbol packages available
this is all good! thanks for the patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/924002 Title: build system strips binaries, so no debug symbol packages available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/924002/+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 997269] Re: dovecot imap broken by apparmor policy
This looks like it could be an apparmor bug instead of dovecot bug, it just happens to manifest itself with dovecot. Adding apparmor in affects. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+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 538470] Re: split sa-compile into a separate package
Hello, this is still a problem in 12.04. I want to avoid having a full compiler package on a mail server. root@root:~# LANG=C apt-get install spamassassin Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: binutils cpp cpp-4.6 gcc gcc-4.6 libc-dev-bin libc6-dev libdigest-hmac-perl libencode-locale-perl liberror-perl libfile-listing-perl libfont-afm-perl libgomp1 libhtml-form-perl libhtml-format-perl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-daemon-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libio-socket-inet6-perl libio-socket-ssl-perl liblwp-mediatypes-perl liblwp-protocol-https-perl libmail-spf-perl libmailtools-perl libmpc2 libmpfr4 libnet-dns-perl libnet-http-perl libnet-ip-perl libnet-ssleay-perl libnetaddr-ip-perl libquadmath0 libsocket6-perl libsys-hostname-long-perl liburi-perl libwww-perl libwww-robotrules-perl linux-libc-dev make manpages manpages-dev re2c spamc Suggested packages: binutils-doc cpp-doc gcc-4.6-locales gcc-multilib autoconf automake1.9 libtool flex bison gdb gcc-doc gcc-4.6-multilib libmudflap0-4.6-dev gcc-4.6-doc libgcc1-dbg libgomp1-dbg libquadmath0-dbg libmudflap0-dbg binutils-gold glibc-doc libdata-dump-perl libcrypt-ssleay-perl libauthen-ntlm-perl make-doc razor libnet-ident-perl pyzor libmail-dkim-perl Any chance this might be fixed in Ubuntu 12.04? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/538470 Title: split sa-compile into a separate package To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/538470/+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 974509] Re: Issues resolving ubuntu archives.
The clear solution here is to use google dns (8.8.8.8) or opendns or some other dns server that does not provide bogus answers for non- existing domains. That said, I think we'll likely be finding a better solution for discovery of a local mirror by an instance. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/974509 Title: Issues resolving ubuntu archives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/974509/+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 538470] Re: split sa-compile into a separate package
As mentioned previously by Scott, this needs to be fixed in debian first. If it gets fixed there soon it can filter into 12.10, but that would be too big a change to SRU to 12.04. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/538470 Title: split sa-compile into a separate package To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/538470/+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 995079] Re: Internal server error when accessing nova/instances_and_volumes/ via horizon
I too had this issue, however it seems to be related to Keystone endpoints. As a test I switched from using the MySQL DB for the endpoints to using the template file. Change /etc/keystone/keystone.conf: [catalog] #driver = keystone.catalog.backends.sql.Catalog driver = keystone.catalog.backends.templated.TemplatedCatalog template_file = /etc/keystone/default_catalog.templates I then restarted keystone and apache2. When I navigated to instances and volumes I was now able to get to the page with no issue. After this I changed back to using MySQL and tried to create an endpoint based off of what I noted in the template file. Restarted services again, but it still failed. It is my guess that I'm not using the correct syntax to create the endpoint or there is something within the URLs being passed that is not working correctly. Any comments from some keystone experts would be welcome at this point. -- 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/995079 Title: Internal server error when accessing nova/instances_and_volumes/ via horizon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/995079/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common
Confirmed removed in Debian upstream - http://packages.debian.org/sid/all/puppet-common/filelist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 997465] [NEW] amavisd-new init script does not work cleanly
Public bug reported: After Installation I get the following output, it seems the restart script does not find the running amavisd process. amavisd-new (1:2.6.5-0ubuntu3) wird eingerichtet ... Creating/updating amavis user account... dpkg: Warnung: Version »configure« hat falsche Syntax: Versionsnummer beginnt nicht mit einer Ziffer Starting amavisd: amavisd-new. amavisd-new-postfix (1:2.6.5-0ubuntu3) wird eingerichtet ... postconf: warning: spf-policyd_time_limit: unknown parameter postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s * Stopping Postfix Mail Transport Agent postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s ...done. * Starting Postfix Mail Transport Agent postfix postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: spf-policyd_time_limit=3600s ...done. Stopping amavisd: (not running). Starting amavisd: The amavisd daemon is already running, PID: [3926] (failed). invoke-rc.d: initscript amavis, action restart failed. dpkg: Fehler beim Bearbeiten von amavisd-new-postfix (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Trigger für libc-bin werden verarbeitet ... ldconfig deferred processing now taking place Fehler traten auf beim Bearbeiten von: amavisd-new-postfix E: Sub-process /usr/bin/dpkg returned an error code (1) This is repeatable by calling ~# /etc/init.d/amavis status * amavisd is running ~# /etc/init.d/amavis stop Stopping amavisd: (not running). ~# /etc/init.d/amavis start Starting amavisd: The amavisd daemon is already running, PID: [4798] (failed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: amavisd-new-postfix 1:2.6.5-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Thu May 10 05:19:35 2012 PackageArchitecture: all ProcEnviron: TERM=xterm-color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: amavisd-new UpgradeStatus: Upgraded to precise on 2012-05-04 (5 days ago) ** Affects: amavisd-new (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/997465 Title: amavisd-new init script does not work cleanly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/997465/+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 997465] Re: amavisd-new init script does not work cleanly
Removing --name ${DAEMONNAME} from the STOP variable in the
initscript fixes this issue, but this is probably not an intended way of
fixing this.
--
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/997465
Title:
amavisd-new init script does not work cleanly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/997465/+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
