PHP Warning: Illegal string offset 'section_id' in /home/xxxx/public_html/vx/wp-content/themes/wp_olympic5-v1.0.1/functions.php on line 310 PHP Warning: Illegal string offset 'placeholder' in /home/xxxx/public_html/vx/wp-content/themes/wp_olympic5-v1.0.1/functions.php on line 309 PHP Warning: Illegal string offset 'choice_new' in /home/xxxx/public_html/vx/wp-content/themes/wp_olympic5-v1.0.1/functions.php on line 308 Those lines are pasted below but I don't think they are applicable to this. The last lines in the file are from a year ago (yes this site does not get new content very often).
Linux permissions reset install#
If I force an error by trying to install a new plugin it does not append anything to the error file. My guess is that the error_log for that folder cannot be written to even though it is set to 0644 and username:username rw-r-r- 1 root adm 113261 Jun 27 10:55 /var/log/mail.Click to expand.The error_log file is there but it hasn't been updated since around the time this problem started happening. maybe syslog-ng needs to actually receive something from the mail log facility in order to reset the permissions? Let's try that:
the permissions are still the same?! Oh, wait. Starting system logging: syslog-ng.Ĭhecking the log's file permissions again: # grep "mail.log" /etc/syslog-ng/nfĭestination d_mail
For /var/log/mail.log this is the default setting: Instead the permissions can also be set in syslog-ng's "destination" option. Some logs contain sensitive information so I wouldn't like to just grant read access to everyone. But his means that all log files would be readable by all the users on this application server. Of course I could just set the permissions to 0644 here. This ownership and permission setting is part of syslog-ng's global configuration. By default (here on a Debian Wheezy installation) this means: It turns out that syslog-ng (which runs on this application server) resets the permissions automatically to the ones defined in the syslog-ng config. I verified and indeed, the permissions of /var/log/mail.log were reset: But just a couple of minutes later the check returned critical because the nagios user wasn't able to read the log file anymore. I enabled the monitoring check and it worked. I even adapted the logrotate config file to ensure the rotated log file is also readable after a log rotation (using the "create" option): Therefore the nagios user needs to be able to read /var/log/mail.log. The check itself is executed through NRPE which runs as "nagios" user. Published on June 27th 2017 - Listed in Linux Mailįor a special application I built a simple monitoring check which reads /var/log/mail.log (and the rotated /var/log/mail.log.1) and counts the number of e-mails sent by that application. Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells With over 10 pre-installed distros to choose from, the worry-free installation life is here Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use. Permissions of log files automatically being reset by syslog
0 kommentar(er)
