Hi,
I have installed Couchbase 4.5 community version on CentOS 7 . Everything works as expected from server side but noticed some messages on “systemctl status couchbase-server.service” and also the service wont come up after the VM reboot.
Here is the output of "“systemctl status couchbase-server.service”
● couchbase-server.service - Couchbase Server
Loaded: loaded (/usr/lib/systemd/system/couchbase-server.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2017-10-27 22:19:22 GMT; 1s ago
Docs: http://docs.couchbase.com
Process: 31277 ExecStop=/opt/couchbase/bin/couchbase-server -k (code=exited, status=0/SUCCESS)
Process: 31348 ExecStart=/opt/couchbase/bin/couchbase-server – -noinput -detached (code=exited, status=0/SUCCESS)
Main PID: 31418 (beam.smp)
CGroup: /system.slice/couchbase-server.service
├─31360 /opt/couchbase/lib/erlang/erts-5.10.4.0.0.1/bin/epmd -daemon
├─31393 /opt/couchbase/lib/erlang/erts-5.10.4.0.0.1/bin/beam.smp -A 16 – -root /opt/couchbase/lib/erlang -progname erl – -h…
├─31418 /opt/couchbase/lib/erlang/erts-5.10.4.0.0.1/bin/beam.smp -A 16 -sbt u -P 327680 -K true -swt low -MMmcs 30 -e102400 -…
├─31448 sh -s disksup
├─31450 /opt/couchbase/lib/erlang/lib/os_mon-2.2.14/priv/bin/memsup
├─31451 /opt/couchbase/lib/erlang/lib/os_mon-2.2.14/priv/bin/cpu_sup
├─31452 inet_gethost 4
├─31453 inet_gethost 4
├─31454 /opt/couchbase/lib/erlang/erts-5.10.4.0.0.1/bin/beam.smp -P 327680 -K true – -root /opt/couchbase/lib/erlang -progna…
├─31483 sh -s disksup
├─31484 /opt/couchbase/lib/erlang/lib/os_mon-2.2.14/priv/bin/memsup
├─31486 /opt/couchbase/lib/erlang/lib/os_mon-2.2.14/priv/bin/cpu_sup
├─31492 /opt/couchbase/bin/priv/godu
├─31496 sh -s ns_disksup
├─31497 /opt/couchbase/bin/priv/godu
├─31503 /opt/couchbase/bin/moxi -Z port_listen=11211,default_bucket_name=default,downstream_max=1024,downstream_conn_max=4,co…
├─31521 portsigar for ns_1@couchbaseadc01-test.adc1.level3.com
├─31522 /opt/couchbase/bin/goport
├─31526 /opt/couchbase/bin/projector -kvaddrs=127.0.0.1:11210 -adminport=:9999 -diagDir=/opt/couchbase/var/lib/couchbase/cras…
├─31540 /opt/couchbase/bin/goport
├─31544 /opt/couchbase/bin/indexer -vbuckets=1024 -cluster=127.0.0.1:8091 -adminPort=9100 -scanPort=9101 -httpPort=9102 -stre…
├─31560 /opt/couchbase/bin/goport
├─31561 /opt/couchbase/bin/saslauthd-port
└─31567 /opt/couchbase/bin/cbq-engine --datastore=http://127.0.0.1:8091 --http=:8093 --configstore=http://127.0.0.1:8091 --en…
Oct 27 22:19:15 couchbaseadc01-test systemd[1]: Starting Couchbase Server…
Oct 27 22:19:16 couchbaseadc01-test systemd[1]: PID file /opt/couchbase/var/lib/couchbase/couchbase-server.pid not readable (yet?.. start.
Oct 27 22:19:22 couchbaseadc01-test systemd[1]: couchbase-server.service: Supervising process 31418 which is not our child. We’ll… exits.
Oct 27 22:19:22 couchbaseadc01-test systemd[1]: Started Couchbase Server.
Hint: Some lines were ellipsized, use -l to show in full.
I always see this message in the status :
Oct 27 22:19:16 couchbaseadc01-test systemd[1]: PID file /opt/couchbase/var/lib/couchbase/couchbase-server.pid not readable (yet?.. start.
Oct 27 22:19:22 couchbaseadc01-test systemd[1]: couchbase-server.service: Supervising process 31418 which is not our child. We’ll… exits.
What could be wrong here ? Then if I reboot the box the process comes up and goes out due the service timeout and the status again gives me the same messages.
If I comment out “PIDFile=/opt/couchbase/var/lib/couchbase/couchbase-server.pid” in the unit file its all clean.
Thanks
Mahesh