• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint

finbarr69

Basic Pleskian
I am getting this message twice every 5 minutes in /var/log/monit.log : Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected

This is on Plesk 11.5.30 Update #32 on CentOs 6.5 (Final)

I found an article which says this was fixed in Plesk 10.4, but we are already at 11.5.30

Any ideas what's wrong?

Thanks

Brian
 
That is weired to still have the same problem if it were resolved in earlier versions ...
My trial would be first to copy and backup the file
Code:
/usr/local/psa/admin/bin/modules/watchdog/monit
Then, replace it according to the instructions here:

http://kb.parallels.com/en/112302

And see if that helps, and if it doesn't then most likely a bug you could report to Plesk team.
 
Yes, that was the article that I found, but I did not want to follow it as it said it only applies to 10.3 and we are on 11.5.30 Update #32

I made the change anyway, and the error still keeps appearing every 5 minutes.

[GMT Feb 10 16:41:31] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[GMT Feb 10 16:41:31] Collector: no server available -- aborting message
[GMT Feb 10 16:46:33] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[GMT Feb 10 16:46:33] Collector: no server available -- aborting message

Doing the following:

netstat -tulpn | grep :2912

shows nothing is listening on that port. What is supposed to be listening on port 2912? Maybe it just needs something started.

Thanks

Brian
 
Try to do following:

1. Edit /usr/local/psa/etc/modules/watchdog/monitrc_vz.tpl

by changing

check host courier_imap with address 127.0.0.1

to

check process courier_imap with pidfile "/var/run/imapd.pid"

2. /usr/local/psa/admin/bin/modules/watchdog/wd --regen-monitrc
3. /usr/local/psa/admin/bin/modules/watchdog/wd --restart-monit
 
Hello and thanks again.

The file /usr/local/psa/etc/modules/watchdog/monitrc_vz.tpl already contains the text check process courier_imap ...

I don't think the problem is necessarily related to courier imap. Watchdog itself is not reporting any services down. Just this log file entry keeps appearing.

There is only one "check host" entry in /usr/local/psa/etc/modules/watchdog/monitrc_vz.tpl and that is check host coldfusion (which I don't have installed).

So I don't know why it is generating this error.

Thanks

Brian
 
Have you tried solution from KB article? As far as I know it is applicable for current Plesk version.
 
Have you tried solution from KB article? As far as I know it is applicable for current Plesk version.

Hello and thanks. Yes I already said I tried (see post #3, "I made the change anyway"). However, it says in that KB that it applies to 10.3 and the issue is fixed in 10.4 and I am on 11.5.30 anyway. :)

I think this is not related to courier-imap and that kb is a red-herring.

Port 2912 has nothing listening on it. Does anyone know what should be listening on that port?

I see from /usr/local/psa/etc/modules/watchdog/monitrc these entries:

set daemon 300

set logfile /var/log/monit.log
set statefile /var/run/monit.state
set pidfile /var/run/monit.pid

set httpd port 2911 and use address 127.0.0.1
allow 127.0.0.1
allow monit:1f85f9b6cd1a4ba

set collector http://127.0.0.1:2912

This explains the frequency of 5 minutes (300 seconds). I do see an httpd server running on port 2911 and it responds to queries. It is just that the collector is not running (or not running using port 2912).

So, my question is: what runs the collector?

Thanks,

Brian




Thanks,

Brian
 
Collector can be started with

# /usr/local/psa/admin/bin/modules/watchdog/wd --start-wdcollect
 
I have the same problem (since very long time).. all 5 minutes this lines appears in monit.log:

[CET Mar 4 11:07:49] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[CET Mar 4 11:07:49] Collector: no server available -- aborting message
[CET Mar 4 11:12:53] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[CET Mar 4 11:12:53] Collector: no server available -- aborting message
[CET Mar 4 11:17:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[CET Mar 4 11:17:55] Collector: no server available -- aborting message
[CET Mar 4 11:22:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[CET Mar 4 11:22:57] Collector: no server available -- aborting message
[CET Mar 4 11:27:59] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[CET Mar 4 11:27:59] Collector: no server available -- aborting message

I have use this http://kb.parallels.com/en/112302 and replace "monit" with version from http://kb.parallels.com/Attachments/17177/Attachments/dist-rpm-CentOS-6-x86_64.zip (thats not help me)

I use Plesk 11.5.30 #34 with "centOS 6".
 
Last edited:
Yesterday stopped monit

[CET Mar 4 11:27:59] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[CET Mar 4 11:27:59] Collector: no server available -- aborting message
[CET Mar 4 11:33:01] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[CET Mar 4 11:33:01] Collector: no server available -- aborting message
[CET Mar 4 11:34:45] Shutting down monit HTTP server
[CET Mar 4 11:34:45] monit HTTP server stopped
[CET Mar 4 11:34:45] monit daemon with pid [1083] killed

END OF LOG

After 24h its not restarting. Yestersay 11:34 I have call
# shutdown -r now

Why monit not restart with server? Its the old monit file from plesk article? I have change back to original file from 2013. I have try this too:
# service monit start
but get only
monit: unrecognized service

How I can restart monit in plesk 11.5.30#34? I must restart the server?
 
How I can restart monit in plesk 11.5.30#34?

# /usr/local/psa/admin/bin/modules/watchdog/monit restart all

# /usr/local/psa/admin/bin/modules/watchdog/monit -h
for details.
 
Thank you. I have restart the server with plesk GUI and get this in monit.log (I have delete the day in quote):

[10:54:55] Starting monit daemon with http interface at [127.0.0.1:2911]
[10:54:55] Starting monit HTTP server at [127.0.0.1:2911]
[10:54:55] monit HTTP server started
[10:54:55] 'plesk_apache' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'plesk_apache' trying to restart
[10:54:55] 'plesk_apache' start: /etc/init.d/sw-cp-server
[10:54:55] 'apache' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'apache' trying to restart
[10:54:55] 'apache' start: /usr/local/psa/admin/bin/websrvmng
[10:54:55] 'courier_authdaemon' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'courier_authdaemon' trying to restart
[10:54:55] 'courier_authdaemon' start: /usr/local/psa/admin/bin/mailmng-service
[10:54:55] 'courier_imap' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'courier_imap' trying to restart
[10:54:55] 'courier_imap' start: /usr/local/psa/admin/bin/mailmng-service
[10:54:55] 'courier_imaps' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'courier_imaps' trying to restart
[10:54:55] 'courier_imaps' start: /usr/local/psa/admin/bin/mailmng-service
[10:54:55] 'courier_pop3' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'courier_pop3' trying to restart
[10:54:55] 'courier_pop3' start: /usr/local/psa/admin/bin/mailmng-service
[10:54:55] 'courier_pop3s' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'courier_pop3s' trying to restart
[10:54:55] 'courier_pop3s' start: /usr/local/psa/admin/bin/mailmng-service
[10:54:55] 'mysql' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'mysql' trying to restart
[10:54:55] 'mysql' start: /etc/init.d/mysql
[10:54:55] 'nginx' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'nginx' trying to restart
[10:54:55] 'nginx' start: /usr/local/psa/admin/bin/nginx_control
[10:54:55] 'postfix' process is not running
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'postfix' trying to restart
[10:54:55] 'postfix' start: /usr/local/psa/admin/bin/mailmng-service
[10:54:55] 'pc_remote' failed, cannot open a connection to INET[127.0.0.1:12768]
[10:54:55] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:55] Collector: no server available -- aborting message
[10:54:55] 'pc_remote' trying to restart
[10:54:55] 'pc_remote' stop: /usr/local/psa/admin/bin/mailmng-service
[10:54:55] 'pc_remote' start: /usr/local/psa/admin/bin/mailmng-service
[10:54:56] 'bind' process is not running
[10:54:56] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:56] Collector: no server available -- aborting message
[10:54:56] 'bind' trying to restart
[10:54:56] 'bind' start: /usr/local/psa/admin/bin/dnsmng
[10:54:56] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:54:56] Collector: no server available -- aborting message
[10:54:58] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:54:59] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:00] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:01] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:02] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:03] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:04] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:05] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:06] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:07] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:08] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:09] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:10] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:55:11] monit: pidfile `/var/run/nginx.pid' does not contain a valid pidnumber
[10:59:56] 'plesk_apache' process is running with pid 1455
[10:59:56] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:56] Collector: no server available -- aborting message
[10:59:56] HTTP error: Server returned status 401
[10:59:56] 'plesk_apache' failed protocol test [HTTP] at INET[localhost:8443].
[10:59:56] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:56] Collector: no server available -- aborting message
[10:59:56] 'plesk_apache' trying to restart
[10:59:56] 'plesk_apache' stop: /etc/init.d/sw-cp-server
[10:59:57] 'plesk_apache' start: /etc/init.d/sw-cp-server
[10:59:57] 'apache' process is running with pid 1732
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'courier_authdaemon' process is running with pid 1633
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'courier_imap' process is running with pid 1622
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'courier_imaps' process is running with pid 1625
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'courier_pop3' process is running with pid 1623
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'courier_pop3s' process is running with pid 1624
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'mysql' process is running with pid 1453
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'nginx' process is running with pid 2201
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'postfix' process is running with pid 1836
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'pc_remote' connection passed
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:57] 'bind' process is running with pid 1766
[10:59:57] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:57] Collector: no server available -- aborting message
[10:59:59] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[10:59:59] Collector: no server available -- aborting message

after 5min, what this means?

[11:04:59] HTTP error: Server returned status 401
[11:04:59] 'plesk_apache' failed protocol test [HTTP] at INET[localhost:8443].
[11:04:59] 'plesk_apache' trying to restart
[11:04:59] 'plesk_apache' stop: /etc/init.d/sw-cp-server
[11:05:00] 'plesk_apache' start: /etc/init.d/sw-cp-server
[11:05:02] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[11:05:02] Collector: no server available -- aborting message

After 5min again... same error. :(
 
Last edited:
Add to post above:

[11:20:09] 'plesk_apache' service timed out and will not be checked anymore
[11:20:09] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[11:20:09] Collector: no server available -- aborting message
[11:20:11] Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
[11:20:11] Collector: no server available -- aborting message


# /usr/local/psa/admin/bin/modules/watchdog/monit restart all

For centOS 6.5 with Plesk 11.5.30 its not working:

# /usr/local/psa/admin/bin/modules/watchdog/monit restart all
monit: Cannot find the control file at ~/.monitrc, /etc/monitrc, /usr/local/etc/monitrc or at ./monitrc
 
Last edited:
@finbarr69

Have you fixed that problem or found a solution?


Can anybody that read this thread look in /var/log/monit.log and say its look like:

Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
Collector: no server available -- aborting message
Collector: cannot open a connection to http://127.0.0.1:2912/ -- Transport endpoint is not connected
Collector: no server available -- aborting message

I think that is a bug, but no one has noticed it before.
 
Last edited:
I have today restart monit with
/usr/local/psa/admin/bin/modules/watchdog/wd --restart-monit

and get this in /var/log/monit.log
[CET Mar 9 15:10:07] Shutting down monit HTTP server
[CET Mar 9 15:10:08] monit HTTP server stopped
[CET Mar 9 15:10:08] monit daemon with pid [15541] killed
[CET Mar 9 15:10:09] Starting monit daemon with http interface at [127.0.0.1:2911]
[CET Mar 9 15:10:09] Starting monit HTTP server at [127.0.0.1:2911]
[CET Mar 9 15:10:09] monit HTTP server started
[CET Mar 9 15:10:09] HTTP error: Server returned status 401
[CET Mar 9 15:10:09] 'plesk_apache' failed protocol test [HTTP] at INET[localhost:8443].
[CET Mar 9 15:10:09] 'plesk_apache' trying to restart
[CET Mar 9 15:10:09] 'plesk_apache' stop: /etc/init.d/sw-cp-server
[CET Mar 9 15:10:10] 'plesk_apache' start: /etc/init.d/sw-cp-server

Why I get this error?
 
@finbarr69

Have you fixed that problem or found a solution?


Can anybody that read this thread look in /var/log/monit.log and say its look like:



I think that is a bug, but no one has noticed it before.

We also faced the same issue. Did a temporary work around.
Copied the file - /usr/local/psa/etc/modules/watchdog/monitrc to /usr/local/etc/monitrc
and then restarted watchdog using

/usr/local/psa/admin/bin/modules/watchdog/monit stop all
/usr/local/psa/admin/bin/modules/watchdog/monit start all

If the watchdog restart script still gives an error, use the following command -

/usr/local/psa/admin/bin/modules/watchdog/wd --start-wdcollect

And verify whether a service is listening on port 2912
 
I'm still getting this error with the latest Plesk;

Plesk Obsidian
Version 18.0.24, last updated on Mar 14, 2020 10:20 PM

No solution?

Also is mailman no longer monitored?
 
Back
Top