[Bug 1518522] [NEW] package dovecot-core 1:2.2.18-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: window freeze when "open shell ... to consider ..." option was selected, with "next" ProblemType: Package DistroRelease: Ubuntu 15.10 Package: dovecot-core 1:2.2.18-2ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-33.38-lowlatency 3.19.8-ckt7 Uname: Linux 3.19.0-33-lowlatency x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Nov 20 23:15:04 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-06 (199 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: dovecot Title: package dovecot-core 1:2.2.18-2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- 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/1518522 Title: package dovecot-core 1:2.2.18-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/dovecot/+bug/1518522/+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 1316293] Re: unable to start
Similar Problem with BackupPC un Ubuntu 14.04: http://sourceforge.net/p/backuppc/mailman/backuppc- users/thread/alpine.DEB.2.10.1505121831320.27187%40diaspar.physics.unc.edu/#msg34107271 Removing ssl start_tls from /etc/ldap.conf allows BackupPC to start. Both applicaions using perl: perl 5, version 18, subversion 2 (v5.18.2) built for x86_64-linux-gnu- thread-multi -- 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/1316293 Title: unable to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1316293/+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 1488567] [NEW] Samba 4.1.6 Panic with Trusty 14.04.3 LTS
Public bug reported: Description:Ubuntu 14.04.3 LTS Release:14.04 The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 26738 (/usr/sbin/smbd). This means there was a problem with the program, such as a segfault. Below is a backtrace for this process generated with gdb, which shows the state of the program at the time the error occurred. The Samba log files may contain additional information about the problem. If the problem persists, you are encouraged to first install the samba-dbg package, which contains the debugging symbols for the Samba binaries. Then submit the provided information as a bug report to Ubuntu by visiting this link: https://launchpad.net/ubuntu/+source/samba/+filebug [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. 0x7f9955f6eb4c in __libc_waitpid (pid=28019, stat_loc=stat_loc@entry=0x7ffe73814640, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31 #0 0x7f9955f6eb4c in __libc_waitpid (pid=28019, stat_loc=stat_loc@entry=0x7ffe73814640, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:31 #1 0x7f9955ef42e2 in do_system (line=line@entry=0x7f9959aa0f20 /usr/share/samba/panic-action 26738) at ../sysdeps/posix/system.c:148 #2 0x7f9955ef464a in __libc_system (line=line@entry=0x7f9959aa0f20 /usr/share/samba/panic-action 26738) at ../sysdeps/posix/system.c:184 #3 0x7f9958fd8235 in system (line=line@entry=0x7f9959aa0f20 /usr/share/samba/panic-action 26738) at pt-system.c:28 #4 0x7f9957888061 in smb_panic_s3 (why=optimized out) at ../source3/lib/util.c:798 #5 0x7f9958db0c6f in smb_panic (why=why@entry=0x7f9958ab9f00 assert failed: conn-force_group_gid != (gid_t)-1) at ../lib/util/fault.c:159 #6 0x7f9958979116 in change_to_user_internal (conn=conn@entry=0x7f9959aa19c0, session_info=optimized out, vuid=831126676) at ../source3/smbd/uid.c:317 #7 0x7f9958979203 in change_to_user (conn=conn@entry=0x7f9959aa19c0, vuid=optimized out) at ../source3/smbd/uid.c:396 #8 0x7f99589a1cef in make_connection_snum (sconn=sconn@entry=0x7f9959a47370, conn=conn@entry=0x7f9959aa19c0, snum=snum@entry=5, pdev=pdev@entry=0x7f9958aabb2f ???, vuser=0x7f9959a6edb0, vuser=0x7f9959a6edb0) at ../source3/smbd/service.c:730 #9 0x7f99589a289c in make_connection_smb2 (sconn=0x7f9959a47370, tcon=0x7f9959a610c0, snum=snum@entry=5, vuser=0x7f9959a6edb0, pdev=pdev@entry=0x7f9958aabb2f ???, pstatus=pstatus@entry=0x7ffe73814b50) at ../source3/smbd/service.c:974 #10 0x7f99589b9214 in smbd_smb2_tree_connect (out_tree_id=0x7f9959acece8, out_maximal_access=0x7f9959acece4, out_capabilities=0x7f9959acece0, out_share_flags=0x7f9959acecdc, out_share_type=0x7f9959acecd8 , in_path=optimized out, req=0x7f9959ace650) at ../source3/smbd/smb2_tcon.c:269 #11 smbd_smb2_tree_connect_send (in_path=optimized out, smb2req=0x7f9959ace650, ev=0x7f9959a14030, mem_ctx=0x7f9959ace650) at ../source3/smbd/smb2_tcon.c:372 #12 smbd_smb2_request_process_tcon (req=req@entry=0x7f9959ace650) at ../source3/smbd/smb2_tcon.c:92 #13 0x7f99589b2f8d in smbd_smb2_request_dispatch (req=req@entry=0x7f9959ace650) at ../source3/smbd/smb2_server.c:2130 #14 0x7f99589b3c3b in smbd_smb2_io_handler (sconn=0x7f9959a47370, fde_flags=optimized out) at ../source3/smbd/smb2_server.c:3253 #15 0x7f99589b48bc in smbd_smb2_connection_handler (ev=0x6d73, fde=0x7ffe73814640, flags=0, private_data=0x) at ../source3/smbd/smb2_server.c:3291 #16 0x7f995789e09c in run_events_poll (ev=0x7f9959a14030, pollrtn=optimized out, pfds=0x7f9959a57020, num_pfds=4) at ../source3/lib/events.c:257 #17 0x7f995789e2f0 in s3_event_loop_once (ev=0x7f9959a14030, location=optimized out) at ../source3/lib/events.c:326 #18 0x7f99562765ed in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 #19 0x7f99589a055a in smbd_process (ev_ctx=0x7f9959a14030, msg_ctx=optimized out, sock_fd=optimized out, interactive=optimized out) at ../source3/smbd/process.c:3626 #20 0x7f9959414fa4 in smbd_accept_connection (ev=0x7f9959a14030, fde=optimized out, flags=optimized out, private_data=optimized out) at ../source3/smbd/server.c:621 #21 0x7f995789e09c in run_events_poll (ev=0x7f9959a14030, pollrtn=optimized out, pfds=0x7f9959a57020, num_pfds=5) at ../source3/lib/events.c:257 #22 0x7f995789e2f0 in s3_event_loop_once (ev=0x7f9959a14030, location=optimized out) at ../source3/lib/events.c:326 #23 0x7f99562765ed in _tevent_loop_once () from /usr/lib/x86_64-linux-gnu/libtevent.so.0 #24 0x7f9959411b8b in smbd_parent_loop (parent=optimized out, ev_ctx=0x7f9959a14030) at ../source3/smbd/server.c:943 #25 main (argc=optimized out, argv=optimized out) at ../source3/smbd/server.c:1577 A debugging session is active. Inferior 1 [process 26738] will be detached. testparm: Load smb config files from
Aw: [Bug 1482640] Re: package sa-compile 3.4.0-3ubuntu2.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 28 zurück
Pardon what? 15.04 is in a pree release Stat! or what you call it. There is a strict ahm announcement Beta. so how can this bee? anyway is my configuration working with 15.04? and by the way there was no strict announcement to change 14.04 LTS to 15.04 regards Andreas - Original Nachricht Von: Seth Arnold 1482...@bugs.launchpad.net An: a_schnei...@arcor.de Datum: 07.08.2015 23:08 Betreff: [Bug 1482640] Re: package sa-compile 3.4.0-3ubuntu2.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 28 zurück Thank you for taking the time to report this bug and helping to make Ubuntu better. You appear to be running a release of Ubuntu that is no longer supported. Please see https://wiki.ubuntu.com/Releases for information on our currently supported releases; consider using one of the LTS releases, as they will be supported for the longest amount of time. Some additional information on upgrading can be found in our community wiki, https://help.ubuntu.com/community/UpgradeNotes Thanks ** Information type changed from Private Security to Public ** Changed in: spamassassin (Ubuntu) Status: New = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1482640 Title: package sa-compile 3.4.0-3ubuntu2.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 28 zurück Status in spamassassin package in Ubuntu: Invalid Bug description: just ente yes at automaticly update and then the trubbel startet after 20 h and a diupdate I can run ubuntu metacity. HW: Nvidia Grafik card 9 sires del xps M1730 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: sa-compile 3.4.0-3ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: amd64 Date: Fri Aug 7 13:56:17 2015 DuplicateSignature: package:sa-compile:3.4.0-3ubuntu2.1:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 28 zurück ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 28 zurück InstallationDate: Installed on 2014-06-11 (421 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: spamassassin Title: package sa-compile 3.4.0-3ubuntu2.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 28 zurück UpgradeStatus: Upgraded to utopic on 2015-08-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1482640/+subscri ptions -- 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/1482640 Title: package sa-compile 3.4.0-3ubuntu2.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 28 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1482640/+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 1357424] Re: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)
Debian 8.0 is now released with amavisd-new 2.10.1 Ubuntu 15.04 still ships 2.7.1, same as debian oldstable What is happening. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1357424 Title: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1357424/+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 1432589] [NEW] package libnuma1:amd64 2.0.9~rc5-1ubuntu3 failed to install/upgrade: package libnuma1:amd64 is already installed and configured
Public bug reported: After try to install gnome-shell ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libnuma1:amd64 2.0.9~rc5-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Fri Mar 13 17:33:40 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libnuma1:amd64:2.0.9~rc5-1ubuntu3:package libnuma1:amd64 is already installed and configured ErrorMessage: package libnuma1:amd64 is already installed and configured InstallationDate: Installed on 2014-11-24 (111 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: numactl Title: package libnuma1:amd64 2.0.9~rc5-1ubuntu3 failed to install/upgrade: package libnuma1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: numactl (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to numactl in Ubuntu. https://bugs.launchpad.net/bugs/1432589 Title: package libnuma1:amd64 2.0.9~rc5-1ubuntu3 failed to install/upgrade: package libnuma1:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numactl/+bug/1432589/+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 1387459] Re: autofs stops working after upgrade to 14.10
YEAH !!! Setting the workaround suggested I could get my network drives back. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1387459 Title: autofs stops working after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1387459/+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 1387459] [NEW] autofs stops working after upgrade to 14.10
Public bug reported: I use the autofs to mount my home storage into the /net directory. It was working normally until I upgrade to the 14.10 with the following error at terminal: andre@X61s:~$ cd /net andre@X61s:/net$ cd stg1 bash: cd: stg1: No such file or directory andre@X61s:/net$ and in the syslog I got this: Oct 29 23:22:58 X61s automount[6818]: key stg1 not found in map source(s). My /etc/hosts have this content: andre@X61s:/net$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 X61s # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters 192.168.25.101 stg1 192.168.25.111 stg2 And the output of showmount executed at terminal is: andre@X61s:/net$ showmount -e stg1 Export list for stg1: /mnt/pools/A/A0/Shows * /mnt/pools/A/A0/Books * /mnt/pools/A/A0/Music * /mnt/pools/A/A0/Series * /mnt/pools/A/A0/Movies * /mnt/pools/A/A0/Backups * /mnt/pools/A/A0/Pictures* /mnt/pools/A/A0/Downloads * /mnt/pools/A/A0/Documents * /mnt/pools/A/A0/TimeMachine * Thanks in advance Andre Luis PS: my actual version is: andre@X61s:/net$ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: autofs 5.0.8-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 29 23:18:07 2014 InstallationDate: Installed on 2012-12-11 (687 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: autofs UpgradeStatus: Upgraded to utopic on 2014-10-27 (2 days ago) ** Affects: autofs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs in Ubuntu. https://bugs.launchpad.net/bugs/1387459 Title: autofs stops working after upgrade to 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1387459/+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 1318803] Re: FreeBSD 9.2-RELEASE installer does not boot (kernel trap 12 with interrupts disabled)
This has been resolved with an upgrade to seabios 1.7.5-1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to seabios in Ubuntu. https://bugs.launchpad.net/bugs/1318803 Title: FreeBSD 9.2-RELEASE installer does not boot (kernel trap 12 with interrupts disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1318803/+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 1318803] Re: FreeBSD 9.2-RELEASE installer does not boot (kernel trap 12 with interrupts disabled)
This has been resolved with an upgrade to seabios 1.7.5-1 ** Changed in: seabios (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to seabios in Ubuntu. https://bugs.launchpad.net/bugs/1318803 Title: FreeBSD 9.2-RELEASE installer does not boot (kernel trap 12 with interrupts disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1318803/+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 1318803] [NEW] FreeBSD 9.2-RELEASE installer does not boot (kernel trap 12 with interrupts disabled)
Public bug reported: This is similar (or perhaps the exact same bug that was thought to be fixed) to this[1] issue on Debian. Essentially, I cannot boot either FreeBSD 10.0-RELEASE nor Freebsd 9.2-RELEASE on KVM/QEMU guests, as they fail with a kernel panic with the following error message: Fatal trap 12: page fault while in kernel mode You can see the full messages (both with acpi and with it disabled) here[2], though I don't imagine they'll be of much importance. This seems to have to do with 'atkbd' on FreeBSD having some sort of issue with seabios -- specifically version 1.7.4-x. Just as in the aforementioned bug, if I downgrade to seabios version 1.7.3, everything works fine. Is this something I should take up with the Debian devs? 1) The release of Ubuntu you are using: Description:Ubuntu 12.04.4 LTS Release:12.04 2) The version of the package you are using: seabios: Installed: 1.7.4-4~cloud0 Candidate: 1.7.4-4~cloud0 Version table: *** 1.7.4-4~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ precise-updates/icehouse/main amd64 Packages 100 /var/lib/dpkg/status 1.7.3-1ubuntu0.1~cloud0 0 500 http://ubuntu-cloud.archive.canonical.com/ubuntu/ precise-updates/havana/main amd64 Packages 0.6.2-0ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 0.6.2-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages ~# virsh version Compiled against library: libvirt 1.2.2 Using library: libvirt 1.2.2 Using API: QEMU 1.2.2 Running hypervisor: QEMU 1.7.91 3) What you expected to happen: I expect 'virsh start $freebsd_image' to start the image without incident. 4)What happened instead: The image indeed starts, however during boot, it runs into a kernel panic. [1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737142 [2]http://www.drenet.net/images/panic1.png http://www.drenet.net/images/panic2.png http://www.drenet.net/images/panic_noacpi1.png http://www.drenet.net/images/panic_noacpi2.png ** Affects: seabios (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to seabios in Ubuntu. https://bugs.launchpad.net/bugs/1318803 Title: FreeBSD 9.2-RELEASE installer does not boot (kernel trap 12 with interrupts disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1318803/+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 1242376] Re: reload php5-fpm crashes
Note that the move to upstart for php5-fpm happened with Ubuntu 13.10 Its not relevant for older releases. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1242376 Title: reload php5-fpm crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+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 1242376] [NEW] reload php5-fpm crashes
Public bug reported: reload php5-fpm with upstart does not work. php5-fpm will crash and leave non-working child processes hanging around that will block any recovery until they are killed off manually. This is because php5-fpm does not handle SIGHUP. It results in an uncontrolled exit. After telling upstart to instead use SIGUSR2 on reload*, things work as expected. * reload signal SIGUSR2 in upstart php5-fpm.conf Signals handled by php5-fpm seems to be: * SIGINT, SIGTERM: immediate termination * SIGQUIT: graceful stop * SIGUSR1: re-open log file * SIGUSR2: graceful reload of all workers + reload of fpm conf/binary Ubuntu 13.10, amd64 ii php5-fpm 5.5.3+dfsg-1ubuntu2 amd64 server-side, HTML-embedded scripting language (FPM-CGI binary) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1242376 Title: reload php5-fpm crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+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 1227313] Re: Error parsing lxc-start apparmor profile
This package (0.9.0-0ubuntu3.6) fixes the bug for me. ** 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/1227313 Title: Error parsing lxc-start apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1227313/+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 1227313] Re: Error parsing lxc-start apparmor profile
1215391 is fixed now. This can now be pushed to raring-proposed, right? -- 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/1227313 Title: Error parsing lxc-start apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1227313/+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 1215391] Re: lxc-start can't parse IPv6 addresses
This package (0.9.0-0ubuntu3.5) fxies the bug for me. ** 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/1215391 Title: lxc-start can't parse IPv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1215391/+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 1230917] [NEW] php5-fpm logrotate errors after package switched to upstart
Public bug reported:
Getting weekly cron warning emails during logrotation after php5-fpm
package switched to upstart in Saucy.
root@ops:~# lsb_release -rd
Description:Ubuntu Saucy Salamander (development branch)
Release:13.10
root@ops:~# apt-cache policy php5-fpm
php5-fpm:
Installed: 5.5.3+dfsg-1ubuntu1
Candidate: 5.5.3+dfsg-1ubuntu1
Version table:
*** 5.5.3+dfsg-1ubuntu1 0
500 http://uk.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
100 /var/lib/dpkg/status
root@ops:~# cat /etc/logrotate.d/php5-fpm
/var/log/php5-fpm.log {
rotate 12
weekly
missingok
notifempty
compress
delaycompress
postrotate
invoke-rc.d php5-fpm reopen-logs /dev/null
endscript
}
root@ops:~# dpkg -S /etc/logrotate.d/php5-fpm
php5-fpm: /etc/logrotate.d/php5-fpm
root@ops:~# invoke-rc.d php5-fpm reopen-logs
initctl: invalid command: reopen-logs
Try `initctl --help' for more information.
invoke-rc.d: initscript php5-fpm, action reopen-logs failed.
** Affects: php5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1230917
Title:
php5-fpm logrotate errors after package switched to upstart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/+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 1227313] [NEW] Error parsing lxc-start apparmor profile
Public bug reported: The lxc-start package reads its apparmor profile from /proc/$PID/attr/current but does not remove the trailing newline character. When trying to run an unconfined container, this causes comparisons with the unconfined string in the source code to fail, and the apparmor profile is set, even when there's no need to do so. This, in turn, makes it impossible to run containers with a read-only /proc filesystem. Ubuntu release: Description:Ubuntu 13.04 Release:13.04 Package being used: lxc: Installed: 0.9.0-0ubuntu3.5 Candidate: 0.9.0-0ubuntu3.5 Version table: *** 0.9.0-0ubuntu3.5 0 500 http://archive.ubuntu.com/ubuntu/ raring-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.9.0-0ubuntu3.4 0 500 ftp://repos.mz.digirati.com.br/ubuntu/ raring-updates/universe amd64 Packages 0.9.0-0ubuntu3 0 500 ftp://repos.mz.digirati.com.br/ubuntu/ raring/universe amd64 Packages What is expected to happen: A container with a read-only /proc filesystem should start successfully. What happened instead: lxc-start fails with Read-only file system - failed to change apparmor profile to unconfined ** 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/1227313 Title: Error parsing lxc-start apparmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1227313/+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 1215386] Re: lxc-start tries to change apparmor profile to unconfined
Just to confirm, the bug wrt the apparmor profile is indeed fixed. -- 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/1215386 Title: lxc-start tries to change apparmor profile to unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1215386/+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 1215386] Re: lxc-start tries to change apparmor profile to unconfined
You are correct, the error I'm seeing comes from the fact that I have this line on the container's fstab: proc /var/lib/lxc/test/rootfs/proc proc ro,nodev,noexec,nosuid 0 0 That is, I was trying to mount /proc as read-only in the container. This works for me in 12.04 but not in 13.04. -- 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/1215386 Title: lxc-start tries to change apparmor profile to unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1215386/+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 1215386] Re: lxc-start tries to change apparmor profile to unconfined
I tried it with /etc/apparmor.d/usr.bin.lxc-start both enabled and disabled, and also with and without lxc.aa_profile = unconfined in the configuration file and all tests worked fine in the four possible combinations of those settings. -- 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/1215386 Title: lxc-start tries to change apparmor profile to unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1215386/+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 1215386] Re: lxc-start tries to change apparmor profile to unconfined
Hi The issue is still not fixed with the patch. While there's no more garbage in the buffer that stores the apparmor profile read from /proc, that data is still terminated by a \n, (ie., the profile is returned as, eg. unconfined\n instead of unconfined). This causes comparisons with the unconfined string further in the code to fail. -- 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/1215386 Title: lxc-start tries to change apparmor profile to unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1215386/+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 1215386] [NEW] lxc-start tries to change apparmor profile to unconfined
Public bug reported: When starting a container that has 'lxc.aa_profile = unconfined' on its configuration file, lxc-start fails with lxc-start: Read-only file system - failed to change apparmor profile to unconfined This happens because the buffer used by lxc-start to read the process' apparmor profile from /proc/PID/attr/current is not properly NULL- terminated. A patch for this has been applied upstream and is available at https://github.com/lxc/lxc/commit/626ad11bfee3e12e675f51e92920030a6f383b19 Ubuntu Release: Ubuntu 13.04 lxc package version: 0.9.0-0ubuntu3.4 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: lxc ** Tags added: 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/1215386 Title: lxc-start tries to change apparmor profile to unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1215386/+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 1215391] [NEW] lxc-start can't parse IPv6 addresses
Public bug reported: A container with an IPv6 address in its configuration (for example, 'lxc.network.ipv6 = 2001:db8:fedc:abcd::2/80') fails to start with the error below. lxc-start 1377083732.942 ERRORlxc_confile - No such file or directory - invalid ipv6 address: 2001:db8:fedc:abcd::2/80 This IPv6 address is valid, however, and the same configuration works fine on 12.04. Ubuntu Release: Ubuntu 13.04 lxc package version: 0.9.0-0ubuntu3.4 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1215391 Title: lxc-start can't parse IPv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1215391/+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 1051451] [NEW] package bind9 1:9.8.1.dfsg.P1-4ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Trying to install bind9 ProblemType: Package DistroRelease: Ubuntu 12.04 Package: bind9 1:9.8.1.dfsg.P1-4ubuntu0.3 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu13 AptOrdering: bind9utils: Install bind9: Install bind9utils: Configure bind9: Configure Architecture: amd64 Date: Sun Sep 16 07:47:41 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Mythbuntu 12.04 Precise Pangolin - Release amd64 (20120425) RelatedPackageVersions: bind9utils 1:9.8.1.dfsg.P1-4ubuntu0.3 apparmor 2.7.102-0ubuntu3.1 SourcePackage: bind9 Title: package bind9 1:9.8.1.dfsg.P1-4ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check precise -- 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/1051451 Title: package bind9 1:9.8.1.dfsg.P1-4ubuntu0.3 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/bind9/+bug/1051451/+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 1051451] Re: package bind9 1:9.8.1.dfsg.P1-4ubuntu0.3 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 bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1051451 Title: package bind9 1:9.8.1.dfsg.P1-4ubuntu0.3 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/bind9/+bug/1051451/+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 362427] Re: Public key ssh auth doesn't work with my Encrypted Home Directory
In reply to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/362427/comments/12 on /sbin/mount.ecryptfs_private I got the following message: keyctl_search: Required key not available Perhaps try the interactive 'ecryptfs-mount-private' This comment is linked to from https://help.ubuntu.com/community/EncryptedHome ecryptfs-mount-private worked fine for me, so I'd like to recommend it as a future inclusion to the howto for this page. I also have my keys in the /etc/ssh/%u/authorized_keys folder and used the above method to allow for ln -d to as ~/.ssh/authorized_keys2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/362427 Title: Public key ssh auth doesn't work with my Encrypted Home Directory To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/362427/+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 848643] Re: eucatools not working
This is just tested with bzr 1604 of nova and still neccessary to patch. So incomplete seems to be wrong for me. I am not running ubuntu, I am testing on SLES. For distribution compatibility this fix should be included, I think. Maybe someone using RHEL or another distribution can have a look. -- 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/848643 Title: eucatools not working To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/848643/+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 848643] [NEW] eucatools not working
Public bug reported: When using eucatools to create and store data (e.g. euca-add-keypair, euca-run-instances) the nova-api creates a traceback with TypeError: create_key_pair() keywords must be strings. The error must be strings always raises when you use any euca-command except the ones which only generates output. A corresponding trace is here: http://paste.openstack.org/show/2426/ Vishy took a quick look and gave me the following: http://paste.openstack.org/show/2427/ Using this patch, the commands work again. I've used the rc for this. Thanks, Vishy. ** Affects: nova (Ubuntu) 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/848643 Title: eucatools not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/848643/+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 683601] [NEW] Class-level dependencies not honored
Public bug reported: Binary package hint: puppet Hello There's a bug in Puppet 0.25.4 that breaks class-level dependency handling when using the require function multiple times: http://projects.puppetlabs.com/issues/3186 The fix is a one-liner: http://projects.puppetlabs.com/projects/puppet/repository/revisions/751df45547162632c41cf98a1b1daabbadb1b901/diff/lib/puppet/parser/functions/require.rb Could the fix be applied to the Ubuntu package? This bug is really serious and makes if very hard to use Puppet reliably. Thanks, Andre ** Affects: puppet (Ubuntu) Importance: Undecided Status: New -- Class-level dependencies not honored https://bugs.launchpad.net/bugs/683601 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet 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 609290] Re: overlapping memcpy in ssl_io_input_read
Jiri, I'm trying it out and will watch my logfiles for a few days. -- overlapping memcpy in ssl_io_input_read https://bugs.launchpad.net/bugs/609290 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 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 595116] Re: ssl error reading the headers
Does anyone know if this will also be fixed in 10.04.1 LTS scheduled for August ? Or should I attempt an upgrade to Maverick when it is released ? -- ssl error reading the headers https://bugs.launchpad.net/bugs/595116 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 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 543148] Re: Private Archive Permissions Are Incorrect
No. It is just the the CGI scripts that have the sgid flag asserted. -- Private Archive Permissions Are Incorrect https://bugs.launchpad.net/bugs/543148 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman 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 543148] [NEW] Private Archive Permissions Are Incorrect
Public bug reported: Binary package hint: mailman This bug report is for: Description:Ubuntu lucid (development branch) Release:10.04 mailman: Installed: 1:2.1.13-1 Candidate: 1:2.1.13-1 It would appear that there is a permission problem for the directory /var/lib/mailman/archives/private: drwxrws--- 8 root www-data 4096 2010-03-21 02:40 private By default, this directory is created with group www-data. This prevents Mailman scripts from accessing the archive as these scripts are run with set group ID list. As a result, nothing is written into the archive. A typical error from /var/log/mailman/error looks like this: Mar 21 02:38:19 2010 (29405) Traceback (most recent call last): File /var/lib/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop self._onefile(msg, msgdata) File /var/lib/mailman/Mailman/Queue/Runner.py, line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /var/lib/mailman/Mailman/Archiver/Archiver.py, line 198, in ArchiveMail self.__archive_to_mbox(msg) File /var/lib/mailman/Mailman/Archiver/Archiver.py, line 167, in __archive_to_mbox mbox = self.__archive_file(afn) File /var/lib/mailman/Mailman/Archiver/Archiver.py, line 155, in __archive_file return Mailbox.Mailbox(open(afn, 'a+')) IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/test.mbox/test.mbox' ** Affects: mailman (Ubuntu) Importance: Undecided Status: New -- Private Archive Permissions Are Incorrect https://bugs.launchpad.net/bugs/543148 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman 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 543148] Re: Private Archive Permissions Are Incorrect
To clarify, Mailman scripts refers to the Mailman CGI scripts. One use of these scripts is to moderate postings which in turn may cause a write into the archive when a posting is accepted. -- Private Archive Permissions Are Incorrect https://bugs.launchpad.net/bugs/543148 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman 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 329053] Re: Cannot use both zlib.output_compression and output_handler together!!
KimKulak's workaround worked for me also. Ubuntu 8.04. $ cat /etc/issue Ubuntu 8.04.2 \n \l Mythweb worked fine before an update today: Preparing to replace php5-mysql 5.2.4-2ubuntu5.4 (using .../php5-mysql_5.2.4-2ubuntu5.5_i386.deb) ... Unpacking replacement php5-mysql ... Preparing to replace libapache2-mod-php5 5.2.4-2ubuntu5.4 (using .../libapache2-mod-php5_5.2.4-2ubuntu5.5_i386.deb) ... Unpacking replacement libapache2-mod-php5 ... Preparing to replace php5-common 5.2.4-2ubuntu5.4 (using .../php5-common_5.2.4-2ubuntu5.5_i386.deb) ... Unpacking replacement php5-common ... Preparing to replace libpq5 8.3.5-0ubuntu0.8.04 (using .../libpq5_8.3.6-0ubuntu8.04_i386.deb) ... Unpacking replacement libpq5 ... Preparing to replace php5 5.2.4-2ubuntu5.4 (using .../php5_5.2.4-2ubuntu5.5_all.deb) ... Unpacking replacement php5 ... Thanks -- Cannot use both zlib.output_compression and output_handler together!! https://bugs.launchpad.net/bugs/329053 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 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 42947] Re: postfix: fatal: /etc/postfix/postfix-script: No such file or directory
I update postfix today and i had that error: Running newaliases * Stopping Postfix Mail Transport Agent postfix postfix/postfix-script: fatal: usage: postfix start (or stop, reload, abort, flush, check, set-permissions, upgrade-configuration) [fail] invoke-rc.d: initscript postfix, action restart failed. dpkg: error processing postfix (--configure): The problem was that the upgrade did not replace /etc/postfix/postfix-script. After replacing it manually from the postfix .deb the update process worked. -- postfix: fatal: /etc/postfix/postfix-script: No such file or directory https://bugs.launchpad.net/bugs/42947 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix 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 265004] [NEW] postfix upgrade does not replace /etc/postfix/postfix-script
Public bug reported: Binary package hint: postfix * Stopping Postfix Mail Transport Agent postfix postfix/postfix-script: fatal: usage: postfix start (or stop, reload, abort, flush, check, set-permissions, upgrade-configuration) [fail] invoke-rc.d: initscript postfix, action restart failed. dpkg: error processing postfix (--configure): subprocess post-installation script returned error exit status 1 The postfix upgrade process does not work when /etc/postfix/postfix-script is not being replaced by the new version from the package. Maybe when it never gets replaced there will be an incompatible script there at some point. The old one i had was from March 2005 and the new one is from August 2008. I had to replace it manually for /etc/init.d/postfix to work. Ubuntu 8.04 postfix 2.5.1-2ubuntu1.1 ** Affects: postfix (Ubuntu) Importance: Undecided Status: New -- postfix upgrade does not replace /etc/postfix/postfix-script https://bugs.launchpad.net/bugs/265004 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix 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 42947] Re: postfix: fatal: /etc/postfix/postfix-script: No such file or directory
Hello Scott, I opened a new one as No such file... is something different. The script is there, it's just an old incompatible one. https://bugs.launchpad.net/bugs/265004 Using Ubuntu 8.04. But i don't know from which version the old postfix- script is from since the system got 2 release upgrades starting from 7.04 and the postfix-script probably never got replaced. -- postfix: fatal: /etc/postfix/postfix-script: No such file or directory https://bugs.launchpad.net/bugs/42947 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix 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
