Details
-
Bug
-
Resolution: Done
-
Major
-
4.5.0
-
None
-
Untriaged
-
Centos 64-bit
-
Unknown
Description
I have a couple of VMs I don't use very often, but I have noticed that every once in a while when I look, port 8091 is no longer listening. That was the case again today.
As root:
[root@e1810893-0a95-e869-8c6c-e74f60849621 ~]# netstat -ln | grep 8091
|
tcp 0 0 0.0.0.0:18091 0.0.0.0:* LISTEN
|
[root@e1810893-0a95-e869-8c6c-e74f60849621 ~]# ps -u couchbase
|
PID TTY TIME CMD
|
5895 ? 4-07:22:00 beam.smp
|
5967 ? 00:00:00 cpu_sup
|
5971 ? 00:03:50 inet_gethost
|
5825 ? 11:54:21 beam.smp
|
5966 ? 00:00:44 memsup
|
5482 ? 00:05:30 epmd
|
5973 ? 00:03:04 inet_gethost
|
5962 ? 00:00:24 bash
|
6739 ? 00:00:00 goport
|
6743 ? 00:00:00 goxdcr
|
6190 ? 01:45:14 goport
|
40324 ? 00:09:43 moxi
|
6192 ? 01:16:18 goport
|
6193 ? 00:00:01 saslauthd-port
|
6195 ? 00:14:54 beam.smp
|
6217 ? 01:20:30 goport
|
6806 ? 00:00:00 beam.smp
|
6231 ? 23:06:09 memcached
|
6258 ? 00:12:01 cbq-engine
|
6259 ? 02:53:53 projector
|
6260 ? 00:10:31 cbft
|
13872 ? 00:04:07 inet_gethost
|
After a restart, 8091 listens again.
Note that you may see some odd things in the logs, as at one point I had two nodes clustered, then broke them up for a different project but had not rebalanced out the node from the other cluster. I don't think it is related to this 8091 stopping listening, because it happened on both the cluster with a node in a failed state and the cluster of one. There should be no way for a node not clustered with another to be able to harmfully impact another one.