process table showing lots of idle airtime processes...
  • I have been checking on the processes running on our airtime 1.8.2 server and have noticed a large number of postgres processes, and quite a few apache2 process too. Is this normal? Is it something to do with the number of users logged in? Please see process table below

    thanks

    James

    ~$ ps ax | grep postgres | grep -v grep:
    
    866 ?        S      1:01 /usr/lib/postgresql/8.4/bin/postgres -D /var/lib/postgresql/8.4/main -c config_file=/etc/postgresql/8.4/main/postgresql.conf
    1085 ?        Ss     0:39 postgres: writer process
    1086 ?        Ss     0:21 postgres: wal writer process
    1087 ?        Ss     0:12 postgres: autovacuum launcher process
    1088 ?        Ss     0:34 postgres: stats collector process
    4257 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(43684) idle
    4341 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(43778) idle
    6321 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(40806) idle
    6334 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(40822) idle
    8556 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(33735) idle
    8630 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(33784) idle
    10174 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(35529) idle
    10175 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(35530) idle
    10176 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(35531) idle
    10351 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(36217) idle
    10369 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(36238) idle
    12727 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(56932) idle
    12828 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(57033) idle
    17580 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(48645) idle
    17705 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(48653) idle
    17706 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(48654) idle
    17724 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(48683) idle  
    17990 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(43901) idle  
    18012 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(55626) idle
    23219 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(34847) idle
    23246 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(34879) idle
    25330 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(33668) idle
    25353 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(33701) idle
    26096 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(40480) idle
    26263 ?        Ss     0:00 postgres: airtime airtime 127.0.0.1(40639) idle


    ~$ ps ax | grep apache2 | grep -v grep
     1366 ?        Ss     0:10 /usr/sbin/apache2 -k start
     3887 ?        S      1:55 /usr/sbin/apache2 -k start
     4026 ?        S      0:37 /usr/sbin/apache2 -k start
     4067 ?        S      1:13 /usr/sbin/apache2 -k start
     5304 ?        S      0:25 /usr/sbin/apache2 -k start
     6223 ?        S      0:51 /usr/sbin/apache2 -k start
     8367 ?        S      0:15 /usr/sbin/apache2 -k start
     9217 ?        S      1:23 /usr/sbin/apache2 -k start
    10602 ?        S      2:28 /usr/sbin/apache2 -k start
    10610 ?        S      1:59 /usr/sbin/apache2 -k start
    11101 ?        S      2:53 /usr/sbin/apache2 -k start
    11103 ?        S      0:55 /usr/sbin/apache2 -k start
    12743 ?        S      5:07 /usr/sbin/apache2 -k start
    13000 ?        S      1:30 /usr/sbin/apache2 -k start
    13307 ?        S      0:52 /usr/sbin/apache2 -k start
    13309 ?        S      1:18 /usr/sbin/apache2 -k start
    13310 ?        S      2:34 /usr/sbin/apache2 -k start
    13383 ?        S      0:50 /usr/sbin/apache2 -k start
    13939 ?        S      2:51 /usr/sbin/apache2 -k start
    14298 ?        S      0:34 /usr/sbin/apache2 -k start
    14342 ?        S      1:17 /usr/sbin/apache2 -k start
    17541 ?        S      0:05 /usr/sbin/apache2 -k start
    22360 ?        S      3:02 /usr/sbin/apache2 -k start
    
  • 3 Comments sorted by
  • Vote Up0Vote Down Andrey PodshivalovAndrey Podshivalov
    Posts: 1,526Member, Administrator, Sourcefabric Team
    It seems that your server is overloaded.
    Could you check load avarage? (run uptime or top)
  • Yes I've been looking at top recently too, and memory is tight, but the PC meets the minimum specification stated on the Airtime website

    Here's the output of top:

    top - 18:59:52 up 2 days,  5:48,  2 users,  load average: 0.34, 0.34, 0.50
    Tasks: 158 total,   1 running, 157 sleeping,   0 stopped,   0 zombie
    Cpu(s): 29.7%us, 16.5%sy,  0.0%ni, 52.5%id,  1.0%wa,  0.0%hi,  0.3%si,  0.0%st
    Mem:    506052k total,   488848k used,    17204k free,    17280k buffers
    Swap:   520188k total,   137060k used,   383128k free,   133308k cached
    
      PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
      886 pypo      20   0 80708  16m 2472 S 28.5  3.3 654:34.08 liquidsoap  
    13310 www-data  20   0 40004  20m 4304 S  9.0  4.1   2:46.99 apache2 
     1085 postgres  20   0 46952 1876 1528 S  0.3  0.4   0:39.94 postgres
     1191 rabbitmq  20   0 20800 3764  768 S  0.3  0.7   2:08.44 beam
     6223 www-data  20   0 41668  16m 5028 S  0.3  3.4   0:53.68 apache2
    12743 www-data  20   0 41668 9264 4808 S  0.3  1.8   5:09.51 apache2
        1 root      20   0  2916  924  536 S  0.0  0.2   0:01.14 init
        2 root      20   0     0    0    0 S  0.0  0.0   0:00.00 kthreadd 
        3 root      20   0     0    0    0 S  0.0  0.0   0:51.84 ksoftirqd/0
        5 root      20   0     0    0    0 S  0.0  0.0   0:00.44 kworker/u:0
        6 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0
        7 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 cpuset 
        8 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 khelper
        9 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 netns
       10 root      20   0     0    0    0 S  0.0  0.0   0:00.65 sync_supers
       11 root      20   0     0    0    0 S  0.0  0.0   0:00.01 bdi-default
       12 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kintegrityd
       13 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kblockd
       14 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kacpid
       15 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kacpi_notify
       16 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kacpi_hotplug
       17 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 ata_sff
       18 root      20   0     0    0    0 S  0.0  0.0   0:00.00 khubd
       19 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 md
       20 root      20   0     0    0    0 S  0.0  0.0   0:00.20 kworker/u:1
       22 root      20   0     0    0    0 S  0.0  0.0   0:00.11 khungtaskd
       23 root      20   0     0    0    0 S  0.0  0.0   0:16.73 kswapd0
       24 root      25   5     0    0    0 S  0.0  0.0   0:00.00 ksmd
       25 root      20   0     0    0    0 S  0.0  0.0   0:00.00 fsnotify_mark
       26 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 aio 
       27 root      20   0     0    0    0 S  0.0  0.0   0:00.00 ecryptfs-kthrea
       28 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 crypto  
       32 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kthrotld
       34 root      20   0     0    0    0 S  0.0  0.0   0:00.03 scsi_eh_0 
       35 root      20   0     0    0    0 S  0.0  0.0   0:00.00 scsi_eh_1
       38 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kmpathd 
       40 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kmpath_handlerd
       41 root       0 -20     0    0    0 S  0.0  0.0   0:00.00 kondemand
  • Vote Up0Vote Down Andrey PodshivalovAndrey Podshivalov
    Posts: 1,526Member, Administrator, Sourcefabric Team
    hmm, interesting. Usually postgres has 4-5 processes and apache about 10 (according conf file settings)