(Initializing stuck and thinking stuck) due to Memory overcommit

[Starblue0]

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.

Common issue

• Thinking Loop that doesn't Put out responses and is stuck
• Initializing loop when starting

Reddis Log

superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.157 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 # 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-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.166 * Ready to accept connections superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.331 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.340 * Background saving started by pid 19 superagi-main-super__redis-1 | 19:C 15 Jun 2023 02:48:00.358 * DB saved on disk superagi-main-super__redis-1 | 19:C 15 Jun 2023 02:48:00.358 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.442 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:53:45.069 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:53:45.070 * Background saving started by pid 20 superagi-main-super__redis-1 | 20:C 15 Jun 2023 02:53:45.081 * DB saved on disk superagi-main-super__redis-1 | 20:C 15 Jun 2023 02:53:45.081 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:53:45.170 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:15:24.639 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:15:24.646 * Background saving started by pid 21 superagi-main-super__redis-1 | 21:C 15 Jun 2023 03:15:24.662 * DB saved on disk superagi-main-super__redis-1 | 21:C 15 Jun 2023 03:15:24.663 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:15:24.747 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:39:21.486 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:39:21.486 * Background saving started by pid 22 superagi-main-super__redis-1 | 22:C 15 Jun 2023 03:39:21.492 * DB saved on disk superagi-main-super__redis-1 | 22:C 15 Jun 2023 03:39:21.492 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:39:21.587 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 04:39:22.058 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 04:39:22.071 * Background saving started by pid 23 superagi-main-super__redis-1 | 23:C 15 Jun 2023 04:39:22.099 * DB saved on disk superagi-main-super__redis-1 | 23:C 15 Jun 2023 04:39:22.099 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 04:39:22.172 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 05:39:23.075 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 05:39:23.079 * Background saving started by pid 24 superagi-main-super__redis-1 | 24:C 15 Jun 2023 05:39:23.094 * DB saved on disk superagi-main-super__redis-1 | 24:C 15 Jun 2023 05:39:23.095 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 05:39:23.179 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 06:39:24.008 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 06:39:24.008 * Background saving started by pid 25 superagi-main-super__redis-1 | 25:C 15 Jun 2023 06:39:24.014 * DB saved on disk superagi-main-super__redis-1 | 25:C 15 Jun 2023 06:39:24.015 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 06:39:24.109 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 07:39:25.035 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 07:39:25.035 * Background saving started by pid 26 superagi-main-super__redis-1 | 26:C 15 Jun 2023 07:39:25.044 * DB saved on disk superagi-main-super__redis-1 | 26:C 15 Jun 2023 07:39:25.045 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 07:39:25.136 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 08:39:26.078 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 08:39:26.078 * Background saving started by pid 27 superagi-main-super__redis-1 | 27:C 15 Jun 2023 08:39:26.085 * DB saved on disk superagi-main-super__redis-1 | 27:C 15 Jun 2023 08:39:26.085 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 08:39:26.179 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 09:39:27.020 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 09:39:27.021 * Background saving started by pid 28 superagi-main-super__redis-1 | 28:C 15 Jun 2023 09:39:27.026 * DB saved on disk superagi-main-super__redis-1 | 28:C 15 Jun 2023 09:39:27.026 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 09:39:27.121 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 10:39:28.084 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 10:39:28.085 * Background saving started by pid 29 superagi-main-super__redis-1 | 29:C 15 Jun 2023 10:39:28.093 * DB saved on disk superagi-main-super__redis-1 | 29:C 15 Jun 2023 10:39:28.093 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 10:39:28.185 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 11:39:29.022 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 11:39:29.022 * Background saving started by pid 30 superagi-main-super__redis-1 | 30:C 15 Jun 2023 11:39:29.028 * DB saved on disk superagi-main-super__redis-1 | 30:C 15 Jun 2023 11:39:29.028 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 11:39:29.123 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 12:39:30.090 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 12:39:30.093 * Background saving started by pid 31 superagi-main-super__redis-1 | 31:C 15 Jun 2023 12:39:30.097 * DB saved on disk superagi-main-super__redis-1 | 31:C 15 Jun 2023 12:39:30.097 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 12:39:30.193 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 13:39:31.055 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 13:39:31.055 * Background saving started by pid 32 superagi-main-super__redis-1 | 32:C 15 Jun 2023 13:39:31.061 * DB saved on disk superagi-main-super__redis-1 | 32:C 15 Jun 2023 13:39:31.061 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 13:39:31.156 * Background saving terminated with success superagi-main-super__redis-1 | 1:signal-handler (1686839298) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 14:28:18.830 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 14:28:18.831 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 14:28:18.842 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 14:28:18.844 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 15:59:35.836 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 15:59:35.839 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 15:59:35.839 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.841 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.853 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.854 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.855 # 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-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.867 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.867 * RDB age 5477 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.867 * RDB memory usage when created 1.43 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.870 * Done loading RDB, keys loaded: 10, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.871 * DB loaded from disk: 0.008 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.871 * Ready to accept connections superagi-main-super__redis-1 | 1:M 15 Jun 2023 16:48:07.237 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 16:48:07.251 * Background saving started by pid 19 superagi-main-super__redis-1 | 19:C 15 Jun 2023 16:48:07.264 * DB saved on disk superagi-main-super__redis-1 | 19:C 15 Jun 2023 16:48:07.264 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 16:48:07.354 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 17:48:08.087 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 17:48:08.089 * Background saving started by pid 20 superagi-main-super__redis-1 | 20:C 15 Jun 2023 17:48:08.101 * DB saved on disk superagi-main-super__redis-1 | 20:C 15 Jun 2023 17:48:08.101 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 17:48:08.189 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 18:48:09.042 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 18:48:09.044 * Background saving started by pid 21 superagi-main-super__redis-1 | 21:C 15 Jun 2023 18:48:09.053 * DB saved on disk superagi-main-super__redis-1 | 21:C 15 Jun 2023 18:48:09.053 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 18:48:09.145 * Background saving terminated with success superagi-main-super__redis-1 | 1:signal-handler (1686857484) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:24.107 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:24.107 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:24.112 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:24.113 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:31:33.475 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:31:33.475 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:31:33.475 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.478 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.483 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.483 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.484 # 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-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.532 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.532 * RDB age 9 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.532 * RDB memory usage when created 1.44 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.533 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.533 * DB loaded from disk: 0.002 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.534 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686857991) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:39:51.663 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:39:51.665 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:39:51.679 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:39:51.680 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:41:11.439 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:41:11.439 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:41:11.439 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.440 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.446 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.446 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.446 # 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-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.455 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.455 * RDB age 80 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.455 * RDB memory usage when created 1.20 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.456 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.456 * DB loaded from disk: 0.004 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.456 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686858288) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:44:48.866 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:44:48.870 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:44:48.912 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:44:48.913 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:45:01.684 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:45:01.685 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:45:01.685 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.686 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.694 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.694 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.695 # 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-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.699 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.699 * RDB age 13 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.699 * RDB memory usage when created 1.20 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.701 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.701 * DB loaded from disk: 0.002 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.701 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686858506) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:48:26.275 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:48:26.279 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:48:26.303 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:48:26.305 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:49:07.278 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:49:07.279 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:49:07.279 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.280 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.283 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.284 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.284 # 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-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * RDB age 41 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * RDB memory usage when created 0.85 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * DB loaded from disk: 0.001 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686858750) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:52:30.466 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:52:30.468 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:52:30.492 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:52:30.494 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 20:00:34.872 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 20:00:34.872 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 20:00:34.872 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.877 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.914 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.916 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.917 # 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-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.940 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.941 * RDB age 484 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.942 * RDB memory usage when created 0.85 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.946 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.946 * DB loaded from disk: 0.013 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.948 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686859358) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:02:38.949 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:02:38.952 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:02:38.986 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:02:38.986 # Redis is now ready to exit, bye bye...

I'm on windows 11 and Config file is setup correctly.

I get Calls and Tokens spent amount that shows up but no reply/ Response shows up just stuck at thinking from the SuperAGI agent when running its either stuck on thinking loop and or at points when loaded back up then stuck on Initializing loop

WIndows's 11 is up to date and So is WSL

[Starblue0]

Here are the full logs `Above is the Redis logs

Here is the full log for the issues

superagi-main-super__postgres-1 | The files belonging to this database system will be owned by user "postgres". superagi-main-super__postgres-1 | This user must also own the server process. superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | The database cluster will be initialized with locale "en_US.utf8". superagi-main-super__postgres-1 | The default database encoding has accordingly been set to "UTF8". superagi-main-celery-1 | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main superagi-main-gui-1 | superagi-main-gui-1 | > [email protected] dev superagi-main-gui-1 | > next dev superagi-main-gui-1 | superagi-main-gui-1 | - ready started server on 0.0.0.0:3000, url: http://localhost:3000 superagi-main-gui-1 | - event compiled client and server successfully in 23.7s (1314 modules) superagi-main-gui-1 | - wait compiling... superagi-main-gui-1 | - event compiled client and server successfully in 1015 ms (1314 modules) superagi-main-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-main-celery-1 | absolutely not recommended! superagi-main-celery-1 | superagi-main-super__postgres-1 | The default text search configuration will be set to "english". superagi-main-gui-1 | - wait compiling /_error (client and server)... superagi-main-gui-1 | - event compiled client and server successfully in 4.2s (1315 modules) superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.157 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 # 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-main-celery-1 | Please specify a different user using the --uid option. superagi-main-celery-1 | superagi-main-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 superagi-main-celery-1 | superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.166 * Ready to accept connections superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.331 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.340 * Background saving started by pid 19 superagi-main-super__redis-1 | 19:C 15 Jun 2023 02:48:00.358 * DB saved on disk superagi-main-super__redis-1 | 19:C 15 Jun 2023 02:48:00.358 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.442 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:53:45.069 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:53:45.070 * Background saving started by pid 20 superagi-main-super__redis-1 | 20:C 15 Jun 2023 02:53:45.081 * DB saved on disk superagi-main-super__redis-1 | 20:C 15 Jun 2023 02:53:45.081 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:53:45.170 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:15:24.639 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:15:24.646 * Background saving started by pid 21 superagi-main-super__redis-1 | 21:C 15 Jun 2023 03:15:24.662 * DB saved on disk superagi-main-super__redis-1 | 21:C 15 Jun 2023 03:15:24.663 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:15:24.747 * Background saving terminated with success superagi-main-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( superagi-main-celery-1 | superagi-main-gui-1 | Do not add stylesheets using next/head (see <link rel="stylesheet"> tag with href="https://fonts.googleapis.com/css2?family=Source+Code+Pro&display=swap"). Use Document instead. superagi-main-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-main-gui-1 | Do not add stylesheets using next/head (see <link rel="stylesheet"> tag with href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&display=swap"). Use Document instead. superagi-main-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-main-gui-1 | - wait compiling /favicon.ico/route (client and server)... superagi-main-gui-1 | - event compiled successfully in 168 ms (146 modules) superagi-main-gui-1 | npm ERR! path /app superagi-main-gui-1 | npm ERR! command failed superagi-main-gui-1 | npm ERR! signal SIGTERM superagi-main-gui-1 | npm ERR! command sh -c next dev superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:39:21.486 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:39:21.486 * Background saving started by pid 22 superagi-main-super__redis-1 | 22:C 15 Jun 2023 03:39:21.492 * DB saved on disk superagi-main-super__redis-1 | 22:C 15 Jun 2023 03:39:21.492 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 03:39:21.587 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 04:39:22.058 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 04:39:22.071 * Background saving started by pid 23 superagi-main-super__redis-1 | 23:C 15 Jun 2023 04:39:22.099 * DB saved on disk superagi-main-super__redis-1 | 23:C 15 Jun 2023 04:39:22.099 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 04:39:22.172 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 05:39:23.075 * 1 changes in 3600 seconds. Saving... superagi-main-backend-1 | wait-for-it.sh: waiting 60 seconds for super__postgres:5432 superagi-main-backend-1 | wait-for-it.sh: super__postgres:5432 is available after 1 seconds superagi-main-backend-1 | INFO [alembic.runtime.migration] Context impl PostgresqlImpl. superagi-main-backend-1 | INFO [alembic.runtime.migration] Will assume transactional DDL. superagi-main-backend-1 | INFO: Will watch for changes in these directories: ['/app'] superagi-main-backend-1 | INFO: Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit) superagi-main-backend-1 | INFO: Started reloader process [1] using WatchFiles superagi-main-backend-1 | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main superagi-main-backend-1 | INFO: Started server process [20] superagi-main-backend-1 | INFO: Waiting for application startup. superagi-main-backend-1 | INFO: Application startup complete. superagi-main-backend-1 | INFO: 172.18.0.1:42112 - "GET /configs/get/env HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42112 - "OPTIONS /users/add HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42112 - "POST /users/add HTTP/1.1" 201 Created superagi-main-backend-1 | INFO: 172.18.0.1:42112 - "GET /organisations/get/user/1 HTTP/1.1" 201 Created superagi-main-backend-1 | INFO: 172.18.0.1:42112 - "GET /projects/get/organisation/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42126 - "GET /tools/get HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42130 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42112 - "GET /configs/get/organisation/1/key/model_api_key HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42112 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request superagi-main-backend-1 | INFO: 172.18.0.1:42126 - "GET /agentexecutions/get/agent/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42126 - "GET /agentexecutionfeeds/get/execution/2 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42126 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42130 - "GET /agents/get/details/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42126 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request superagi-main-backend-1 | INFO: 172.18.0.1:42112 - "GET /agentexecutions/get/agent/4 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42130 - "GET /agents/get/details/4 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42130 - "GET /agentexecutionfeeds/get/execution/5 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42130 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:37612 - "GET /agentexecutions/get/agent/3 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:37628 - "GET /agents/get/details/3 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:37602 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request superagi-main-super__redis-1 | 1:M 15 Jun 2023 05:39:23.079 * Background saving started by pid 24 superagi-main-super__redis-1 | 24:C 15 Jun 2023 05:39:23.094 * DB saved on disk superagi-main-super__redis-1 | 24:C 15 Jun 2023 05:39:23.095 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 05:39:23.179 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 06:39:24.008 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 06:39:24.008 * Background saving started by pid 25 superagi-main-super__redis-1 | 25:C 15 Jun 2023 06:39:24.014 * DB saved on disk superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | Data page checksums are disabled. superagi-main-super__postgres-1 | superagi-main-celery-1 | -------------- celery@ea59d3726db5 v5.2.7 (dawn-chorus) superagi-main-super__redis-1 | 25:C 15 Jun 2023 06:39:24.015 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 06:39:24.109 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 07:39:25.035 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 07:39:25.035 * Background saving started by pid 26 superagi-main-super__redis-1 | 26:C 15 Jun 2023 07:39:25.044 * DB saved on disk superagi-main-super__redis-1 | 26:C 15 Jun 2023 07:39:25.045 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 07:39:25.136 * Background saving terminated with success superagi-main-super__postgres-1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok superagi-main-super__postgres-1 | creating subdirectories ... ok superagi-main-backend-1 | INFO: 172.18.0.1:37602 - "GET /agentexecutionfeeds/get/execution/4 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:37602 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:37602 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request superagi-main-celery-1 | --- ***** ----- superagi-main-celery-1 | -- ******* ---- Linux-5.15.90.1-microsoft-standard-WSL2-x86_64-with-glibc2.36 2023-06-15 20:00:53 superagi-main-celery-1 | - *** --- * --- superagi-main-celery-1 | - ** ---------- [config] superagi-main-celery-1 | - ** ---------- .> app: superagi:0x7f0e97ed34f0 superagi-main-celery-1 | - ** ---------- .> transport: redis://super__redis:6379/0 superagi-main-celery-1 | - ** ---------- .> results: redis://super__redis:6379/0 superagi-main-celery-1 | - *** --- * --- .> concurrency: 10 (prefork) superagi-main-celery-1 | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) superagi-main-celery-1 | --- ***** ----- superagi-main-celery-1 | -------------- [queues] superagi-main-super__redis-1 | 1:M 15 Jun 2023 08:39:26.078 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 08:39:26.078 * Background saving started by pid 27 superagi-main-super__redis-1 | 27:C 15 Jun 2023 08:39:26.085 * DB saved on disk superagi-main-super__redis-1 | 27:C 15 Jun 2023 08:39:26.085 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 08:39:26.179 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 09:39:27.020 * 1 changes in 3600 seconds. Saving... superagi-main-super__postgres-1 | selecting dynamic shared memory implementation ... posix superagi-main-gui-1 | superagi-main-celery-1 | .> celery exchange=celery(direct) key=celery superagi-main-celery-1 | superagi-main-celery-1 | superagi-main-celery-1 | [tasks] superagi-main-celery-1 | . execute_agent superagi-main-gui-1 | npm ERR! A complete log of this run can be found in: superagi-main-gui-1 | npm ERR! /root/.npm/_logs/2023-06-15T19_45_04_186Z-debug-0.log superagi-main-gui-1 | superagi-main-gui-1 | > [email protected] dev superagi-main-gui-1 | > next dev superagi-main-gui-1 | superagi-main-gui-1 | - ready started server on 0.0.0.0:3000, url: http://localhost:3000 superagi-main-gui-1 | - event compiled client and server successfully in 10.9s (1314 modules) superagi-main-gui-1 | - wait compiling... superagi-main-gui-1 | - event compiled client and server successfully in 1609 ms (1314 modules) superagi-main-gui-1 | - wait compiling /_error (client and server)... superagi-main-gui-1 | - event compiled client and server successfully in 3.8s (1315 modules) superagi-main-gui-1 | Do not add stylesheets using next/head (see <link rel="stylesheet"> tag with href="https://fonts.googleapis.com/css2?family=Source+Code+Pro&display=swap"). Use Document instead. superagi-main-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-main-gui-1 | Do not add stylesheets using next/head (see <link rel="stylesheet"> tag with href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&display=swap"). Use Document instead. superagi-main-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-main-gui-1 | - wait compiling /favicon.ico/route (client and server)... superagi-main-gui-1 | - event compiled successfully in 494 ms (146 modules) superagi-main-gui-1 | npm ERR! path /app superagi-main-gui-1 | npm ERR! command failed superagi-main-gui-1 | npm ERR! signal SIGTERM superagi-main-gui-1 | npm ERR! command sh -c next dev superagi-main-gui-1 | superagi-main-gui-1 | npm ERR! A complete log of this run can be found in: superagi-main-gui-1 | npm ERR! /root/.npm/_logs/2023-06-15T19_49_09_317Z-debug-0.log superagi-main-gui-1 | superagi-main-gui-1 | > [email protected] dev superagi-main-gui-1 | > next dev superagi-main-gui-1 | superagi-main-gui-1 | - ready started server on 0.0.0.0:3000, url: http://localhost:3000 superagi-main-gui-1 | - event compiled client and server successfully in 37s (1314 modules) superagi-main-gui-1 | - wait compiling... superagi-main-gui-1 | - event compiled client and server successfully in 4.1s (1314 modules) superagi-main-gui-1 | - wait compiling /_error (client and server)... superagi-main-gui-1 | - event compiled client and server successfully in 860 ms (1315 modules) superagi-main-gui-1 | Do not add stylesheets using next/head (see <link rel="stylesheet"> tag with href="https://fonts.googleapis.com/css2?family=Source+Code+Pro&display=swap"). Use Document instead. superagi-main-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-main-super__redis-1 | 1:M 15 Jun 2023 09:39:27.021 * Background saving started by pid 28 superagi-main-super__redis-1 | 28:C 15 Jun 2023 09:39:27.026 * DB saved on disk superagi-main-celery-1 | superagi-main-super__redis-1 | 28:C 15 Jun 2023 09:39:27.026 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 09:39:27.121 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 10:39:28.084 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 10:39:28.085 * Background saving started by pid 29 superagi-main-super__redis-1 | 29:C 15 Jun 2023 10:39:28.093 * DB saved on disk superagi-main-super__redis-1 | 29:C 15 Jun 2023 10:39:28.093 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__postgres-1 | selecting default max_connections ... 100 superagi-main-super__postgres-1 | selecting default shared_buffers ... 128MB superagi-main-super__postgres-1 | selecting default time zone ... Etc/UTC superagi-main-super__postgres-1 | creating configuration files ... ok superagi-main-super__postgres-1 | running bootstrap script ... ok superagi-main-super__postgres-1 | performing post-bootstrap initialization ... ok superagi-main-super__postgres-1 | initdb: warning: enabling "trust" authentication for local connections superagi-main-super__postgres-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-main-super__postgres-1 | syncing data to disk ... ok superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | Success. You can now start the database server using: superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | pg_ctl -D /var/lib/postgresql/data -l logfile start superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | waiting for server to start....2023-06-15 02:08:23.652 UTC [48] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit superagi-main-super__redis-1 | 1:M 15 Jun 2023 10:39:28.185 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 11:39:29.022 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 11:39:29.022 * Background saving started by pid 30 superagi-main-super__redis-1 | 30:C 15 Jun 2023 11:39:29.028 * DB saved on disk superagi-main-super__redis-1 | 30:C 15 Jun 2023 11:39:29.028 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 11:39:29.123 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 12:39:30.090 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 12:39:30.093 * Background saving started by pid 31 superagi-main-super__redis-1 | 31:C 15 Jun 2023 12:39:30.097 * DB saved on disk superagi-main-celery-1 | [2023-06-15 20:00:55,918: INFO/MainProcess] Connected to redis://super__redis:6379/0 superagi-main-celery-1 | [2023-06-15 20:00:55,926: INFO/MainProcess] mingle: searching for neighbors superagi-main-celery-1 | [2023-06-15 20:00:56,960: INFO/MainProcess] mingle: all alone superagi-main-celery-1 | [2023-06-15 20:00:56,988: INFO/MainProcess] celery@ea59d3726db5 ready. superagi-main-celery-1 | superagi-main-celery-1 | worker: Warm shutdown (MainProcess) superagi-main-gui-1 | Do not add stylesheets using next/head (see <link rel="stylesheet"> tag with href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&display=swap"). Use Document instead. superagi-main-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-main-gui-1 | - wait compiling /favicon.ico/route (client and server)... superagi-main-gui-1 | - event compiled successfully in 118 ms (146 modules) superagi-main-gui-1 | npm ERR! path /app superagi-main-gui-1 | npm ERR! command failed superagi-main-gui-1 | npm ERR! signal SIGTERM superagi-main-gui-1 | npm ERR! command sh -c next dev superagi-main-gui-1 | superagi-main-gui-1 | npm ERR! A complete log of this run can be found in: superagi-main-gui-1 | npm ERR! /root/.npm/_logs/2023-06-15T20_00_38_804Z-debug-0.log superagi-main-super__redis-1 | 31:C 15 Jun 2023 12:39:30.097 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 12:39:30.193 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 13:39:31.055 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 13:39:31.055 * Background saving started by pid 32 superagi-main-super__redis-1 | 32:C 15 Jun 2023 13:39:31.061 * DB saved on disk superagi-main-super__redis-1 | 32:C 15 Jun 2023 13:39:31.061 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 13:39:31.156 * Background saving terminated with success superagi-main-super__redis-1 | 1:signal-handler (1686839298) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 14:28:18.830 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 14:28:18.831 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 14:28:18.842 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 14:28:18.844 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 15:59:35.836 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 15:59:35.839 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 15:59:35.839 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.841 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.853 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.854 # Server initialized superagi-main-super__postgres-1 | 2023-06-15 02:08:23.665 UTC [48] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-main-super__postgres-1 | 2023-06-15 02:08:23.700 UTC [51] LOG: database system was shut down at 2023-06-15 02:08:22 UTC superagi-main-super__postgres-1 | 2023-06-15 02:08:23.777 UTC [48] LOG: database system is ready to accept connections superagi-main-backend-1 | INFO: 172.18.0.1:37612 - "GET /agentexecutions/get/agent/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:37628 - "GET /agents/get/details/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:37612 - "GET /agentexecutionfeeds/get/execution/2 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:37612 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:50460 - "GET /agentexecutionfeeds/get/execution/2 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:50460 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request superagi-main-backend-1 | INFO: 172.18.0.1:50460 - "GET /agents/get/details/4 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:59428 - "GET /agentexecutions/get/agent/4 HTTP/1.1" 200 OK superagi-main-super__postgres-1 | done superagi-main-super__postgres-1 | server started superagi-main-super__postgres-1 | CREATE DATABASE superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.855 # 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-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.867 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.867 * RDB age 5477 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.867 * RDB memory usage when created 1.43 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.870 * Done loading RDB, keys loaded: 10, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.871 * DB loaded from disk: 0.008 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 15:59:35.871 * Ready to accept connections superagi-main-super__redis-1 | 1:M 15 Jun 2023 16:48:07.237 * 100 changes in 300 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 16:48:07.251 * Background saving started by pid 19 superagi-main-super__redis-1 | 19:C 15 Jun 2023 16:48:07.264 * DB saved on disk superagi-main-super__redis-1 | 19:C 15 Jun 2023 16:48:07.264 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 16:48:07.354 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 17:48:08.087 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 17:48:08.089 * Background saving started by pid 20 superagi-main-super__redis-1 | 20:C 15 Jun 2023 17:48:08.101 * DB saved on disk superagi-main-super__redis-1 | 20:C 15 Jun 2023 17:48:08.101 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 17:48:08.189 * Background saving terminated with success superagi-main-super__redis-1 | 1:M 15 Jun 2023 18:48:09.042 * 1 changes in 3600 seconds. Saving... superagi-main-super__redis-1 | 1:M 15 Jun 2023 18:48:09.044 * Background saving started by pid 21 superagi-main-super__redis-1 | 21:C 15 Jun 2023 18:48:09.053 * DB saved on disk superagi-main-super__redis-1 | 21:C 15 Jun 2023 18:48:09.053 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB superagi-main-super__redis-1 | 1:M 15 Jun 2023 18:48:09.145 * Background saving terminated with success superagi-main-super__redis-1 | 1:signal-handler (1686857484) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:24.107 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:24.107 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:24.112 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:24.113 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:31:33.475 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:31:33.475 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:31:33.475 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.478 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.483 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.483 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.484 # 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-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.532 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.532 * RDB age 9 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.532 * RDB memory usage when created 1.44 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.533 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.533 * DB loaded from disk: 0.002 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:31:33.534 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686857991) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:39:51.663 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:39:51.665 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:39:51.679 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:39:51.680 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:41:11.439 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:41:11.439 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:41:11.439 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.440 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.446 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.446 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.446 # 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-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.455 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.455 * RDB age 80 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.455 * RDB memory usage when created 1.20 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.456 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.456 * DB loaded from disk: 0.004 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:41:11.456 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686858288) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:44:48.866 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:44:48.870 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:44:48.912 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:44:48.913 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:45:01.684 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:45:01.685 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:45:01.685 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.686 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.694 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.694 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.695 # 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-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.699 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.699 * RDB age 13 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.699 * RDB memory usage when created 1.20 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.701 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.701 * DB loaded from disk: 0.002 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:45:01.701 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686858506) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:48:26.275 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:48:26.279 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:48:26.303 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:48:26.305 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:49:07.278 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:49:07.279 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 19:49:07.279 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.280 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.283 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.284 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.284 # 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-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * RDB age 41 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * RDB memory usage when created 0.85 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * DB loaded from disk: 0.001 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:49:07.287 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686858750) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:52:30.466 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:52:30.468 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:52:30.492 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 19:52:30.494 # Redis is now ready to exit, bye bye... superagi-main-super__redis-1 | 1:C 15 Jun 2023 20:00:34.872 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-main-super__redis-1 | 1:C 15 Jun 2023 20:00:34.872 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-main-super__redis-1 | 1:C 15 Jun 2023 20:00:34.872 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.877 * monotonic clock: POSIX clock_gettime superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.914 * Running mode=standalone, port=6379. superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.916 # Server initialized superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.917 # 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-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.940 * Loading RDB produced by version 7.0.11 superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.941 * RDB age 484 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.942 * RDB memory usage when created 0.85 Mb superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.946 * Done loading RDB, keys loaded: 11, keys expired: 0. superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.946 * DB loaded from disk: 0.013 seconds superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:00:34.948 * Ready to accept connections superagi-main-super__redis-1 | 1:signal-handler (1686859358) Received SIGTERM scheduling shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:02:38.949 # User requested shutdown... superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:02:38.952 * Saving the final RDB snapshot before exiting. superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:02:38.986 * DB saved on disk superagi-main-super__redis-1 | 1:M 15 Jun 2023 20:02:38.986 # Redis is now ready to exit, bye bye... superagi-main-backend-1 | INFO: 172.18.0.1:59428 - "GET /agentexecutionfeeds/get/execution/5 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:59428 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:59428 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request superagi-main-backend-1 | INFO: 172.18.0.1:50460 - "GET /agents/get/details/3 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:50460 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request superagi-main-backend-1 | INFO: 172.18.0.1:59428 - "GET /agents/get/details/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:59444 - "GET /agentexecutions/get/agent/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:59444 - "GET /agentexecutionfeeds/get/execution/2 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:59444 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: 172.18.0.1:42572 - "GET /agentexecutionfeeds/get/execution/2 HTTP/1.1" 200 OK superagi-main-backend-1 | INFO: Shutting down superagi-main-backend-1 | INFO: Waiting for application shutdown. superagi-main-backend-1 | INFO: Application shutdown complete. superagi-main-backend-1 | INFO: Finished server process [20] superagi-main-backend-1 | INFO: Stopping reloader process [1] superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/* superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | 2023-06-15 02:08:27.139 UTC [48] LOG: received fast shutdown request superagi-main-super__postgres-1 | waiting for server to shut down....2023-06-15 02:08:27.169 UTC [48] LOG: aborting any active transactions superagi-main-super__postgres-1 | 2023-06-15 02:08:27.195 UTC [48] LOG: background worker "logical replication launcher" (PID 54) exited with exit code 1 superagi-main-super__postgres-1 | 2023-06-15 02:08:27.208 UTC [49] LOG: shutting down superagi-main-super__postgres-1 | 2023-06-15 02:08:27.218 UTC [49] LOG: checkpoint starting: shutdown immediate superagi-main-super__postgres-1 | 2023-06-15 02:08:27.753 UTC [49] LOG: checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.380 s, sync=0.115 s, total=0.545 s; sync files=250, longest=0.005 s, average=0.001 s; distance=4223 kB, estimate=4223 kB superagi-main-super__postgres-1 | 2023-06-15 02:08:27.805 UTC [48] LOG: database system is shut down superagi-main-super__postgres-1 | done superagi-main-super__postgres-1 | server stopped superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | PostgreSQL init process complete; ready for start up. superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | 2023-06-15 02:08:27.946 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit superagi-main-super__postgres-1 | 2023-06-15 02:08:27.949 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-main-super__postgres-1 | 2023-06-15 02:08:27.949 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-main-super__postgres-1 | 2023-06-15 02:08:27.954 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-main-super__postgres-1 | 2023-06-15 02:08:27.965 UTC [64] LOG: database system was shut down at 2023-06-15 02:08:27 UTC superagi-main-super__postgres-1 | 2023-06-15 02:08:27.981 UTC [1] LOG: database system is ready to accept connections superagi-main-super__postgres-1 | 2023-06-15 02:13:28.061 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 02:13:48.155 UTC [62] LOG: checkpoint complete: wrote 201 buffers (1.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=20.062 s, sync=0.011 s, total=20.096 s; sync files=90, longest=0.003 s, average=0.001 s; distance=954 kB, estimate=954 kB superagi-main-super__postgres-1 | 2023-06-15 02:33:29.239 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 02:33:32.108 UTC [62] LOG: checkpoint complete: wrote 29 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.840 s, sync=0.012 s, total=2.870 s; sync files=22, longest=0.003 s, average=0.001 s; distance=23 kB, estimate=861 kB superagi-main-super__postgres-1 | 2023-06-15 02:48:29.400 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 02:48:31.473 UTC [62] LOG: checkpoint complete: wrote 21 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.042 s, sync=0.007 s, total=2.074 s; sync files=15, longest=0.003 s, average=0.001 s; distance=7 kB, estimate=775 kB superagi-main-super__postgres-1 | 2023-06-15 02:53:29.572 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 02:53:31.814 UTC [62] LOG: checkpoint complete: wrote 23 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.219 s, sync=0.009 s, total=2.242 s; sync files=23, longest=0.002 s, average=0.001 s; distance=24 kB, estimate=700 kB superagi-main-super__postgres-1 | 2023-06-15 02:58:29.911 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 02:58:30.030 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.103 s, sync=0.006 s, total=0.120 s; sync files=2, longest=0.004 s, average=0.003 s; distance=5 kB, estimate=631 kB superagi-main-super__postgres-1 | 2023-06-15 03:08:29.131 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 03:08:30.381 UTC [62] LOG: checkpoint complete: wrote 13 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.212 s, sync=0.012 s, total=1.251 s; sync files=13, longest=0.005 s, average=0.001 s; distance=22 kB, estimate=570 kB superagi-main-super__postgres-1 | 2023-06-15 03:13:29.470 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 03:13:29.600 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.104 s, sync=0.010 s, total=0.131 s; sync files=2, longest=0.009 s, average=0.005 s; distance=5 kB, estimate=513 kB superagi-main-super__postgres-1 | 2023-06-15 03:18:29.693 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 03:18:30.936 UTC [62] LOG: checkpoint complete: wrote 13 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.222 s, sync=0.009 s, total=1.244 s; sync files=7, longest=0.004 s, average=0.002 s; distance=67 kB, estimate=469 kB superagi-main-super__postgres-1 | 2023-06-15 03:33:30.233 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 03:33:30.857 UTC [62] LOG: checkpoint complete: wrote 7 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.604 s, sync=0.007 s, total=0.624 s; sync files=5, longest=0.004 s, average=0.002 s; distance=20 kB, estimate=424 kB superagi-main-super__postgres-1 | 2023-06-15 03:39:37.428 UTC [491] FATAL: sorry, too many clients already superagi-main-super__postgres-1 | 2023-06-15 03:40:08.638 UTC [494] FATAL: sorry, too many clients already superagi-main-super__postgres-1 | 2023-06-15 03:43:31.055 UTC [62] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 03:43:31.168 UTC [62] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.102 s, sync=0.002 s, total=0.114 s; sync files=2, longest=0.001 s, average=0.001 s; distance=1 kB, estimate=382 kB superagi-main-super__postgres-1 | 2023-06-15 14:28:09.691 UTC [484] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.690 UTC [480] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.692 UTC [490] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.694 UTC [483] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.694 UTC [487] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.694 UTC [489] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.704 UTC [441] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.705 UTC [486] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.707 UTC [442] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.713 UTC [477] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.728 UTC [254] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.730 UTC [445] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.734 UTC [438] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.737 UTC [158] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.743 UTC [344] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.756 UTC [289] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.758 UTC [261] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.761 UTC [449] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.763 UTC [266] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.764 UTC [244] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.781 UTC [263] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.783 UTC [253] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.787 UTC [210] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.790 UTC [339] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.800 UTC [243] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.811 UTC [479] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.812 UTC [476] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.822 UTC [214] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.823 UTC [215] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.821 UTC [450] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.823 UTC [345] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.853 UTC [288] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.865 UTC [211] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.871 UTC [159] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.872 UTC [268] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.880 UTC [444] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.891 UTC [143] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:09.902 UTC [439] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 14:28:18.837 UTC [1] LOG: received fast shutdown request superagi-main-super__postgres-1 | 2023-06-15 14:28:18.842 UTC [1] LOG: aborting any active transactions superagi-main-super__postgres-1 | 2023-06-15 14:28:18.850 UTC [1] LOG: background worker "logical replication launcher" (PID 67) exited with exit code 1 superagi-main-super__postgres-1 | 2023-06-15 14:28:18.861 UTC [62] LOG: shutting down superagi-main-super__postgres-1 | 2023-06-15 14:28:18.864 UTC [62] LOG: checkpoint starting: shutdown immediate superagi-main-super__postgres-1 | 2023-06-15 14:28:18.892 UTC [62] LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.019 s, sync=0.001 s, total=0.030 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=343 kB superagi-main-super__postgres-1 | 2023-06-15 14:28:18.915 UTC [1] LOG: database system is shut down superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | 2023-06-15 15:59:36.652 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit superagi-main-super__postgres-1 | 2023-06-15 15:59:36.675 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-main-super__postgres-1 | 2023-06-15 15:59:36.675 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-main-super__postgres-1 | 2023-06-15 15:59:36.680 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-main-super__postgres-1 | 2023-06-15 15:59:36.688 UTC [29] LOG: database system was shut down at 2023-06-15 14:28:18 UTC superagi-main-super__postgres-1 | 2023-06-15 15:59:36.713 UTC [1] LOG: database system is ready to accept connections superagi-main-super__postgres-1 | 2023-06-15 16:04:36.812 UTC [27] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 16:04:39.950 UTC [27] LOG: checkpoint complete: wrote 33 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=3.046 s, sync=0.007 s, total=3.140 s; sync files=30, longest=0.003 s, average=0.001 s; distance=29 kB, estimate=29 kB superagi-main-super__postgres-1 | 2023-06-15 19:31:20.725 UTC [62] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.725 UTC [58] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.728 UTC [55] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.730 UTC [54] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.732 UTC [61] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.745 UTC [45] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.752 UTC [52] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.753 UTC [57] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.760 UTC [51] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.763 UTC [48] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:20.768 UTC [47] LOG: unexpected EOF on client connection with an open transaction superagi-main-super__postgres-1 | 2023-06-15 19:31:24.034 UTC [1] LOG: received fast shutdown request superagi-main-super__postgres-1 | 2023-06-15 19:31:24.039 UTC [1] LOG: aborting any active transactions superagi-main-super__postgres-1 | 2023-06-15 19:31:24.064 UTC [1] LOG: background worker "logical replication launcher" (PID 32) exited with exit code 1 superagi-main-super__postgres-1 | 2023-06-15 19:31:24.069 UTC [27] LOG: shutting down superagi-main-super__postgres-1 | 2023-06-15 19:31:24.072 UTC [27] LOG: checkpoint starting: shutdown immediate superagi-main-super__postgres-1 | 2023-06-15 19:31:24.117 UTC [27] LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.024 s, sync=0.001 s, total=0.047 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=26 kB superagi-main-super__postgres-1 | 2023-06-15 19:31:24.150 UTC [1] LOG: database system is shut down superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | 2023-06-15 19:31:34.846 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit superagi-main-super__postgres-1 | 2023-06-15 19:31:34.927 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-main-super__postgres-1 | 2023-06-15 19:31:34.928 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-main-super__postgres-1 | 2023-06-15 19:31:34.932 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-main-super__postgres-1 | 2023-06-15 19:31:34.956 UTC [29] LOG: database system was shut down at 2023-06-15 19:31:24 UTC superagi-main-super__postgres-1 | 2023-06-15 19:31:34.998 UTC [1] LOG: database system is ready to accept connections superagi-main-super__postgres-1 | 2023-06-15 19:36:34.694 UTC [27] LOG: checkpoint starting: time superagi-main-super__postgres-1 | 2023-06-15 19:36:34.855 UTC [27] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.129 s, sync=0.008 s, total=0.165 s; sync files=3, longest=0.005 s, average=0.003 s; distance=5 kB, estimate=5 kB superagi-main-super__postgres-1 | 2023-06-15 19:39:51.607 UTC [1] LOG: received fast shutdown request superagi-main-super__postgres-1 | 2023-06-15 19:39:51.612 UTC [1] LOG: aborting any active transactions superagi-main-super__postgres-1 | 2023-06-15 19:39:51.628 UTC [1] LOG: background worker "logical replication launcher" (PID 32) exited with exit code 1 superagi-main-super__postgres-1 | 2023-06-15 19:39:51.632 UTC [27] LOG: shutting down superagi-main-super__postgres-1 | 2023-06-15 19:39:51.636 UTC [27] LOG: checkpoint starting: shutdown immediate superagi-main-super__postgres-1 | 2023-06-15 19:39:51.668 UTC [27] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.016 s, sync=0.003 s, total=0.036 s; sync files=2, longest=0.002 s, average=0.002 s; distance=6 kB, estimate=6 kB superagi-main-super__postgres-1 | 2023-06-15 19:39:51.679 UTC [1] LOG: database system is shut down superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | 2023-06-15 19:41:11.884 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit superagi-main-super__postgres-1 | 2023-06-15 19:41:11.926 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-main-super__postgres-1 | 2023-06-15 19:41:11.926 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-main-super__postgres-1 | 2023-06-15 19:41:11.931 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-main-super__postgres-1 | 2023-06-15 19:41:11.942 UTC [30] LOG: database system was shut down at 2023-06-15 19:39:51 UTC superagi-main-super__postgres-1 | 2023-06-15 19:41:11.971 UTC [1] LOG: database system is ready to accept connections superagi-main-super__postgres-1 | 2023-06-15 19:44:48.863 UTC [1] LOG: received fast shutdown request superagi-main-super__postgres-1 | 2023-06-15 19:44:48.880 UTC [1] LOG: aborting any active transactions superagi-main-super__postgres-1 | 2023-06-15 19:44:48.895 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1 superagi-main-super__postgres-1 | 2023-06-15 19:44:48.928 UTC [28] LOG: shutting down superagi-main-super__postgres-1 | 2023-06-15 19:44:48.934 UTC [28] LOG: checkpoint starting: shutdown immediate superagi-main-super__postgres-1 | 2023-06-15 19:44:49.022 UTC [28] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.042 s, sync=0.004 s, total=0.090 s; sync files=3, longest=0.003 s, average=0.002 s; distance=6 kB, estimate=6 kB superagi-main-super__postgres-1 | 2023-06-15 19:44:49.041 UTC [1] LOG: database system is shut down superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | 2023-06-15 19:45:02.503 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit superagi-main-super__postgres-1 | 2023-06-15 19:45:02.635 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-main-super__postgres-1 | 2023-06-15 19:45:02.636 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-main-super__postgres-1 | 2023-06-15 19:45:02.642 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-main-super__postgres-1 | 2023-06-15 19:45:02.665 UTC [29] LOG: database system was shut down at 2023-06-15 19:44:49 UTC superagi-main-super__postgres-1 | 2023-06-15 19:45:02.699 UTC [1] LOG: database system is ready to accept connections superagi-main-super__postgres-1 | 2023-06-15 19:48:26.214 UTC [1] LOG: received fast shutdown request superagi-main-super__postgres-1 | 2023-06-15 19:48:26.245 UTC [1] LOG: aborting any active transactions superagi-main-super__postgres-1 | 2023-06-15 19:48:26.263 UTC [1] LOG: background worker "logical replication launcher" (PID 32) exited with exit code 1 superagi-main-super__postgres-1 | 2023-06-15 19:48:26.292 UTC [27] LOG: shutting down superagi-main-super__postgres-1 | 2023-06-15 19:48:26.296 UTC [27] LOG: checkpoint starting: shutdown immediate superagi-main-super__postgres-1 | 2023-06-15 19:48:26.386 UTC [27] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.051 s, sync=0.004 s, total=0.094 s; sync files=2, longest=0.003 s, average=0.002 s; distance=0 kB, estimate=0 kB superagi-main-super__postgres-1 | 2023-06-15 19:48:26.440 UTC [1] LOG: database system is shut down superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | 2023-06-15 19:49:07.558 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit superagi-main-super__postgres-1 | 2023-06-15 19:49:07.560 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-main-super__postgres-1 | 2023-06-15 19:49:07.560 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-main-super__postgres-1 | 2023-06-15 19:49:07.564 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-main-super__postgres-1 | 2023-06-15 19:49:07.577 UTC [29] LOG: database system was shut down at 2023-06-15 19:48:26 UTC superagi-main-super__postgres-1 | 2023-06-15 19:49:07.652 UTC [1] LOG: database system is ready to accept connections superagi-main-super__postgres-1 | 2023-06-15 19:52:30.379 UTC [1] LOG: received fast shutdown request superagi-main-super__postgres-1 | 2023-06-15 19:52:30.386 UTC [1] LOG: aborting any active transactions superagi-main-super__postgres-1 | 2023-06-15 19:52:30.395 UTC [1] LOG: background worker "logical replication launcher" (PID 32) exited with exit code 1 superagi-main-super__postgres-1 | 2023-06-15 19:52:30.405 UTC [27] LOG: shutting down superagi-main-super__postgres-1 | 2023-06-15 19:52:30.409 UTC [27] LOG: checkpoint starting: shutdown immediate superagi-main-super__postgres-1 | 2023-06-15 19:52:30.435 UTC [27] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.013 s, sync=0.002 s, total=0.029 s; sync files=2, longest=0.002 s, average=0.001 s; distance=0 kB, estimate=0 kB superagi-main-super__postgres-1 | 2023-06-15 19:52:30.447 UTC [1] LOG: database system is shut down superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-main-super__postgres-1 | superagi-main-super__postgres-1 | 2023-06-15 20:00:35.981 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit superagi-main-super__postgres-1 | 2023-06-15 20:00:35.991 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-main-super__postgres-1 | 2023-06-15 20:00:35.992 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-main-super__postgres-1 | 2023-06-15 20:00:35.999 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-main-super__postgres-1 | 2023-06-15 20:00:36.032 UTC [30] LOG: database system was shut down at 2023-06-15 19:52:30 UTC superagi-main-super__postgres-1 | 2023-06-15 20:00:36.095 UTC [1] LOG: database system is ready to accept connections superagi-main-super__postgres-1 | 2023-06-15 20:02:38.964 UTC [1] LOG: received fast shutdown request superagi-main-super__postgres-1 | 2023-06-15 20:02:38.980 UTC [1] LOG: aborting any active transactions superagi-main-super__postgres-1 | 2023-06-15 20:02:39.015 UTC [1] LOG: background worker "logical replication launcher" (PID 34) exited with exit code 1 superagi-main-super__postgres-1 | 2023-06-15 20:02:39.028 UTC [28] LOG: shutting down superagi-main-super__postgres-1 | 2023-06-15 20:02:39.033 UTC [28] LOG: checkpoint starting: shutdown immediate superagi-main-super__postgres-1 | 2023-06-15 20:02:39.138 UTC [28] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.048 s, sync=0.011 s, total=0.098 s; sync files=3, longest=0.008 s, average=0.004 s; distance=7 kB, estimate=7 kB superagi-main-super__postgres-1 | 2023-06-15 20:02:39.163 UTC [1] LOG: database system is shut down `

