I’m trying to configure the event daemon and test the simple example logArgs plugin, but I’m met with several errors regarding the os.environ variables, a connection refusal, and being unable to register a callback function from logArgs. I’ve tried to find a few clues to why, my first assumption is …

Figured it out. I’m silly and forgot to set the logArgs scriptname/key for the callback params.

Went a little further and cleared up the connection problem- Now I’m just getting CRITICAL:engine:Error running register callback function from logArgs. It gets caught up at os.environ[“SGDAEMON_LOGARGS_NAME”] (left it at default for now). Past that, it raises a KeyError(key) from None (KeyError: …

Glad you got there, @victorfranjo and thanks for sharing the solution! :medal_sports:

Running into the same issue; could you explain a bit more what you did? I’m a little new to all of this, but I found those defaults you’re mentioning. Do os.environ[“SGDAEMON_LOGARGS_NAME”] and os.environ[“SGDAEMON_LOGARGS_KEY”] need to match the script and key that you place in shotgunEventDaemon.…

Thank you, @ali-jafargholi ! Looks like this is exactly what I was looking for!

LogArgs example plugin presenting several errors

Flow Production Tracking

ali-jafargholi October 20, 2022, 9:41pm 6

Hey @josephh
Take a look at this post, it should give you some idea

Topic		Replies	Views
Not sure what the "SGDAEMON_LOGARGS_NAME" value is supposed to be Flow Production Tracking	6	635	August 9, 2022
Event-daemon does not trigger event	1	337	December 2, 2021
Event Daemon don't work and logs won't update when the Plugin's name is changed Pipeline Integrations python-api , event-daemon , event-log	1	525	January 6, 2022
Shotgun Events Daemon not working Pipeline Integrations event-daemon	4	684	November 16, 2021
Key Error when starting shotgunEventDaemon Pipeline Integrations event-daemon	5	1640	September 9, 2020

LogArgs example plugin presenting several errors

Related topics