Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

SOLVED Crashplan Upgrade fails + can't install bash.

Western Digital Drives - The Preferred Drives of FreeNAS and TrueNAS CORE
Status
Not open for further replies.

Xelas

Explorer
Joined
Sep 10, 2013
Messages
95
OK - I'm getting REALLY fed up with this.
Crashplan UI stopped connecting to server. Went through updating the .ui.info rigmarole, but now have a new problem, with crashplan unable to update due to missing bash (it upgraded fine for the last year? Why now?!)
pkg update / pkg install bash fails, with:
Code:
pkg: http://pkg.FreeBSD.org/freebsd:9:x86:64/latest/All/bash-4.3.18_2.txz: Not Found

Well, that's right - that file really does not exist - browsing to the repo manually shows that 4.3.42 is the latest version.
Well, Fine.
Code:
root@Crashplan:/# pkg add http://pkg.freebsd.org/freebsd:9:x86:64/latest/All/bash-4.3.42.txz
bash-4.3.42.txz                                                                                                                                                                                  100% 1249KB   1.2MB/s   1.2MB/s   00:00
Installing bash-4.3.42...pkg: Missing dependency matching Origin: 'print/indexinfo' Version: '0.2.3'

Failed to install the following 1 package(s): http://pkg.freebsd.org/freebsd:9:x86:64/latest/All/bash-4.3.42.txz

Well, damn.
Then I find out that
Code:
 pkg -v
1.2.7_2

pkg upgrade tells me "nothing to do".
What now?!

EDIT - is the plugin immune to this BS? Any advantage to running in a jail vs plugin?
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,630
CrashPlan changed their update routine to require Bash. Updates to versions prior to 4.4 did not require bash, so that's probably why you were able to update, and are now unable to update.

When you ran "pkg update" it should have updated the repo catalogue to show the most recent version of bash. I would say that is the root of your problem. It also explains why it can't install the dependencies of the required version: it doesn't know that there's a new version.

Go back and run "pkg update" and let us know what spits out.
 

Xelas

Explorer
Joined
Sep 10, 2013
Messages
95
Thank you, Nick! My grumbling was more along the lines of why suddenly require bash when it worked fine without. Oh well, it's a learning opportunity, although I'm eager to get this fixed ASAP, as the server needs to keep about 4TB backed up, and it took me about 30 days to seed the initial backup. I don't want to fall too far behind as the backup becomes more stale.

I am executing pkg commands from inside the jail.

Code:
root@Crashplan:/ # pkg update
Updating repository catalogue
root@Crashplan:/ #


Oh - here's pkg -vv, for good measure. I agree that pkg seems to be whonky, but it's beyond my knowledge level to fix. From what I understand, the jail has a very old version of pkg:
Code:
root@Crashplan:/ # pkg -vv
Version  : 1.2.7_2
PACKAGESITE  :
PKG_DBDIR  : /var/db/pkg
PKG_CACHEDIR  : /var/cache/pkg
PORTSDIR  : /usr/ports
PUBKEY  :
HANDLE_RC_SCRIPTS  : no
ASSUME_ALWAYS_YES  : no
REPOS_DIR  : [
  /etc/pkg/,
  /usr/local/etc/pkg/repos/,
]
PLIST_KEYWORDS_DIR  :
SYSLOG  : yes
AUTODEPS  : yes
ABI  : freebsd:9:x86:64
DEVELOPER_MODE  : no
PORTAUDIT_SITE  : http://portaudit.FreeBSD.org/auditfile.tbz
VULNXML_SITE  : http://www.vuxml.org/freebsd/vuln.xml.bz2
MIRROR_TYPE  : SRV
FETCH_RETRY  : 3
PKG_PLUGINS_DIR  : /usr/local/lib/pkg/
PKG_ENABLE_PLUGINS  : yes
PLUGINS  : [
]
DEBUG_SCRIPTS  : no
PLUGINS_CONF_DIR  : /usr/local/etc/pkg/
PERMISSIVE  : no
REPO_AUTOUPDATE  : yes
NAMESERVER  :
EVENT_PIPE  :
FETCH_TIMEOUT  : 30
UNSET_TIMESTAMP  : no
SSH_RESTRICT_DIR  :
PKG_SSH_ARGS  :
PKG_ENV  : {
}
DISABLE_MTREE  : no
DEBUG_LEVEL  : 0
ALIAS  : {
}

Repositories:
  FreeBSD: {
  url  : "pkg+http://pkg.FreeBSD.org/freebsd:9:x86:64/latest",
  enabled  : yes,
  mirror_type  : "SRV"
  }
root@Crashplan:/ #
 
Last edited:

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,630
Yeah, that seems like a pretty old version. I'm currently running 1.6.1 in my Crashplan Jail.

