Please see listing below - postfix is running, this can be confirmed by Linux commands ( “ps” and “systemctl status”).
BESAgent “qna” is clearly wrong… I saw it being wrong for several other services.
Any ideas?
Thank you,
Aleksandr
[root@myhost ~]# ps -ef | egrep -i postf
root 2951 1 0 Mar30 ? 00:00:01 /usr/libexec/postfix/master -w
postfix 2966 2951 0 Mar30 ? 00:00:00 qmgr -l -t unix -u
postfix 958627 2951 0 18:30 ? 00:00:00 pickup -l -t unix -u
root 1039525 1015259 0 19:45 pts/0 00:00:00 grep -E --color=auto -i postf
[root@myhost ~]#
[root@myhost ~]# systemctl status postfix
● postfix.service - Postfix Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2025-03-30 17:51:46 EDT; 4 days ago
Main PID: 2951 (master)
Tasks: 3 (limit: 1647195)
Memory: 7.8M
CGroup: /system.slice/postfix.service
├─ 2951 /usr/libexec/postfix/master -w
├─ 2966 qmgr -l -t unix -u
└─958627 pickup -l -t unix -u
Apr 01 21:20:00 myhost postfix/pickup[2424613]: 3BF6F215E78D: uid=0 from=
Apr 01 21:20:00 myhost postfix/cleanup[2497690]: 3BF6F215E78D: message-id=20250402012000.3BF6F215E78D@myhost.domain.mycompany.com
Apr 01 21:20:00 myhost postfix/qmgr[2966]: 3BF6F215E78D: from=root@myhost.domain.mycompany.com, size=440, nrcpt=1 (queue active)
Apr 01 21:20:00 myhost postfix/local[2497693]: 3BF6F215E78D: to=root@myhost.domain.mycompany.com, orig_to=, relay=local, delay=0.05, >
Apr 01 21:20:00 myhost postfix/qmgr[2966]: 3BF6F215E78D: removed
Apr 02 21:20:00 myhost postfix/pickup[3696047]: 13EF0215E78E: uid=0 from=
Apr 02 21:20:00 myhost postfix/cleanup[3725941]: 13EF0215E78E: message-id=20250403012000.13EF0215E78E@myhost.domain.mycompany.com
Apr 02 21:20:00 myhost postfix/qmgr[2966]: 13EF0215E78E: from=root@myhost.domain.mycompany.com, size=440, nrcpt=1 (queue active)
Apr 02 21:20:00 myhost postfix/local[3725944]: 13EF0215E78E: to=root@myhost.domain.mycompany.com, orig_to=, relay=local, delay=0.07, >
Apr 02 21:20:00 myhost postfix/qmgr[2966]: 13EF0215E78E: removed
[root@myhost ~]#
[root@myhost ~]#
[root@myhost ~]# /opt/BESClient/bin/qna
Default masthead location, using /etc/opt/BESClient/actionsite.afxm
Q: service “postfix”
A: “postfix” “postfix” “Stopped”
T: 4981
Q: ^C
[root@myhost ~]#
Are you trying to understand if the Service is enabled or If the process is running?
If you want to check if the service is enabled - please check - Check if unbound-anchor.timer enabled using relevance
There is also an idea to expand the service inspector to all OS: HCL Software - Sign In, welcome to vote.
Thanks a lot for pointing me to the document!
My system is Red Hat Linux, it is not one of the Linux flavors mentioned in the document, so I still think that the observed behavior is a bug.
Please see the output from “services” below, status of services is mostly correct.
[root@myhost ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.10 (Ootpa)
[root@myhost ~]#
[root@myhost ~]# /opt/BESClient/bin/qna
Default masthead location, using /etc/opt/BESClient/actionsite.afxm
Q: services
A: “afd” “afd” “Unknown”
A: “enlinuxpc” “enlinuxpc” “Unknown”
A: “gcagent” “gcagent” “Unknown”
A: “init.ohasd” “init.ohasd” “Unknown”
A: “init.tfa” “init.tfa” “Unknown”
A: “netprobe” “netprobe” “Unknown”
A: “ohasd” “ohasd” “Unknown”
A: “oracle-database-preinstall-19c-firstboot” “oracle-database-preinstall-19c-firstboot” “Unknown”
A: “OSWatcher” “OSWatcher” “Unknown”
A: “arp-ethers” “arp” “Stopped”
A: “atd” “atd” “Running”
A: “auditd” “auditd” “Stopped”
A: “autofs” “automount” “Running”
A: “autovt@” “agetty” “Running”
A: “BESClient” “BESClient” “Running”
A: “blk-availability” “true” “Stopped”
A: “chronyd” “chronyd” “Running”
A: “chrony-wait” “chronyc” “Stopped”
A: “console-getty” “agetty” “Running”
A: “cpupower” “cpupower” “Stopped”
A: “crond” “crond” “Running”
A: “debug-shell” “sh” “Stopped”
A: “dnf-system-upgrade” “dnf” “Stopped”
A: “ebtables” “ebtables” “Stopped”
A: “falcon-sensor” “falcond” “Stopped”
A: “firewalld” “firewalld” “Stopped”
A: “getty@” “agetty” “Running”
A: “goferd” “env” “Stopped”
A: “gssproxy” “gssproxy” “Running”
A: “import-state” “import-state” “Stopped”
A: “insights-client-boot” “insights-client” “Stopped”
A: “iprdump” “iprdump” “Stopped”
A: “iprinit” “iprinit” “Stopped”
A: “iprupdate” “iprupdate” “Stopped”
A: “irqbalance” “irqbalance” “Running”
A: “kdump” “kdumpctl” “Stopped”
A: “kvm_stat” “kvm_stat” “Stopped”
A: “loadmodules” “loadmodules” “Stopped”
A: “lvm2-monitor” “lvm” “Stopped”
A: “man-db-restart-cache-update” “systemd-run” “Stopped”
A: “mdmonitor” “mdadm” “Stopped”
A: “microcode” “reload_microcode” “Stopped”
A: “NetworkManager” “NetworkManager” “Running”
A: “NetworkManager-wait-online” “nm-online” “Stopped”
A: “nfs-blkmap” “blkmapd” “Stopped”
A: “nfs-server” “sh” “Stopped”
A: “nftables” “nft” “Stopped”
A: “nis-domainname” “nis-domainname” “Stopped”
A: “oddjobd” “oddjobd” “Running”
A: “pmloadcheck” “pmloadcheck” “Running”
A: “pmserviced” “pmserviced” “Running”
A: “postfix” “postfix” “Stopped”
A: “qualys-cloud-agent” “qualys-cloud-agent” “Running”
A: “rdisc” “rdisc” “Stopped”
A: “rhsmcertd” “rhsmcertd” “Running”
A: “rhsm-facts” “rhsm-facts-service” “Stopped”
A: “rhsm” “rhsm-service” “Stopped”
A: “rngd” “rngd” “Running”
A: “rpcbind” “rpcbind” “Running”
A: “rsyslog” “rsyslogd” “Running”
A: “salt-minion” “salt-minion” “Stopped”
A: “salt-proxy@” “salt-proxy” “Stopped”
A: “selinux-autorelabel-mark” “touch” “Stopped”
A: “serial-getty@” “agetty” “Running”
A: “smartd” “smartd” “Running”
A: “sshd-keygen@” “sshd-keygen” “Stopped”
A: “sshd” “sshd” “Running”
A: “sssd” “sssd” “Running”
A: “sysstat” “sa1” “Stopped”
A: “systemd-pstore” “systemd-pstore” “Stopped”
A: “systemd-resolved” “systemd-resolved” “Stopped”
A: “tcsd” “tcsd” “Stopped”
A: “tuned” “tuned” “Stopped”
A: “udisks2” “udisksd” “Running”
A: “vmtoolsd” “vmtoolsd” “Running”
T: 1118246
Q: ^C
[root@myhost ~]#
Thank you for writing!
I don’t think my issue requires adding new functionality to the service inspector - I think vendor should fix the bug in the existing BESAgent.
@anepomn have you opened a support case?
I believe the issue is in the inspector still using init.d rather than systemd services. I’d recommend opening a support incident, at least for tracking, but I think this is a problem that might work itself out over the next release or two.
Does this mean that there is work happening to improve this inspector?
Future roadmap things (even short term) is the domain of @Aram
Thank you, I did open a support case.
Jason,
thank you, I did open a support case.
Jason,
You were right as always 
It appears that issue is fixed in BESAgent-11.0.4.60-rhe7.x86_64 (I am using BESAgent-11.0.2.125-rhe7.x86_64 on all the hosts).
Thank you,
Aleksandr
1 Like
Interesting cause it is not even documented in the “Inspector Changes” of the new version, cause this is significant enough change to allow a ton of Compliance Checks and entire delivery mechanisms to be rewritten, including the complete removal of Compliance “Deploy & Run” functionality which was all based on the fact that client can’t check service statuses, so an action is ran to output statuses to file which then all the service-based checks were using…
Yeah, that’s, uh, interesting.
There were several notes on systemd service inspector changes on our internal docs, I’ll check later today to see what more we should put on the announcement.
In case you need it - please see listing from basic testing below.
Behavior changed after an upgrade - status of 2 services was reported incorrectly with BESAgent-11.0.2.125-rhe7.x86_64 is reported correctly with BESAgent-11.0.4.60-rhe7.x86_64.
========================================= before upgrade
[root@myhost ~]# rpm -q BESAgent
BESAgent-11.0.2.125-rhe7.x86_64
[root@myhost ~]#
[root@myhost ~]# /opt/BESClient/bin/qna
Default masthead location, using /etc/opt/BESClient/actionsite.afxm
Q: service “postfix”
A: “postfix” “postfix” “Stopped”
T: 4146
Q: service “salt-minion”
A: “salt-minion” “salt-minion” “Stopped”
T: 232
Q: ^C
[root@myhost ~]#
========================================= after upgrade
[root@myhost ~]# rpm -q BESAgent
BESAgent-11.0.4.60-rhe7.x86_64
[root@myhost ~]#
[root@myhost ~]# /opt/BESClient/bin/qna
Default masthead location, using /etc/opt/BESClient/actionsite.afxm
Q: service “postfix”
A: “postfix” “postfix” “Running”
T: 5321
Q: service “salt-minion”
A: “salt-minion” “salt-minion” “Running”
T: 853
Q: ^C
[root@myhost ~]#
1 Like
I agree, this seems like the kind of plumbing change that is noteworthy enough to, er, note in the release notes.
Given the oft-alignment of issues shared among not-Windows platforms, if the work on this was somehow related?
New “named” constructor for process inspector on MacOS to return the process object corresponding to the specified name.
-Andrew
I’m talking internally to update the Release Notes in this area.
We’ve enhanced the ‘service’ inspector, to support systemd services and distinguish between systemd and systemV services, for RHEL, SLES, and derived platforms only; I don’t think this applies to Debian, Ubuntu, or their derivations.
- ‘runlevel’ property (systemV services only)
- ‘target’ property (systemd services only)
Affects ‘state’, ‘running’ properties and ‘service’, ‘service ’ creation.
- Only on RHEL, SLES, and derived platforms.
Q: targets of service "sshd"
A: multi-user.target
T: 252
Q: (it, state of it) of services
A: "accounts-daemon" "accounts-daemon" "Running", Running
A: "arp-ethers" "arp" "Stopped", Stopped
A: "atd" "atd" "Running", Running
A: "auditd" "auditd" "Running", Running
A: "autovt@" "agetty" "Stopped", Stopped
A: "avahi-daemon" "avahi-daemon" "Running", Running
...
3 Likes
