MRatWork Forum by Mustafa Ramadhan

Sawo Project - Kloxo-MR Discussions => Kloxo-MR Technical Helps => Topic started by: alexo on 2014-02-01, 16:42:56

Title: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: alexo on 2014-02-01, 16:42:56
Hello,

After fresh install (it's my 3-rd vps account), after last update i got such text at the end
Code: [Select]

[root@dl ~]# supervise: fatal: unable to acquire send/supervise/lock: temporary failure
supervise: fatal: unable to acquire send/supervise/lock: temporary failure
supervise: fatal: unable to acquire send/supervise/lock: temporary failure

Load average is high

Code: [Select]
top - 10:37:38 up 20:18,  1 user,  load average: 3.01, 3.36, 3.37

Sar command

Code: [Select]
10:00:01          all     91.96      0.01      7.89      0.00      0.10      0.04
10:10:01          all     91.98      0.01      7.87      0.00      0.08      0.06
10:20:01          all     91.86      0.03      7.96      0.00      0.07      0.08
10:30:01          all     92.01      0.00      7.87      0.00      0.06      0.06
Average:          all     92.03      0.03      7.78      0.00      0.09      0.07
Code: [Select]
php -v
PHP 5.3.28 (cli) (built: Dec 18 2013 20:33:28)
Copyright (c) 1997-2013 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2013 Zend Technologies

Code: [Select]
A. Kloxo-MR: 6.5.0.f-2014013101

B. OS: CentOS release 5.10 (Final) i686

C. Apps:
   1. MySQL: mysql55-5.5.35-1.ius.el5
   2. PHP: php53u-5.3.28-1.ius.el5
   3. Httpd: httpd-2.2.26-1.el5
   4. Lighttpd: --uninstalled--
   5. Nginx: --uninstalled--
   6. Qmail: qmail-toaster-1.03-1.3.35.mr.el5
      - with: courier-imap-toaster-4.1.2-1.3.14.mr.el5
   7. Dns: bind-9.9.5-1.el5

D. Php-type (for Httpd/proxy): php-fpm_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:           512        451         60          0          0        224
   -/+ buffers/cache:        227        284
   Swap:          512          4        507

Any advice?
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: chrisf on 2014-02-01, 16:46:12
Reboot.
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: alexo on 2014-02-01, 17:10:16
Code: [Select]
yum reinstall *-toaster
yum reinstall mysql*
sh /script/fixmail-all
yum clean all
yum update
sh /script/cleanup
reboot

sar 3 30
Code: [Select]
11:07:27          all     92.15      0.00      7.85      0.00      0.00      0.00
11:07:30          all     90.55      0.00      8.29      0.00      0.83      0.33

top

Code: [Select]
top - 11:08:07 up 3 min,  2 users,  load average: 2.93, 1.54, 0.62
Tasks: 120 total,   4 running, 114 sleeping,   2 stopped,   0 zombie
Cpu(s): 91.7%us,  7.8%sy,  0.0%ni,  0.2%id,  0.0%wa,  0.0%hi,  0.0%si,  0.3%st
Mem:    524288k total,   198344k used,   325944k free,        0k buffers
Swap:   524288k total,        0k used,   524288k free,    52400k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1223 qmailr    20   0  2564 1104  980 R 83.8  0.2   1:44.82 qmail-remote
 1192 qmailr    20   0  2564 1108  980 R 65.5  0.2   2:01.74 qmail-remote
 1200 qmailr    20   0  2564 1104  980 R 49.2  0.2   3:05.68 qmail-remote
 2088 root      20   0 10164 3308 2752 S  0.3  0.6   0:00.04 sshd
    1 root      20   0  2176  668  576 S  0.0  0.1   0:00.01 init
    2 root      20   0     0    0    0 S  0.0  0.0   0:00.00 kthreadd/465
    3 root      20   0     0    0    0 S  0.0  0.0   0:00.00 khelper/465
  326 root      16  -4  2280  596  384 S  0.0  0.1   0:00.00 udevd
 1071 root      20   0  1832  580  488 S  0.0  0.1   0:00.00 syslogd

:-(
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: chrisf on 2014-02-01, 17:14:09
did you reboot?
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: alexo on 2014-02-01, 17:15:58
Yes of course. But after repoot i wait 10 minutes, and only after this boot server only via SolusVM panel "boot " option.

Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: chrisf on 2014-02-01, 17:18:23
From command line try 'reboot'

Supervise lock should go away on reboot.  In panel, is there mail stuck in the queue?

Could be you have a lot of mail backed up and qmail is trying to process it.  What is /var/log/maillog reporting?
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: alexo on 2014-02-01, 17:26:02
Ok. i'll try to reboot it from command line.
No, just 3 emails in mail queue.
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: chrisf on 2014-02-01, 17:31:08
Report /var/log/maillog any errors?
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: alexo on 2014-02-01, 17:53:25
Quote
Could be you have a lot of mail backed up and qmail is trying to process it.  What is /var/log/maillog reporting?

No, it's impossible, as i don't use any mail service in this account (all my sites, which are disabled just now, use external email settings on gmail).

it's a short part for today -

Code: [Select]
Feb  1 11:15:51 dl send: 1391271351.351459 end msg 38278330
Feb  1 11:16:50 dl authlib: 1391271410.282226 INFO: stopping authdaemond children
Feb  1 11:24:16 dl smtp: 1391271856.296260 tcpserver: status: 0/10
Feb  1 11:24:16 dl authlib: 1391271856.297516 INFO: modules="authvchkpw", daemons=15
Feb  1 11:24:16 dl authlib: 1391271856.297693 INFO: Installing libauthvchkpw
Feb  1 11:24:16 dl authlib: 1391271856.297707 INFO: Installation complete: authvchkpw
Feb  1 11:24:16 dl pop3: 1391271856.304100 tcpserver: status: 0/200
Feb  1 11:24:16 dl send: 1391271856.305643 status: local 0/10 remote 0/60
Feb  1 11:24:16 dl send: 1391271856.305924 starting delivery 1: msg 38289854 to remote root@localhost.
Feb  1 11:24:16 dl send: 1391271856.306011 status: local 0/10 remote 1/60
Feb  1 11:24:16 dl send: 1391271856.306118 starting delivery 2: msg 38289856 to remote root@.
Feb  1 11:24:16 dl send: 1391271856.306531 status: local 0/10 remote 2/60
Feb  1 11:24:16 dl send: 1391271856.306580 starting delivery 3: msg 38289858 to remote root@.
Feb  1 11:24:16 dl send: 1391271856.306592 status: local 0/10 remote 3/60
Feb  1 11:24:16 dl imap4-ssl: 1391271856.336968 tcpserver: status: 0/40
Feb  1 11:24:16 dl imap4: 1391271856.337603 tcpserver: status: 0/40
Feb  1 11:24:16 dl pop3-ssl: 1391271856.346278 tcpserver: status: 0/40
Feb  1 11:24:16 dl submission: 1391271856.350222 tcpserver: status: 0/10
Feb  1 11:24:16 dl smtp-ssl: 1391271856.367666 tcpserver: status: 0/10
Feb  1 11:26:42 dl authlib: 1391272002.935540 INFO: stopping authdaemond children
Feb  1 11:32:14 dl send: 1391272334.216895 status: local 0/10 remote 0/60
Feb  1 11:32:14 dl send: 1391272334.217073 starting delivery 1: msg 38289854 to remote root@localhost.
Feb  1 11:32:14 dl send: 1391272334.217088 status: local 0/10 remote 1/60
Feb  1 11:32:14 dl send: 1391272334.217099 starting delivery 2: msg 38289856 to remote root@.
Feb  1 11:32:14 dl send: 1391272334.217108 status: local 0/10 remote 2/60
Feb  1 11:32:14 dl send: 1391272334.217118 starting delivery 3: msg 38289858 to remote root@.
Feb  1 11:32:14 dl send: 1391272334.217128 status: local 0/10 remote 3/60
Feb  1 11:32:14 dl authlib: 1391272334.226792 INFO: modules="authvchkpw", daemons=15
Feb  1 11:32:14 dl authlib: 1391272334.226977 INFO: Installing libauthvchkpw
Feb  1 11:32:14 dl authlib: 1391272334.226992 INFO: Installation complete: authvchkpw
Feb  1 11:32:14 dl pop3: 1391272334.236848 tcpserver: status: 0/200
Feb  1 11:32:14 dl imap4-ssl: 1391272334.272165 tcpserver: status: 0/40
Feb  1 11:32:14 dl pop3-ssl: 1391272334.276597 tcpserver: status: 0/40
Feb  1 11:32:14 dl imap4: 1391272334.285205 tcpserver: status: 0/40
Feb  1 11:32:14 dl submission: 1391272334.297618 tcpserver: status: 0/10
Feb  1 11:32:14 dl smtp: 1391272334.311676 tcpserver: status: 0/10
Feb  1 11:32:14 dl smtp-ssl: 1391272334.319673 tcpserver: status: 0/10
Hmm,

It's something amazing -

full file is here - http://bit.ly/1cGXwhB (just change "MyRealDomain" name to "mydomain.net")

--
What this mean?????

Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: alexo on 2014-02-01, 18:19:24
Nice :-)
Now i cann't boot it via SolusVM ? just have Console access :-(
Is there any way to stop the process that eat so much resources and boot server ?

Any advice !!! please

Via console
Code: [Select]
service qmail stop
Already stopped.
Qmail-send: no process killed
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: MRatWork on 2014-02-01, 18:39:24
Try from VNC.
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: chrisf on 2014-02-01, 19:03:48
It appears that after numerous problems on this forum, one pattern exist.   Servers with 512 mb ram.  KloxoMR 'IN MY OPINION' needs at least 1GB for normal hosting (private) and 4+ GB for shared (depending on total clients).

It will run on 512 MB, just seems to be problematic.
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: MRatWork on 2014-02-01, 19:07:15
If using php-fpm (apache with php-fpm_worker/_event, nginx, lighttpd and hiawatha) please don't create many clients (reseller and customer). For 512MB better no more then 5 clients.
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: alexo on 2014-02-02, 16:17:07
Quote
If using php-fpm (apache with php-fpm_worker/_event, nginx, lighttpd and hiawatha) please don't create many clients (reseller and customer). For 512MB better no more then 5 clients.

Ok. You said me 512mb is less, i move from this VPS to 1gb RAM.
Once again fresh install, php53u, no more than 5 users and after few days the same picture,

1. the same error -> "supervise: fatal: unable to acquire send/supervise/lock: temporary failure"
2. load average is load average: 3.93, 1.54, 0.62


and as result - my account is DOWN !!!
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: MRatWork on 2014-02-03, 04:28:33
For 'supervise: fatal: unable to acquire send/supervise/lock: temporary failure', try 'yum reinstall *-toaster; sh /script/fixmail-all; sh /script/restart-mail'.

About using php, possible any website using php itself too much (too long process upper then timeout).
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: alexo on 2014-02-03, 14:45:19
Thank you very much

For 'supervise: fatal: unable to acquire send/supervise/lock: temporary failure', try 'yum reinstall *-toaster; sh /script/fixmail-all; sh /script/restart-mail'.

Ok, I'll try.

About using php, possible any website using php itself too much (too long process upper then timeout).

There isn't any heavy website in this account, so it's a little suprizing for me. Anyway this account work well 3 years on Kloxo official with 512MB RAM.

Thx
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: MRatWork on 2014-02-03, 14:58:18
In my experience, it's enough for 5 clients with wordpress with 'standard' plugins. Plugin like 'seo optimize' need more php process.
Title: Re: supervise: fatal: unable to acquire send/supervise/lock: temporary failure
Post by: MRatWork on 2014-02-03, 15:00:08
I mean 5 clients including 'admin' user. So, not using for domain hosting make waste php resource.