What happens if you run "pkg install pkg"? You might try forcing it to update to the new version of pkg: http://pkg.freebsd.org/freebsd:9:x86:64/latest/All/pkg-1.6.1.txz

EDIT: I wonder if you're actually missing your repos entirely. When you run pkg update, it should list out your repos, and since it didn't, it might not be there. Check if you have a FreeBSD.conf file in /usr/local/etc/pkg/repos. If you don't you might want to create it. My FreeBSD.conf file for reference:

Code:
root@crashplan_1:/ # cat /usr/local/etc/pkg/repos/FreeBSD.conf
FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/freebsd:9:x86:64/latest",
  mirror_type: "srv",
  enabled: yes
}
 

Xelas

Explorer
Joined
Sep 10, 2013
Messages
95
Code:
root@Crashplan:/usr/local/etc # pkg install pkg
Updating repository catalogue
pkg-1.2.7_2 already installed
root@Crashplan:/usr/local/etc #


I do have a FreeBSD.conf in the right directory, and it's identical to yours. I also have a pkg.conf in /usr/local/etc/ with the same contents - I tried with and without that, but it doesn't make a difference either way.

Forcing pkg to reinstall finally seems to have done it. THANK YOU!

Code:
root@Crashplan:/ # pkg add -f http://pkg.freebsd.org/freebsd:9:x86:64/latest/All/pkg-1.6.1.txz
pkg-1.6.1.txz  100% 2080KB  2.0MB/s  2.0MB/s  00:01
Installing pkg-1.6.1...pkg: package pkg is already installed, forced install
done
root@Crashplan:/ # pkg update
Updating FreeBSD repository catalogue...
Repo "FreeBSD" upgrade schema 2006 to 2007: Add conflicts and provides
Repo "FreeBSD" upgrade schema 2007 to 2008: Add FTS index
Repo "FreeBSD" upgrade schema 2008 to 2009: Optimize indicies
Repo "FreeBSD" upgrade schema 2009 to 2010: Add legacy digest field
pkg: Unable to upgrade "FreeBSD" repo schema version 2010 (target version 2012) -- change not found
pkg: need to re-create repo FreeBSD to upgrade schema version
[Crashplan] Fetching meta.txz: 100%  968 B  1.0kB/s  00:01
[Crashplan] Fetching packagesite.txz: 100%  5 MiB  5.5MB/s  00:01
Processing entries: 100%
FreeBSD repository update completed. 24450 packages processed.
root@Crashplan:/ # pkg install bash
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
The following 25 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
  neon29-0.29.6_6

New packages to be INSTALLED:
  bash: 4.3.42
  indexinfo: 0.2.3
  libffi: 3.2.1
  gettext-runtime: 0.19.6
  db5: 5.3.28_2
  gettext-tools: 0.19.6

Installed packages to be UPGRADED:
  libiconv: 1.14_3 -> 1.14_9
  libxml2: 2.9.1_1 -> 2.9.2_3
  aria2: 1.18.5_1 -> 1.19.0
  sqlite3: 3.8.4.3 -> 3.8.11.1_1
  subversion: 1.8.9 -> 1.8.14_2
  expat: 2.1.0 -> 2.1.0_3
  gettext: 0.18.3.1_1 -> 0.19.6
  python27: 2.7.6_4 -> 2.7.10
  gdbm: 1.11 -> 1.11_2
  apr: 1.5.1.1.5.3 -> 1.5.2.1.5.4
  db48: 4.8.30.0_1 -> 4.8.30.0_2
  serf: 1.3.6 -> 1.3.8
  binutils: 2.24 -> 2.25.1
  gcc: 4.7.3_1 -> 4.8.5
  libidn: 1.28_1 -> 1.31
  wget: 1.15 -> 1.16.3

Installed packages to be REINSTALLED:
  gmp-5.1.3_2
  mpfr-3.1.2_2 (direct dependency changed: indexinfo)

The process will require 34 MiB more space.
108 MiB to be downloaded.

Proceed with this action? [y/N]: y
[Crashplan] Fetching bash-4.3.42.txz: 100%  1 MiB  1.3MB/s  00:01

...a LOT of packages suddenly realizing they are years out of date!...

 
Last edited:

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,630
Excellent! I'm glad you were able to get it working.
 

diskdiddler

Wizard
Joined
Jul 9, 2014
Messages
2,330
Anyone else with this problem - as per above the version has changed, the command to force the install is now.

"pkg add -f http://pkg.freebsd.org/freebsd:9:x86:64/latest/All/pkg-1.6.1_2.txz"
Then a "pkg update" will work fine again.
Finally, you can NOW run the
"pkg install bash"
which should fix some crashplan update issues.

Thanks to those in this thread!
 

Xelas

Explorer
Joined
Sep 10, 2013
Messages
95
Status
Not open for further replies.
Top