$ supervisorctl -s "http://192.168.1.1:9001" -i
Error: .ini file does not include supervisorctl section
For help, use /usr/local/bin/supervisorctl -h
Running the same command in a different directory works fine.
I'd suggest either allowing explicit command line arguments to override the implicitly detected config file, or informing the user that they are ignored.
version 3.1.3
          
I've this same problem on centos, in my conf I've added a section [supervisord] in addition to my program conf.
$ easy_install supervisor
$ supervisord -v
3.2.1
$ supervisord -c /etc/supervisord.conf
$ supervisorctl restart program:secor -c /etc/supervisord.conf
Error: .ini file does not include supervisorctl section
For help, use /bin/supervisorctl -h
I fixed the issue by concatinating echo_supervisord_conf to my config file.
          
Hi, I used the supervisor on the Mac to write the configuration file to execute the command

supervisord - c/Users/wujunze/etc/supervisor. The conf

Then execute supervisorctl reported this error:
The supervisor > update
Error: < class 'socket. The error >, [61] Errno Connection refused: file: / System/Library/Frameworks/Python framework Versions / 2.7 / lib/python2.7 / socket. Py line: 575 ```
          
I also have the same problem
sudo supervisorctl -c /etc/supervisor/supervisord.conf
error: <class 'socket.error'>, [Errno 99] Cannot assign requested address: file: /usr/lib/python2.7/socket.py line: 575
supervisor>
  NaitikShah, xiaokli-in, sriramnambi, MythriNagaraju, yugaego, hiCabrera30, sahedbs23, lihliang, RSickenberg, NightOwlPrgmr, and prabba90rock reacted with thumbs up emoji
  jordanboston, kenugraha, rocramer, gitkv, and Zamiell reacted with thumbs down emoji
    All reactions
          
for me the solve was, the daemon was no running

sudo systemctl status supervisord

sudo systemctl enable supervisord

sudo systemctl start supervisord
ready

sudo supervisorctl reread

sudo supervisorctl start process:*
          
I came upon this issue with a similar error, when running in a Docker container:
# supervisorctl 
error: <class 'socket.error'>, [Errno 99] Cannot assign requested address: file: /usr/lib/python2.7/socket.py line: 575
The problem in my case was not a missing supervisord.conf in current directory, and -c supervisord.conf did not help.  The problem was that the supervisord.conf in the current directory was just too thin, and was missing things that supervisorctl needs.  Here's what I had to add:
[unix_http_server]
file=/var/run/supervisor.sock
chmod=0700
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
[supervisorctl]
serverurl=unix:///var/run/supervisor.sock
  m01, luisnabais, ahora-mismo, bodva, dawidgora-old-account, thinckx, christippett, wbednarczyk, GonzaloCenteno, ptrthomas, and 45 more reacted with thumbs up emoji
  caryxiao, akgitcom, lelinhtinh, and Rikj000 reacted with laugh emoji
  dawidgora-old-account, GonzaloCenteno, shinebayar-g, ptrthomas, mattbroekhuis, mlodic, andrejsstepanovs, AndrewFarley, dhuang919, SidneyNemzer, and 8 more reacted with hooray emoji
  ptrthomas, jose-magalhaes-deel, mattbroekhuis, AndrewFarley, dhuang919, SidneyNemzer, isudakoff, mhemrg, caryxiao, allxone, and 7 more reacted with heart emoji
  ziyadsfaxi reacted with rocket emoji
    All reactions
          
Docker:

error: <class 'socket.error'>, [Errno 2] No such file or directory: file: /usr/lib/python2.7/socket.py line: 228

The command '/bin/sh -c supervisorctl update' returned a non-zero code: 2
          
I have

I have encountered the same problem, but the usage scenario is that the virtual environment of anaconda, after the non-root user starts, the subsequent reload fails through the non-root user.
The error is as follows:

error: <class 'socket.error'>, [Errno 2] No such file or directory: file: /usr/work/tool/anaconda3/envs/python27/lib/python2.7/socket.py line: 228
I came upon this issue with a similar error, when running in a Docker container:
# supervisorctl 
error: <class 'socket.error'>, [Errno 99] Cannot assign requested address: file: /usr/lib/python2.7/socket.py line: 575
The problem in my case was not a missing supervisord.conf in current directory, and -c supervisord.conf did not help. The problem was that the supervisord.conf in the current directory was just too thin, and was missing things that supervisorctl needs. Here's what I had to add:
[unix_http_server]
file=/var/run/supervisor.sock
chmod=0700
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
[supervisorctl]
serverurl=unix:///var/run/supervisor.sock
mark~
          
Facing the python file not found an error, code=exited, status=2 once I try with the official document but still same.

I have tried so many solutions for my laravel application.
But at last, I have tried with my solution.
Here is an example for the code :
[program:dev-worker]
process_name=%(program_name)s_%(process_num)02d
command=cd /var/www/html/example.com && php artisan queue:work --sleep=3 --tries=3
autostart=true
autorestart=true
user=ubuntu
numprocs=8
redirect_stderr=true
stdout_logfile=/var/www/html/example.com/storage/logs/laravel.log
stopwaitsecs=3600
Ref: https://laravel.com/docs/7.x/queues#supervisor-configuration
https://stackoverflow.com/questions/41286526/supervisor-no-such-file-socket-py/65791261#65791261
          
The suggestion from @javabrett unfortunately causes errors like the following to be logged at each startup:
CRIT Server 'unix_http_server' running without any HTTP authentication checking
As discussed in ticket #717, this can be avoided by securing the configuration. For example:
[unix_http_server]
file=/var/run/supervisor.sock
chmod=0700
username = dummy
password = impossibleToGuess
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
[supervisorctl]
serverurl=unix:///var/run/supervisor.sock
username = dummy
password = impossibleToGuess
I've tried the suggestions above, and I'm getting unix:///var/run/supervisor.sock no such file when configuring the supervisord.conf file as suggested. I'm inside a Docker container running Ubuntu 20.04
Same issue here. Did you manage to find a solution for it?