Unable to install or uninstall any apps

The following is a detailed report on my attempts to fix my ReadyNAS package install/remove problems.

Report Summary

The root cause of my package installation problem was the result of running out of disk space when installing a PLEX update. It had nothing to do with the OS upgrade.

The failed PLEX installation left the Debenian Pakage Manage with a failed installation state. There is no interface from the ReadyNAS admin interface that can trigger the cleanup of the failed installation.

If you attempt to install another package, the logs indicated that the package was installed. However, the Debian Package Manager processes all of the outstanding package states, including the failed PLEX package. This returns a failure status that triggers the backout of the current package install.

This overall failue status is returned to the ReadyNAS with no indication of why the package installation failed.

I recommend that the ReadyNAS test the Debian package status before attempting to install a new package and report more information status back to the user. Also, the /var/log/apt/term.log and /var/log/dpkg.log should be included in the logs returned by NETGEAR RAIDer.

This woud help in resolving package installation problems. Note that NETGEAR  RAIDer logs include /var/log/readynasd/install_debpkg.log

 There appears to be a problem with the rslog-mysql install/uninstall script. The suspects are the update to the rsyslog configuration file or the relocation of the MySQL databases to the data volume by support.

Report Details

Fault history from install_debpkg.log

....
START(/tmp/plexmediaserver-ros6-binaries_1.4.3.3433-03e4cfa35_amd64.deb): Thu Mar 16 22:05:46 EST 2017
.....
DONE(0): Fri Mar 17 00:37:52 EST 2017
spooler returns spool_status=0 outbuf=(null) errbuf=(null) is_localapp=1 name=plexmediaserver-ros6-binaries_1.4.3.3433-03e4cfa35_amd64.deb pkgname=plexmediaserver-ros6-binaries

START(/tmp/plexmediaserver-ros6-binaries_1.4.4.3495-edef59192_amd64.deb): Sun Mar 19 15:19:01 EST 2017
Hit http://security.debian.org jessie/updates InRelease
Hit http://egnyte-cdn.egnyte.com 6.6 InRelease
Ign http://mirrors.kernel.org jessie InRelease
Hit http://apt.readynas.com 6.6.1 InRelease
Hit http://mirrors.kernel.org jessie Release.gpg
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://mirrors.kernel.org jessie Release
Hit http://egnyte-cdn.egnyte.com 6.6/egnyte amd64 Packages
Hit http://apt.readynas.com 6.6.1/updates amd64 Packages
Hit http://mirrors.kernel.org jessie/main amd64 Packages
Hit http://apt.readynas.com 6.6.1/apps amd64 Packages
Hit http://apt.readynas.com 6.6.1/main amd64 Packages
Reading package lists...
 new debian package, version 2.0.
 size 102975454 bytes: control archive=72725 bytes.
     582 bytes,    14 lines      control              
  342540 bytes,  2481 lines      md5sums              
    2858 bytes,    73 lines   *  postinst             #!/bin/sh
     132 bytes,     7 lines   *  postrm               #!/bin/sh
    1175 bytes,    42 lines   *  prerm                #!/bin/sh
    2854 bytes,    58 lines      shlibs               
 Package: plexmediaserver-ros6-binaries
 Source: plexmediaserver-ros6
 Version: 1.4.4.3495-edef59192
 Architecture: amd64
 Maintainer: Plex, inc. <linux@plexapp.com>
 Installed-Size: 213964
 Conflicts: plexmediaserver-ros6, plexmediaserver-ros6-binaries
 Breaks: plexmediaserver-ros6, plexmediaserver-ros6-binaries
 Replaces: plexmediaserver-ros6, plexmediaserver-ros6-binaries
 Provides: plexmediaserver-ros6, plexmediaserver-ros6-binaries
 Section: video
 Priority: extra
 Homepage: https://plex.tv
 Description: Plex organizes all of your personal media so you can easily access and enjoy it.
fv-dpkginstall.awk: error 0
Successfully installed dependencies for /tmp/plexmediaserver-ros6-binaries_1.4.4.3495-edef59192_amd64.deb
(Reading database ... 25780 files and directories currently installed.)
Preparing to unpack .../plexmediaserver-ros6-binaries_1.4.4.3495-edef59192_amd64.deb ...
Removed /etc/systemd/system/multi-user.target.wants/fvapp-plexmediaserver.service.
Unpacking plexmediaserver-ros6-binaries (1.4.4.3495-edef59192) over (1.4.3.3433-03e4cfa35) ...
Setting up plexmediaserver-ros6-binaries (1.4.4.3495-edef59192) ...
Adding 'diversion of /apps/plexmediaserver/plexmediaserver_environment to /apps/plexmediaserver/plexmediaserver_environment.orig by plexmediaserver-ros6-binaries'
Ignoring request to rename file '/apps/plexmediaserver/plexmediaserver_environment' owned by diverting package 'plexmediaserver-ros6-binaries'
dpkg-divert: error: unable to create new file '/var/lib/dpkg/diversions-new': No space left on device
dpkg: error processing package plexmediaserver-ros6-binaries (--install):
 subprocess installed post-installation script returned error exit status 2
