must select atleast one tool

[sturdy-hub]

keep recieving prompt saying must select atleast 1 tool but i have ?

[starboost]

same here

[JungSY98]

same here 2

Please, Help me...

[luciferlinx101]

Hey guys this mostly happens when there is some issue with backend setup when you do docker compose up can you share the docker logs to understand the problem better

[JungSY98]

Thanks for attention.

[root@localhost SuperAGI]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 96c935c2192a superagi_backend "/wait-for-it.sh sup…" 54 minutes ago Up 54 minutes 0.0.0.0:8001->8001/tcp, :::8001->8001/tcp superagi_backend_1 2dccc61efd00 superagi_celery "celery -A superagi.…" 54 minutes ago Up 54 minutes superagi_celery_1 0bf7d3d932e4 postgres:latest "docker-entrypoint.s…" 54 minutes ago Up 54 minutes 5432/tcp superagi_superpostgres_1 719e134c02ba redis:latest "docker-entrypoint.s…" 54 minutes ago Up 54 minutes 6379/tcp superagi_superredis_1 b88c8791c4b3 superagi_gui "docker-entrypoint.s…" 54 minutes ago Up 54 minutes 0.0.0.0:3000->3000/tcp, :::3000->3000/tcp superagi_gui_1 [root@localhost SuperAGI]#

I checked all logs which is located /var/lib/docker/(container-id)/(container-id)-json.log But couldn't find about "Add atleast one tool".

Can you [luciferlinx101] tell me about log file in detail?

[luciferlinx101]

Try using docker compose up --build readme was updated for the same.

[Veloptesaurazor]

I am having the same issue with the backend. Here is my code when I use docker compose up --build

[starboost]

when i check docker i saw that backend-1 is not starting even i tried to manually start, its not starting

[starboost]

backend-1 logs 2023-06-04 21:30:52 /usr/bin/env: ‘bash\r’: No such file or directory

[Fluder-Paradyne]

can we know which OS you are using

try pulling main once again because we pushed a change to fix it in windows

@starboost @Veloptesaurazor

[iamsuperzb]

I also faced the same problem in debian11 @Fluder-Paradyne

[Fluder-Paradyne]

backend-1 logs 2023-06-04 21:30:52 /usr/bin/env: ‘bash\r’: No such file or directory

This error occurs due of end of line in windows

in vscode at bottom right check for CLRF if it is CLRF then click on it and change it to LF

in entrypoint.sh and wait-for-it.sh then do docker compose up --build

[Fluder-Paradyne]

@iamsuperzb pull main git pull origin main and try running docker compose up --build

if it doesnt run can you send logs by running docker compose logs

[mhsekr]

