AnsweredAssumed Answered

Fileserver process has incorrect Buildversion after 3.1 to 5.1 upgrade

Question asked by andyt22 on Apr 26, 2016
Latest reply on Apr 27, 2016 by mufeed

I upgraded my Ubuntu-based 15 node cluster from MapR M3 edition to 5.1 following the instructions at Offline MapR Core Upgrade Using Manual Steps - MapR 5.0 Documentation -, using a local repository server onto which I had already downloaded the .deb packages from MapR. I just used 'apt-get install <package name>' to do the updates as described in this documentation.


I was a bit confused by this instruction in the upgrade documentation:


4. Manually update configuration files and license text files:

  • On all nodes, manually merge new configuration settings from the /opt/mapr/ file into the /opt/mapr/conf/warden.conf file.
  • On all nodes, manually merge new configuration settings from the files in the /opt/mapr/conf/ directory to the files in the /opt/mapr/conf/conf.d/ directory.


because I found that the update script seemed to have already altered files in both the existing conf.d and folders. So I left these config folders exactly as they were and started the cluster. HDFS works but I'm getting this alarm message in the MCS from every node:


FileServe process has incorrect BuildVersion: expected version


The new mapr-fileserver is definitely installed, eg:


dpkg -l mapr-fileserver


| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

||/ Name           Version      Architecture Description


ii  mapr-fileserve amd64        MapR: fileserver role package


and I get the expected BuidVersion from:


cat /opt/mapr/MapRBuildVersion


but this MAPRCLI command is returning the old 3.1 version:


maprcli config load -keys mapr.targetversion



What am I doing wrong?