dpkg: error: unable to create new file '/var/lib/dpkg/status-new': No space left on device
spooler returns spool_status=2 outbuf=(null) errbuf=(null) is_localapp=1 name=plexmediaserver-ros6-binaries_1.4.4.3495-edef59192_amd64.deb pkgname=plexmediaserver-ros6-binaries


At the time my ReadyNAS system was having boot problems. This was resolved by mdgm on 2017-05-29

    "In addition to running into the full root issue you root volume actually was very full. I moved your MySQL databases to the data volume and created a symlink. Your system should be fine now."

Problem #1

    "spooler returns spool_status=2 outbuf=(null) errbuf=(null) is_localapp=1 name=plexmediaserver-ros6-binaries_1.4.4.3495-edef59192_amd64.deb pkgname=plexmediaserver-ros6-binaries"
    
This was the last enty in the install_debpkg.log There were no entries of my later attempts to install a new version of PLEX or install/uninstall ReadyNAS apps.

The next problem was generated when I ran 'dpkg --configure -a'

.......

root@Eventide2:~# dpkg --configure -a
Processing triggers for libc-bin (2.19-18+deb8u9.netgear1) ...
Setting up rsyslog (8.4.2-1+deb8u2) ...

Configuration file '/etc/init.d/rsyslog'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** rsyslog (Y/I/N/O/D/Z) [default=N] ? D
--- /etc/init.d/rsyslog 2017-07-03 10:29:00.664107378 +1000
+++ /etc/init.d/rsyslog.dpkg-new        2015-12-14 23:34:27.000000000 +1100
@@ -22,14 +22,13 @@
 NAME=rsyslog

 RSYSLOGD=rsyslogd
-RSYSLOGD_BIN=/usr/sbin/rsyslogd
-RSYSLOGD_OPTIONS="-c5"
-RSYSLOGD_PIDFILE=/var/run/rsyslogd.pid
+DAEMON=/usr/sbin/rsyslogd
+PIDFILE=/var/run/rsyslogd.pid

 SCRIPTNAME=/etc/init.d/$NAME

 # Exit if the package is not installed
-[ -x "$RSYSLOGD_BIN" ] || exit 0
+[ -x "$DAEMON" ] || exit 0

 # Read configuration variable file if it is present
 [ -r /etc/default/$NAME ] && . /etc/default/$NAME
@@ -39,22 +38,15 @@

 do_start()
 {
-       DAEMON="$RSYSLOGD_BIN"
-       DAEMON_ARGS="$RSYSLOGD_OPTIONS"
-       PIDFILE="$RSYSLOGD_PIDFILE"
-
        # Return
        #   0 if daemon has been started
        #   1 if daemon was already running
        #   other if daemon could not be started or a failure occured
-       start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- $DAEMON_ARGS
+       start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- $RSYSLOGD_OPTIONS
 }

 do_stop()
 {
-       DAEMON="$RSYSLOGD_BIN"
-       PIDFILE="$RSYSLOGD_PIDFILE"
-
        # Return
        #   0 if daemon has been stopped
        #   1 if daemon was already stopped
@@ -66,9 +58,6 @@
 # Tell rsyslogd to close all open files
 #
 do_rotate() {
-       DAEMON="$RSYSLOGD_BIN"
-       PIDFILE="$RSYSLOGD_PIDFILE"
-
        start-stop-daemon --stop --signal HUP --quiet --pidfile $PIDFILE --exec $DAEMON
 }

@@ -88,13 +77,12 @@
 sendsigs_omit() {
        OMITDIR=/run/sendsigs.omit.d
        mkdir -p $OMITDIR
-       ln -sf $RSYSLOGD_PIDFILE $OMITDIR/rsyslog
+       ln -sf $PIDFILE $OMITDIR/rsyslog
 }

 case "$1" in
   start)
        log_daemon_msg "Starting $DESC" "$RSYSLOGD"
-       do_stop
        create_xconsole
        do_start
        case "$?" in
@@ -104,6 +92,7 @@
                   log_end_msg 0 ;;
                *) log_end_msg 1 ;;
        esac
+
        ;;
   stop)
        log_daemon_msg "Stopping $DESC" "$RSYSLOGD"
@@ -126,7 +115,7 @@
        $0 start
        ;;
   status)
-       status_of_proc -p $RSYSLOGD_PIDFILE $RSYSLOGD_BIN $RSYSLOGD && exit 0 || exit $?
+       status_of_proc -p $PIDFILE $DAEMON $RSYSLOGD && exit 0 || exit $?
        ;;
   *)
        echo "Usage: $SCRIPTNAME {start|stop|rotate|restart|force-reload|status}" >&2

