> > *dpkg: error processing package bb-node-red-installer (--configure):* > * subprocess installed post-installation script returned error exit status 137*
My understanding is that exit status 137 == exit status 128 + n where n here would seem to be 9. So . . . SIGKILL 9 . . . Quite possibly this is the oomkiller killing your process because it thinks, or knows it's using too much memory. On Thu, Feb 25, 2016 at 5:42 PM, Wally Bkg <[email protected]> wrote: > I've been running bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz > since shortly after it was released with great success on my BBW. I've > kept reasonably current with apt-get update ; apt-get upgrade, although > there are 73 packages to be upgraded with c9-core-installer held back when > I looked a few minutes ago. Its installed to an 8GB SD card so space is > not an issue. This system has been running 24/7 since mid December doing > an essential job, but the system is evolving with new features added > incrementally, so I'd like to "roll" with Jessie as things progress. > > ~# cat /etc/dogtag > BeagleBoard.org Debian Image 2015-11-12 > > ~# uname -a > Linux alarmbone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 > armv7l GNU/Linux > > Before I do this much of an upgrade, I'll shut the system down and "clone" > the sdcard so I can quickly go back, should something go wrong, but before > I start I'd like to know if I'm leaving out some packages that I don't know > the names of. > > > This part seem obvious and reasonably well documented, update kernel and > dtb files, but is this the "correct" kernel to be tracking these Jessie > Testing images?: > git clone https://github.com/beagleboard/bb.org-overlays cd > ./bb.org-overlays > ./dtc-overlay.sh > ./install.sh > cd /opt/scripts/tools > git pull > sudo ./update_kernel.sh --lts-4_1 --ti-channel > > > Next I'd like to install the basic lxqt package so things like gedit would > work over ssh -X > What packages are needed to upgrade the 2GB console image to the 4GB lxqt > testing image? > > > I'm also concerned about the various "installer" packages I've seen > mentioned in various threads, like: > bb-bonescript-installer-beta > bb-node-red-installer > > What others might I be missing from my 2015-11-12 image? > > Or is it not really a viable option to try and evolve with apt-get update > ; apt-get upgrade? > > > Things don't seem right with Jessie updates. I ended up with an unusable > system (no ssh, no usb gadget) after trying apt-get update ; apt-get > upgrade trying to move from 8.2 to 8.3. back in early December, so I'm > being more careful this time. > > Doing something that should be relatively "safe" (as I'm not sure I'll > really use it, so unless it does really bad things all I risk > is wasting some SD card space) but it didtn't work: > ~# apt-get install bb-node-red-installer > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following extra packages will be installed: > bb-npm-installer > The following NEW packages will be installed: > bb-node-red-installer bb-npm-installer > 0 upgraded, 2 newly installed, 0 to remove and 74 not upgraded. > Need to get 6,884 B of archives. > After this operation, 78.8 kB of additional disk space will be used. > Do you want to continue? [Y/n] Y > Get:1 http://repos.rcn-ee.com/debian/ jessie/main bb-npm-installer all > 3.7.5-0rcnee1~bpo80+20160224+1 [2,800 B] > Get:2 http://repos.rcn-ee.com/debian/ jessie/main bb-node-red-installer > all 0.13.2-0rcnee1~bpo80+20160222+1 [4,084 B] > Fetched 6,884 B in 0s (40.7 kB/s) > Selecting previously unselected package bb-npm-installer. > (Reading database ... 33721 files and directories currently installed.) > Preparing to unpack > .../bb-npm-installer_3.7.5-0rcnee1~bpo80+20160224+1_all.deb ... > Unpacking bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ... > Setting up bb-npm-installer (3.7.5-0rcnee1~bpo80+20160224+1) ... > bb-npm-installer:npm: [1.4.21] > bb-npm-installer:node: [v0.10.41] > bb-npm-installer:Installing: npm-3.7.5 (for bb-npm-installer) > /usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js > [email protected] /usr/local/lib/node_modules/npm > bb-npm-installer:Installed > Selecting previously unselected package bb-node-red-installer. > (Reading database ... 33723 files and directories currently installed.) > Preparing to unpack > .../bb-node-red-installer_0.13.2-0rcnee1~bpo80+20160222+1_all.deb ... > Unpacking bb-node-red-installer (0.13.2-0rcnee1~bpo80+20160222+1) ... > Setting up bb-node-red-installer (0.13.2-0rcnee1~bpo80+20160222+1) ... > bb-node-red-installer:npm: [1.4.21] > bb-node-red-installer:node: [v0.10.41] > bb-node-red-installer:Installing: systemd-0.2.6 (for node-red) > [email protected] /usr/local/lib/node_modules/systemd > bb-node-red-installer:Installing: node-red-0.13.2 (for node-red) > > > [email protected] install > /usr/local/lib/node_modules/node-red/node_modules/bcrypt > > node-gyp rebuild > > make: Entering directory > '/usr/local/lib/node_modules/node-red/node_modules/bcrypt/build' > CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o > CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o > CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o > Killed > dpkg: error processing package bb-node-red-installer (--configure): > subprocess installed post-installation script returned error exit status > 137 > Errors were encountered while processing: > bb-node-red-installer > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Any ideas as to what is wrong? > Do I need a kernel update first? or something else? if so, then it seems > by definition some dependencies are broken. > > I won't be doing anything else with this system until I've had time to > shutdown and clone the current SD card. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
