Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think the problem is quite simple, the "numprocs" configuration item is only introduced in v3.0, see <a href="http://supervisord.org/configuration.html">http://supervisord.org/configuration.html</a>.</p> <p>I was able to duplicate your problem on a stock CentOS 6.x system, which lags behind significantly in terms of releases.</p> <pre><code># supervisord -n 2013-09-14 17:19:52,708 CRIT Supervisor running as root (no user in config file) 2013-09-14 17:19:52,724 INFO /var/tmp/supervisor.sock:Medusa (V1.1.1.1) started at Sat Sep 14 17:19:52 2013 Hostname: &lt;unix domain socket&gt; Port:/var/tmp/supervisor.sock 2013-09-14 17:19:52,809 CRIT Running without any HTTP authentication checking 2013-09-14 17:19:52,809 INFO supervisord started with pid 21521 2013-09-14 17:19:52,817 INFO spawned: 'gearman-test-worker' with pid 21522 2013-09-14 17:19:53,820 INFO success: gearman-test-worker entered RUNNING state, process has stayed up for &gt; than 1 seconds (startsecs) # rpm -qa | grep supervisor supervisor-2.1-8.el6.noarch # uname -a Linux dev26.sumilux.com 2.6.32-279.5.1.el6.i686 #1 SMP Tue Aug 14 21:14:52 UTC 2012 i686 i686 i386 GNU/Linux </code></pre> <p>If I upgrade the supervisor package to 3.x (actually by switching over to an ancient Fedora system), everything works as expected (I set 3 workers instead of 5).</p> <pre><code># supervisord -n 2013-09-14 17:24:56,205 CRIT Supervisor running as root (no user in config file) 2013-09-14 17:24:56,251 INFO RPC interface 'supervisor' initialized 2013-09-14 17:24:56,252 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2013-09-14 17:24:56,252 INFO supervisord started with pid 20889 2013-09-14 17:24:57,258 INFO spawned: 'gearman-test-worker_00' with pid 20890 2013-09-14 17:24:57,263 INFO spawned: 'gearman-test-worker_01' with pid 20891 2013-09-14 17:24:57,269 INFO spawned: 'gearman-test-worker_02' with pid 20892 2013-09-14 17:24:58,271 INFO success: gearman-test-worker_00 entered RUNNING state, process has stayed up for &gt; than 1 seconds (startsecs) 2013-09-14 17:24:58,271 INFO success: gearman-test-worker_01 entered RUNNING state, process has stayed up for &gt; than 1 seconds (startsecs) 2013-09-14 17:24:58,272 INFO success: gearman-test-worker_02 entered RUNNING state, process has stayed up for &gt; than 1 seconds (startsecs) # rpm -qa | grep supervisor supervisor-3.0-0.5.a10.fc14.noarch </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POSupervisord spawns only 1 instance
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USstevel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSupervisord spawns only 1 instance
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthanks! I wasn't even looking at the version numbers. I'll just use my 5 subsections for now.
      singulars
      1. PO
      1. USMartin Müller
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload