Question: Were I can find the logFile?

[coderDem]

Hello,

I am tryinig this tool, for this call I get an sucessfull message:

curl -d '{"command": "create_user", "server": "SERVERURL", "data": {"zox47348@eoopy.com": { "fullName": "Super Duper Tester", "pwd": "test123", "provider": "greenlight"}}}' -H 'Content-Type: application/json' -X POST http://SERVERURL:8008/api/v1/commands

{ "data": { "command": "create_user", "data": { "zox47348@eoopy.com": { "fullName": "Super Duper Tester", "pwd": "test123", "provider": "greenlight" } }, "server": "http://live.hkbis.de" }, "message": "command queued successfully" }

But nothing is happening. I would like to understand what is going on.
Could you please tell me were I can find the LogFile?

[coderDem]

Ok, I found the log:

./scheduLight.log

[mtsonline]

great you found the logfile.
you get a lot of feedback in the systemctl status and the syslog too. ;-)
the single components have their own logging.
should be centraliced in the file though.

first thing I can see is, that you specify "server url" this won't work. you have to add a server to the system first and use the ID you give this server.

[coderDem]

Hello @mtsonline ,

the SERVERURL is a placeholder for my server url.

I got also an answer for:

curl -X GET http://SERVER_URL:8008/api/v1/meetings

{ "data": [], "message": "found meetings" }

[mtsonline]

as I Said, you cannot specify a server url in the api commands of scheduLight.
First add servers and then use the given Name/ID to interact with them.
Have a look at the example config file to understand how servers/users objects look like.
hth

[coderDem]

Hello @mtsonline ,

thank you for the answer, I have specified the serverentrys:

BBB_SECRET: SECRET BBB_URL: https://myurl.de/bigbluebutton/api link_base: https://myurl.de/b

If I change something in greenLight.py do I need to recompile it?

[mtsonline]

regarding the bbb server where did you specify the url and secret? the parent should be the id you later can use.

no you do not have to recompile you just have to restart the processors.
hth

[coderDem]

Hello @mtsonline ,

I have specified the values in the file: config.yml

[coderDem]

Hello @mtsonline ,

I only see this warning in the log:

2020-09-22 12:38:45 scheduLight DEBUG Redis stream warning: BUSYGROUP Consumer Group name already exists

It seems that the commands are not called.

[coderDem]

I also can't find the log greenLight.log

[mtsonline]

ok.

1. the processors must be running.

2. there is no greenlight log - this just is a class that is imported.

3. if you specify everything in the config you have to run the read process manually to have it importet.
   hth

[coderDem]

Hello @mtsonline,

1. I thought the processors are runnig if I stop:
   systemctl stop scheduLight.target and restart it:
   systemctl start scheduLight

But you are right, I am running this:
systemctl -l status scheduLight-commandsProcessor
it says that is inactive:
scheduLight-commandsProcessor.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)

Do I need to start it manually?

2. I thought there is an greenLight.log if I look at this line:
   def __init__(self, gl_dbName, gl_dbUser, gl_dbPassword, gl_dbHost, gl_dbPort, gl_logFile='greenLight.log'):
   and this line:
   fh = logging.handlers.RotatingFileHandler(gl_logFile, maxBytes=1000000, backupCount=5)

3. Is this not done if I do this:
   systemctl stop scheduLight.target and this
   systemctl start scheduLight

[mtsonline]

it is commandProcessor not commandsProcessor ;-) what does it say?

the relevant logdata should be in schedulight logfile.

you have to execute: slReadConfig.py
this will read the config from your config.yml into the db and process it. This is necessary, to prevent having the config file read the whole time so you can editwithout interruption.
You only have to execute this if you change something in the file.

hth

[coderDem]

Hello @mtsonline ,

if it is commandProcessor and not commandsProcessor, it would be cool if you can update your README file see:
systemctl -l status scheduLight-[api|commandsProcessor|...]

Thank you for the help. :)

[mtsonline]

oh, thank you for pointing this typo out. will change it. :-) sorry for that.

[coderDem]

Hello @mtsonline,

you are welcome :-)
Thank you for the project.

Restart service:
systemctl restart scheduLight-commandProcessor

this is what I needed.