./chip.sh start does not work

[Capsar]

@Archer6621 After cloning the repository and running ./chip.sh start the following logs are printed and nothing is launched.

Logs:

./chip.sh start
No core module configuration found, creating one from defaults...
No module configuration found for module ./modules/front-end-gradio, creating one from defaults...
No module configuration found for module ./modules/front-end-quasar, creating one from defaults...
No module configuration found for module ./modules/knowledge-demo, creating one from defaults...
No module configuration found for module ./modules/logger-default, creating one from defaults...
No module configuration found for module ./modules/reasoning-demo, creating one from defaults...
No module configuration found for module ./modules/redis, creating one from defaults...
No module configuration found for module ./modules/response-generator-demo, creating one from defaults...
No module configuration found for module ./modules/response-generator-gemini, creating one from defaults...
No module configuration found for module ./modules/response-generator-llm-local, creating one from defaults...
No module configuration found for module ./modules/text-to-triples-llm, creating one from defaults...
No module configuration found for module ./modules/text-to-triples-rule-based, creating one from defaults...
env file /chip-demo/setup.env not found: stat /chip-demo/setup.env: no such file or directory
Unable to find image 'mikefarah/yq:latest' locally
latest: Pulling from mikefarah/yq
f18232174bc9: Already exists
ce6d7092d924: Pull complete
b9466747e2c7: Pull complete
02e9dcbbcebd: Pull complete
5a329cb375ee: Pull complete
Digest: sha256:7cf28e5d67782f4b274a93a7bc54a840b553447a0807efd843d069f46bff718c
Status: Downloaded newer image for mikefarah/yq:latest
Created module-address and core-module mappings in setup.env...
Starting system with core modules:
logger-default front-end-quasar response-generator-demo reasoning-demo text-to-triples-rule-based
line 1: key cannot contain a space
line 1: key cannot contain a space

[Archer6621]

Doing a very quick search I stumbled upon this stackoverflow post: https://stackoverflow.com/questions/69512549/key-cannot-contain-a-space-error-while-running-docker-compose

There might be an issue in one of the environment files. Please post the generated setup.env file, how does it look?

[Capsar]

It looks like this:

CHIP.SH CORE-MODULES.YAML CORE-MODULES.YAML.DEFAULT DEMO_SCENARIO.MD DOCKER-COMPOSE-BASE.YML MODULES README.MD SETUP.ENV=*:

[Archer6621]

It looks like this:

CHIP.SH CORE-MODULES.YAML CORE-MODULES.YAML.DEFAULT DEMO_SCENARIO.MD DOCKER-COMPOSE-BASE.YML MODULES README.MD SETUP.ENV=*:

That looks very broken, I haven't seen it ever do that. What kind of OS are you running this one? And are you running it in sh or in bash? If it is the former, I'd recommend trying the latter if possible.

It almost looks as if it is iterating over the wrong folder to get the modules, but I don't know how that could happen if you are running ./chip.sh start from the root folder. Will investigate.

[Capsar]

Hi Archer,

Thank you for taking the time to look into this. We are trying to run the script on a Linux server, running Ubuntu 24.04.2 LTS.
The command is run in a bash terminal. The output of echo $0, echo $SHELL, ps -p $$ all refer to bash.

What should the standard setup.env look like?

[Archer6621]

Here's an example:

FRONT_END_GRADIO=front-end-gradio:5000
FRONT_END_QUASAR=front-end-quasar:5000
FRONTEND_MODULE=FRONT_END_QUASAR
KNOWLEDGE_DEMO=knowledge-demo:7200
LOGGER_DEFAULT=logger-default:5000
LOGGER_MODULE=LOGGER_DEFAULT
REASONING_DEMO=reasoning-demo:5000
REASONER_MODULE=REASONING_DEMO
REDIS=redis:6379
RESPONSE_GENERATOR_DEMO=response-generator-demo:5000
RESPONSE_GENERATOR_MODULE=RESPONSE_GENERATOR_DEMO
RESPONSE_GENERATOR_GEMINI=response-generator-gemini:5000
RESPONSE_GENERATOR_LLM_LOCAL=response-generator-llm-local:5000
TEXT_TO_TRIPLES_LLM=text-to-triples-llm:5000
TEXT_TO_TRIPLES_RULE_BASED=text-to-triples-rule-based:5000
TRIPLE_EXTRACTOR_MODULE=TEXT_TO_TRIPLES_RULE_BASED

The script basically reads out information from the modules by iterating over their paths, and establishes address mappings from that.

[Archer6621]

I managed to reproduce it, it's a silly bug. It happens when there is no setup.env initially in the folder, because the base compose.yml has it configured as an environment file to load, so doing anything that has to do with that compose file before having that setup.env file in the folder will break things.

For now the fix is just to have an empty setup.env in there. I will fix it in the script by just creating an empty setup.env beforehand.