thanks @Fluder-Paradyne (;

[6R15]

Thanks a lot. It helps

[iamsuperzb]

Thanks for attention. But is not working 4 me. @Fluder-Paradyne

These are logs by "docker compose logs".

root@localhost:~/SuperAGI# docker compose logs superagi-celery-1 | Connected to the database! @ postgresql://superagi:password@superpostgres/super_agi_main superagi-celery-1 | /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is superagi-celery-1 | absolutely not recommended! superagi-celery-1 | superagi-celery-1 | Please specify a different user using the --uid option. superagi-celery-1 | superagi-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 superagi-celery-1 | superagi-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( superagi-celery-1 |
superagi-celery-1 | -------------- celery@919915b69ff1 v5.2.7 (dawn-chorus) superagi-celery-1 | --- * ----- superagi-celery-1 | -- *** ---- Linux-5.10.0-23-amd64-x86_64-with-glibc2.31 2023-06-06 01:43:16 superagi-celery-1 | - --- --- superagi-celery-1 | - ---------- [config] superagi-celery-1 | - ---------- .> app: superagi:0x7f33b355cd90 superagi-celery-1 | - ---------- .> transport: redis://superredis:6379/0 superagi-celery-1 | - ---------- .> results: redis://super__redis:6379/0 superagi-celery-1 | - --- --- .> concurrency: 10 (prefork) superagi-celery-1 | -- *** ---- .> task events: OFF (enable -E to monitor tasks in this worker) superagi-celery-1 | --- * ----- superagi-celery-1 | -------------- [queues] superagi-celery-1 | .> celery exchange=celery(direct) key=celery superagi-celery-1 |
superagi-celery-1 | superagi-celery-1 | [tasks] superagi-celery-1 | . execute_agent superagi-celery-1 | superagi-celery-1 | [2023-06-06 01:43:17,180: INFO/MainProcess] Connected to redis://superredis:6379/0 superagi-celery-1 | [2023-06-06 01:43:17,186: INFO/MainProcess] mingle: searching for neighbors superagi-celery-1 | [2023-06-06 01:43:18,193: INFO/MainProcess] mingle: all alone superagi-celery-1 | [2023-06-06 01:43:18,205: INFO/MainProcess] celery@919915b69ff1 ready. superagi-gui-1 | superagi-gui-1 | > super-agi@0.1.0 dev superagi-gui-1 | > next dev superagi-gui-1 | superagi-gui-1 | - ready started server on 0.0.0.0:3000, url: http://localhost:3000 superagi-gui-1 | - warn Invalid next.config.js options detected: superagi-gui-1 | - warn The root value has an unexpected property, webpackDevMiddleware, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, configOrigin, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, target, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack). superagi-gui-1 | - warn See more info here: https://nextjs.org/docs/messages/invalid-next-config superagi-gui-1 | - event compiled client and server successfully in 2s (775 modules) superagi-gui-1 | - wait compiling... superagi-gui-1 | - event compiled client and server successfully in 668 ms (775 modules) superagi-gui-1 | - wait compiling /_error (client and server)... superagi-gui-1 | - event compiled client and server successfully in 208 ms (776 modules) superagi-gui-1 | Do not add stylesheets using next/head (see tag with href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&display=swap"). Use Document instead. superagi-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-backend-1 | wait-for-it.sh: waiting 60 seconds for superpostgres:5432 superagi-backend-1 | wait-for-it.sh: superpostgres:5432 is available after 0 seconds superagi-backend-1 | INFO [alembic.runtime.migration] Context impl PostgresqlImpl. superagi-backend-1 | INFO [alembic.runtime.migration] Will assume transactional DDL. superagi-backend-1 | INFO: Will watch for changes in these directories: ['/app'] superagi-backend-1 | INFO: Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit) superagi-backend-1 | INFO: Started reloader process [1] using WatchFiles superagi-backend-1 | Connected to the database! @ postgresql://superagi:password@superpostgres/super_agi_main superagi-backend-1 | INFO: Started server process [20] superagi-backend-1 | INFO: Waiting for application startup. superagi-backend-1 | INFO: Application startup complete. superagi-superpostgres-1 | The files belonging to this database system will be owned by user "postgres". superagi-superpostgres-1 | This user must also own the server process. superagi-superpostgres-1 | superagi-super__postgres-1 | The database cluster will be initialized with locale "en_US.utf8". superagi-superpostgres-1 | The default database encoding has accordingly been set to "UTF8". superagi-superpostgres-1 | The default text search configuration will be set to "english". superagi-superpostgres-1 | superagi-superpostgres-1 | Data page checksums are disabled. superagi-superpostgres-1 | superagi-superpostgres-1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok superagi-superpostgres-1 | creating subdirectories ... ok superagi-superpostgres-1 | selecting dynamic shared memory implementation ... posix superagi-superpostgres-1 | selecting default max_connections ... 100 superagi-superpostgres-1 | selecting default shared_buffers ... 128MB superagi-superpostgres-1 | selecting default time zone ... Etc/UTC superagi-superpostgres-1 | creating configuration files ... ok superagi-superpostgres-1 | running bootstrap script ... ok superagi-superpostgres-1 | performing post-bootstrap initialization ... ok superagi-superpostgres-1 | syncing data to disk ... ok superagi-superpostgres-1 | superagi-superpostgres-1 | superagi-superpostgres-1 | Success. You can now start the database server using: superagi-superpostgres-1 | superagi-superpostgres-1 | pg_ctl -D /var/lib/postgresql/data -l logfile start superagi-superpostgres-1 | superagi-superpostgres-1 | initdb: warning: enabling "trust" authentication for local connections superagi-superpostgres-1 | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. superagi-superpostgres-1 | waiting for server to start....2023-06-06 01:40:30.647 UTC [50] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit superagi-superpostgres-1 | 2023-06-06 01:40:30.647 UTC [50] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-superpostgres-1 | 2023-06-06 01:40:30.651 UTC [53] LOG: database system was shut down at 2023-06-06 01:40:30 UTC superagi-superpostgres-1 | 2023-06-06 01:40:30.660 UTC [50] LOG: database system is ready to accept connections superagi-superpostgres-1 | done superagi-superpostgres-1 | server started superagi-superpostgres-1 | CREATE DATABASE superagi-superpostgres-1 | superagi-superpostgres-1 | superagi-superpostgres-1 | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/* superagi-superpostgres-1 | superagi-superpostgres-1 | waiting for server to shut down...2023-06-06 01:40:30.965 UTC [50] LOG: received fast shutdown request superagi-superpostgres-1 | .2023-06-06 01:40:30.966 UTC [50] LOG: aborting any active transactions superagi-superpostgres-1 | 2023-06-06 01:40:30.968 UTC [50] LOG: background worker "logical replication launcher" (PID 56) exited with exit code 1 superagi-superpostgres-1 | 2023-06-06 01:40:30.968 UTC [51] LOG: shutting down superagi-superpostgres-1 | 2023-06-06 01:40:30.979 UTC [51] LOG: checkpoint starting: shutdown immediate superagi-superpostgres-1 | 2023-06-06 01:40:31.015 UTC [51] LOG: checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.029 s, sync=0.007 s, total=0.047 s; sync files=250, longest=0.001 s, average=0.001 s; distance=4217 kB, estimate=4217 kB superagi-superpostgres-1 | 2023-06-06 01:40:31.020 UTC [50] LOG: database system is shut down superagi-superpostgres-1 | done superagi-superpostgres-1 | server stopped superagi-superpostgres-1 | superagi-superpostgres-1 | PostgreSQL init process complete; ready for start up. superagi-superpostgres-1 | superagi-super__postgres-1 | 2023-06-06 01:40:31.092 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit superagi-superpostgres-1 | 2023-06-06 01:40:31.092 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-superpostgres-1 | 2023-06-06 01:40:31.092 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-superpostgres-1 | 2023-06-06 01:40:31.093 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-superpostgres-1 | 2023-06-06 01:40:31.102 UTC [66] LOG: database system was shut down at 2023-06-06 01:40:31 UTC superagi-superpostgres-1 | 2023-06-06 01:40:31.104 UTC [1] LOG: database system is ready to accept connections superagi-superpostgres-1 | 2023-06-06 01:42:52.712 UTC [1] LOG: received fast shutdown request superagi-superpostgres-1 | 2023-06-06 01:42:52.713 UTC [1] LOG: aborting any active transactions superagi-superpostgres-1 | 2023-06-06 01:42:52.715 UTC [1] LOG: background worker "logical replication launcher" (PID 69) exited with exit code 1 superagi-superpostgres-1 | 2023-06-06 01:42:52.717 UTC [64] LOG: shutting down superagi-superpostgres-1 | 2023-06-06 01:42:52.718 UTC [64] LOG: checkpoint starting: shutdown immediate superagi-superpostgres-1 | 2023-06-06 01:42:52.727 UTC [64] LOG: checkpoint complete: wrote 164 buffers (1.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.004 s, sync=0.004 s, total=0.010 s; sync files=75, longest=0.002 s, average=0.001 s; distance=760 kB, estimate=760 kB superagi-superpostgres-1 | 2023-06-06 01:42:52.731 UTC [1] LOG: database system is shut down superagi-superpostgres-1 | superagi-superpostgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-superpostgres-1 | superagi-superpostgres-1 | 2023-06-06 01:43:12.623 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit superagi-superpostgres-1 | 2023-06-06 01:43:12.623 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-superpostgres-1 | 2023-06-06 01:43:12.623 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-superpostgres-1 | 2023-06-06 01:43:12.626 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-superpostgres-1 | 2023-06-06 01:43:12.628 UTC [30] LOG: database system was shut down at 2023-06-06 01:42:52 UTC superagi-superpostgres-1 | 2023-06-06 01:43:12.631 UTC [1] LOG: database system is ready to accept connections superagi-superpostgres-1 | 2023-06-06 01:48:12.706 UTC [28] LOG: checkpoint starting: time superagi-superpostgres-1 | 2023-06-06 01:48:13.011 UTC [28] LOG: checkpoint complete: wrote 6 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.302 s, sync=0.002 s, total=0.305 s; sync files=5, longest=0.001 s, average=0.001 s; distance=4 kB, estimate=4 kB superagi-superredis-1 | 1:C 06 Jun 2023 01:40:29.620 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-superredis-1 | 1:C 06 Jun 2023 01:40:29.620 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-superredis-1 | 1:C 06 Jun 2023 01:40:29.620 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-super__redis-1 | 1:M 06 Jun 2023 01:40:29.622 * monotonic clock: POSIX clock_gettime superagi-superredis-1 | 1:M 06 Jun 2023 01:40:29.624 Running mode=standalone, port=6379. superagi-superredis-1 | 1:M 06 Jun 2023 01:40:29.624 # Server initialized superagi-superredis-1 | 1:M 06 Jun 2023 01:40:29.624 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. superagi-super__redis-1 | 1:M 06 Jun 2023 01:40:29.624 Ready to accept connections superagi-superredis-1 | 1:signal-handler (1686015772) Received SIGTERM scheduling shutdown... superagi-superredis-1 | 1:M 06 Jun 2023 01:42:52.809 # User requested shutdown... superagi-superredis-1 | 1:M 06 Jun 2023 01:42:52.809 * Saving the final RDB snapshot before exiting. superagi-superredis-1 | 1:M 06 Jun 2023 01:42:52.810 DB saved on disk superagi-superredis-1 | 1:M 06 Jun 2023 01:42:52.810 # Redis is now ready to exit, bye bye... superagi-superredis-1 | 1:C 06 Jun 2023 01:43:12.770 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-superredis-1 | 1:C 06 Jun 2023 01:43:12.770 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-superredis-1 | 1:C 06 Jun 2023 01:43:12.770 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-super__redis-1 | 1:M 06 Jun 2023 01:43:12.771 monotonic clock: POSIX clock_gettime superagi-superredis-1 | 1:M 06 Jun 2023 01:43:12.771 * Running mode=standalone, port=6379. superagi-superredis-1 | 1:M 06 Jun 2023 01:43:12.771 # Server initialized superagi-superredis-1 | 1:M 06 Jun 2023 01:43:12.771 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. superagi-superredis-1 | 1:M 06 Jun 2023 01:43:12.772 Loading RDB produced by version 7.0.11 superagi-super__redis-1 | 1:M 06 Jun 2023 01:43:12.772 RDB age 20 seconds superagi-superredis-1 | 1:M 06 Jun 2023 01:43:12.772 * RDB memory usage when created 1.18 Mb superagi-superredis-1 | 1:M 06 Jun 2023 01:43:12.772 Done loading RDB, keys loaded: 1, keys expired: 0. superagi-super__redis-1 | 1:M 06 Jun 2023 01:43:12.772 DB loaded from disk: 0.000 seconds superagi-super__redis-1 | 1:M 06 Jun 2023 01:43:12.772 * Ready to accept connections

[ethicallymad]

I am having the same issue. Running windows 11, fresh clone from 1 hour ago, and tried using the suggestions in this thread, but no luck. No tools showing in the side bar, or as options in the dropdown in the agents setup. Have tried rebuilding, and running in different browsers, but same bug every time.

[jazzjazzy]

I had the same issue where I had no tools and if I tried to run the agent would get the add atleast one tool

I went back and looked at my config.yaml and found I had added a hidden 'tab' before my openAIKey, after I removed that and did 'docker-compose up --build' it worked like a charm.

[ethicallymad]

I had the same issue where I had no tools and if I tried to run the agent would get the add atleast one tool

I went back and looked at my config.yaml and found I had added a hidden 'tab' before my openAIKey, after I removed that and did 'docker-compose up --build' it worked like a charm.

Thanks for the tip - sadly did not work for me. Double checked everything, and no hidden tabs before or after any of the keys

[Veloptesaurazor]

It finally worked for me!! It was this plus also making sure that the config.yaml file was also in LF. For some reason, it was in CRLF even though the template is in LF.

[jorgitobg]

Same issue here.... nothing tried works.... allways no tools...

superuser@DESKTOP-GAMTHT1:/mnt/d/OneDrive/PROYECTOS/01_AI/SuperAGI$ docker-compose logs superagi-celery-1 | Connected to the database! @ postgresql://superagi:password@superpostgres/super_agi_main superagi-celery-1 | /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is superagi-celery-1 | absolutely not recommended! superagi-celery-1 | superagi-celery-1 | Please specify a different user using the --uid option. superagi-celery-1 | superagi-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 superagi-celery-1 | superagi-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( superagi-celery-1 | superagi-celery-1 | -------------- celery@0337267414fc v5.2.7 (dawn-chorus) superagi-celery-1 | --- * ----- superagi-celery-1 | -- *** ---- Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.31 2023-06-06 11:25:04 superagi-celery-1 | - --- --- superagi-celery-1 | - ---------- [config] superagi-celery-1 | - ---------- .> app: superagi:0x7f74147b1040 superagi-celery-1 | - ---------- .> transport: redis://superredis:6379/0 superagi-celery-1 | - ---------- .> results: redis://super__redis:6379/0 superagi-celery-1 | - --- --- .> concurrency: 10 (prefork) superagi-celery-1 | -- *** ---- .> task events: OFF (enable -E to monitor tasks in this worker) superagi-celery-1 | --- * ----- superagi-celery-1 | -------------- [queues] superagi-celery-1 | .> celery exchange=celery(direct) key=celery superagi-gui-1 | superagi-gui-1 | > super-agi@0.1.0 dev superagi-gui-1 | > next dev superagi-gui-1 | superagi-celery-1 | superagi-gui-1 | - ready started server on 0.0.0.0:3000, url: http://localhost:3000 superagi-gui-1 | - warn Invalid next.config.js options detected: superagi-gui-1 | - warn The root value has an unexpected property, webpackDevMiddleware, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, configOrigin, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, target, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack). superagi-gui-1 | - warn See more info here: https://nextjs.org/docs/messages/invalid-next-config superagi-gui-1 | Attention: Next.js now collects completely anonymous telemetry regarding usage. superagi-superredis-1 | 1:C 06 Jun 2023 11:24:59.824 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-superredis-1 | 1:C 06 Jun 2023 11:24:59.824 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
superagi-superredis-1 | 1:C 06 Jun 2023 11:24:59.824 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-superredis-1 | 1:M 06 Jun 2023 11:24:59.825 monotonic clock: POSIX clock_gettime superagi-super__redis-1 | 1:M 06 Jun 2023 11:24:59.825 Running mode=standalone, port=6379. superagi-superredis-1 | 1:M 06 Jun 2023 11:24:59.825 # Server initialized superagi-superredis-1 | 1:M 06 Jun 2023 11:24:59.825 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. superagi-celery-1 | superagi-superredis-1 | 1:M 06 Jun 2023 11:24:59.826 * Ready to accept connections superagi-superredis-1 | 1:signal-handler (1686050814) Received SIGTERM scheduling shutdown... superagi-superredis-1 | 1:M 06 Jun 2023 11:26:54.037 # User requested shutdown... superagi-superredis-1 | 1:M 06 Jun 2023 11:26:54.037 Saving the final RDB snapshot before exiting. superagi-super__redis-1 | 1:M 06 Jun 2023 11:26:54.043 DB saved on disk superagi-superredis-1 | 1:M 06 Jun 2023 11:26:54.043 # Redis is now ready to exit, bye bye... superagi-gui-1 | This information is used to shape Next.js' roadmap and prioritize features. superagi-gui-1 | You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: superagi-gui-1 | https://nextjs.org/telemetry superagi-gui-1 | superagi-celery-1 | [tasks] superagi-gui-1 | - event compiled client and server successfully in 5.5s (775 modules) superagi-gui-1 | - wait compiling... superagi-gui-1 | - event compiled client and server successfully in 2s (775 modules) superagi-superpostgres-1 | superagi-superpostgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-superpostgres-1 | superagi-super__postgres-1 | 2023-06-06 11:24:59.890 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit superagi-superpostgres-1 | 2023-06-06 11:24:59.890 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-superpostgres-1 | 2023-06-06 11:24:59.890 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-superpostgres-1 | 2023-06-06 11:24:59.928 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-superpostgres-1 | 2023-06-06 11:24:59.978 UTC [30] LOG: database system was shut down at 2023-06-06 11:14:30 UTC superagi-superpostgres-1 | 2023-06-06 11:25:00.000 UTC [1] LOG: database system is ready to accept connections superagi-superpostgres-1 | 2023-06-06 11:26:54.031 UTC [1] LOG: received fast shutdown request superagi-superpostgres-1 | 2023-06-06 11:26:54.035 UTC [1] LOG: aborting any active transactions superagi-superpostgres-1 | 2023-06-06 11:26:54.036 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1 superagi-superpostgres-1 | 2023-06-06 11:26:54.036 UTC [28] LOG: shutting down superagi-gui-1 | - wait compiling /_error (client and server)... superagi-gui-1 | - event compiled client and server successfully in 212 ms (776 modules) superagi-gui-1 | Do not add stylesheets using next/head (see tag with href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&display=swap"). Use Document instead. superagi-celery-1 | . execute_agent superagi-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-celery-1 | superagi-celery-1 | [2023-06-06 11:25:04,891: INFO/MainProcess] Connected to redis://superredis:6379/0 superagi-celery-1 | [2023-06-06 11:25:04,894: INFO/MainProcess] mingle: searching for neighbors superagi-celery-1 | [2023-06-06 11:25:05,902: INFO/MainProcess] mingle: all alone superagi-celery-1 | [2023-06-06 11:25:05,912: INFO/MainProcess] celery@0337267414fc ready. superagi-celery-1 | superagi-celery-1 | worker: Warm shutdown (MainProcess) superagi-backend-1 | wait-for-it.sh: waiting 60 seconds for superpostgres:5432 superagi-backend-1 | wait-for-it.sh: superpostgres:5432 is available after 0 seconds superagi-backend-1 | INFO [alembic.runtime.migration] Context impl PostgresqlImpl. superagi-gui-1 | npm ERR! path /app superagi-gui-1 | npm ERR! command failed superagi-backend-1 | INFO [alembic.runtime.migration] Will assume transactional DDL. superagi-gui-1 | npm ERR! signal SIGTERM superagi-backend-1 | INFO: Will watch for changes in these directories: ['/app'] superagi-backend-1 | INFO: Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit) superagi-backend-1 | INFO: Started reloader process [1] using WatchFiles superagi-backend-1 | Connected to the database! @ postgresql://superagi:password@superpostgres/super_agi_main superagi-backend-1 | INFO: Started server process [20] superagi-backend-1 | INFO: Waiting for application startup. superagi-backend-1 | INFO: Application startup complete. superagi-backend-1 | INFO: 172.23.0.1:41132 - "OPTIONS /users/add HTTP/1.1" 400 Bad Request superagi-gui-1 | npm ERR! command sh -c next dev superagi-backend-1 | INFO: 172.23.0.1:41128 - "GET /agents/get/project/ HTTP/1.1" 307 Temporary Redirect superagi-backend-1 | INFO: 172.23.0.1:41124 - "GET /tools/get HTTP/1.1" 200 OK superagi-gui-1 | superagi-backend-1 | INFO: 172.23.0.1:41140 - "GET /projects/get/organisation/1 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.23.0.1:41136 - "GET /organisations/get/1 HTTP/1.1" 200 OK superagi-backend-1 | INFO: Shutting down superagi-backend-1 | INFO: Waiting for application shutdown. superagi-backend-1 | INFO: Application shutdown complete. superagi-backend-1 | INFO: Finished server process [20] superagi-backend-1 | INFO: Stopping reloader process [1] superagi-superpostgres-1 | 2023-06-06 11:26:54.039 UTC [28] LOG: checkpoint starting: shutdown immediate superagi-superpostgres-1 | 2023-06-06 11:26:54.062 UTC [28] LOG: checkpoint complete: wrote 5 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.005 s, sync=0.005 s, total=0.027 s; sync files=4, longest=0.003 s, average=0.002 s; distance=4 kB, estimate=4 kB superagi-superpostgres-1 | 2023-06-06 11:26:54.065 UTC [1] LOG: database system is shut down superagi-gui-1 | npm ERR! A complete log of this run can be found in: superagi-gui-1 | npm ERR! /root/.npm/_logs/2023-06-06T11_25_00_137Z-debug-0.log

[chrisbrighouse]

I've still got the same problem, I switched to LF and checked for any rogue tabs etc. in the config.yaml file. I've got pinecone, google and openai keys included, but still no tools showing. Running on Windows 10.

[kristiansDraguns]

I tried deleting the folder and re doing everything. Now it finally works <3

[ethicallymad]

Have tried everything here so far, and yet still same issue. (No tabs in config, all LFs, reinstalled etc).

I did spot this in the build files though, not sure if this is related (everything else appears to be working that I can see)

superagi-gui-1 | - warn Invalid next.config.js options detected: superagi-gui-1 | - warn The root value has an unexpected property, webpackDevMiddleware, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, configOrigin, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, target, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack). superagi-gui-1 | - warn See more info here: https://nextjs.org/docs/messages/invalid-next-config

[jeffreyha-dev]

Hi folks,

I resolved it on linux by replacing the localhost with ipaddress in this section of the docker compose file

gui: build: ./gui ports:

• "3000:3000" environment:
• NEXT_PUBLIC_API_BASE_URL=http://192.168.1.9:8001

In addition, replaced the localhost in main.py for these sections too.

origins = [

"http://192.168.1.9:3000",
"http://192.168.1.9:3001",

]

@app.get('/github-auth') def github_auth_handler(code: str = Query(...),Authorize: AuthJWT = Depends()): github_token_url = 'https://github.com/login/oauth/access_token' github_client_id = "" github_client_secret = "" frontend_url = "http://192.168.1.9:3000"

[ethicallymad]

Hi folks,

I resolved it on linux by replacing the localhost with ipaddress in this section of the docker compose file

gui: build: ./gui ports: - "3000:3000" environment: - NEXT_PUBLIC_API_BASE_URL=http://192.168.1.9:8001

In addition, replaced the localhost in main.py for these sections too.

origins = [

"http://192.168.1.9:3000",
"http://192.168.1.9:3001",

]

@app.get('/github-auth') def github_auth_handler(code: str = Query(...),Authorize: AuthJWT = Depends()): github_token_url = 'https://github.com/login/oauth/access_token' github_client_id = "" github_client_secret = "" frontend_url = "http://192.168.1.9:3000"