Again I'm on windows 11 and Config file is setup correctly.

I get Calls and Tokens spent amount that shows up but no reply/ Response shows up just stuck at thinking from the SuperAGI agent when running its either stuck on thinking loop and or at points when loaded back up then stuck on Initializing loop

WIndows's 11 is up to date and So is WSL

[iskandarreza]

I'm on Windows as well and had the same exact issue.

What does your .wslconfig file look like? It should be in your C:/Users/<username> folder

[Starblue0]

[wsl2] memory=4GB # Limits VM memory in WSL 2 to 4 GB processors=2 # Makes the WSL 2 VM use two virtual processors

[Talelo]

Experiencing the same exact issue, on both Win11 and Macbook Air ... Installation successful, but when I create an agent, it consumes tokens and keeps thinking with no output. In the console I can see the same error happening on both MacOS and Windows. Thanks for your help.

[neelayan7]

172.18.0.1:42126 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request We are noticing this error in the logs. I think because of this, you are not getting any feed and the agent is stuck on thinking. SuperAgi might be working in the backend and feed should be getting stored in the database, but due to this error maybe you're not seeing it in the frontend. Can you go to the network tab and send/check the http request body for this api call?

[Talelo]

Here's the HAR , converted to CSV. I hope that helps output.csv

[neelayan7]

