vicidial.org

Support,
Jan 16 03:02:01 jsh postfix/postdrop[2498]: warning: unable to look up public/pickup: No such file or directory
Jan 16 03:02:01 jsh postfix/postdrop[2496]: warning: unable to look up public/pickup: No such file or directory
Jan 16 07:01:02 jsh postfix/postdrop[10637]: warning: unable to look up public/pickup: No such file or directory
Jan 16 20:00:09 jsh logrotate: ALERT exited abnormally with [1]
Jan 16 20:00:09 jsh logrotate: error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix $
Jan 16 20:00:09 jsh logrotate: last message repeated 4 times
Jan 16 20:00:09 jsh logrotate: error: "/var/log/atftpd" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix th$
Jan 16 20:00:09 jsh logrotate: #007/usr/bin/mysqladmin: refresh failed; error: 'Unknown error'
Jan 16 20:00:09 jsh logrotate: /logrotate.d/mysql failed, probably because
Jan 16 20:00:09 jsh logrotate: the root acount is protected by password.
Jan 16 20:00:09 jsh logrotate: See comments in /logrotate.d/mysql on how to fix this
Jan 16 20:00:09 jsh logrotate: error: error running non-shared postrotate script for /var/log/mysql/mysqld.log of '/var/log/mysql/mysqld.log '
Jan 16 20:00:09 jsh logrotate: redirecting to systemctl

Can someone help me? Is this bad? How can I correct this?
Thank you.

Post your logrotate configurations content from /etc/logrotate.d/

check the permissions:
ls -l /var/log/
ls -l /var/log/asterisk
as the log say "It must be owned and be writable by root only to avoid security issues"
use chown and chmod to correct the issues

you could also tell us what you have done
because this looks like problems that would appear if someone changes stuff
and they don't really know what they are doing

Or worse yet, they DO know what they are doing ... just not with OpenSuSE or Vicidial or something else which does not work the way they think it does.

Thank you Williamconley.
/etc/logrotate.d/
apache2 asterisk atftp mcelog mysql net-snmp ntp rsync snapper syslog vsftpd wtmp xinetd zypp-history.lr zypp-refresh.lr zypper.lr

Did not touch anything. Fresh install of Vicibox 4.0.1


Looked at ls -l but don't know what to look for or which one i'm going to change the permission...Sorry...

I used winscp looked in /var/log
I noticed that folder asterisk owner is asterisk and folder atftpd owner is tftp.
Is this what causing the error?
Should I change the owner to root? or Just change the permissions?

richardroi wrote:Did not touch anything. Fresh install of Vicibox 4.0.1

are you really sure about that?
then do a complete reinstall and tell me if you still got problems with logrotate.

btw, is there really any problems? doesn't logrotate do its job?

Everything seems ok. How can i check if logrotate is doing its job? We will be using this box next week, just want it to be stable.

Code: Select all

/etc/logrotate.d # ll
total 64
-rw-r--r-- 1 root root 1427 Feb 16  2012 apache2
-rw-r--r-- 1 root root 1187 Dec 18 08:07 asterisk
-rw-r--r-- 1 root root  215 Jun  9  2012 atftp
-rw-r--r-- 1 root root  267 Oct 30  2011 mcelog
-rw-r--r-- 1 root root 1044 Dec 24 05:26 mysql
-rw-r--r-- 1 root root  329 May 15  2012 net-snmp
-rw-r--r-- 1 root root  187 Oct 30  2011 ntp
-rw-r--r-- 1 root root  141 Oct 30  2011 rsync
-rw-r--r-- 1 root root  134 Nov 21  2011 snapper
-rw-r--r-- 1 root root 1390 Mar 20  2012 syslog
-rw-r--r-- 1 root root  201 Oct 30  2011 vsftpd
-rw-r--r-- 1 root root  148 Feb  8  2012 wtmp
-rw-r--r-- 1 root root  200 Oct 29  2011 xinetd
-rw-r--r-- 1 root root  137 Jun  8  2012 zypp-history.lr
-rw-r--r-- 1 root root  139 Apr 30  2012 zypp-refresh.lr
-rw-r--r-- 1 root root  134 Apr 30  2012 zypper.lr


[reformatted a bit by williamconley]

Will this help?
Someone?

are the logs being rotated? LOL

as in: log files get moved to dated files, then to .gz dated files after a few days.

you should try "man logrotate" or just google it to see how it works. it IS a very useful tool

