Comments (9)
hburke123
commented on May 29, 2024
The reason that you don't see any services with references to nginx is due to WALKOFF failing to build at line 486 and never reaching the point of full deployment. It seems as though minio is taking an unusual amount of time to spin up. This may be due to your machine specs. How many times did you see the message "BOOTLOADER - INFO:Minio not available yet, waiting to try again..." print?
from walkoff.
ch40s
commented on May 29, 2024
@hburke123 the message Minio not available yet, waiting to try again... is shown 10 times. Would it help to increase the waiting time somehow?
from walkoff.
hburke123
commented on May 29, 2024
Yes! We currently set the max wait time to 10 in the bootloader. You want to change this number, you can change line 367 in /bootloader/bootloader.py to a higher number. That should fix the issue; however, could you please inform me of the specs of your machine (i.e: memory, processor(s))
from walkoff.
ch40s
commented on May 29, 2024
I changed it from 10 to 30 and it still failed with the same error. CPU and memory utilization are not even close to max so I don't think it's related to my machine's specs. Any other ideas?
from walkoff.
emrodas10
commented on May 29, 2024
Can you run this command and send me the output? "docker service ps walkoff_resource_minio --no-trunc" I can't replicate your issue unfortunately.
from walkoff.
ch40s
commented on May 29, 2024
@emrodas10 : I'm wondering if it has to do with the fact that I'm trying to install it on armv7l.
$ docker service ps walkoff_resource_minio --no-trunc
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
ivz7nw9zybp3mnuu627312pi2 walkoff_resource_minio.1 bitnami/minio:2019-debian-9@sha256:7fb42f1749ce9db87af5683b57f6adca32c853da3329ff3550c5b92b07fdfd83 Running Pending 4 hours ago "no suitable node (unsupported platform on 1 node)"
from walkoff.
emrodas10
commented on May 29, 2024
As you suspected, the minio image we use is built for x86. It is possible that if you use this image: "dimianstudio/minio-arm" instead (or any other minio arm image), it may fix your issue. Put that as the image in WALKOFF/bootloader/base-compose.yml at line 58. Hope this works!
from walkoff.
ch40s
commented on May 29, 2024
Thanks @emrodas10 and @hburke123 for your assistance!
I used the arm image for minio and as you can see below I don't get the same error for an unsupported platform, however the script is still waiting for minio to become available. I also included below some errors and warning that I found in system logs.
# docker service ps walkoff_resource_minio --no-trunc
ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
eoaegsjcyb1q7hniwoknzie6x walkoff_resource_minio.1 dimianstudio/minio-arm:latest@sha256:d9c479b98b053129aa3c40e24406a4424c366a9123bbaefdb39a37ae38c42254 Ready Ready 4 seconds ago
xsd9h7thytn5cccso07eqinqs \_ walkoff_resource_minio.1 dimianstudio/minio-arm:latest@sha256:d9c479b98b053129aa3c40e24406a4424c366a9123bbaefdb39a37ae38c42254 Shutdown Complete 4 seconds ago
2wa0jbl54sjqn63zwjn65gnea \_ walkoff_resource_minio.1 dimianstudio/minio-arm:latest@sha256:d9c479b98b053129aa3c40e24406a4424c366a9123bbaefdb39a37ae38c42254 Shutdown Complete 14 seconds ago
pllegew49qoqo8f8wvzbjl0ds \_ walkoff_resource_minio.1 dimianstudio/minio-arm:latest@sha256:d9c479b98b053129aa3c40e24406a4424c366a9123bbaefdb39a37ae38c42254 Shutdown Complete 23 seconds ago
v1da7prw8zouxyie6k70bpcu9 \_ walkoff_resource_minio.1 dimianstudio/minio-arm:latest@sha256:d9c479b98b053129aa3c40e24406a4424c366a9123bbaefdb39a37ae38c42254 Shutdown Complete 33 seconds ago
# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e1a51e39ad79 dimianstudio/minio-arm:latest "minio" 4 seconds ago Created walkoff_resource_minio.1.0jat04638gs32fxdho52ys5sg
7718726cf58c dimianstudio/minio-arm:latest "minio" 13 seconds ago Exited (0) 6 seconds ago walkoff_resource_minio.1.x3kv41gvngjxv1r9yraususwd
6b6c2bc9c1d3 dimianstudio/minio-arm:latest "minio" 23 seconds ago Exited (0) 16 seconds ago walkoff_resource_minio.1.kq7osos0elsnafrn4xug32xoh
84049d7e1a19 dimianstudio/minio-arm:latest "minio" 32 seconds ago Exited (0) 25 seconds ago walkoff_resource_minio.1.c6dgrm22o8otmy182c5lfzrtw
d37c35af6990 dimianstudio/minio-arm:latest "minio" 42 seconds ago Exited (0) 35 seconds ago walkoff_resource_minio.1.nvcwfgh4x8w4srlho2fq6069v
Repeating errors and warnings in syslog while docker is running:
localhost dockerd[]: time="..." level=error msg="fatal task error" error="task: non-zero exit (2)" module=node/agent/taskmanager node.id=wxs2ba95cjbfj7wyj0623f015 service.id=vvudvgo5rnh2zxqmgqlzjpolz task.id=7a4rtrlr4wrngqiwskpz96j1v
...
localhost kernel: [ 3115.260792] eth0: renamed from veth7989c29
localhost kernel: [ 3115.296643] br0: port 6(veth156) entered blocking state
localhost kernel: [ 3115.296652] br0: port 6(veth156) entered forwarding state
localhost kernel: [ 3115.406018] eth1: renamed from veth68a163d
localhost kernel: [ 3115.432425] br0: port 3(veth158) entered blocking state
localhost kernel: [ 3115.432433] br0: port 3(veth158) entered forwarding state
localhost kernel: [ 3115.460621] eth2: renamed from veth6f18bd5
localhost kernel: [ 3115.476671] IPv6: ADDRCONF(NETDEV_CHANGE): veth0c3bc3a: link becomes ready
localhost kernel: [ 3115.476756] docker_gwbridge: port 3(veth0c3bc3a) entered blocking state
localhost kernel: [ 3115.476762] docker_gwbridge: port 3(veth0c3bc3a) entered forwarding state
...
localhost dockerd... level=warning msg="32805b81f0c71c96... cleanup: failed to unmount IPC: umount /var/lib/docker/containers/32805b81f0c71c96e4785ca5c962.../mounts/shm, flags: 0x2: no such file or directory"
localhost dockerd... level=warning msg="69979b837ed10bb8... cleanup: failed to unmount IPC: umount /var/lib/docker/containers/69979b837ed10bb8c174c318756a.../mounts/shm, flags: 0x2: no such file or directory"
...
localhost dockerd... level=error msg="fatal task error" error="task: non-zero exit (2)" module=node/agent/taskmanager node.id=wxs2ba95cjbfj7wyj0623f015 service.id=vvudvgo5rnh2zxqmgqlzjpolz task.id=c92skwp38e26exo6c9v307ft4
localhost dockerd... level=error msg="fatal task error" error="task: non-zero exit (2)" module=node/agent/taskmanager node.id=wxs2ba95cjbfj7wyj0623f015 service.id=vvudvgo5rnh2zxqmgqlzjpolz task.id=k85uy01wahul74uyh1qd4wk0o
...
from walkoff.
ch40s
commented on May 29, 2024
Apparently some of these issues, including the one with minio, go away by picking the right arm image. The following are still failing (exit & restart every few seconds) for some reason though:
- 127.0.0.1:5000/walkoff_core_api:latest
- 127.0.0.1:5000/walkoff_core_socketio:latest
- 127.0.0.1:5000/walkoff_core_umpire:latest
- malaslt/mongo-express-arm:latest [the only arm image on hub.docker.com]
Current status:
BOOTLOADER - INFO:Deploying Walkoff stack...
BOOTLOADER - INFO:Creating service walkoff_app_ssh
BOOTLOADER - INFO:Creating service walkoff_core_api
BOOTLOADER - INFO:Creating service walkoff_core_socketio
BOOTLOADER - INFO:Creating service walkoff_core_umpire
BOOTLOADER - INFO:Creating service walkoff_core_worker
BOOTLOADER - INFO:Creating service walkoff_resource_nginx
BOOTLOADER - INFO:Creating service walkoff_app_basics
BOOTLOADER - INFO:Creating service walkoff_app_sdk
BOOTLOADER - INFO:Walkoff stack deployed, it may take a little time to converge.
Use 'docker stack services walkoff' to check on Walkoff services.
Web interface should be available at 'https://127.0.0.1:8080' once walkoff_resource_nginx is up.
UMPIRE - INFO:Docker connection closed.
from walkoff.
Related Issues (20)
- "build_bootloader.sh" doesn't exist and "walkoff.sh up --build" fails HOT 3
- 502 Bad Gateway Connecting to WALKOFF UI HOT 5
- "aioredis.errors.AuthError: ERR Client sent AUTH, but no password is set" HOT 1
- "pymongo.errors.OperationFailure: auth failed" HOT 6
- Unable to connect to API HOT 8
- Global not saving HOT 1
- Error in umpire with powershell
- "./walkoff.sh up -d" failed HOT 1
- Minio image constantly crashing with "Invalid Credentials"
- WALKOFF Trigger Management Documentation Not found
- stop workflow execution
- Walkoff disconnect per 5 min
- Webhook for workflow execution Missing ?
- Can execute workflow
- Update the angular 8 to angular 9
- 502 Bad Gateway Error HOT 4
- Is this project active ? There has been no activity since the last WALKOFF Consortium. HOT 2
- Is there anyone share the requirement file with exactly version that can work? HOT 1
- Is this project still maintained HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from walkoff.