Thanks @jeffreyha-dev - awesome you managed to get it going. Sadly this fix is not working for me on Windows 11.

[Fluder-Paradyne]

can you show output of these

docker compose ps -a

and a screenshot of network tab for failing request

specifically want to see errors

[ethicallymad]

Here is a list of errors I am getting

[hanhyalex123]

Fantastic! After trying all the methods mentioned above, I finally solved my issue on my Mac. @jeffreyha-dev truly inspired me. When I checked the Chrome console, I found it was a cross-domain issue preventing access, and different ports were still considered as causing a cross-domain issue. Documentation link: https://fastapi.tiangolo.com/zh/tutorial/cors/

The modification is in main.py, I changed:

app.add_middleware( CORSMiddleware, allow_origins=["*"], allow_credentials=True, allow_methods=["*"], allow_headers=["*"], )

Hi folks,

I resolved it on linux by replacing the localhost with ipaddress in this section of the docker compose file

gui: build: ./gui ports: - "3000:3000" environment: - NEXT_PUBLIC_API_BASE_URL=http://192.168.1.9:8001

In addition, replaced the localhost in main.py for these sections too.

origins = [

"http://192.168.1.9:3000",
"http://192.168.1.9:3001",

]

@app.get('/github-auth') def github_auth_handler(code: str = Query(...),Authorize: AuthJWT = Depends()): github_token_url = 'https://github.com/login/oauth/access_token' github_client_id = "" github_client_secret = "" frontend_url = "http://192.168.1.9:3000"

