LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Enterprise Linux Forums > Linux - Enterprise
User Name
Password
Linux - Enterprise This forum is for all items relating to using Linux in the Enterprise.

Notices


Reply
  Search this Thread
Old 01-31-2018, 09:41 AM   #1
stonith
LQ Newbie
 
Registered: Jan 2018
Location: Rome
Distribution: Red Hat - Centos
Posts: 4

Rep: Reputation: Disabled
Systemctl shows inactive service in PCS Cluster


Hi all,
first post here hence thanks to all who are reading.
I've a two node pcs cluster with VIP Address, a bounch of other resources and a vsftpd service.
My question is: we are able to login to ftp service and use it but, meanwhile, systemctl shows the vsftpd service as inactive and unloaded in the running host (and obviously on the other one).
Is that behaviour correct? I'm supposed to monitor the status with a nagios based product looking at the service status but I'm actually unable to do it.

Thanks in advance.
 
Old 01-31-2018, 07:36 PM   #2
JockVSJock
Senior Member
 
Registered: Jan 2004
Location: SATX
Distribution: RHEL/CentOS
Posts: 1,254
Blog Entries: 4

Rep: Reputation: 135Reputation: 135
What OS are you using?

Using systemd? If so, what happens if you try to restart the daemon?

Code:
systemctl status service-goes-here && systemctl restart service-goes-here
Does journalctl show anything along with system-analyze?
 
Old 02-01-2018, 03:29 AM   #3
stonith
LQ Newbie
 
Registered: Jan 2018
Location: Rome
Distribution: Red Hat - Centos
Posts: 4

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by JockVSJock View Post
What OS are you using?

Using systemd? If so, what happens if you try to restart the daemon?

Code:
systemctl status service-goes-here && systemctl restart service-goes-here
Does journalctl show anything along with system-analyze?
Hi,

we're using Centos 7.3.1611

if we run systemctl status vsftpd the output goes like this:

Code:
[root@visualweather-cls2 ~]# systemctl status vsftpd && systemctl restart vsftpd
● vsftpd.service - Vsftpd ftp daemon
   Loaded: loaded (/usr/lib/systemd/system/vsftpd.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

Jan 30 15:44:06 visualweather-cls2 systemd[1]: Starting Vsftpd ftp daemon...
Jan 30 15:44:09 visualweather-cls2 systemd[1]: vsftpd.service: control process exited, code=exited status=1
Jan 30 15:44:09 visualweather-cls2 systemd[1]: Failed to start Vsftpd ftp daemon.
Jan 30 15:44:09 visualweather-cls2 systemd[1]: Unit vsftpd.service entered failed state.
Jan 30 15:44:09 visualweather-cls2 systemd[1]: vsftpd.service failed.
[root@visualweather-cls2 ~]#
journalctl doesn't give us any clue.

I noticed that the resource seems to have a proprietary provider:

Code:
Cluster name: visualweathercls
Stack: corosync
Current DC: visualweather-cls1 (version 1.1.15-11.el7_3.4-e174ec8) - partition with quorum
Last updated: Thu Feb  1 09:27:49 2018          Last change: Sat Jan 27 12:55:22 2018 by hacluster via crmd on visualweather-cls1

2 nodes and 8 resources configured

Online: [ visualweather-cls1 visualweather-cls2 ]

Full list of resources:

 virtual_ip     (ocf::heartbeat:IPaddr2):       Started visualweather-cls2
 Resource Group: vw-storage
     vw-app     (ocf::heartbeat:Filesystem):    Started visualweather-cls2
     vw-supercache      (ocf::heartbeat:Filesystem):    Started visualweather-cls2
     vw-home    (ocf::heartbeat:Filesystem):    Started visualweather-cls2
     vw-data    (ocf::heartbeat:Filesystem):    Started visualweather-cls2
     area_test  (ocf::heartbeat:Filesystem):    Started visualweather-cls2
 VisualWeather  (ocf::ibl:visualweather):       Started visualweather-cls2
 vsftpd (ocf::ibl:vsftpd):      Started visualweather-cls2

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
this could be done by a custom installation by the software team, I'm going to investigate that thing.
 
Old 02-01-2018, 12:58 PM   #4
sgrlscz
Member
 
Registered: Aug 2008
Posts: 75

Rep: Reputation: 46
When you're running as a cluster, the cluster resource manager controls the services that are defined as resources. So, if vsftpd is defined as a cluster resource, then the cluster software would be managing it.

Systemd would be used to start/stop the cluster service, then the cluster service would control starting/stopping the cluster resources.
 
Old 02-02-2018, 04:08 AM   #5
stonith
LQ Newbie
 
Registered: Jan 2018
Location: Rome
Distribution: Red Hat - Centos
Posts: 4

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by sgrlscz View Post
When you're running as a cluster, the cluster resource manager controls the services that are defined as resources. So, if vsftpd is defined as a cluster resource, then the cluster software would be managing it.

Systemd would be used to start/stop the cluster service, then the cluster service would control starting/stopping the cluster resources.
What give me nuts is that on corosync/pacemaker running on Centos/RHEL v 6.x we don't notice a similar behaviour. For istance, we have an nfs server running several fs shares over network. Once started we already have the control of the daemon by simply submit "service nfs status".
Maybe there could be some differences between the cluster stacks?
 
Old 02-02-2018, 08:44 AM   #6
sgrlscz
Member
 
Registered: Aug 2008
Posts: 75

Rep: Reputation: 46
Quote:
Originally Posted by stonith View Post
What give me nuts is that on corosync/pacemaker running on Centos/RHEL v 6.x we don't notice a similar behaviour. For istance, we have an nfs server running several fs shares over network. Once started we already have the control of the daemon by simply submit "service nfs status".
Maybe there could be some differences between the cluster stacks?
It's more likely it's because there is a huge difference between systemd and chkconfig/service.

On Centos/RHEL 6, the startup scripts could be run by calling them directly or using the service command or enabling them through chkconfig, and you'd get the same behavior because they are doing the same thing. The service command is just a script that invokes the startup script, so it doesn't distinguish between services enabled through chkconfig or started by directly invoking the startup script.

Systemd is completely different, and if it's not controlling the service itself, it can't report the status of the service. So, if corosync/pacemaker starts vsftp on it's own, systemd doesn't know it's running.
 
1 members found this post helpful.
Old 02-02-2018, 08:47 AM   #7
stonith
LQ Newbie
 
Registered: Jan 2018
Location: Rome
Distribution: Red Hat - Centos
Posts: 4

Original Poster
Rep: Reputation: Disabled
Thanks for your reply, everything is clear now
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
I am unable to start named.service using systemctl blason Linux - Server 5 12-01-2017 01:57 PM
Problem with MySQL install on virt CentOS,no /var/lib/mysql/mysql.sock , systemctl start mysqld.service dont run the service Positive1 CentOS 1 08-13-2016 04:33 AM
Job for vncserver@:1.service failed. See 'systemctl status vncserver@:1.service' and anis123 Linux - Server 0 09-16-2015 09:44 AM
[SOLVED] What is the purpose of systemctl start named.service? Echopurrs Linux - Newbie 1 07-07-2014 01:43 AM

LinuxQuestions.org > Forums > Enterprise Linux Forums > Linux - Enterprise

All times are GMT -5. The time now is 05:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration