Problems with EOS Studio

[Cemil]

Dear all, dear @filip

I’m using the online version of EOS studio, but it’s giving errors. I have followed all the steps outlined in the EOS Programming 101 course regarding the building and deploying the contract (HelloWorld) but to no avail. Here are the errors:

1. In the helloworld.wasm file it says
   Error: readWasm failed:
   0000000: error: unable to read uint32_t: magic

2. helloworld.abi file is empty.

3. When I nevertheless try to go ahead the build the contract, it given the following error:
   eosio-cpp -abigen -I include -R resource -contract helloworld -o helloworld.wasm src/helloworld.cpp
   Internal Server Error, real status: 500
   Although it still says that the building of contract was successful.

4. And when I try to deploy it, the following error appears
   Deploy Failed
   Unexpected end of JSON input

I stick to the instructions given in the lecture and also chose EOSIO.CDT version 1.6.2.

In fact, I even tried this online version on two separate computers, one Windows and one Mac, but the same errors persist. Unfortunately, I cannot install the desktop version of EOS Studio because neither of those computers has 8 GB space to accomodate it. So, I’m bound to use the online version.

Could you please help me solve this issue?

[thecil]

Hello sir, check this topic where we already discussed that error with EOStudio, you can find here a lot of information that has been shared with me and other students about this subject!

Basic EOS Programming - Discussion

Carlos Z.

[tbaker]

I’m completely stuck in getting the web version of EOS Studio working. The videos beyond a certain point were directed completely towards the local version for the Mac/Linux people and so I’m missing something. I’ve tried Brave with the shields down and Chrome and am getting the same results.

When I try to create a new account in EOS Studio, I get the message below. It will tell me to import keys from testnet.eos.io, which I did as you can see in the next image. That’s all I could figure to do, but after I continued on to create the helloworld smart contract, it won’t compile. I get the following error: “Internal Server Error, real status: 500.” I also notice that the .abi and .wasm files are empty which does not match what the video is showing.

The problem it seems is that there’s no specific instruction for the Windows (web) people, so we’re left to doing the parts from the Mac/Linux video that seem to apply.

[thecil]

EOS Studio has not been working properly on their website, we encourage to install it locally in your PC, here you can check many tips to made easy for students the process to install or work with EOS Studio locally.

Basic EOS Programming - Discussion

@ivga80 here i am bro, yes, this is the exact order that i took before jumping into EOS 101 & 201. Deep Blockchain Fundamentals (now sharded into many, so just start with #2 on this list). Blockchain & Bitcoin 101. Javascript Programming for Blockchain Developers. C++ Programming for Blockchain Developers. EOS Programming 101. EOS Programming 201. From my perspective, EOS is a more advanced tech than ethereum, we just can’t see it’s full potential yet; You must understand the fundamenta…

If you have any more questions, please let us know so we can help you!

Carlos Z.

[tbaker]

I got this error when I went to run the VMware virtual machine with Ubuntu OS. It did warn me about my CPU earlier (Intel® Core™ i7 CPU 920 @ 2.67GHz, 2793 Mhz, 4 Core(s), 8 Logical Processor(s)), but it wasn’t in the list of the ones they didn’t support.

[thecil]

Hey @tbaker, hope you are great.

Apparently is a direct problem on your CPU model with the last version of VMware Workstation, I could suggest you to try https://www.virtualbox.org/.

Here you can read more about the problem you are facing:
https://communities.vmware.com/t5/VMware-Workstation-Pro/quot-VMX-Unrestricted-Guest-quot/td-p/446570

If you have any more questions, please let us know so we can help you!

Carlos Z.

[tbaker]

OK, I got Ubuntu installed (zero experience with this) and I could only find a couple of guides on how to install EOS Studio. They both say use terminal for the commands below:

git clone https://github.com/eosio/eos --recursive
./eosio_build.sh

./eosio_build.sh produced the following error:
You must be running 16.04.x or 18.04.x to install EOSIO

I’m on 20.04, but no versions were specified anywhere, so I have no idea how to deal with this.

[thecil]

You are following the wrong tutorial, that one is to install the official EOS node (nodeos).

First I could advice you to download and install ubuntu version 18.04, which is the most compatible version with software related to blockchain (including nodeos and EOS Studio).

Then you have to follow this guidelines from EOS Studio
https://medium.com/@ObsidianLabs/eos-studio-tutorial-1-set-up-the-environment-for-eosio-development-53fe3f9cb1f

After installing it properly, you can follow this tutorial to learn how to use the EOS Studio UI.
https://medium.com/@ObsidianLabs/eos-studio-tutorial-2-eosio-development-on-local-node-7576a74185e

If you have any more questions, please let us know so we can help you!

Carlos Z.

[tbaker]

I have the shared clipboard set to bidirectional, but it’s not working.

Also, in the instructions for Docker installation, they specify to type in the following:

sudo apt-get install \
apt-transport-https \
ca-certificates
curl
gnupg
lsb-release

That’s literally what it says. What do they mean? I tried typing this all at once or one line at a time starting with “sudo” or “sudo apt-get” but only the first part "install’ worked.

And I tried the following to get the vm window to allow a higher resolution, which worked in 20.04 but not 18.04 (it executed, but the resolution didn’t change):

sudo apt install build-essential dkms linux-headers-$(uname -r)

[tbaker]

I resolved the issue with those Docker commands above, but the next step presented another problem. I resolved that, and as I’ve come to expect more problems came up. Also, the problem with the bi-directional clipboard not working is making this process more difficult. I’m having to manually retype a lot of the commands and errors.

I’m reading from https://docs.docker.com/engine/install/ubuntu/#ins

I got no feedback on this command, just a new prompt:

echo \
  "deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
  $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

Got an error here:

sudo apt-get update
https://download.docker.com/linux/ubuntu/ \Release

The result was:

404: Not Found

If I visit https://download.docker.com/linux/ubuntu/, I can see there’s more to the path that was not provided.

Which is probably why the following didn’t work:

sudo apt-get install docker-ce docker-ce-cli containerd.io

The result:

E: Unable to locate package docker-ce-cli
E: Unable to locate package containerd.io
E: Couldn’t find any package by glob ‘containerd.io’
E: Couldn’t find any package by regex ‘containerd.io’

At this point I’m calling this an unmitigated disaster. I’m not sure if you’re aware, but this course was marketed to non-developers. I actually have some coding experience (never dealt with other operating systems before) which may be why I made it even this far, but it’s clear to me now that this back and forth between you and I could go on for WEEKS. The failure of someone over there to go through the process, identify problems, and create some instructions is creating a huge stumbling block for us uninitiated types. I’ve already lost about five days on these issues. Why is your company putting this arbitrary burden on its students? One person over there could handle this in less time than I’ve already spent. There HAS to be a better way. What can you suggest?

[thecil]

The instructions are quite simple, apparently you forgot to add docker repositories to your apt repository list.

This are just packages need it to install docker properly.

• Update the apt package index and install packages to allow apt to use a repository over HTTPS:

sudo apt-get update //update repositories.

// install packages
sudo apt-get install \
    apt-transport-https \
    ca-certificates \
    curl \
    gnupg \
    lsb-release

Then you add the repository with:

 curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg

After that try to install docker with:

 sudo apt-get update
 sudo apt-get install docker-ce docker-ce-cli containerd.io

If you have any more questions, please let us know so we can help you!

Carlos Z.

[tbaker]

After

sudo apt-get update

I get:

Err:5 https://download.docker.com/linux/ubuntu \ Release
404 Not Found [IP: 99.84.198.57 443]
E: The repository ‘https://download.docker.com/linux/ubuntu \ Release’ does not have a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.

I went back to the beginning and repeated the steps to make sure, but got the same results.

[thecil]

Ok, try now adding an stable version with:

 echo \
  "deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
  $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

Then try again with updating the repositories.

Carlos Z

[tbaker]

According to the video in the EOS course, we want to install 1.8.1. Here are the choices I have:

[thecil]

For cleos, keosd nodeos, try with v2.0.6, next will be CDT contracts, you should choose version 1.7.1 (i think thats the one filip suggest, verify please )

Carlos Z

[tbaker]

Also, he didn’t emphasize the importance of System Contracts as much, but it looks like I don’t have the option of installing 1.7.0 which is what the video recommends.

[thecil]

no worries, try with that one, it should not be that much of a difference

Carlos Z

[tbaker]

I’m at https://academy.ivanontech.com/products/eos-programming-201/categories/1681089/posts/5646899 and I ran into problems installing CentOS/Redhat. The first thing was the command sudo yum install ./eosio.cdt-1.6.1-1.centos-x86_64.rpm which returned the error sudo: yum: command not found I was able to get past this with sudo apt -y install yum-utils You may want to update your documentation with this step since I’m running Ubuntu 18.04 Debian Package which is one of the ones recommended.

But then when running the sudo yum install... command, I got a slew of errors that I figured maybe could be solved by doing something like sudo apt update but no luck there. Here’s the feedback I got:

Setting up Install Process
Examining ./eosio.cdt-1.6.1-1.centos-x86_64.rpm: eosio.cdt-1.6.1-1.x86_64
Marking ./eosio.cdt-1.6.1-1.centos-x86_64.rpm to be installed
Resolving Dependencies
–> Running transaction check
—> Package eosio.cdt.x86_64 0:1.6.1-1 will be installed
–> Processing Dependency: /usr/bin/env for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: ld-linux-x86-64.so.2()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: ld-linux-x86-64.so.2(GLIBC_2.3)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libc.so.6(GLIBC_2.14)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libc.so.6(GLIBC_2.15)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libc.so.6(GLIBC_2.2.5)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libc.so.6(GLIBC_2.3)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libc.so.6(GLIBC_2.3.4)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libc.so.6(GLIBC_2.4)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libc.so.6(GLIBC_2.6)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libdl.so.2(GLIBC_2.2.5)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libgcc_s.so.1(GCC_3.0)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libgcc_s.so.1(GCC_3.3)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libgcc_s.so.1(GCC_3.4)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libm.so.6(GLIBC_2.2.5)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libpthread.so.0(GLIBC_2.12)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libpthread.so.0(GLIBC_2.2.5)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(CXXABI_1.3)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(CXXABI_1.3.2)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(CXXABI_1.3.3)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(CXXABI_1.3.5)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.11)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.13)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.14)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.15)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.17)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.18)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.19)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4.9)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libz.so.1(ZLIB_1.2.0)(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: rtld(GNU_HASH) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libc.so.6()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libdl.so.2()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libgcc_s.so.1()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libm.so.6()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libpthread.so.0()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: librt.so.1()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libstdc++.so.6()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: libz.so.1()(64bit) for package: eosio.cdt-1.6.1-1.x86_64
–> Processing Dependency: /usr/bin/env for package: eosio.cdt-1.6.1-1.x86_64
–> Finished Dependency Resolution
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: rtld(GNU_HASH)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libgcc_s.so.1(GCC_3.4)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libc.so.6(GLIBC_2.4)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4.17)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(CXXABI_1.3)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libpthread.so.0()(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: ld-linux-x86-64.so.2(GLIBC_2.3)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4.9)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4.19)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4.18)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libgcc_s.so.1(GCC_3.0)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libc.so.6(GLIBC_2.3)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4.11)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6()(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libdl.so.2(GLIBC_2.2.5)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(CXXABI_1.3.2)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libc.so.6()(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(CXXABI_1.3.3)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libgcc_s.so.1()(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libgcc_s.so.1(GCC_3.3)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(CXXABI_1.3.5)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4.14)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libm.so.6(GLIBC_2.2.5)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libz.so.1()(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libc.so.6(GLIBC_2.6)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: librt.so.1()(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libdl.so.2()(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libpthread.so.0(GLIBC_2.12)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libpthread.so.0(GLIBC_2.2.5)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libz.so.1(ZLIB_1.2.0)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4.13)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: ld-linux-x86-64.so.2()(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libstdc++.so.6(GLIBCXX_3.4.15)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libc.so.6(GLIBC_2.14)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libc.so.6(GLIBC_2.2.5)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libc.so.6(GLIBC_2.15)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libc.so.6(GLIBC_2.3.4)(64bit)
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: /usr/bin/env
Error: Package: eosio.cdt-1.6.1-1.x86_64 (/eosio.cdt-1.6.1-1.centos-x86_64)
Requires: libm.so.6()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

I tried the rpm -VA… thing, but it made no difference. Then I tried the --skip-broken… and it told me:

Packages skipped because of dependency problems:
eosio.cdt-1.6.1-1.x86_64 from /eosio.cdt-1.6.1-1.centos-x86_64

Which probably explains the trouble I’m having now. I did move on to the next section where we start nodeos using the following and did not get any errors.

nodeos -e -p eosio --plugin eosio::producer_plugin --plugin eosio::chain_api_plugin --plugin eosio::http_plugin --plugin eosio::history_plugin --plugin eosio::history_api_plugin --access-control-allow-origin=’*’ --contracts-console --http-validate-host=false >> nodeos.log 2>&1 &

But the next step failed. At the top, you’ll see I verified that nodeos.log is in the folder I executed from, but then when I tried to execute tail -f nodeos.log I got the error below.

ted@ted-VirtualBox:~/contracts$ ls
eosio.cdt_1.6.1-1_amd64.deb eosio.cdt-1.6.1-1.centos-x86_64.rpm nodeos.log
ted@ted-VirtualBox:~/contracts$ tail -f nodeos.log

Command ‘nodeos’ not found, did you mean:

command ‘nodejs’ from deb nodejs
command ‘nodefs’ from deb noweb

Try: sudo apt install

[thecil]

Hey @tbaker, hope you are ok.

Why you are using centOS/Redhat? i could suggest you to try witn ubuntu, since its a more friendly distro from linux, and also you will find more support for it, centOS/redhat is a linux distro focused on server, so its a more complex distro (advance one).

Carlos Z

[tbaker]

OK, I misread that last part. I see that’s for Redhat users, not Ubuntu. I did do the Ubuntu part successfully, but then there’s was that line that failed afterwards:

Below, you’ll see I verified that nodeos.log is in the folder I executed from, but then when I tried to execute tail -f nodeos.log I got the error below.

ted@ted-VirtualBox:~/contracts$ ls
eosio.cdt_1.6.1-1_amd64.deb eosio.cdt-1.6.1-1.centos-x86_64.rpm nodeos.log
ted@ted-VirtualBox:~/contracts$ tail -f nodeos.log

Command ‘nodeos’ not found, did you mean:

command ‘nodejs’ from deb nodejs
command ‘nodefs’ from deb noweb

Try: sudo apt install