Hi folks,

I resolved it on linux by replacing the localhost with ipaddress in this section of the docker compose file

gui: build: ./gui ports: - "3000:3000" environment: - NEXT_PUBLIC_API_BASE_URL=http://192.168.1.9:8001

In addition, replaced the localhost in main.py for these sections too.

origins = [

"http://192.168.1.9:3000",
"http://192.168.1.9:3001",

]

@app.get('/github-auth') def github_auth_handler(code: str = Query(...),Authorize: AuthJWT = Depends()): github_token_url = 'https://github.com/login/oauth/access_token' github_client_id = "" github_client_secret = "" frontend_url = "http://192.168.1.9:3000"

[rakesh-krishna]

@ethicallymad sudo docker ps run this sudo docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}'

can you ping which ip you get

if the first command doesnt work try this

docker inspect \ --format '{{ .NetworkSettings.IPAddress }}' container_id

[jorgitobg]

Finally SuperAGI is working.

It seems that doesn't work fine with changing the URL. I was using HTTP://superagi.local:3000, redirecting 127.0.0.1 to superagi.local in my windows hosts configuration.

After deleting folder, re-install everything (git pull included) from zero using WSL inside windows (not the regular cmd), and calling the app by HTTP://localhost:3000, then superAGI seems to be running fine.

