facebookarchive / CommunityCellularManager

Tool for deploying, managing and controlling your Community Cellular Networks
Other
87 stars 36 forks source link

Facebook Community Cellular Manager Client errors = Can't find ruby library file or shared library fpm #21

Closed PeterCielos closed 7 years ago

PeterCielos commented 7 years ago

Hello,

Hello,

Following the instructions per Facebook's CommunityCellularManager for Client, I am getting errors

Here is the git checkout version of Facebook's Community Cellular Manager I'm using:

ubuntu@ubuntu:~/CommunityCellularManager$ sudo git log -n1 commit 9e5415db9a3692f9b1691a4a0c95b7bd43c29fff Author: Steve Muir muir@fb.com Date: Mon Dec 19 11:31:50 2016 -0800

Only ignore top-level static dir, not deeper ones

Summary:
The .gitignore rule was intended to only exclude cloud/static, not
cloud/endagaweb/static. The typo meant the static images and such weren't
pushed to GH. A subsequent push will restore them.

Reviewed By: shaddi

Differential Revision: D4341788

fbshipit-source-id: 4741c24327c9e6d3af485e2b6084d532c835a064

Here is what I'm running:

lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty

I have the following installed:

ubuntu@ubuntu:~/CommunityCellularManager/cloud$ pip3 --version pip 9.0.1 from /usr/local/lib/python2.7/dist-packages (python 2.7)

ubuntu@ubuntu:~/CommunityCellularManager/cloud$ pip --version pip 9.0.1 from /usr/local/lib/python2.7/dist-packages (python 2.7)

ubuntu@ubuntu:~/CommunityCellularManager/cloud$ vagrant --version Vagrant 1.8.7

VBoxManage --version 4.3.36_Ubuntur105129

ansible --version ansible 2.3.0

Here is the error message I receive:

**ubuntu@ubuntu:~/CommunityCellularManager/client$ sudo fab dev package [localhost] local: vagrant ssh-config openbts | grep HostName [localhost] local: vagrant ssh-config openbts | grep Port [localhost] local: vagrant ssh-config openbts | grep IdentityFile ['/home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key'] [vagrant@127.0.0.1:2201] Executing task 'package' [vagrant@127.0.0.1:2201] run: mkdir -p ~/endaga-packages current contents of ~/endaga-packages: [vagrant@127.0.0.1:2201] run: ls ~/endaga-packages packaging /home/vagrant/openbts-python [vagrant@127.0.0.1:2201] run: mkdir -p ~/endaga-packages [vagrant@127.0.0.1:2201] run: gem which fpm [vagrant@127.0.0.1:2201] out: ERROR: Can't find ruby library file or shared library fpm [vagrant@127.0.0.1:2201] out:

Fatal error: run() received nonzero return code 1 while executing!

Requested: gem which fpm Executed: /bin/bash -l -c "gem which fpm"**

But I have "fpm" installed as you can see below:

ubuntu@ubuntu:~/CommunityCellularManager/client$ gem which fpm /var/lib/gems/1.9.1/gems/fpm-1.7.0/lib/fpm.rb

I haven't been able to get either Facebook's CCM Cloud, nor Client, to function yet.

Any assistance would be greatly appreciated!

9muir commented 7 years ago

Thanks for the bug report Peter, sorry you're having problems. Not sure why these steps aren't just working for you, they're generally pretty straightforward. I confirmed that there's nothing particularly unusual about the way Fabric runs the command gem which fpm, so I'm at a bit of a loss to diagnose your problem.

As a workaround you should be able to bring up a new client VM without actually creating any packages yourself; despite the language in the README, the binary releases available from our repo are pretty much up to date. Just apt-get install endaga-openbts

PeterCielos commented 7 years ago

9muir,

I think you got it correct: the "README" isn't up-to-date but none of the commands you've provided work either as the "README" stated to "sudo apt-get install endaga" from within the endaga_packages" directory versus what you've posted here.

But I followed the "README" and your above comments and tried to bring up the VM with the following errors:

ubuntu@ubuntu:~/CommunityCellularManager/cloud$ cd .. && cd client ubuntu@ubuntu:~/CommunityCellularManager/client$ sudo vagrant up --provision

Bringing machine 'openbts' up with 'virtualbox' provider... ==> openbts: Checking if box 'ubuntu/trusty32' is up to date... ==> openbts: Clearing any previously set forwarded ports... ==> openbts: Fixed port collision for 22 => 2222. Now on port 2200. ==> openbts: Clearing any previously set network interfaces... ==> openbts: Preparing network interfaces based on configuration... openbts: Adapter 1: nat openbts: Adapter 2: hostonly ==> openbts: Forwarding ports... openbts: 22 (guest) => 2200 (host) (adapter 1) ==> openbts: Running 'pre-boot' VM customizations... ==> openbts: Booting VM... ==> openbts: Waiting for machine to boot. This may take a few minutes... openbts: SSH address: 127.0.0.1:2200 openbts: SSH username: vagrant openbts: SSH auth method: private key openbts: Warning: Remote connection disconnect. Retrying... openbts: Warning: Remote connection disconnect. Retrying... openbts: Warning: Remote connection disconnect. Retrying... ==> openbts: Machine booted and ready! [openbts] GuestAdditions 4.3.36 running --- OK. ==> openbts: Checking for guest additions in VM... ==> openbts: Setting hostname... ==> openbts: Configuring and enabling network interfaces... ==> openbts: Mounting shared folders... openbts: /vagrant => /home/ubuntu/CommunityCellularManager/client openbts: /home/vagrant/common => /home/ubuntu/CommunityCellularManager/common openbts: /home/vagrant/client => /home/ubuntu/CommunityCellularManager/client openbts: /home/vagrant/sms_utilities => /home/ubuntu/CommunityCellularManager/sms_utilities openbts: /home/vagrant/osmocom-python => /home/ubuntu/CommunityCellularManager/osmocom-python openbts: /home/vagrant/openbts-python => /home/ubuntu/CommunityCellularManager/openbts-python ==> openbts: Running provisioner: ansible... openbts: Running ansible-playbook... PYTHONUNBUFFERED=1 ANSIBLE_FORCE_COLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -i '/home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key' -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook --connection=ssh --timeout=30 --extra-vars="ansible_ssh_user='vagrant'" --limit="openbts" --inventory-file=deploy/hosts -vvvv --timeout=30 deploy/openbts.dev.yml Using /home/ubuntu/CommunityCellularManager/client/ansible.cfg as config file statically included: /home/ubuntu/CommunityCellularManager/client/deploy/base.yml statically included: /home/ubuntu/CommunityCellularManager/client/deploy/openbts.yml Loading callback plugin default of type stdout, v2.0 from /usr/local/lib/python2.7/dist-packages/ansible/plugins/callback/init.pyc

PLAYBOOK: openbts.dev.yml ** 1 plays in deploy/openbts.dev.yml

PLAY [Set up development pre-reqs on a local machine] **

TASK [Gathering Facts] ***** Using module file /usr/local/lib/python2.7/dist-packages/ansible/modules/system/setup.py <192.168.40.100> ESTABLISH SSH CONNECTION FOR USER: vagrant <192.168.40.100> SSH: EXEC ssh -vvv -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -i /home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o Port=22 -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=30 -o ControlPath=/home/ubuntu/.ansible/cp/ansible-ssh-%h-%p-%r 192.168.40.100 '/bin/sh -c '"'"'( umask 77 && mkdir -p "echo ~/.ansible/tmp/ansible-tmp-1482450050.13-176371891980080" && echo ansible-tmp-1482450050.13-176371891980080="echo ~/.ansible/tmp/ansible-tmp-1482450050.13-176371891980080" ) && sleep 0'"'"'' fatal: [openbts]: UNREACHABLE! => { "changed": false, "msg": "Failed to connect to the host via ssh: OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for \r\ndebug1: auto-mux: Trying existing master\r\ndebug1: Control socket \"/home/ubuntu/.ansible/cp/ansible-ssh-192.168.40.100-22-vagrant\" does not exist\r\ndebug2: ssh_connect: needpriv 0\r\ndebug1: Connecting to 192.168.40.100 [192.168.40.100] port 22.\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug1: fd 3 clearing O_NONBLOCK\r\ndebug1: Connection established.\r\ndebug3: timeout: 29998 ms remain after connect\r\ndebug1: permanently_set_uid: 0/0\r\ndebug3: Incorrect RSA1 identifier\r\ndebug3: Could not load \"/home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key\" as a RSA1 public key\r\ndebug1: identity file /home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key type -1\r\ndebug1: identity file /home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key-cert type -1\r\ndebug1: Enabling compatibility mode for protocol 2.0\r\ndebug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8\r\ndebug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8\r\ndebug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 pat OpenSSH_6.6.1 compat 0x04000000\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug3: load_hostkeys: loading entries for host \"192.168.40.100\" from file \"/dev/null\"\r\ndebug3: load_hostkeys: loaded 0 keys\r\ndebug1: SSH2_MSG_KEXINIT sent\r\ndebug1: SSH2_MSG_KEXINIT received\r\ndebug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1\r\ndebug2: kex_parse_kexinit: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa,ssh-dss\r\ndebug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se\r\ndebug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se\r\ndebug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96\r\ndebug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96\r\ndebug2: kex_parse_kexinit: none,zlib@openssh.com,zlib\r\ndebug2: kex_parse_kexinit: none,zlib@openssh.com,zlib\r\ndebug2: kex_parse_kexinit: \r\ndebug2: kex_parse_kexinit: \r\ndebug2: kex_parse_kexinit: first_kex_follows 0 \r\ndebug2: kex_parse_kexinit: reserved 0 \r\ndebug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1\r\ndebug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519\r\ndebug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se\r\ndebug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se\r\ndebug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96\r\ndebug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96\r\ndebug2: kex_parse_kexinit: none,zlib@openssh.com\r\ndebug2: kex_parse_kexinit: none,zlib@openssh.com\r\ndebug2: kex_parse_kexinit: \r\ndebug2: kex_parse_kexinit: \r\ndebug2: kex_parse_kexinit: first_kex_follows 0 \r\ndebug2: kex_parse_kexinit: reserved 0 \r\ndebug2: mac_setup: setup hmac-md5-etm@openssh.com\r\ndebug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none\r\ndebug2: mac_setup: setup hmac-md5-etm@openssh.com\r\ndebug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none\r\ndebug1: sending SSH2_MSG_KEX_ECDH_INIT\r\ndebug1: expecting SSH2_MSG_KEX_ECDH_REPLY\r\ndebug1: Server host key: ECDSA 21:93:67:61:d1:05:95:a8:67:e8:52:a3:6f:fb:a0:20\r\ndebug3: load_hostkeys: loading entries for host \"192.168.40.100\" from file \"/dev/null\"\r\ndebug3: load_hostkeys: loaded 0 keys\r\nWarning: Permanently added '192.168.40.100' (ECDSA) to the list of known hosts.\r\ndebug1: ssh_ecdsa_verify: signature correct\r\ndebug2: kex_derive_keys\r\ndebug2: set_newkeys: mode 1\r\ndebug1: SSH2_MSG_NEWKEYS sent\r\ndebug1: expecting SSH2_MSG_NEWKEYS\r\ndebug2: set_newkeys: mode 0\r\ndebug1: SSH2_MSG_NEWKEYS received\r\ndebug1: SSH2_MSG_SERVICE_REQUEST sent\r\ndebug2: service_accept: ssh-userauth\r\ndebug1: SSH2_MSG_SERVICE_ACCEPT received\r\ndebug2: key: /home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key ((nil)), explicit\r\ndebug1: Authentications that can continue: publickey,password\r\ndebug3: start over, passed a different list publickey,password\r\ndebug3: preferred gssapi-with-mic,gssapi-keyex,hostbased,publickey\r\ndebug3: authmethod_lookup publickey\r\ndebug3: remaining preferred: ,gssapi-keyex,hostbased,publickey\r\ndebug3: authmethod_is_enabled publickey\r\ndebug1: Next authentication method: publickey\r\ndebug1: Trying private key: /home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key\r\ndebug1: key_parse_private2: missing begin marker\r\ndebug1: read PEM private key done: type RSA\r\ndebug3: sign_and_send_pubkey: RSA 49:c8:ea:62:45:e9:51:5c:62:ab:56:de:4e:86:0e:7f\r\ndebug2: we sent a publickey packet, wait for reply\r\ndebug1: Authentication succeeded (publickey).\r\nAuthenticated to 192.168.40.100 ([192.168.40.100]:22).\r\ndebug1: setting up multiplex master socket\r\ndebug3: muxserver_listen: temporary control path /home/ubuntu/.ansible/cp/ansible-ssh-192.168.40.100-22-vagrant.PBcit4DznCbq8mgf\r\ndebug2: fd 4 setting O_NONBLOCK\r\ndebug3: fd 4 is O_NONBLOCK\r\ndebug3: fd 4 is O_NONBLOCK\r\ndebug1: channel 0: new [/home/ubuntu/.ansible/cp/ansible-ssh-192.168.40.100-22-vagrant]\r\ndebug3: muxserver_listen: mux listener channel 0 fd 4\r\ndebug2: fd 3 setting TCP_NODELAY\r\ndebug3: packet_set_tos: set IP_TOS 0x08\r\ndebug1: control_persist_detach: backgrounding master process\r\ndebug2: control_persist_detach: background process is 27407\r\nControl socket connect(/home/ubuntu/.ansible/cp/ansible-ssh-192.168.40.100-22-vagrant): Connection refused\r\nFailed to connect to new control master\r\n", "unreachable": true } to retry, use: --limit @/home/ubuntu/CommunityCellularManager/client/deploy/openbts.dev.retry

PLAY RECAP ***** openbts : ok=0 changed=0 unreachable=1 failed=0

Ansible failed to complete successfully. Any error output should be visible above. Please fix these errors and try again. ubuntu@ubuntu:~/CommunityCellularManager/client$ sudo vagrant ssh-config openbts Host openbts HostName 127.0.0.1 User vagrant Port 2200 UserKnownHostsFile /dev/null StrictHostKeyChecking no PasswordAuthentication no IdentityFile /home/ubuntu/CommunityCellularManager/client/.vagrant/machines/openbts/virtualbox/private_key IdentitiesOnly yes LogLevel FATAL

ubuntu@ubuntu:~/CommunityCellularManager/client$

ubuntu@ubuntu:~/CommunityCellularManager/client$ sudo vagrant ssh-config osmocom Host osmocom HostName 127.0.0.1 User vagrant Port 2202 UserKnownHostsFile /dev/null StrictHostKeyChecking no PasswordAuthentication no IdentityFile /home/ubuntu/CommunityCellularManager/client/.vagrant/machines/osmocom/virtualbox/private_key IdentitiesOnly yes LogLevel FATAL

ubuntu@ubuntu:~/CommunityCellularManager/client$

ubuntu@ubuntu:~/CommunityCellularManager/client$ sudo vagrant ssh openbts Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-105-generic i686)

8 packages can be updated. 8 updates are security updates.

New release '16.04.1 LTS' available. Run 'do-release-upgrade' to upgrade to it.

Last login: Wed Dec 21 04:00:11 2016 from 10.0.2.2 vagrant@endaga-client-openbts:~$ ls client common endaga-packages openbts-python osmocom-python sms_utilities vagrant@endaga-client-openbts:~$ cd endaga-packages vagrant@endaga-client-openbts:~/endaga-packages$ apt-get install endaga-openbts E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root? vagrant@endaga-client-openbts:~/endaga-packages$ sudo apt-get install endaga-openbts Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package endaga-openbts vagrant@endaga-client-openbts:~/endaga-packages$

ubuntu@ubuntu:~/CommunityCellularManager/client$ sudo vagrant ssh openbts Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-105-generic i686)

8 packages can be updated. 8 updates are security updates.

New release '16.04.1 LTS' available. Run 'do-release-upgrade' to upgrade to it.

Last login: Wed Dec 21 04:00:11 2016 from 10.0.2.2 vagrant@endaga-client-openbts:~$ ls client common endaga-packages openbts-python osmocom-python sms_utilities vagrant@endaga-client-openbts:~$ cd endaga-packages vagrant@endaga-client-openbts:~/endaga-packages$ apt-get install endaga-openbts E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root? vagrant@endaga-client-openbts:~/endaga-packages$ sudo apt-get install endaga-openbts Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package endaga-openbts vagrant@endaga-client-openbts:~/endaga-packages$ sudo apt-get install endaga Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package endaga vagrant@endaga-client-openbts:~/endaga-packages$ sudo apt-get update

vagrant@endaga-client-openbts:~/endaga-packages$ cd .. && sudo apt-get update Ign http://archive.ubuntu.com trusty InRelease Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB] Get:2 http://archive.ubuntu.com trusty-updates InRelease [65.9 kB] Get:3 http://archive.ubuntu.com trusty-backports InRelease [65.9 kB]
Get:4 http://security.ubuntu.com trusty-security/main Sources [123 kB] Hit http://archive.ubuntu.com trusty Release.gpg
Get:5 http://security.ubuntu.com trusty-security/universe Sources [46.5 kB] Get:6 http://archive.ubuntu.com trusty-updates/main Sources [388 kB]
Get:7 http://security.ubuntu.com trusty-security/main i386 Packages [528 kB] Get:8 http://archive.ubuntu.com trusty-updates/restricted Sources [5,888 B]
Get:9 http://security.ubuntu.com trusty-security/universe i386 Packages [147 kB] Get:10 http://archive.ubuntu.com trusty-updates/universe Sources [170 kB] Get:11 http://security.ubuntu.com trusty-security/main Translation-en [314 kB] Get:12 http://archive.ubuntu.com trusty-updates/multiverse Sources [7,523 B]
Get:13 http://security.ubuntu.com trusty-security/universe Translation-en [86.6 kB] Get:14 http://archive.ubuntu.com trusty-updates/main i386 Packages [893 kB] Get:15 http://archive.ubuntu.com trusty-updates/restricted i386 Packages [16.2 kB] Get:16 http://archive.ubuntu.com trusty-updates/universe i386 Packages [392 kB] Get:17 http://archive.ubuntu.com trusty-updates/multiverse i386 Packages [14.5 kB] Get:18 http://archive.ubuntu.com trusty-updates/main Translation-en [457 kB] Get:19 http://archive.ubuntu.com trusty-updates/multiverse Translation-en [7,340 B] Get:20 http://archive.ubuntu.com trusty-updates/restricted Translation-en [3,842 B] Get:21 http://archive.ubuntu.com trusty-updates/universe Translation-en [207 kB] Get:22 http://archive.ubuntu.com trusty-backports/main Sources [9,636 B] Get:23 http://archive.ubuntu.com trusty-backports/restricted Sources [28 B] Get:24 http://archive.ubuntu.com trusty-backports/universe Sources [35.3 kB] Get:25 http://archive.ubuntu.com trusty-backports/multiverse Sources [1,898 B] Get:26 http://archive.ubuntu.com trusty-backports/main i386 Packages [13.3 kB] Get:27 http://archive.ubuntu.com trusty-backports/restricted i386 Packages [28 B] Get:28 http://archive.ubuntu.com trusty-backports/universe i386 Packages [43.2 kB] Get:29 http://archive.ubuntu.com trusty-backports/multiverse i386 Packages [1,552 B] Get:30 http://archive.ubuntu.com trusty-backports/main Translation-en [7,493 B] Get:31 http://archive.ubuntu.com trusty-backports/multiverse Translation-en [1,215 B] Get:32 http://archive.ubuntu.com trusty-backports/restricted Translation-en [28 B] Get:33 http://archive.ubuntu.com trusty-backports/universe Translation-en [36.8 kB] Hit http://archive.ubuntu.com trusty Release
Hit http://archive.ubuntu.com trusty/main Sources
Hit http://archive.ubuntu.com trusty/restricted Sources
Hit http://archive.ubuntu.com trusty/universe Sources
Hit http://archive.ubuntu.com trusty/multiverse Sources Hit http://archive.ubuntu.com trusty/main i386 Packages Hit http://archive.ubuntu.com trusty/restricted i386 Packages Hit http://archive.ubuntu.com trusty/universe i386 Packages Hit http://archive.ubuntu.com trusty/multiverse i386 Packages Hit http://archive.ubuntu.com trusty/main Translation-en Hit http://archive.ubuntu.com trusty/multiverse Translation-en Hit http://archive.ubuntu.com trusty/restricted Translation-en Hit http://archive.ubuntu.com trusty/universe Translation-en Ign http://archive.ubuntu.com trusty/main Translation-en_US Ign http://archive.ubuntu.com trusty/multiverse Translation-en_US Ign http://archive.ubuntu.com trusty/restricted Translation-en_US Ign http://archive.ubuntu.com trusty/universe Translation-en_US Fetched 4,156 kB in 52s (79.1 kB/s)
Reading package lists... Error! E: Unable to synchronize mmap - msync (5: Input/output error) E: The package lists or status file could not be parsed or opened. vagrant@endaga-client-openbts:~$ ls /var/lib/dpkg/status-old /var/lib/dpkg/status-old vagrant@endaga-client-openbts:~$ ls /var/lib/dpkg/status /var/lib/dpkg/status vagrant@endaga-client-openbts:~$ sudo mv /var/lib/dpkg/status /var/lib/dpkg/status.bad vagrant@endaga-client-openbts:~$ sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status vagrant@endaga-client-openbts:~$ sudo apt-get update

Get:1 http://security.ubuntu.com trusty-security InRelease [65.9 kB] Ign http://archive.ubuntu.com trusty InRelease
Get:2 http://security.ubuntu.com trusty-security/main Sources [123 kB] Get:3 http://archive.ubuntu.com trusty-updates InRelease [65.9 kB] Get:4 http://security.ubuntu.com trusty-security/universe Sources [46.5 kB]
Get:5 http://security.ubuntu.com trusty-security/main i386 Packages [528 kB]
Get:6 http://security.ubuntu.com trusty-security/universe i386 Packages [147 kB] Hit http://security.ubuntu.com trusty-security/main Translation-en
Get:7 http://archive.ubuntu.com trusty-backports InRelease [65.9 kB]
Hit http://security.ubuntu.com trusty-security/universe Translation-en Hit http://archive.ubuntu.com trusty Release.gpg
Get:8 http://archive.ubuntu.com trusty-updates/main Sources [388 kB]
Get:9 http://archive.ubuntu.com trusty-updates/restricted Sources [5,888 B]
Get:10 http://archive.ubuntu.com trusty-updates/universe Sources [170 kB] Get:11 http://archive.ubuntu.com trusty-updates/multiverse Sources [7,523 B] Get:12 http://archive.ubuntu.com trusty-updates/main i386 Packages [893 kB] Get:13 http://archive.ubuntu.com trusty-updates/restricted i386 Packages [16.2 kB] Get:14 http://archive.ubuntu.com trusty-updates/universe i386 Packages [392 kB] Get:15 http://archive.ubuntu.com trusty-updates/multiverse i386 Packages [14.5 kB] Hit http://archive.ubuntu.com trusty-updates/main Translation-en Hit http://archive.ubuntu.com trusty-updates/multiverse Translation-en Hit http://archive.ubuntu.com trusty-updates/restricted Translation-en
Hit http://archive.ubuntu.com trusty-updates/universe Translation-en
Get:16 http://archive.ubuntu.com trusty-backports/main Sources [9,636 B]
Get:17 http://archive.ubuntu.com trusty-backports/restricted Sources [28 B] Get:18 http://archive.ubuntu.com trusty-backports/universe Sources [35.3 kB] Get:19 http://archive.ubuntu.com trusty-backports/multiverse Sources [1,898 B] Get:20 http://archive.ubuntu.com trusty-backports/main i386 Packages [13.3 kB] Get:21 http://archive.ubuntu.com trusty-backports/restricted i386 Packages [28 B] Get:22 http://archive.ubuntu.com trusty-backports/universe i386 Packages [43.2 kB] Get:23 http://archive.ubuntu.com trusty-backports/multiverse i386 Packages [1,552 B] Hit http://archive.ubuntu.com trusty-backports/main Translation-en Hit http://archive.ubuntu.com trusty-backports/multiverse Translation-en Hit http://archive.ubuntu.com trusty-backports/restricted Translation-en Hit http://archive.ubuntu.com trusty-backports/universe Translation-en Hit http://archive.ubuntu.com trusty Release
Hit http://archive.ubuntu.com trusty/main Sources Hit http://archive.ubuntu.com trusty/restricted Sources Hit http://archive.ubuntu.com trusty/universe Sources Hit http://archive.ubuntu.com trusty/multiverse Sources Hit http://archive.ubuntu.com trusty/main i386 Packages Hit http://archive.ubuntu.com trusty/restricted i386 Packages Hit http://archive.ubuntu.com trusty/universe i386 Packages Hit http://archive.ubuntu.com trusty/multiverse i386 Packages Hit http://archive.ubuntu.com trusty/main Translation-en Hit http://archive.ubuntu.com trusty/multiverse Translation-en Hit http://archive.ubuntu.com trusty/restricted Translation-en Hit http://archive.ubuntu.com trusty/universe Translation-en Ign http://archive.ubuntu.com trusty/main Translation-en_US
Ign http://archive.ubuntu.com trusty/multiverse Translation-en_US
Ign http://archive.ubuntu.com trusty/restricted Translation-en_US
Ign http://archive.ubuntu.com trusty/universe Translation-en_US
Fetched 3,034 kB in 8s (364 kB/s)
Reading package lists... 99% Fetched 3,034 kB in 8s (364 kB/s)
Reading package lists... Done vagrant@endaga-client-openbts:~$ vagrant@endaga-client-openbts:~$ sudo apt-get install endaga Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package endaga vagrant@endaga-client-openbts:~$ vagrant@endaga-client-openbts:~$ sudo apt-get install endaga-openbts Reading package lists... Done Building dependency tree
Reading state information... Done E: Unable to locate package endaga-openbts vagrant@endaga-client-openbts:~$

