604 CRIT Server 'unix_http_server' running without any HTTP authentication checking

Supervisor running as root error when running the command

sudo service supervisor status

Response error

604 CRIT Server 'unix_http_server' running without any HTTP authentication checking

Check the supervisord.conf file in the directory

cd /etc/supervisor/

The file content was

; supervisor config file

[unix_http_server]
file=/var/run/supervisor.sock   ; (the path to the socket file)
chmod=0700                       ; sockef file mode (default 0700)

[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

; 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.

[inet_http_server]
port=*:9001
username=admin
password=admin

[include]
files = /etc/supervisor/conf.d/*.conf

You can set the same username/password in the [unix_http_server] and [supervisorctl] sections of the config file. This will remove the CRIT message that you have not set authentication checking, and supervisorctl will not prompt for a password.  Enter the following into the two areas:

username=dummy
password=dummy

Restart supervisor

sudo service supervisor restart

Then once Supervisor had restarted, ran the status command

sudo service supervisor status

Response

● supervisor.service - Supervisor process control system for UNIX
     Loaded: loaded (/lib/systemd/system/supervisor.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-08-05 01:16:01 UTC; 35s ago
       Docs: http://supervisord.org
   Main PID: 7431 (supervisord)
      Tasks: 4 (limit: 9530)
     Memory: 67.0M
     CGroup: /system.slice/supervisor.service
             ├─7431 /usr/bin/python3 /usr/bin/supervisord -n -c /etc/supervisor/supervisord.conf
             ├─7435 /usr/lib/ckan/default/bin/uwsgi -i /etc/ckan/default/ckan-uwsgi.ini
             ├─7438 /usr/lib/ckan/default/bin/uwsgi -i /etc/ckan/default/ckan-uwsgi.ini
             └─7439 /usr/lib/ckan/default/bin/uwsgi -i /etc/ckan/default/ckan-uwsgi.ini

systemd[1]: Stopped Supervisor process control system for UNIX.
systemd[1]: Started Supervisor process control system for UNIX.
supervisord[7431]: 777 INFO Included extra file "/etc/supervisor/conf.d/ckan-uwsgi.conf" during parsing
supervisord[7431]: 777 INFO Set uid to user 0 succeeded
supervisord[7431]: 020 INFO RPC interface 'supervisor' initialized
supervisord[7431]: 021 INFO RPC interface 'supervisor' initialized
supervisord[7431]: 021 INFO supervisord started with pid 7431
supervisord[7431]: 024 INFO spawned: 'ckan-uwsgi-00' with pid 7435
supervisord[7431]: 812 INFO success: ckan-uwsgi-00 entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

Critical error removed.