Configuration file '/etc/init.d/rsyslog'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** rsyslog (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/init.d/rsyslog ...
insserv: can not symlink(../init.d/forked-daapd, ../rc2.d/S05forked-daapd): File exists
insserv: can not symlink(../init.d/avahi-daemon, ../rc2.d/S04avahi-daemon): File exists
insserv: can not symlink(../init.d/dbus, ../rc2.d/S03dbus): File exists
insserv: can not symlink(../init.d/apache2, ../rc2.d/S02apache2): File exists
insserv: can not symlink(../init.d/lsyncd, ../rc2.d/S01lsyncd): File exists
insserv: can not symlink(../init.d/connman, ../rc2.d/S04connman): File exists
insserv: can not symlink(../init.d/rsync, ../rc2.d/S03rsync): File exists
insserv: can not symlink(../init.d/cron, ../rc2.d/S03cron): File exists
insserv: can not symlink(../init.d/forked-daapd, ../rc3.d/S05forked-daapd): File exists
insserv: can not symlink(../init.d/avahi-daemon, ../rc3.d/S04avahi-daemon): File exists
insserv: can not symlink(../init.d/dbus, ../rc3.d/S03dbus): File exists
insserv: can not symlink(../init.d/apache2, ../rc3.d/S02apache2): File exists
insserv: can not symlink(../init.d/lsyncd, ../rc3.d/S01lsyncd): File exists
insserv: can not symlink(../init.d/connman, ../rc3.d/S04connman): File exists
insserv: can not symlink(../init.d/rsync, ../rc3.d/S03rsync): File exists
insserv: can not symlink(../init.d/cron, ../rc3.d/S03cron): File exists
insserv: can not symlink(../init.d/forked-daapd, ../rc4.d/S05forked-daapd): File exists
insserv: can not symlink(../init.d/avahi-daemon, ../rc4.d/S04avahi-daemon): File exists
insserv: can not symlink(../init.d/dbus, ../rc4.d/S03dbus): File exists
insserv: can not symlink(../init.d/apache2, ../rc4.d/S02apache2): File exists
insserv: can not symlink(../init.d/lsyncd, ../rc4.d/S01lsyncd): File exists
insserv: can not symlink(../init.d/connman, ../rc4.d/S04connman): File exists
insserv: can not symlink(../init.d/rsync, ../rc4.d/S03rsync): File exists
insserv: can not symlink(../init.d/cron, ../rc4.d/S03cron): File exists
insserv: can not symlink(../init.d/forked-daapd, ../rc5.d/S05forked-daapd): File exists
insserv: can not symlink(../init.d/avahi-daemon, ../rc5.d/S04avahi-daemon): File exists
insserv: can not symlink(../init.d/dbus, ../rc5.d/S03dbus): File exists
insserv: can not symlink(../init.d/apache2, ../rc5.d/S02apache2): File exists
insserv: can not symlink(../init.d/lsyncd, ../rc5.d/S01lsyncd): File exists
insserv: can not symlink(../init.d/connman, ../rc5.d/S04connman): File exists
insserv: can not symlink(../init.d/rsync, ../rc5.d/S03rsync): File exists
insserv: can not symlink(../init.d/cron, ../rc5.d/S03cron): File exists
Job for rsyslog.service failed because the control process exited with error code.
See "systemctl status rsyslog.service" and "journalctl -xe" for details.
invoke-rc.d: initscript rsyslog, action "restart" failed.
dpkg: error processing package rsyslog (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up plexmediaserver-ros6-binaries (1.4.4.3495-edef59192) ...
^Cdpkg: error processing package plexmediaserver-ros6-binaries (--configure):
 subprocess installed post-installation script was interrupted
dpkg: dependency problems prevent configuration of rsyslog-gnutls:
 rsyslog-gnutls depends on rsyslog (= 8.4.2-1+deb8u2); however:
  Package rsyslog is not configured yet.

dpkg: error processing package rsyslog-gnutls (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of rsyslog-mysql:
 rsyslog-mysql depends on rsyslog (= 8.4.2-1+deb8u2); however:
  Package rsyslog is not configured yet.

dpkg: error processing package rsyslog-mysql (--configure):
 dependency problems - leaving unconfigured
Processing triggers for systemd (230-7~bpo8+2.netgear2) ...
Errors were encountered while processing:
 rsyslog
 plexmediaserver-ros6-binaries
 rsyslog-gnutls
 rsyslog-mysql
 
 
 ..........
 
 By answering to Y or I  : install the package maintainer's version, I triggered a package state problem with rsyslog, rsyslog-gnutls
and rsyslog-mysql.

rsyslog is used by LogAnalyzer, so that stopped working on my system.

 END of Part 1