Bug#826257: jetty9: Installation fails "jetty9.pid exists, but jetty was not running"
> > Setting up jetty9 (9.2.16-1) ... > > Job for jetty9.service failed because the control process exited with error > > code. > > See "systemctl status jetty9.service" and "journalctl -xe" for details. > > invoke-rc.d: initscript jetty9, action "start" failed. > Are you able to start the service after removing the /var/run/jetty9.pid file? # rm /var/run/jetty9.pid # env LC_ALL=C apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up jetty9 (9.2.16-1) ... Job for jetty9.service failed because the control process exited with error code. See "systemctl status jetty9.service" and "journalctl -xe" for details. invoke-rc.d: initscript jetty9, action "start" failed. dpkg: error processing package jetty9 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: jetty9 E: Sub-process /usr/bin/dpkg returned an error code (1) # rm /var/run/jetty9.pid # systemctl start jetty9 Job for jetty9.service failed because the control process exited with error code. See "systemctl status jetty9.service" and "journalctl -xe" for details.
Bug#826257: jetty9: Installation fails "jetty9.pid exists, but jetty was not running"
Package: jetty9 Version: 9.2.16-1 Severity: important * What led up to the situation? Trying to install via "aptitude install jetty9" * What was the outcome of this action? Setting up jetty9 (9.2.16-1) ... Job for jetty9.service failed because the control process exited with error code. See "systemctl status jetty9.service" and "journalctl -xe" for details. invoke-rc.d: initscript jetty9, action "start" failed. systemctl: jetty9.service - LSB: Start Jetty Loaded: loaded (/etc/init.d/jetty9; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Fr 2016-06-03 19:35:16 CEST; 51s ago Docs: man:systemd-sysv-generator(8) Process: 22147 ExecStart=/etc/init.d/jetty9 start (code=exited, status=1/FAILURE) Jun 03 19:35:11 w530-lx-jpl systemd[1]: Starting LSB: Start Jetty... Jun 03 19:35:11 w530-lx-jpl jetty9[22147]: Starting Jetty 9 Servlet Engine: jetty9/var/run/jetty9.pid exists, but jetty was not running. Ignoring /var/run/jet Jun 03 19:35:16 w530-lx-jpl jetty9[22147]: failed! Jun 03 19:35:16 w530-lx-jpl systemd[1]: jetty9.service: Control process exited, code=exited status=1 Jun 03 19:35:16 w530-lx-jpl systemd[1]: Failed to start LSB: Start Jetty. Jun 03 19:35:16 w530-lx-jpl systemd[1]: jetty9.service: Unit entered failed state. Jun 03 19:35:16 w530-lx-jpl systemd[1]: jetty9.service: Failed with result 'exit-code'. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages jetty9 depends on: ii adduser 3.114 ii apache2-utils2.4.20-2 ii default-jre-headless [java7-runtime-headless]2:1.8-57 ii libjetty9-extra-java 9.2.16-1 ii libjetty9-java 9.2.16-1 ii openjdk-8-jre-headless [java7-runtime-headless] 8u91-b14-2 Versions of packages jetty9 recommends: ii authbind 2.1.1+nmu1 jetty9 suggests no packages. -- no debconf information
Bug#784314: postgresql-common: config uses sh(dash) for supported-versions script: bad substitution
Package: postgresql-common Version: 165 Severity: important $ aptitude install postgresql-9.4 results in a "bad substitution" error the script "postgresql-common.config" has the line SUPPORTED=`sh /usr/share/postgresql-common/supported-versions` which triggers the error. using /bin/bash works. /bin/sh is a symlink to /bin/dash (s.b.) not fixed in 166. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (1001, 'stable'), (500, 'stable-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages postgresql-common depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii init-system-helpers 1.22 ii lsb-base 4.1+Debian13+nmu1 ii postgresql-client-common 165 ii procps2:3.3.9-9 ii ssl-cert 1.0.35 ii ucf 3.0030 Versions of packages postgresql-common recommends: ii logrotate 3.8.7-1+b1 postgresql-common suggests no packages. -- debconf information: postgresql-common/obsolete-major: postgresql-common/ssl: true
Bug#750080: XMonad 0.11-8 fails
xmonad_0.11-8_amd64 still fails when there is no .xmonad/xmonad.hs.
Bug#750080:
There's no difference.Same error message: $HOME/.xmonad/xmonad-x86_64-linux: executeFile: does not exist (No such file or directory) (which makes sense).
Bug#750080: User directories
.xmonad is empty .ghc doesn't exist .cabal doesn't exist either xmonad still tries to compile the non-existant xmonad.hs file
Bug#750080: No .xmonad directory
There is no ~/.xmonad directory and therefore no xmonad.hs file in it. (Are packages supposed to install files in user directories?) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
