pooler_bottom, not calling plug in anymore

[Rno]

It's look like I have a problem with the plugin hock for poller_bottom
since the upgrade to 1.1.2 it's look like this function exec_background($command_string, $extra_args); inside poller_bottom, is not called correctly

And I have it under monitor or my own plugin, all acting the same.

I find that in the log:
2017-04-21 14:39:39 - POLLER: Poller[1] DEBUG: About to Spawn a Remote Process [CMD: /bin/php, ARGS: /usr/share/cacti-1/plugins/linkdiscovery/findhosts.php > /tmp/findhost.php]
2017-04-21 14:39:39 - POLLER: Poller[1] DEBUG: About to Spawn a Remote Process [CMD: /bin/php, ARGS: -q /usr/share/cacti-1/plugins/monitor/poller_monitor.php > /tmp/monitor.php]

but nothing more, even if i put an error inside eache file called (poller_monitor.php or findhost.php) nothing is displayed oin any log (cacti.log, php_errror or httpd/error_log)

but if i call, at least findhost.php, from the command line it's working.

How can i trace more of this call ?
i try the args to php -q, -e but nothing more to explain what happen

[cigamit]

SELinux?

All my plugins seem to be called just fine.

[Rno]

no, centos

And i can't find why.
i event try that:
into monitor/setup.php, on function monitor_poller_bottom()
I add the following line:
exec_background($command_string, '/usr/share/cacti-1/plugins/linkdiscovery/test.php');

and the test.php his like that:
<?php

print 'test php';

?>

And nothing come out on cacti.log

I can't figure out what is wrong with my system !!
On the same server I have a version 0.8.8h in another directory who is working fine, the user right access is setup correctly all the way arround (to apache:apache)
and on my log nothing, nothing on error_log

[Rno]

I setup my login in DEBUG mode, and I think in this level I should see this messages:
cacti_log("DEBUG: About to Spawn a Remote Process [CMD: $filename, ARGS: $args]", true, 'POLLER', ($debug ? POLLER_VERBOSITY_NONE:POLLER_VERBOSITY_DEBUG));


from the axec_background call, but nothing show up on the cacti log, how come ?

[cigamit]

no, centos

No, my query about SELinux is whether SELinux is enabled under Centos.
cat /etc/sysconfig/selinux

[Rno]

Sorry

here it is:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of three two values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted