omegaup / deploy Goto Github PK

Deployment for omegaUp

Shell 28.49% Ruby 5.28% Makefile 5.98% Python 60.24%

deploy's Introduction

Ver el contenido en Español: Español
View the content in English: English
Veja o conteúdo em Português: Português
Vedi il contenuto in Italiano: Italiano

Español

omegaUp es una plataforma educativa gratuita que ayuda a mejorar las habilidades en programación, usada por decenas de miles de estudiantes y docentes en Latinoamérica.

Directorios

Directorios que se utilizan activamente en el desarrollo.

Directorio	Descripción
frontend/server/src/Controllers	Lógica de negocio que implementa la API de omegaUp.
frontend/server/libs	Bibliotecas y utilerías.
frontend/server/src/DAO	Los Data Access Objects [DAO] y Value Objects [VO]. Clases utilizadas para representar los esquemas de la base de datos y facilitar su consumo por los controladores.
frontend/templates	Plantillas utilizadas para generar el HTML que se despliega a los usuarios. También aquí están los archivos de internacionalización para inglés, español y portugués.
frontend/www	Los contenidos completos de la página de internet.

El resto del código está en otros repositorios

Repositorio	Descripción
quark	Incluye el código del grader para la calificación de problemas y ejecutar los códigos bajo minijail, así como el servicio utilizado en los servidores de la nube para servir la cola de envíos.
karel.js	La versión oficial de Karel utilizada por la Olimpiada Mexicana de Informática.
omegajail	Un mecanismo de ejecución segura que basado en contenedores de Linux y seccomp-bpf. Utiliza minijail, escrito por el proyecto Chromium.
libinteractive	Una librería para hacer problemas interactivos fácilmente.

Navegadores Soportados

Los navegadores oficialmente soportados son aquellos que soportan ECMAScript 2015 (ES6), e incluyen los siguientes:

Navegador	Versión
Chrome	51
Firefox	68
Edge	12
Safari	12

Esto también incluye todos los navegadores basados en Blink / WebKit cuyas versiones sean compatibles con las de Chrome / Safari.

Licencia

BSD

English

omegaUp is a free educational platform that helps improve programming skills, used by tens of thousands of students and teachers in Latin America.

Directories

Directories that are actively used in development.

Directory	Description
frontend/server/src/Controllers	Business logic that implements the omegaUp API.
frontend/server/libs	Libraries and props.
frontend/server/src/DAO	Data Access Objects [DAO] and Value Objects [VO]. Classes used to represent database schemas and facilitate their consumption by controllers.
frontend/templates	Templates used to generate the HTML that is displayed to users. Also here are the internationalization files for English, Spanish and Portuguese.
frontend/www	The complete contents of the website.

The rest of the code is in other repositories

Repository	Description
quark	It includes the grader code for rating issues and running the codes under minijail, as well as the service used on the cloud servers to serve the submission queue.
karel.js	The official version of Karel used by the Mexican Informatics Olympiad.
omegajail	A secure execution mechanism based on Linux containers and seccomp-bpf. It uses minijail, written by the Chromium project.
libinteractive	A library to easily do interactive problems.

Supported Browsers

Officially supported browsers are those that support ECMAScript 2015 (ES6), and include the following:

Browser	Version
Chrome	51
Firefox	68
Edge	12
Safari	12

This also includes all Blink/WebKit-based browsers whose versions are compatible with Chrome/Safari.

License

BSD

Português

omegaUp é uma plataforma educacional gratuita que ajuda a melhorar as habilidades de programação, usada por dezenas de milhares de estudantes e professores na América Latina.

Diretórios

Diretórios que são usados ativamente no desenvolvimento.

Diretório	Descrição
frontend/server/src/Controllers	Lógica de negócios que implementa a API omegaUp.
frontend/server/libs	Bibliotecas e adereços.
frontend/server/src/DAO	Objetos de acesso a dados [DAO] e objetos de valor [VO]. Classes utilizadas para representar esquemas de banco de dados e facilitar seu consumo pelos controladores.
frontend/templates	Modelos usados para gerar o HTML que é exibido aos usuários. Aqui também estão os arquivos de internacionalização para inglês, espanhol e português.
frontend/www	O conteúdo completo do site.

O resto do código está em outros repositórios

