Error processing tar file(exit status 1): write /2782fef5844dd5a1e2174c448dd88e2fa69971d42810f6dfc87457fcdeaeb4a3/layer.tar: no space left on device
Error processing tar file(exit status 1): write /usr/lib/x86_64-linux-gnu/libz3.so.4: no space left on device
Loading UI..
Error processing tar file(exit status 1): write /bb3d2a51cf081d2b8d37b490acb74472df12dd2b6c16928d7000c5c6c468647b/layer.tar: no space left on device
Loading Gateway..
Error processing tar file(exit status 1): write /acd0b277f7bb7c7d1585a3ee7c444a081cce54eeace02121ae96258a8d808aac/layer.tar: no space left on device
Details
This issue persist when the device run out of the space on which user is trying to install ONES Application, ONES application need at least 256 GB storage to work with 128 devices
Before the installation user needs to make sure there is enough space to install ONES application
Check ONES-User-Guide for more Hardware requirement details
Resolution
Increase the Server storage
Command : df -h // to check the size of server
docker dependency
Issue Summary
Loading docker images..
Loading Collector..
./ones-installer.sh: line 25: docker: command not found
Loading DB..
./ones-installer.sh: line 28: docker: command not found
./ones-installer.sh: line 29: docker: command not found
Loading UI..
./ones-installer.sh: line 32: docker: command not found
Loading Gateway..
./ones-installer.sh: line 35: docker: command not found
Loading FM..
./ones-installer.sh: line 38: docker: command not found
./ones-installer.sh: line 40: docker: command not found
Details
Before ONES application installation, the user needs to check the
prerequisite, ONES application has few dependencies on docker, docker must be
available before ONES application installation
Check ONES-User-Guide for installation prerequisite
Resolution
Install Docker on Server
Command : apt-get install docker.io //to install
Command : docker --version //to verify
Docker version 20.10.12, build 20.10.12-0ubuntu4
Permission issue during docker installation
Issue Summary
apt-get install docker.io
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
Details
While doing any installation related to Docker or any other dependencies,
user needs to make sure to do the installation using root credentials
Resolution
User Root credentials or give super user user permission
Command : sudo su //to allow user to do any task using super user permission
docker-compose Issue
Issue Summary
Bringing up ONES app containers
./ones-installer.sh: line 46: docker-compose: command not found
Details
While doing ONES-installation, docker-compose component is required as
dependencies
So user need to make sure all the dependencies should be addressed before doing
ONES installation
./ones-installer.sh
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/images/load?quiet=0": dial unix /var/run/docker.sock: connect: permission denied
Loading DB..
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/images/load?quiet=0": dial unix /var/run/docker.sock: connect: permission denied
Details
While executing ONES installation, user needs to make sure to do the installation
using root credentials
Resolution
User Root credentials or give super user user permission
Command : sudo su //to allow user to do any task using super user permission
python3 Issue
Issue Summary
$./ones-installer.sh
Installing ONES application...
Bringing up ONES app containers
./ones-installer.sh: line 46: docker-compose: command not found
./ones-installer.sh: line 47: docker-compose: command not found
Creating default user accounts
Error: No such container: sh
Adding license..
Error: No such container: sh
Installed ONES application successfully.
Open browser at http://<host-ip>:3002
Details
If Python is not available on Server so we get these errors and even user will
not be able to access the ONES application
As dependencies user needs to install python3 first
paramiko issue uninstallation
$python3 ones_agent_uninstaller.py
Traceback (most recent call last):
File "ones_agent_uninstaller.py", line 1, in <module>
import paramiko
File "/usr/local/lib/python3.8/dist-packages/paramiko/__init__.py", line 22, in <module>
from paramiko.transport import SecurityOptions, Transport
File "/usr/local/lib/python3.8/dist-packages/paramiko/transport.py", line 33, in <module>
from cryptography.hazmat.backends import default_backend
ModuleNotFoundError: No module named 'cryptography'
ONES-GA package have few dependencies on python library, and Paramiko is one of
them,so while doing uninstallation we need paramiko python library to be activated
on server
paramiko issue installation
$ python3 ones_agent_installer.py
Traceback (most recent call last):
File "ones_agent_installer.py", line 12, in <module>
from ones_agent_helper import install_ones_agent
File "/home/GA/ones_t_agent/ones_agent_helper.py", line 1, in <module>
import paramiko
File "/usr/local/lib/python3.8/dist-packages/paramiko/__init__.py", line 22, in <module>
from paramiko.transport import SecurityOptions, Transport
File "/usr/local/lib/python3.8/dist-packages/paramiko/transport.py", line 33, in <module>
from cryptography.hazmat.backends import default_backend
ModuleNotFoundError: No module named 'cryptography'
ONES-GA package have few dependencies on python library, and Paramiko is one
of them,so while doing installation we need paramiko python library to be
activated on server
ones-collector java -jar /app/collector.jar Restarting
2022-11-02 02:36:20.648 INFO 1 --- [ main] c.a.collector.CollectorApplication : Starting CollectorApplication v0.0.1-SNAPSHOT using Java 11.0.16 on fe7dc44eb4cb with PID 1 (/app/collector.jar started by root in /app)
2022-11-02 02:36:20.673 INFO 1 --- [ main] c.a.collector.CollectorApplication : No active profile set, falling back to 1 default profile: "default"
2022-11-02 02:36:24.509 INFO 1 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2022-11-02 02:36:25.535 INFO 1 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 971 ms. Found 26 JPA repository interfaces.
2022-11-02 02:36:29.916 INFO 1 --- [ main] o.f.c.internal.license.VersionPrinter : Flyway Community Edition 8.5.13 by Redgate
2022-11-02 02:36:29.950 INFO 1 --- [ main] o.f.c.internal.license.VersionPrinter : See what's new here: https://flywaydb.org/documentation/learnmore/releaseNotes#8.5.13
2022-11-02 02:36:29.950 INFO 1 --- [ main] o.f.c.internal.license.VersionPrinter :
2022-11-02 02:36:30.025 INFO 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2022-11-02 02:36:30.685 INFO 1 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed.
2022-11-02 02:36:30.814 INFO 1 --- [ main] o.f.c.i.database.base.BaseDatabaseType : Database: jdbc:postgresql://collector-db:5432/collector (PostgreSQL 13.7)
2022-11-02 02:36:31.362 INFO 1 --- [ main] o.f.core.internal.command.DbValidate : Successfully validated 25 migrations (execution time 00:00.295s)
2022-11-02 02:36:31.470 WARN 1 --- [ main] onfigReactiveWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Found non-empty schema(s) "public" but no schema history table. Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
This happens when the DB is populated with some schema before the collector initializes the DB.
There is a order in which the DB schema has to be populated. First the Collector has to start and create the necessary tables. Then the UI will add more tables and create default users.
In this scenario, I believe the DB container took some time to start and ready to accept connections. We have a sleep time of 15s to wait for the collector and DB to start and initialize, then the UI will create it's own tables and user data. Here the UI created the tables first. That's the issue.
Command : docker-compose stop collector-db
Command : docker-compose rm collector-db
Command : docker-compose stop collector
Command : docker-compose rm collector
Command : docker-compose create collector
Command : docker-compose create collector-db
Command : docker-compose start collector-db
Command : docker-compose start collector
# we have to wait till the collector initilializes the DB. We can check the collector logs to verify that. Once initialized