This doesn't contain the request body, only the URL, can you send the request body?

[Talelo]

@neelayan7 here's the new HAR, note that the conversion to CSV was the issue for not getting the request Body. Please change the extension to HAR. I didn't convert it this time 400BadRequest_Win11_4.csv

[Starblue0]

2023-06-15 14:00:43 superagi-main-celery-1 | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main 2023-06-15 14:00:53 superagi-main-celery-1 | /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is 2023-06-15 14:00:53 superagi-main-celery-1 | absolutely not recommended! 2023-06-15 14:00:53 superagi-main-celery-1 | 2023-06-15 14:00:53 superagi-main-celery-1 | Please specify a different user using the --uid option. 2023-06-15 14:00:35 superagi-main-backend-1 | wait-for-it.sh: waiting 60 seconds for super__postgres:5432 2023-06-15 14:00:36 superagi-main-backend-1 | wait-for-it.sh: super__postgres:5432 is available after 1 seconds 2023-06-15 14:00:41 superagi-main-backend-1 | INFO [alembic.runtime.migration] Context impl PostgresqlImpl. 2023-06-15 14:00:41 superagi-main-backend-1 | INFO [alembic.runtime.migration] Will assume transactional DDL. 2023-06-15 14:00:42 superagi-main-backend-1 | INFO: Will watch for changes in these directories: ['/app'] 2023-06-15 14:00:42 superagi-main-backend-1 | INFO: Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit) 2023-06-15 14:00:53 superagi-main-celery-1 | 2023-06-15 14:00:53 superagi-main-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 2023-06-15 14:00:53 superagi-main-celery-1 | 2023-06-15 14:00:53 superagi-main-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( 2023-06-15 14:00:53 superagi-main-celery-1 | 2023-06-15 14:00:53 superagi-main-celery-1 | -------------- celery@ea59d3726db5 v5.2.7 (dawn-chorus) 2023-06-15 14:00:53 superagi-main-celery-1 | --- ***** ----- 2023-06-15 14:00:53 superagi-main-celery-1 | -- ******* ---- Linux-5.15.90.1-microsoft-standard-WSL2-x86_64-with-glibc2.36 2023-06-15 20:00:53 2023-06-15 14:00:53 superagi-main-celery-1 | - *** --- * --- 2023-06-15 14:00:53 superagi-main-celery-1 | - ** ---------- [config] 2023-06-15 14:00:53 superagi-main-celery-1 | - ** ---------- .> app: superagi:0x7f0e97ed34f0 2023-06-15 14:00:53 superagi-main-celery-1 | - ** ---------- .> transport: redis://super__redis:6379/0 2023-06-15 14:00:53 superagi-main-celery-1 | - ** ---------- .> results: redis://super__redis:6379/0 2023-06-15 14:00:53 superagi-main-celery-1 | - *** --- * --- .> concurrency: 10 (prefork) 2023-06-15 14:00:53 superagi-main-celery-1 | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) 2023-06-15 14:00:53 superagi-main-celery-1 | --- ***** ----- 2023-06-15 14:00:53 superagi-main-celery-1 | -------------- [queues] 2023-06-15 14:00:53 superagi-main-celery-1 | .> celery exchange=celery(direct) key=celery 2023-06-15 14:00:53 superagi-main-celery-1 | 2023-06-15 14:00:53 superagi-main-celery-1 | 2023-06-15 14:00:53 superagi-main-celery-1 | [tasks] 2023-06-15 14:00:53 superagi-main-celery-1 | . execute_agent 2023-06-15 14:00:53 superagi-main-celery-1 | 2023-06-15 14:00:55 superagi-main-celery-1 | [2023-06-15 20:00:55,918: INFO/MainProcess] Connected to redis://super__redis:6379/0 2023-06-15 14:00:55 superagi-main-celery-1 | [2023-06-15 20:00:55,926: INFO/MainProcess] mingle: searching for neighbors 2023-06-15 14:00:56 superagi-main-celery-1 | [2023-06-15 20:00:56,960: INFO/MainProcess] mingle: all alone 2023-06-15 14:00:56 superagi-main-celery-1 | [2023-06-15 20:00:56,988: INFO/MainProcess] celery@ea59d3726db5 ready. 2023-06-15 14:02:30 superagi-main-celery-1 | 2023-06-15 14:02:30 superagi-main-celery-1 | worker: Warm shutdown (MainProcess) 2023-06-15 16:25:42 superagi-main-celery-1 | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main 2023-06-15 16:25:59 superagi-main-celery-1 | /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is 2023-06-15 16:25:59 superagi-main-celery-1 | absolutely not recommended! 2023-06-15 16:25:59 superagi-main-celery-1 | 2023-06-15 16:25:59 superagi-main-celery-1 | Please specify a different user using the --uid option. 2023-06-15 16:25:59 superagi-main-celery-1 | 2023-06-15 16:25:59 superagi-main-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 2023-06-15 16:25:59 superagi-main-celery-1 | 2023-06-15 16:25:59 superagi-main-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( 2023-06-15 16:25:59 superagi-main-celery-1 | 2023-06-15 16:25:59 superagi-main-celery-1 | -------------- celery@ea59d3726db5 v5.2.7 (dawn-chorus) 2023-06-15 16:25:59 superagi-main-celery-1 | --- ***** ----- 2023-06-15 16:25:59 superagi-main-celery-1 | -- ******* ---- Linux-5.15.90.1-microsoft-standard-WSL2-x86_64-with-glibc2.36 2023-06-15 22:25:59 2023-06-15 16:25:59 superagi-main-celery-1 | - *** --- * --- 2023-06-15 16:25:59 superagi-main-celery-1 | - ** ---------- [config] 2023-06-15 16:25:59 superagi-main-celery-1 | - ** ---------- .> app: superagi:0x7fd618aefeb0 2023-06-15 16:25:59 superagi-main-celery-1 | - ** ---------- .> transport: redis://super__redis:6379/0 2023-06-15 16:25:59 superagi-main-celery-1 | - ** ---------- .> results: redis://super__redis:6379/0 2023-06-15 16:25:59 superagi-main-celery-1 | - *** --- * --- .> concurrency: 10 (prefork) 2023-06-15 16:25:59 superagi-main-celery-1 | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) 2023-06-15 16:25:59 superagi-main-celery-1 | --- ***** ----- 2023-06-15 16:25:59 superagi-main-celery-1 | -------------- [queues] 2023-06-15 16:25:59 superagi-main-celery-1 | .> celery exchange=celery(direct) key=celery 2023-06-15 16:25:59 superagi-main-celery-1 | 2023-06-15 16:25:59 superagi-main-celery-1 | 2023-06-15 16:25:59 superagi-main-celery-1 | [tasks] 2023-06-15 16:25:59 superagi-main-celery-1 | . execute_agent 2023-06-15 16:25:59 superagi-main-celery-1 | 2023-06-15 16:26:10 superagi-main-celery-1 | [2023-06-15 22:26:10,100: INFO/MainProcess] Connected to redis://super__redis:6379/0 2023-06-15 16:26:10 superagi-main-celery-1 | [2023-06-15 22:26:10,139: INFO/MainProcess] mingle: searching for neighbors 2023-06-15 16:26:11 superagi-main-celery-1 | [2023-06-15 22:26:11,208: INFO/MainProcess] mingle: all alone 2023-06-15 16:26:11 superagi-main-celery-1 | [2023-06-15 22:26:11,341: INFO/MainProcess] celery@ea59d3726db5 ready. 2023-06-15 16:31:34 superagi-main-celery-1 | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main 2023-06-15 16:31:40 superagi-main-celery-1 | /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is 2023-06-15 16:31:40 superagi-main-celery-1 | absolutely not recommended! 2023-06-15 16:31:40 superagi-main-celery-1 | 2023-06-15 16:31:40 superagi-main-celery-1 | Please specify a different user using the --uid option. 2023-06-15 16:31:40 superagi-main-celery-1 | 2023-06-15 16:31:40 superagi-main-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 2023-06-15 16:31:40 superagi-main-celery-1 | 2023-06-15 16:31:40 superagi-main-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( 2023-06-15 16:31:40 superagi-main-celery-1 | 2023-06-15 16:31:40 superagi-main-celery-1 | -------------- celery@ea59d3726db5 v5.2.7 (dawn-chorus) 2023-06-15 16:31:40 superagi-main-celery-1 | --- ***** ----- 2023-06-15 16:31:40 superagi-main-celery-1 | -- ******* ---- Linux-5.15.90.1-microsoft-standard-WSL2-x86_64-with-glibc2.36 2023-06-15 22:31:40 2023-06-15 16:31:40 superagi-main-celery-1 | - *** --- * --- 2023-06-15 16:31:40 superagi-main-celery-1 | - ** ---------- [config] 2023-06-15 16:31:40 superagi-main-celery-1 | - ** ---------- .> app: superagi:0x7f6942800eb0 2023-06-15 16:31:40 superagi-main-celery-1 | - ** ---------- .> transport: redis://super__redis:6379/0 2023-06-15 16:31:40 superagi-main-celery-1 | - ** ---------- .> results: redis://super__redis:6379/0 2023-06-15 16:31:40 superagi-main-celery-1 | - *** --- * --- .> concurrency: 10 (prefork) 2023-06-15 16:31:40 superagi-main-celery-1 | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) 2023-06-15 16:31:40 superagi-main-celery-1 | --- ***** ----- 2023-06-15 16:31:40 superagi-main-celery-1 | -------------- [queues] 2023-06-15 16:31:40 superagi-main-celery-1 | .> celery exchange=celery(direct) key=celery 2023-06-15 16:31:40 superagi-main-celery-1 | 2023-06-15 16:31:40 superagi-main-celery-1 | 2023-06-15 16:31:40 superagi-main-celery-1 | [tasks] 2023-06-15 16:31:40 superagi-main-celery-1 | . execute_agent 2023-06-15 16:31:40 superagi-main-celery-1 | 2023-06-15 16:31:49 superagi-main-celery-1 | [2023-06-15 22:31:49,832: INFO/MainProcess] Connected to redis://super__redis:6379/0 2023-06-15 16:31:49 superagi-main-celery-1 | [2023-06-15 22:31:49,843: INFO/MainProcess] mingle: searching for neighbors 2023-06-15 16:31:50 superagi-main-celery-1 | [2023-06-15 22:31:50,873: INFO/MainProcess] mingle: all alone 2023-06-15 16:31:50 superagi-main-celery-1 | [2023-06-15 22:31:50,905: INFO/MainProcess] celery@ea59d3726db5 ready. 2023-06-15 18:12:10 superagi-main-celery-1 | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main 2023-06-15 18:12:14 superagi-main-celery-1 | /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is 2023-06-15 18:12:14 superagi-main-celery-1 | absolutely not recommended! 2023-06-15 18:12:14 superagi-main-celery-1 | 2023-06-15 18:12:14 superagi-main-celery-1 | Please specify a different user using the --uid option. 2023-06-15 18:12:14 superagi-main-celery-1 | 2023-06-15 18:12:14 superagi-main-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 2023-06-15 18:12:14 superagi-main-celery-1 | 2023-06-15 18:12:14 superagi-main-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( 2023-06-15 18:12:14 superagi-main-celery-1 | 2023-06-15 18:12:14 superagi-main-celery-1 | -------------- celery@ea59d3726db5 v5.2.7 (dawn-chorus) 2023-06-15 18:12:14 superagi-main-celery-1 | --- ***** ----- 2023-06-15 18:12:14 superagi-main-celery-1 | -- ******* ---- Linux-5.15.90.1-microsoft-standard-WSL2-x86_64-with-glibc2.36 2023-06-16 00:12:14 2023-06-15 18:12:14 superagi-main-celery-1 | - *** --- * --- 2023-06-15 18:12:14 superagi-main-celery-1 | - ** ---------- [config] 2023-06-15 18:12:14 superagi-main-celery-1 | - ** ---------- .> app: superagi:0x7f626880feb0 2023-06-15 18:12:14 superagi-main-celery-1 | - ** ---------- .> transport: redis://super__redis:6379/0 2023-06-15 18:12:14 superagi-main-celery-1 | - ** ---------- .> results: redis://super__redis:6379/0 2023-06-15 18:12:14 superagi-main-celery-1 | - *** --- * --- .> concurrency: 10 (prefork) 2023-06-15 18:12:14 superagi-main-celery-1 | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) 2023-06-15 18:12:14 superagi-main-celery-1 | --- ***** ----- 2023-06-15 18:12:14 superagi-main-celery-1 | -------------- [queues] 2023-06-15 18:12:14 superagi-main-celery-1 | .> celery exchange=celery(direct) key=celery 2023-06-15 14:00:42 superagi-main-backend-1 | INFO: Started reloader process [1] using WatchFiles 2023-06-15 18:12:14 superagi-main-celery-1 | 2023-06-15 18:12:14 superagi-main-celery-1 | 2023-06-15 18:12:14 superagi-main-celery-1 | [tasks] 2023-06-15 18:12:14 superagi-main-celery-1 | . execute_agent 2023-06-15 18:12:14 superagi-main-celery-1 | 2023-06-15 18:12:17 superagi-main-celery-1 | [2023-06-16 00:12:17,088: INFO/MainProcess] Connected to redis://super__redis:6379/0 2023-06-15 18:12:17 superagi-main-celery-1 | [2023-06-16 00:12:17,100: INFO/MainProcess] mingle: searching for neighbors 2023-06-15 18:12:18 superagi-main-celery-1 | [2023-06-16 00:12:18,126: INFO/MainProcess] mingle: all alone 2023-06-15 18:12:18 superagi-main-celery-1 | [2023-06-16 00:12:18,451: INFO/MainProcess] celery@ea59d3726db5 ready. 2023-06-15 18:17:39 superagi-main-celery-1 | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main 2023-06-15 18:17:43 superagi-main-celery-1 | /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is 2023-06-15 18:17:43 superagi-main-celery-1 | absolutely not recommended! 2023-06-15 18:17:43 superagi-main-celery-1 | 2023-06-15 18:17:43 superagi-main-celery-1 | Please specify a different user using the --uid option. 2023-06-15 18:17:43 superagi-main-celery-1 | 2023-06-15 18:17:43 superagi-main-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 2023-06-15 18:17:43 superagi-main-celery-1 | 2023-06-14 20:08:20 superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 2023-06-14 20:08:20 superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started 2023-06-14 20:08:20 superagi-main-super__redis-1 | 1:C 15 Jun 2023 02:08:20.155 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf 2023-06-14 20:08:20 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.157 * monotonic clock: POSIX clock_gettime 2023-06-14 20:08:20 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 * Running mode=standalone, port=6379. 2023-06-14 20:08:20 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 # Server initialized 2023-06-14 20:08:20 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.163 # 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. 2023-06-14 20:08:20 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:08:20.166 * Ready to accept connections 2023-06-14 20:48:00 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.331 * 100 changes in 300 seconds. Saving... 2023-06-14 20:48:00 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.340 * Background saving started by pid 19 2023-06-14 20:48:00 superagi-main-super__redis-1 | 19:C 15 Jun 2023 02:48:00.358 * DB saved on disk 2023-06-14 20:48:00 superagi-main-super__redis-1 | 19:C 15 Jun 2023 02:48:00.358 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB 2023-06-14 20:48:00 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:48:00.442 * Background saving terminated with success 2023-06-14 20:53:45 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:53:45.069 * 100 changes in 300 seconds. Saving... 2023-06-14 20:53:45 superagi-main-super__redis-1 | 1:M 15 Jun 2023 02:53:45.070 * Background saving started by pid 20 2023-06-14 20:53:45 superagi-main-super__redis-1 | 20:C 15 Jun 2023 02:53:45.081 * DB saved on disk 2023-06-14 20:53:45 superagi-main-super__redis-1 | 20:C 15 Jun 2023 02:53:45.081 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB 2023-06-15 14:00:49 superagi-main-backend-1 | Connected to the database! @ postgresql://superagi:password@super__postgres/super_agi_main 2023-06-15 18:17:43 superagi-main-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( 2023-06-15 18:17:43 superagi-main-celery-1 | 2023-06-15 18:17:43 superagi-main-celery-1 | -------------- celery@ea59d3726db5 v5.2.7 (dawn-chorus) 2023-06-15 18:17:43 superagi-main-celery-1 | --- ***** ----- 2023-06-15 18:17:43 superagi-main-celery-1 | -- ******* ---- Linux-5.15.90.1-microsoft-standard-WSL2-x86_64-with-glibc2.36 2023-06-16 00:17:43 2023-06-15 18:17:43 superagi-main-celery-1 | - *** --- * --- 2023-06-15 18:17:43 superagi-main-celery-1 | - ** ---------- [config] 2023-06-15 18:17:43 superagi-main-celery-1 | - ** ---------- .> app: superagi:0x7f6d7a810eb0 2023-06-15 18:17:43 superagi-main-celery-1 | - ** ---------- .> transport: redis://super__redis:6379/0 2023-06-15 18:17:43 superagi-main-celery-1 | - ** ---------- .> results: redis://super__redis:6379/0 2023-06-15 18:17:43 superagi-main-celery-1 | - *** --- * --- .> concurrency: 10 (prefork) 2023-06-15 18:17:43 superagi-main-celery-1 | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker) 2023-06-15 18:17:43 superagi-main-celery-1 | --- ***** ----- 2023-06-15 18:17:43 superagi-main-celery-1 | -------------- [queues] 2023-06-15 18:17:43 superagi-main-celery-1 | .> celery exchange=celery(direct) key=celery 2023-06-15 18:17:43 superagi-main-celery-1 | 2023-06-15 18:17:43 superagi-main-celery-1 | 2023-06-15 18:17:43 superagi-main-celery-1 | [tasks] 2023-06-15 18:17:43 superagi-main-celery-1 | . execute_agent 2023-06-15 18:17:43 superagi-main-celery-1 | 2023-06-15 18:17:48 superagi-main-celery-1 | [2023-06-16 00:17:48,257: INFO/MainProcess] Connected to redis://super__redis:6379/0 2023-06-15 18:17:48 superagi-main-celery-1 | [2023-06-16 00:17:48,263: INFO/MainProcess] mingle: searching for neighbors 2023-06-15 18:17:49 superagi-main-celery-1 | [2023-06-16 00:17:49,282: INFO/MainProcess] mingle: all alone 2023-06-15 18:17:49 superagi-main-celery-1 | [2023-06-16 00:17:49,350: INFO/MainProcess] celery@ea59d3726db5 ready. 2023-06-15 18:18:50 superagi-main-celery-1 | [2023-06-16 00:18:50,702: INFO/MainProcess] Task execute_agent[3b91712b-d0cf-43a3-94d9-afef4f817017] received 2023-06-15 18:18:50 superagi-main-celery-1 | [2023-06-16 00:18:50,707: WARNING/ForkPoolWorker-7] Execute agent:2023-06-16T00:18:50.525335,6 2023-06-15 18:18:54 superagi-main-celery-1 | [2023-06-16 00:18:54,799: WARNING/ForkPoolWorker-7] You are SuperAGI an AI assistant to solve complex problems. Your decisions must always be made independently without seeking user assistance. 2023-06-15 18:18:54 superagi-main-celery-1 | Play to your strengths as an LLM and pursue simple strategies with no legal complications. 2023-06-15 18:18:54 superagi-main-celery-1 | If you have completed all your tasks or reached end state, make sure to use the "finish" tool. 2023-06-15 18:18:54 superagi-main-celery-1 | 2023-06-15 13:45:04 superagi-main-gui-1 | 2023-06-15 13:45:04 superagi-main-gui-1 | > [email protected] dev 1969-12-31 18:00:00 error from daemon in stream: Error grabbing logs: invalid character '\x00' looking for beginning of value

[jtantley]

Does this mean that SuperAGI can only be run natively on Linux or a virtual environment? Or is there a way to enable memory overcommit on Windows?

[clappo143]

172.18.0.1:42126 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 400 Bad Request We are noticing this error in the logs. I think because of this, you are not getting any feed and the agent is stuck on thinking. SuperAgi might be working in the backend and feed should be getting stored in the database, but due to this error maybe you're not seeing it in the frontend.

I've got no idea, but intuitively I feel like this is the central problem. The frontend and backend don't really seem to be speaking to each other...

Here's some GPT-4 responses on this issue which may or may not be helpful

The error message Error fetching execution feeds: AxiosErrorcode: "ERR_BAD_REQUEST" indicates that the client made a bad request. This usually means that there was a problem with the syntax of the request or the request could not be fulfilled.

The URL /agentexecutionfeeds/get/execution/0 returned a 400 Bad Request error with the message {"detail":"Agent Run not found!"}. This suggests that the server could not find an agent execution with the ID 0. You should check whether the ID 0 is valid and whether the agent execution with this ID exists in your database.

The CORS error seems to be resolved now, as it's not appearing in the logs you provided. The issue seems to be with the request you're making to the server.

The WebSocket error WebSocket connection to 'ws:<URL>/_next/webpack-hmr' failed: WebSocket is closed before the connection is established. is related to the hot module replacement (HMR) feature of webpack, which is a tool for bundling JavaScript applications. This error might occur if the frontend application was stopped or if there was a network issue. However, this should not affect the functionality of your application unless you're relying on HMR for some functionality.

The DevTools failed to load source map warnings are related to Chrome DevTools. Source maps are files that map the bundled JavaScript code back to the original source code. These warnings can occur if the source map files are not available. These warnings should not affect the functionality of your application.

In summary, you should check the request to /agentexecutionfeeds/get/execution/0 and make sure that the agent execution with the ID 0 exists.

Yes, you can modify the code to try different IDs if the requested one does not exist. However, this might not be the best approach to solve the problem.

The ID '0' is likely coming from the frontend application, which means that the frontend is trying to fetch an AgentExecution that it expects to exist. If it doesn't exist, then there might be an issue with how the frontend is determining which AgentExecution to fetch.

Instead of modifying the backend to try different IDs, it might be better to investigate why the frontend is requesting an AgentExecution that doesn't exist. This could involve looking at the frontend code to see how it determines which AgentExecution to fetch, or it could involve looking at the process that creates AgentExecution records to see if there's an issue there.

Thank you for providing the code for the AgentWorkspace.js file.

From the code, it appears that the ActivityFeed component is being used in the AgentWorkspace component. The ActivityFeed component is passed two props: selectedView and selectedRunId. The selectedRunId prop seems to be crucial for the ActivityFeed component to fetch and display the correct data.

The ActivityFeed component fetches data every 10 seconds using the fetchFeeds function. This function calls the getExecutionFeeds function from the DashboardService with the selectedRunId as an argument. The getExecutionFeeds function likely makes an API call to fetch the data for the selected run.

The ActivityFeed component also listens for an event updateRunStatus on the EventBus. When this event is emitted, the updateRunStatus function is called, which updates the run status if the selectedRunId matches the selectedRunId from the event data.

If the ActivityFeed component is not updating as expected, there could be several potential issues:

The selectedRunId prop might not be getting updated correctly in the AgentWorkspace component. This could be due to a bug in the AgentWorkspace component or because the selected run is not being updated in the state of a parent component.

The getExecutionFeeds function might not be returning the correct data. This could be due to an issue with the API or the function itself.

The updateRunStatus event might not be getting emitted correctly, or the event data might not contain the correct selectedRunId.

To debug this issue, you could:

Check if the selectedRunId prop is getting updated correctly in the AgentWorkspace component. You could add some console.log statements or use a React debugger to check the state of the component.

Check the data returned by the getExecutionFeeds function. You could add a console.log statement in the then block of the promise returned by the function to log the data.

Check if the updateRunStatus event is getting emitted correctly and if the event data is correct. You could add a console.log statement in the updateRunStatus function to log the event data.

If the issue is not with the front-end code, you might need to check the API and the backend code.