Repositório	Descrição
quark	Inclui o código do avaliador para avaliar problemas e executar os códigos no minijail, bem como o serviço usado nos servidores em nuvem para atender a fila de envio.
karel.js	A versão oficial do Karel usada pela Olimpíada Mexicana de Informática.
omegajail	Um mecanismo de execução seguro baseado em contêineres Linux e seccomp-bpf. Ele usa minijail, escrito pelo projeto Chromium.
libinterativo	Uma biblioteca para resolver facilmente problemas interativos.

Navegadores Suportados

Os navegadores oficialmente suportados são aqueles que suportam ECMAScript 2015 (ES6) e incluem o seguinte:

Navegador	Versão
Chrome	51
Firefox	68
Edge	12
Safari	12

Isso também inclui todos os navegadores baseados em Blink/WebKit cujas versões são compatíveis com Chrome/Safari.

Licença

BSD

Italiano

omegaUp è una piattaforma educativa gratuita che aiuta a migliorare le abilità nella programmazione, usata da decine di migliaia di studenti ed insegnanti in America Latina.

Cartelle

Le cartelle che sono attivamente utilizzate nello sviluppo.

Cartella	Descrizione
frontend/server/src/Controllers	Logica di business che implementa le API di omegaUp.
frontend/server/libs	Librerie e utility.
frontend/server/src/DAO	I Data Access Objects [DAO] e Value Objects [VO]. Classi utilizzate per rappresentare gli schemi del database e facilitare il loro utilizzo da parte dei controller.
frontend/templates	Modelli utilizzati per generare l'HTML visualizzato agli utenti. Sono anche presenti i file di internazionalizzazione per inglese, spagnolo e portoghese.
frontend/www	L'intero contenuto del sito web.

Il resto del codice si trova in altre repository.

Repository	Descrizione
quark	Include il codice del grader per la valutazione dei problemi e l'esecuzione dei codici sotto minijail, così come il servizio utilizzato nei server cloud per gestire la coda delle sottomissioni.
karel.js	La versione ufficiale di Karel utilizzata dall'Olimpiade Messicana di Informatica.
omegajail	Un meccanismo di esecuzione sicura basato su container Linux e seccomp-bpf. Utilizza minijail, sviluppato dal progetto Chromium.
libinteractive	Una libreria per creare facilmente problemi interattivi.

Browser supportati

I browser ufficialmente supportati sono quelli che supportano ECMAScript 2015 (ES6), e comprendono i seguenti:

Browser	Versione
Chrome	51
Firefox	68
Edge	12
Safari	12

Questo include anche tutti i browser basati su Blink/WebKit le cui versioni sono compatibili con quelle di Chrome/Safari.

Licenza

BSD

deploy's People

Contributors

Stargazers

Watchers

Forkers

rcxr edhzsz zatarain samdsmx atharvakhare alirizwi pabloaguilar ruizyugen

deploy's Issues

Permission denied en docker container cuando el UID no es 1000

Al seguir las instrucciones para instalar el entorno de desarrollo con docker container, obtengo muchos mensajes de error al ejecutar:

docker-compose up --no-build

Ejemplo:

...
frontend_1     | 2020-10-03 23:10:21,134 INFO spawned: 'developer-environment' with pid 17402
frontend_1     | mkdir: cannot create directory ‘/opt/omegaup/frontend/www/phpminiadmin’: Permission denied
frontend_1     | 2020-10-03 23:10:21,139 INFO success: developer-environment entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
frontend_1     | 2020-10-03 23:10:21,139 INFO exited: developer-environment (exit status 1; not expected)
frontend_1     | 2020-10-03 23:10:21,141 INFO spawned: 'developer-environment' with pid 17404
frontend_1     | mkdir: cannot create directory ‘/opt/omegaup/frontend/www/phpminiadmin’: Permission denied
frontend_1     | 2020-10-03 23:10:21,147 INFO success: developer-environment entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
frontend_1     | 2020-10-03 23:10:21,147 INFO exited: developer-environment (exit status 1; not expected)
frontend_1     | 2020-10-03 23:10:21,148 INFO spawned: 'developer-environment' with pid 17410
frontend_1     | mkdir: cannot create directory ‘/opt/omegaup/frontend/www/phpminiadmin’: Permission denied
frontend_1     | 2020-10-03 23:10:21,154 INFO success: developer-environment entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
frontend_1     | 2020-10-03 23:10:21,154 INFO exited: developer-environment (exit status 1; not expected)
frontend_1     | 2020-10-03 23:10:21,155 INFO spawned: 'developer-environment' with pid 17412
frontend_1     | mkdir: cannot create directory ‘/opt/omegaup/frontend/www/phpminiadmin’: Permission denied
...

Al tratar de ver la instancia local de OmegaUp (http://localhost:8001) obtengo:

No config file.
You are missing the config file. These are the default values:

        <?php
require_once dirname(__DIR__) . '/server/try_define.php';

# ###################################
# GLOBAL CONFIG
# ###################################
...

No es posible copiar el folder opt/omegaup de Vagrant a un folder local

Intenté clonar un fork del repositorio omegaup al host y así activar la sincronización de vagrant para tenerlo funcionando en la máquina virtual, pero hay una serie de configuraciones faltantes que desconozco y no están descritas en la Wiki.
De igual manera, intento copiar la carpeta /opt/omegaup desde la máquina virtual de vagrant hacia mi host local usando vagrant scp, pero tampoco me es permitido.

Trato de conseguir tener el repositorio en el host local para así conseguir usar algún editor de código en el desarrollo.

Vagrant Up - problems with installation

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 80 (guest) => 8080 (host) (adapter 1)
    default: 21680 (guest) => 21680 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default: 
    default: Guest Additions Version: 5.0.40
    default: VirtualBox Version: 5.2
==> default: Mounting shared folders...
    default: /vagrant => /home/maxi/Documentos/Programming/deploy
    default: /opt/omegaup => /home/maxi/Documentos/Programming/deploy/omegaup
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20180219-8242-sdtd1t.sh
    default: dpkg-query: no packages found matching puppet-common
    default: dpkg-query: no packages found matching ruby
    default: WARNING: 
    default: apt
    default:  
    default: does not have a stable CLI interface. 
    default: Use with caution in scripts.
    default: Reading package lists...
    default: E
    default: : 
    default: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
    default: E
    default: : 
    default: Unable to lock directory /var/lib/apt/lists/
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

This was the output, I received when using vagrant up the last time.
I still haven't learned a lot about Vagrant to interpret this output, but I decided to share this here since it can be useful to future contributors.
Sorry for not providing reproduction steps, I don't have continuous access to this computer, but eventually I can get more information about it if you ask for it.

Issue with installation

Hello @lhchavez I tried deploying Omegaup locally and vagrant Up is done with some errors, I have also ran vagrant up --provision and vagrant provision with errors. Here is a link with the error details https://pastebin.com/K03AFPG1. When i navigate to http://localhost:8080/ i do see the omegaup site though.

Lint SQL

Descripcion

Al hacer un commit y correr las pruebas de lint, si el archivo SQL tiene letras con acento me las reemplaza por otro tipo de encoding.

Screenshot

Warning: Authentication failure. Retrying.

Estoy tratando de installar el entorno de desarrollo, pero estoy teniendo algunos problemas. Uno de ellos, con una de mis computadoras, es que utilizar vagrant up comienza a procesar algo, que al llegar al 100% termina por congelar mi computadora. Pienso que puede deberse a un problema de hardware, en cuyo caso, sería genial especificar requerimientos mínimos en la Wiki para futuros contribuidores.

Por otro lado, decidí intentar en una computadora con hardware más capaz, y en este caso, a pesar de que no se congela, me surgen los siguientes mensajes:

==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 80 (guest) => 8080 (host) (adapter 1)
    default: 21680 (guest) => 21680 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: ubuntu
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...

Luego:

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

El mensaje de error es bastante claro, voy a seguir investigando, pero obviamente, sería genial tener todo esto documentado en la guía, o en alguna sección de troubleshooting.

Saludos.

EDIT:

Acabo de leer esta respuesta en stackoverflow sobre el tema. Luego de seguir los pasos en la primer respuesta (activar el GUI), obtuve que la máquina virtual se traba en la siguiente pantalla:

se paraliza mi maquina en la ejecucion del comando "vagrant up"

tenia problemas en Virtual box asi que lo desintale y lo volvi a instalar y ejecute el comando "vagrant up" y despues de un tiempo mi maquina se paraliza , no funciona la pantalla porque se queda congelada y no se que mas hacer ya que siempre pasa ello despues de ejecutar el comando "vagrant up".

OFSHACKATHON: Grader does not work out-of-the-box after vagrant up

in /opt/omegaup/frontend/server/libs/Grader.php:66
Stack trace:
#0 /opt/omegaup/frontend/server/libs/Grader.php(119): Grader->executeCurl()
#1 /opt/omegaup/frontend/server/controllers/GraderController.php(127): Grader->status()
#2 /opt/omegaup/frontend/server/libs/Request.php(72): GraderController::apiStatus()
#3 /opt/omegaup/frontend/www/api/ApiCaller.php(31): Request->execute()
#4 /opt/omegaup/frontend/www/api/ApiCaller.php(52): ApiCaller::call()
#5 /opt/omegaup/frontend/www/api/ApiEntryPoint.php(5): ApiCaller::httpEntryPoint()
#6 {main} (/opt/omegaup/frontend/www/api/ApiCaller.php:36)```

Problems while setting up the development server

The following include some of the bigger warning and error messages while running the command vagrant up in the directory containing the VagrantFile.

Apart from these there are some minor warning floating throughout the log files

default: dpkg-query: no packages found matching puppet-common
default: dpkg-query: no packages found matching ruby
default: WARNING:
default: apt
default:
default: does not have a stable CLI interface.
default: Use with caution in scripts.

default: WARNING:
default: apt
default:
default: does not have a stable CLI interface.
default: Use with caution in scripts.

default: dpkg-preconfigure: unable to re-open stdin: No such file or directory

default: invalid options: -SHN
default: (invalid options are ignored)

default: Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults

default: Error: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 72ECF46A56B4AD39C907BBB71646B01B86E50310' returned 2: Executing: /tmp/tmp.oVL0AVtLjc/gpg.1.sh --keyserver
default: keyserver.ubuntu.com
default: --recv-keys
default: 72ECF46A56B4AD39C907BBB71646B01B86E50310
default: gpg: requesting key 86E50310 from hkp server keyserver.ubuntu.com
default: gpg: keyserver timed out
default: gpg: keyserver receive failed: keyserver error
default: Error: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[yarn]/Apt::Key[Add key: 72ECF46A56B4AD39C907BBB71646B01B86E50310 from Apt::Source yarn]/Apt_key[Add key: 72ECF46A56B4AD39C907BBB71646B01B86E50310 from Apt::Source yarn]/ensure: change from absent to present failed: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 72ECF46A56B4AD39C907BBB71646B01B86E50310' returned 2: Executing: /tmp/tmp.oVL0AVtLjc/gpg.1.sh --keyserver
default: keyserver.ubuntu.com
default: --recv-keys
default: 72ECF46A56B4AD39C907BBB71646B01B86E50310
default: gpg: requesting key 86E50310 from hkp server keyserver.ubuntu.com
default: gpg: keyserver timed out
default: gpg: keyserver receive failed: keyserver error

default: Warning: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[yarn]/Apt::Key[Add key: 72ECF46A56B4AD39C907BBB71646B01B86E50310 from Apt::Source yarn]/Anchor[apt_key 72ECF46A56B4AD39C907BBB71646B01B86E50310 present]: Skipping because of failed dependencies
default: Error: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62' returned 2: Executing: /tmp/tmp.pcNpqbtMXY/gpg.1.sh --keyserver
default: keyserver.ubuntu.com
default: --recv-keys
default: 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62
default: gpg: requesting key 7BD9BF62 from hkp server keyserver.ubuntu.com
default: gpg: keyserver timed out
default: gpg: keyserver receive failed: keyserver error
default: Error: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[nginx]/Apt::Key[Add key: 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62 from Apt::Source nginx]/Apt_key[Add key: 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62 from Apt::Source nginx]/ensure: change from absent to present failed: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62' returned 2: Executing: /tmp/tmp.pcNpqbtMXY/gpg.1.sh --keyserver
default: keyserver.ubuntu.com
default: --recv-keys
default: 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62
default: gpg: requesting key 7BD9BF62 from hkp server keyserver.ubuntu.com
default: gpg: keyserver timed out
default: gpg: keyserver receive failed: keyserver error

default: Warning: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[yarn]/Apt::Setting[list-yarn]/File[/etc/apt/sources.list.d/yarn.list]: Skipping because of failed dependencies
default: Error: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796' returned 2: Executing: /tmp/tmp.IaG4YCD7La/gpg.1.sh --keyserver
default: keyserver.ubuntu.com
default: --recv-keys
default: EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796
default: gpg: requesting key D38B4796 from hkp server keyserver.ubuntu.com
default: gpg: keyserver timed out
default: gpg: keyserver receive failed: keyserver error

default: Error: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[google-chrome]/Apt::Key[Add key: EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796 from Apt::Source google-chrome]/Apt_key[Add key: EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796 from Apt::Source google-chrome]/ensure: change from absent to present failed: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796' returned 2: Executing: /tmp/tmp.IaG4YCD7La/gpg.1.sh --keyserver
default: keyserver.ubuntu.com
default: --recv-keys
default: EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796
default: gpg: requesting key D38B4796 from hkp server keyserver.ubuntu.com
default: gpg: keyserver timed out
default: gpg: keyserver receive failed: keyserver error

default: Warning: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[google-chrome]/Apt::Key[Add key: EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796 from Apt::Source google-chrome]/Anchor[apt_key EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796 present]: Skipping because of failed dependencies
default: Warning: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[google-chrome]/Apt::Setting[list-google-chrome]/File[/etc/apt/sources.list.d/google-chrome.list]: Skipping because of failed dependencies

default: Warning: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[nginx]/Apt::Key[Add key: 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62 from Apt::Source nginx]/Anchor[apt_key 573BFD6B3D8FBC641079A6ABABF5BD827BD9BF62 present]: Skipping because of failed dependencies

default: Warning: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[nginx]/Apt::Setting[list-nginx]/File[/etc/apt/sources.list.d/nginx.list]: Skipping because of failed dependencies
default: Error: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280' returned 2: Executing: /tmp/tmp.EC3I5niyOJ/gpg.1.sh --keyserver
default: keyserver.ubuntu.com
default: --recv-keys
default: 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280
default: gpg: requesting key 68576280 from hkp server keyserver.ubuntu.com
default: gpg: keyserver timed out
default: gpg: keyserver receive failed: keyserver error
default: Error: /Stage[init]/Omegaup::Apt_sources::Internal/Apt::Source[nodesource]/Apt::Key[Add key: 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 from Apt::Source nodesource]/Apt_key[Add key: 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 from Apt::Source nodesource]/ensure: change from absent to present failed: Execution of '/usr/bin/apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280' returned 2: Executing: /tmp/tmp.EC3I5niyOJ/gpg.1.sh --keyserver
default: keyserver.ubuntu.com
default: --recv-keys
default: 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280
default: gpg: requesting key 68576280 from hkp server keyserver.ubuntu.com
default: gpg: keyserver timed out
default: gpg: keyserver receive failed: keyserver error

default: Error: /Stage[main]/Omegaup::Database/Mysql::Db[omegaup-test]/Mysql_database[omegaup-test]: Provider mysql is not functional on this host
default: Error: /Stage[main]/Omegaup::Database/Mysql::Db[omegaup]/Mysql_user[omegaup@localhost]: Provider mysql is not functional on this host
default: Error: /Stage[main]/Omegaup::Database/Mysql::Db[omegaup]/Mysql_database[omegaup]: Provider mysql is not functional on this host
default: Error: Could not prefetch mysql_grant provider 'mysql': Command mysql is missing

default: Error: Could not find a suitable provider for mysql_datadir
default: Error: Could not find a suitable provider for mysql_user

vagrant up not working

After installing virtuabox and vagrant using

sudo apt-get install virtualbox
sudo apt-get install vagrant

When I do vagrant up I get

No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.

Output of vagrant up --provider virtualbox is:

The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant has detected that you have a version of VirtualBox installed
that is not supported by this version of Vagrant. Please install one of
the supported versions listed below to use Vagrant:

4.0, 4.1, 4.2, 4.3, 5.0

A Vagrant update may also be available that adds support for the version
you specified. Please check www.vagrantup.com/downloads.html to download
the latest version.

Output of vagrant --version is:

Vagrant 1.8.1

Output of vboxmanage --version is:

5.1.34_Ubuntur121010

I am using Linux Mint 18.3 Sylvia

Error al usar Vagrant Up

Al finalizar manda el siguiente mensaje:

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong. Envio Log de consola
log.txt

Al ingresar al aplicativo me despliega el mensaje No Config file. Envío pantalla