[Bug 1717378] Re: uwsgi-plugin-php depends on an unreleased version of libphp-embed
I just upgraded to uwsgi 2.0.12-5ubuntu3.2 and uwsgi-plugin-php 2.0.12-5ubuntu3.2. I don't have any held broken packages with these: $ dpkg -l uwsgi* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===- ii uwsgi 2.0.12-5ubuntu3.2 amd64 fast, self-healing application container server ii uwsgi-core2.0.12-5ubuntu3.2 amd64 fast, self-healing application container server (core) ... ii uwsgi-plugin-php 2.0.12-5ubuntu3.2 amd64 PHP plugin for uWSGI So I think this is fixed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717378 Title: uwsgi-plugin-php depends on an unreleased version of libphp-embed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1717378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717378] [NEW] uwsgi-plugin-php depends on an unreleased version of libphp-embed
Public bug reported: When I try and upgrade uwsgi-plugin-php 2.0.12-5ubuntu3.1 I get: $ sudo apt-get install uwsgi-plugin-php Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: uwsgi-plugin-php : Depends: libphp-embed (>= 1:7.0+35ubuntu6.1~) E: Unable to correct problems, you have held broken packages. There doesn't seem to be a version of libphp-embed that has been released with that version (yet): $ apt-cache policy uwsgi-plugin-php uwsgi-plugin-php: Installed: 2.0.12-5ubuntu3 Candidate: 2.0.12-5ubuntu3.1 Version table: 2.0.12-5ubuntu3.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages *** 2.0.12-5ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libphp7.0-embed libphp7.0-embed: Installed: 7.0.22-0ubuntu0.16.04.1 Candidate: 7.0.22-0ubuntu0.16.04.1 Version table: *** 7.0.22-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 7.0.4-7ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ apt-cache policy libphp-embed libphp-embed: Installed: 1:7.0+35ubuntu6 Candidate: 1:7.0+35ubuntu6 Version table: *** 1:7.0+35ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 I expected to be able to upgrade uwsgi-plugin-php to 2.0.12-5ubuntu3.1. I was unable to upgrade. ** Affects: uwsgi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717378 Title: uwsgi-plugin-php depends on an unreleased version of libphp-embed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1717378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711255] Re: systemd RestartSec does not seem to work consistently
>A minimal working reproducer with e.g. ExecStart=/bin/false would be useful. To remove the >uncertainties w.r.t. executables involved. As I do not have access to the masked product. OK, I'll try and reproduce it with that. >Is this reproducible in Ubuntu Artful which has much newer systemd? Never tried running our software on Artful since Xenial is our current target platform. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711255 Title: systemd RestartSec does not seem to work consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1711255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711255] [NEW] systemd RestartSec does not seem to work consistently
Public bug reported: The unit file for my service -33005.service: [Unit] Description=product 33005 service Wants=some.mount After=some.mount PartOf=product.target PartOf=someother.service [Service] Type=simple ExecStart=/opt/product/bin/ -conf=/etc/product.conf Restart=on-failure User=product Group=product LimitCORE=infinity LimitNOFILE=1 Slice=.slice WatchdogSec=120 RestartSec=10 StartLimitInterval=120 StartLimitBurst=10 [Install] WantedBy=product.target specifies RestartSec=10, which is also what systemd sees: $ systemctl show -33005.service Type=simple Restart=on-failure NotifyAccess=main RestartUSec=10s ... However, today I saw in the journalctl log: $ journalctl -u -33005.service ... Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Watchdog timeout (limit 2min)! Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Unit entered failed state. Aug 15 23:28:29 a-hostname systemd[1]: -33005.service: Failed with result 'exit-code'. Aug 15 23:28:39 a-hostname systemd[1]: -33005.service: Service hold-off time over, scheduling restart. Aug 15 23:28:39 a-hostname systemd[1]: Stopped product 33005 service. Aug 15 23:28:39 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:28:45 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:28:45 a-hostname systemd[1]: Stopping product 33005 service... Aug 15 23:28:45 a-hostname systemd[1]: Stopped product 33005 service. Aug 15 23:33:51 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:33:51 a-hostname [3629]: Get http://127.0.0.1:8081/: dial tcp 127.0.0.1:8081: getsockopt: connection refused Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Unit entered failed state. Aug 15 23:33:51 a-hostname systemd[1]: -33005.service: Failed with result 'exit-code'. Aug 15 23:34:01 a-hostname systemd[1]: -33005.service: Service hold-off time over, scheduling restart. Aug 15 23:34:02 a-hostname systemd[1]: Stopped product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: Started product 33005 service. Aug 15 23:34:02 a-hostname systemd[1]: -33005.service: Start request repeated too quickly. Aug 15 23:34:02 a-hostname systemd[1]: Failed to start product 33005 service. Everything looks to me that systemd is behaving as expected until Aug 15 23:34:02 when it attempts to start -33005.service not at the rate I specified in RestartSec, but possibly at the default 100ms rate. This excerpt shows both the expected 10s restart rate as well as the unexpected restart rate. $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ uname -a Linux a-hostname 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy systemd systemd: Installed: 229-4ubuntu16 Candidate: 229-4ubuntu19 Version table: 229-4ubuntu19 500 500 http://internal-repo/ubuntu xenial-updates/main amd64 Packages *** 229-4ubuntu16 100 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://internal-repo/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://internal-repo/ubuntu xenial/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: - The unit file for my service : + The unit file for my service -33005.service: [Unit] Description=product 33005 service Wants=some.mount After=some.mount PartOf=product.target PartOf=someother.service [Service] Type=simple ExecStart=/opt/product/bin/ -conf=/etc/product.conf Restart=on-failure User=product Group=product LimitCORE=infinity LimitNOFILE=1 Slice=.slice WatchdogSec=120 RestartSec=10 StartLimitInterval=120 StartLimitBurst=10 [Install] WantedBy=product.target specifies RestartSec=10, which is also what systemd sees: $ systemctl show -33005.service Type=simple Restart=on-failure NotifyAccess=main RestartUSec=10s ... However, today I saw in the journalctl log: $ journalctl -u -
[Bug 1420570] Re: clang and clang++ are missing on update
Still missing even after today's clang package update. ii clang-3.5 1:3.5-4ubuntu2~trusty2 amd64C, C++ and Objective-C compiler (LLVM based) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420570 Title: clang and clang++ are missing on update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/+bug/1420570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420570] [NEW] clang and clang++ are missing on update
Public bug reported: When I upgraded clang 3.5 yesterday, /usr/bin/clang and /usr/bin/clang++ (at least) that were clang 3.5 binaries are no longer installed. These are the clang packages I have installed: ii clang-3.5 1:3.5-4ubuntu2~trusty1 amd64C, C++ and Objective-C compiler (LLVM based) ii clang-3.5-doc 1:3.5-4ubuntu2~trusty1 all C, C++ and Objective-C compiler (LLVM based) - Documentation ii clang-format-3.5 1:3.5-4ubuntu2~trusty1 amd64Tool to format C/C++/Obj-C code ii libclang-common-3.4-dev 1:3.4-1ubuntu3 amd64clang library - Common development package ii libclang-common-3.5-dev 1:3.5-4ubuntu2~trusty1 amd64clang library - Common development package ii libclang1-3.4:amd64 1:3.4-1ubuntu3 amd64C interface to the clang library ii libclang1-3.5:amd64 1:3.5-4ubuntu2~trusty1 amd64C interface to the clang library These are the llvm packages I have installed: ii libllvm3.4:amd64 1:3.4-1ubuntu3 amd64Modular compiler and toolchain technologies, runtime library ii libllvm3.5:amd64 1:3.5-4ubuntu2~trusty1 amd64Modular compiler and toolchain technologies, runtime library ii llvm-3.4 1:3.4-1ubuntu3 amd64Modular compiler and toolchain technologies ii llvm-3.4-dev 1:3.4-1ubuntu3 amd64Modular compiler and toolchain technologies, libraries and headers ii llvm-3.4-runtime 1:3.4-1ubuntu3 amd64Modular compiler and toolchain technologies, IR interpreter ii llvm-3.5 1:3.5-4ubuntu2~trusty1 amd64Modular compiler and toolchain technologies ii llvm-3.5-dev 1:3.5-4ubuntu2~trusty1 amd64Modular compiler and toolchain technologies, libraries and headers ii llvm-3.5-runtime 1:3.5-4ubuntu2~trusty1 amd64Modular compiler and toolchain technologies, IR interpreter The /usr/bin/clang-3.5 and /usr/bin/clang++-3.5 binaries are installed (and seem to work OK): $ clang-3.5 --version Ubuntu clang version 3.5.0-4ubuntu2~trusty1 (tags/RELEASE_350/final) (based on LLVM 3.5.0) Target: x86_64-pc-linux-gnu Thread model: posix ** Affects: llvm-toolchain-snapshot (Ubuntu) Importance: Undecided Status: New ** Tags: clang clang++ upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420570 Title: clang and clang++ are missing on update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/+bug/1420570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
