fixed supervisor errors in log

configure_supervisor.yml

@@ -4,6 +4,14 @@
   hosts: all
   tasks:
     # create current supervisor configs and start it
+    - name: create global supervisor-config from template
+      template:
+        src: templates/supervisord.conf.j2
+        dest: "/etc/supervisor/supervisord.conf"
+        owner: root
+        group: root
+        mode: "0640"
+
     - name: create supervisor-config for otree instances from template
       template:
         src: templates/supervisor_otree.conf.j2

templates/supervisord.conf.j2

+; supervisor config file
+
+[unix_http_server]
+file=/var/run/supervisor.sock   ; (the path to the socket file)
+chmod=0700                       ; sockef file mode (default 0700)
+username = dummy ; to prevent log message, creds doesn't matter on local machine
+password = dummy 
+
+[supervisord]
+logfile=/var/log/supervisor/supervisord.log ; (main log file;default $CWD/supervisord.log)
+pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
+childlogdir=/var/log/supervisor            ; ('AUTO' child log dir, default $TEMP)
+user = root
+; the below section must remain in the config file for RPC
+; (supervisorctl/web interface) to work, additional interfaces may be
+; added by defining them in separate rpcinterface: sections
+[rpcinterface:supervisor]
+supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
+
+[supervisorctl]
+serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL  for a unix socket
+username = dummy
+password = dummy
+
+; The [include] section can just contain the "files" setting.  This
+; setting can list multiple files (separated by whitespace or
+; newlines).  It can also contain wildcards.  The filenames are
+; interpreted as relative to this file.  Included files *cannot*
+; include files themselves.
+
+[include]
+files = /etc/supervisor/conf.d/*.conf