Hello all,
I have a SuSE 9.2 system with the following specs:
cacti-0.8.6e-2.3
perl-5.8.5-3.2
mysql-4.0.21-4.4
Later installed: CACTID Version 0.8.6e
After running the cron job for a while I still did not get any information into the graphs.
But because i didn´t found any failures in the logs I removed the trailing pipe from the cron logs: > /dev/null 2>&1
After that I got the failures:
Insecure dependency in `` while running setuid at /usr/share/cacti/scripts/linux_memory.pl line 3.
Insecure dependency in `` while running setuid at /usr/share/cacti/scripts/linux_memory.pl line 3.
Insecure $ENV{PATH} while running setuid at /usr/share/cacti/scripts/loadavg_multi.pl line 4.
Insecure $ENV{PATH} while running setuid at /usr/share/cacti/scripts/unix_users.pl line 8.
Insecure $ENV{PATH} while running setuid at /usr/share/cacti/scripts/unix_processes.pl line 3.
Because I found out that it could be some security setting on PERL I installed the CACTID so the scripts were wrapped.
But that didn´t help either......
So I´m out of idea´s, has anybody some idea´s how to solve this problem?
Greetz, and thanks in advance.
IcemanErwin
PERL failures whith cron job
Moderators: Developers, Moderators
-
- Posts: 1
- Joined: Fri Jul 29, 2005 8:34 am
- Contact:
Hi all,
Further to the original question, on Suse 9.2, I have found that a user name with the underscore also causes problems if programs produce any output in cron. User id without the underscore works fine.
For example
as user a_b "date >/dev/null" in (user) cron tab is OK but "date" produces security warnings and the process seems to segfault.
as user a, both of the above commands in cron work fine.
Any ideas
Many thanks
Further to the original question, on Suse 9.2, I have found that a user name with the underscore also causes problems if programs produce any output in cron. User id without the underscore works fine.
For example
as user a_b "date >/dev/null" in (user) cron tab is OK but "date" produces security warnings and the process seems to segfault.
as user a, both of the above commands in cron work fine.
Any ideas
Many thanks
Who is online
Users browsing this forum: No registered users and 2 guests