Cannot start open office by oocalc | Coursera Community

Cannot start open office by oocalc

  • 29 March 2021
  • 4 replies

Badge +1

In “Big Data Modeling and Management Systems” course, after install Cloudera & download the  big-data-2, I can not run the command “oocalc”. It just report “Command not found”. How can solve this problem?

4 replies

The Cloudera VM runs on GNU/Linux-based (CentOS 6.4) operating system - this is a very sized-down version of it.

Did you also execute ./ script, as shown in step “5. Install tools.” of the instruction?

All additional tools have to be correctly installed first, either via the script or manually - because by default they are not installed in the Cloudera VM guest OS. Without completing this step, the Calc application will also not run. Before installing any software in the guest OS, make sure the guest OS has unrestricted access to the Internet.

By the way, Calc is installed as a part of the LibreOffice software package, not package - as this is what I saw in the script.

If the required software is already installed in the Cloudera VM guest OS, you can also try invoking it by:

libreoffice --calc instead of oocalc

Badge +1

Thanks a lot for your reply.

There’s error when running the shell script file as below:


That’s why libre calc was not installed and oocalc not work.

Among the shell script code the below lines are fail to execute:

  • sudo yum install -y python-matplotlib libreoffice-calc python-imaging python-pip

  • pip install tweepy --user

  • pip install textblob --user

Only the below one is success:


cd $HOME/Downloads


tar -xvzf lucene-5.5.0.tgz

cd $d


How can I solve this problem?


Yes. It turns out, that CentOS 6.4 GNU/Linux (on which the Cloudera VM is based for this course), is currently an outdated system - all releases from 6.x line reached their End Of Life status fairly recently - November 30, 2020.

You can attempt some manual fixes, like e.g. executing in the VM’s shell / terminal 2 commands below (each command beginning with sudo is one single line, in which each “word” is separated by a single space):

sudo mv /etc/yum.repos.d/CentOS-Base.repo /etc/yum.repos.d/CentOS-Base.$(date +%Y%m%d-%H%M)

sudo curl -k -s | sed 's/6.10/6.4/g' > /etc/yum.repos.d/CentOS-Base.repo

If this doesn’t work, you can either:

  1. create and execute another shell script, which will do some repository setup for you,
  2. manually modify the repository file /etc/yum.repos.d/CentOS-Base.repo

My sample script (named e.g. written in Bash:

#!/usr/bin/env bash
if [[ -f /etc/yum.repos.d/CentOS-Base.repo ]]
sudo mv /etc/yum.repos.d/CentOS-Base.repo /etc/yum.repos.d/CentOS-Base.$(date +%Y%m%d-%H%M)

for repoentry in base updates extras contrib centosplus
echo "[C6.4-${repoentry}]"
echo "name=CentOS-6.4 - ${repoentry^*}"
echo "baseurl=${repoentry}/\$basearch/"
echo "gpgcheck=1"
echo "gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6"
echo "enabled=1"
echo "metadata_expire=never"
echo ""
done | sed 's/\/base\//\/os\//' > /etc/yum.repos.d/CentOS-Base.repo

Save the file and execute it e.g. by invoking in the shell / terminal:

sudo bash

See for reference.

You may then encounter additional issues with Cloudera repositories, but they can be temporarily disabled during the installation of other software:

sudo yum --disablerepo=cloudera-cdh5,cloudera-manager install -y python-matplotlib libreoffice-calc python-imaging python-pip


Please note, that since the Cloudera VM is apparently based on an outdated operating system, it will only get worse over time, and you may encounter further issues with software management. It would be better, if all necessary course contents (like VM images) were appropriately updated by the teaching staff.

Badge +1

This problem is really tough but I managed to get it done in someway, although not all error can be fixed.

  • 1st step is fix error due to Centos 6 at the end of support at last year.

How to fix CentOS 6 error: YumRepo Error: All mirror URLs are not using ftp, http[s] or file - Computer How To (

Considering this situation, we should get newer Centos version to avoid future problem...