9muir, if you were to just download Ubuntu 14.04.05 iso, boot from it, install Vagrant, VirtualBox 4.3.12, which will upgrade itself to 4.3.36 - 40, and follow the "README" located here https://github.com/facebookincubator/CommunityCellularManager, anyone will incur the above errors.

9muir commented 7 years ago

I'll create a VM from scratch as you suggested and report back. We haven't heard from anyone else with similar problems, but I want to resolve this.

PeterCielos commented 7 years ago

9muir,

Thank you very sincerely!

9muir commented 7 years ago

Hey Peter, I've recreated the problem you described in getting fpm installed by gem, by creating a VM from the Ubuntu ISO (as you described) and jumping through a few hoops to get it associated with Vagrant. I'm sure I could get it working if necessary, but before I do so I'd recommend that you just try destroying that VM and letting Vagrant create a new one by pulling down its own base box. That's the normal process and we haven't had any reports of problems from people who followed that path.

If, for some reason, you need to be able to install on an existing VM then we can probably get that to work, but it will take more time.

PeterCielos commented 7 years ago

9muir,

Thank you for trying and as you can see just downloading Ubuntu 14.04. burning it to a USB stick, and adding VirtualBox and Vagrant will occur the same issues you and I have so far.

And YES I did do "Vagrant Destroy" and all of that: deleted the VMs, had VirtualBox redownload them and Vagrant did its thing, but all the problems seems to stem around the actual Facebook Community Cellular files.

I've yet to get past any of the above and have even tried installing Endaga Deb files on Ubuntu 12.04 (32bit) which just gives more problems.

So for the moment this is unresolved for me/and/or anyone else doing as both you and I have done.

Which OS. (Ubuntu 13.10?) can the Endaga Deb files be installed on without having to do any virtualization ?

9muir commented 7 years ago

If you don't want to use Vagrant/VB you should be able to install successfully on Ubuntu 14.04. I'm doing exactly that right now for the cloud certifier VM on AWS, I think I've traced the problem down to a missing dependency in the system packages on make. That should be a relatively easy fix, but let me confirm.

9muir commented 7 years ago

Commit 95be778 resolves the problems installing FPM.

9muir commented 7 years ago

Closing since the specific problem has been resolved.