Now I'm playing with vectorial long term data.... I'm not sure is working fine, every time I try a "new run" seems everything begins from zero not saving previous progress.

[ethicallymad]

@rakesh-krishna I tried, but sudo was not recognised. Ran without sudo and got the following:

I tried the second 2 commands, but the second one would not work and the last one would not recognise the container :(

[Thelyoncrypt]

Attention, everyone! If you've been struggling with the "No tools Issue" and have spent countless hours troubleshooting it, I have a workaround to share. This workaround has consistently worked for me, and I don't want anyone else to go through the same frustrating experience. I was determined to find a solution, and I'm happy to share it with you now.

[Thelyoncrypt]

Attention, everyone! If you've been struggling with the "No tools Issue" and have spent countless hours troubleshooting it, I have a workaround to share. This workaround has consistently worked for me, and I don't want anyone else to go through the same frustrating experience. I was determined to find a solution, and I'm happy to share it with you now.

USER RAVI SAYS: I don't understand what is the workaround how is this different from the normal installation process? Crusader — Today at 8:44 PM ahh!!! I will explain! when using Visual studio it causes the No tools to issue the docker images do not install correctly if you run through the terminal it works I tried changing the CLRF to RF it did not work, so this was the fix I was using chat GPT to diagnose the issue I will find the details. swcMinify, target, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack). superagi-gui-1 | - warn See more info here: https://nextjs.org/docs/messages/invalid-next-config superagi-backend-1 exited with code 127 superagi-celery-1 | Connected to the database! @ invalid-next-config | Next.js backend failed to install causing no tools issue Backend: The error message /usr/bin/env: ‘bash\r’: No such file or directory suggests that the file being executed might have Windows-style line endings (CRLF), which can cause issues on Unix-based systems. You may need to convert the line endings to Unix-style (LF) using a tool like dos2unix. so when changing entrypoint .sh to LF it did not resolve issue so the above was the fix hope that explains it better there may be another fix but after 5 hours and being really frustrated this is what got me across the line and I am not complaining!!

[neelayan7]

Are you still facing the same issue with the newer version updates?

[jorgitobg]

hi @neelayan7 i didn't find this issue again on the latest versions... also I discovered Its better to install SuperAGI repo ALWAYS using windows11+wsl console... never using CMD because file format and permissions sometimes do not work as expected....

[neelayan7]

Thanks. We are closing this issue for now. Do let me know if you face any other issue.