showing a list of the items in the logrotate folder is not actually helpful.

man logrotate

learn how to use it

to see if logs are rotating:

ls -l /var/log

I ran /usr/sbin/logrotate -dv /etc/logrotate.conf and got this;
rotating pattern: /var/log/asterisk/full after 1 days (5 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/asterisk/full
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
log /var/log/asterisk/full does not exist -- skipping
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/asterisk/queue_log after 1 days (5 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/asterisk/queue_log
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
log does not need rotating
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/asterisk/event_log after 1 days (5 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/asterisk/event_log
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
log does not need rotating
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/asterisk/messages after 1 days (5 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/asterisk/messages
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
log does not need rotating
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/asterisk/h323_log after 1 days (5 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/asterisk/h323_log
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
log /var/log/asterisk/h323_log does not exist -- skipping
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/asterisk/cdr-csv/Master.csv after 1 days (5 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/asterisk/cdr-csv/Master.csv
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/atftpd/atftp.log 4194304 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/atftpd/atftp.log
error: "/var/log/atftpd" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
log /var/log/atftpd/atftp.log does not exist -- skipping
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/mcelog 2097152 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/mcelog
log does not need rotating
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/mysql/mysqld.log after 1 days (3 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/mysql/mysqld.log
log does not need rotating
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/net-snmpd.log 1048576 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/net-snmpd.log
log /var/log/net-snmpd.log does not exist -- skipping
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/ntp 2097152 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/ntp
log does not need rotating
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/rsyncd.log 1048576 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/rsyncd.log
log /var/log/rsyncd.log does not exist -- skipping

rotating pattern: /var/log/snapper.log 10485760 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/snapper.log
log /var/log/snapper.log does not exist -- skipping

rotating pattern: /var/log/warn /var/log/messages /var/log/allmessages /var/log/localmessages /var/log/firewall /var/log/acpid /var/log/NetworkManager 4194304 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/warn
log does not need rotating
considering log /var/log/messages
log does not need rotating
considering log /var/log/allmessages
log /var/log/allmessages does not exist -- skipping
considering log /var/log/localmessages
log does not need rotating
considering log /var/log/firewall
log does not need rotating
considering log /var/log/acpid
log does not need rotating
considering log /var/log/NetworkManager
log does not need rotating
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/mail /var/log/mail.info /var/log/mail.warn /var/log/mail.err 4194304 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/mail
log does not need rotating
considering log /var/log/mail.info
log does not need rotating
considering log /var/log/mail.warn
log does not need rotating
considering log /var/log/mail.err
log does not need rotating
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/news/news.crit /var/log/news/news.err /var/log/news/news.notice 4194304 bytes (99 rotations)
empty log files are not rotated, old logs are removed
switching euid to 9 and egid to 13
considering log /var/log/news/news.crit
log does not need rotating
considering log /var/log/news/news.err
log does not need rotating
considering log /var/log/news/news.notice
log does not need rotating
not running postrotate script, since no logs were rotated
switching euid to 0 and egid to 0

rotating pattern: /var/log/vsftpd.log 1048576 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/vsftpd.log
log /var/log/vsftpd.log does not exist -- skipping
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/wtmp /var/log/btmp 409600 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/wtmp
log does not need rotating
considering log /var/log/btmp
log does not need rotating

rotating pattern: /var/log/xinetd.log 2097152 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/xinetd.log
log /var/log/xinetd.log does not exist -- skipping
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/zypp/history 10485760 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/zypp/history
log /var/log/zypp/history does not exist -- skipping

rotating pattern: /var/log/zypp-refresh.log 10485760 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/zypp-refresh.log
log /var/log/zypp-refresh.log does not exist -- skipping

rotating pattern: /var/log/zypper.log 10485760 bytes (99 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/zypper.log
log /var/log/zypper.log does not exist -- skipping


I ran /usr/sbin/logrotate -f /etc/logrotate.conf and got this error;
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: destination /var/log/asterisk/queue_log-20130117 already exists, skipping rotation
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: destination /var/log/asterisk/event_log-20130117 already exists, skipping rotation
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: destination /var/log/asterisk/messages-20130117 already exists, skipping rotation
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/atftpd" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.

Any advice?

/usr/sbin/logrotate /etc/logrotate.conf test this also same error;
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/atftpd" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
how to correct this?

ok changed permissions;

chown root:root /var/log/asterisk

chown root:root /var/log/atftpd

then execute
/usr/sbin/logrotate /etc/logrotate.conf

NO MORE ERRORS.

Hope everything is ok now.

Restart asterisk and make sure it writes logs at it should, if its not then you should do this method:
"Please fix the directory permissions or set the "su" directive in the config file."

I told you to use chown because I though you had messes up the permissions, but then you said its a fresh install.

to use the other method then you need to back the permissions on /var/log/asterisk
and add:
su asterisk asterisk
to /etc/logrotate.d/asterisk instead
http://www.novell.com/support/kb/doc.php?id=7005219

I'm gonna check out if this is something they missed when creating the iso

DomeDan,

I did try reinstall using another hard drive because like I told you, it is fresh install and I did not touch anything.
When I checked logrotate it gave me same error.

jsh:/var/log # /usr/sbin/logrotate /etc/logrotate.conf
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/asterisk" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
error: "/var/log/atftpd" has insecure permissions. It must be owned and be writable by root only to avoid security issues. Please fix the directory permissions or set the "su" directive in the config file.
Just to update you.
Thank you for your help.

How can i back the permissions, coz i already ran chown again? and how can i check if it writes logs at it should. when I check var /log/messgaes this is what i have;
Jan 17 08:12:53 jsh vicidial[2393]: Started Vicidial
Jan 17 08:12:53 jsh vicidial[2393]: ..done
Jan 17 08:12:53 jsh systemd[1]: Startup finished in 4s 660ms 614us (kernel) + 37s 755ms 424us (userspace) = 42s 416ms 38us.
Jan 17 08:13:01 jsh /USR/SBIN/CRON[2661]: (root) CMD (/usr/share/astguiclient/ADMIN_keepalive_ALL.pl)
Jan 17 08:13:01 jsh /USR/SBIN/CRON[2662]: (root) CMD (/usr/share/astguiclient/AST_CRON_audio_2_compress.pl --MP3)
Jan 17 08:13:01 jsh /USR/SBIN/CRON[2663]: (root) CMD (/usr/share/astguiclient/AST_conf_update.pl)
Jan 17 08:13:01 jsh /USR/SBIN/CRON[2665]: (root) CMD (/usr/share/astguiclient/AST_VDhopper.pl -q)
Jan 17 08:13:01 jsh /USR/SBIN/CRON[2666]: (root) CMD (/usr/share/astguiclient/AST_manager_kill_hung_congested.pl)
Jan 17 08:13:01 jsh /USR/SBIN/CRON[2664]: (root) CMD (/usr/share/astguiclient/AST_vm_update.pl)
Jan 17 08:14:01 jsh /USR/SBIN/CRON[2766]: (root) CMD (/usr/share/astguiclient/AST_conf_update.pl)
Jan 17 08:14:01 jsh /USR/SBIN/CRON[2767]: (root) CMD (/usr/share/astguiclient/AST_manager_kill_hung_congested.pl)
Jan 17 08:14:01 jsh /USR/SBIN/CRON[2769]: (root) CMD (/usr/share/astguiclient/ADMIN_keepalive_ALL.pl)
Jan 17 08:14:01 jsh /USR/SBIN/CRON[2770]: (root) CMD (/usr/share/astguiclient/AST_VDhopper.pl -q)
Jan 17 08:14:01 jsh /USR/SBIN/CRON[2768]: (root) CMD (/usr/share/astguiclient/AST_vm_update.pl)
Jan 17 08:15:01 jsh /USR/SBIN/CRON[2873]: (root) CMD (/usr/share/astguiclient/AST_vm_update.pl)
Jan 17 08:15:01 jsh /USR/SBIN/CRON[2874]: (root) CMD (/usr/share/astguiclient/AST_conf_update.pl)
Jan 17 08:15:01 jsh /USR/SBIN/CRON[2878]: (root) CMD (/usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl)
Jan 17 08:15:01 jsh /USR/SBIN/CRON[2877]: (root) CMD (/usr/share/astguiclient/ADMIN_keepalive_ALL.pl)
Jan 17 08:15:01 jsh /USR/SBIN/CRON[2879]: (root) CMD (/usr/share/astguiclient/AST_manager_kill_hung_congested.pl)
Jan 17 08:15:01 jsh /USR/SBIN/CRON[2875]: (root) CMD (/usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX)
Jan 17 08:15:01 jsh /USR/SBIN/CRON[2876]: (root) CMD (/usr/share/astguiclient/AST_VDhopper.pl -q)
Jan 17 08:15:05 jsh su: (to nobody) root on none
Jan 17 08:15:53 jsh su: last message repeated 2 times
Jan 17 08:16:01 jsh /USR/SBIN/CRON[4209]: (root) CMD (/usr/share/astguiclient/ADMIN_keepalive_ALL.pl)
Jan 17 08:16:01 jsh /USR/SBIN/CRON[4211]: (root) CMD (/usr/share/astguiclient/AST_conf_update.pl)
Jan 17 08:16:01 jsh /USR/SBIN/CRON[4212]: (root) CMD (/usr/share/astguiclient/AST_VDhopper.pl -q)
Jan 17 08:16:01 jsh /USR/SBIN/CRON[4214]: (root) CMD (/usr/share/astguiclient/AST_CRON_audio_2_compress.pl --MP3)
Jan 17 08:16:01 jsh /USR/SBIN/CRON[4213]: (root) CMD (/usr/share/astguiclient/AST_manager_kill_hung_congested.pl)
Jan 17 08:16:01 jsh /USR/SBIN/CRON[4210]: (root) CMD (/usr/share/astguiclient/AST_vm_update.pl)
Jan 17 08:17:01 jsh /USR/SBIN/CRON[4315]: (root) CMD (/usr/share/astguiclient/ADMIN_keepalive_ALL.pl)
Jan 17 08:17:01 jsh /USR/SBIN/CRON[4317]: (root) CMD (/usr/share/astguiclient/AST_VDhopper.pl -q)
Jan 17 08:17:01 jsh /USR/SBIN/CRON[4316]: (root) CMD (/usr/share/astguiclient/AST_vm_update.pl)
Jan 17 08:17:01 jsh /USR/SBIN/CRON[4318]: (root) CMD (/usr/share/astguiclient/AST_manager_kill_hung_congested.pl)
Jan 17 08:17:01 jsh /USR/SBIN/CRON[4319]: (root) CMD (/usr/share/astguiclient/AST_conf_update.pl)
Jan 17 08:18:01 jsh /USR/SBIN/CRON[4420]: (root) CMD (/usr/share/astguiclient/AST_vm_update.pl)

Does this mean it is writing its log?

set the owner to the default the same way as you set it to root, I told you to run "ls -l /var/log" so you should know what the default was if you saved the output from ls somewhere
or just check in the new install you said you've been doing.

to check if asterisk can write log I would suggest doing a restart of the system
and then reattach asterisk and check if theres any errors about the log in the CLI
then check /var/log/messages if theres any complains there etc
use asterisk as long as its needed to make a big log-file that requires that logrotate will rotate the log and check if theres any complains after that is done.

haven't been able to test 4.0.1 out that much, it wont runt that good in virtualbox

"set the owner to the default the same way as you set it to root" sorry but i am lost here.
This is the original in ls drwxr-x--- 2 asterisk asterisk 4096 Jan 18 00:29 asterisk
after chown root
drwxr-xr-x 2 root root 4096 Jan 18 02:25 asterisk, now how do i revert it back?

I did restart the newly installed.
No errors or complains so far.
Thank you.

then just "chown asterisk asterisk /var/log/asterisk"

the user asterisk is proabably running asterisk and then you should use use "su asterisk asterisk" in the logrotate config

DomeDan,
chown asterisk:asterisk /var/log/asterisk
then edit logrotate.d configfile (thank you for the link example)
Everything's ok now!!!

Forever thankful!

Asterisk doesn't run as user or group asterisk because of the perl script that write out the autoconfiguration files in /etc/asterisk, namely sip-vicidial.com, extensions-vicidial.conf, iax-vicidial.conf, and a few others. These perl scripts are ran from the root cron in order to be consistent with the ViciDial legacy documentation and install base. There are also some permission issues when it comes to moving and managing the recordings. Unfortunately the path of least resistance was to continue running asterisk as the 'root' user.

I've modified the asterisk build package to reflect the changes needed for logrotate.d configuration as well as the /var/log/asterisk directory. I believe any updates on v.4.0+ will pull in these changes and take care of the issue.

Sir Kumba,
Do I still need to update? Or what I did was wrong, editing.etc.? But the box seems to be ok.
Please advice.
This is my second box on production, but i still need some reading & learning ...

Thank you.

If it's working as a dialer ... no need to change anything. But if you have the urge to rebuild, use the 4.0.X (presently 4.0.2) version for your install. We've had great experience with the latest versions of the installer. No problems at all.