Logs Grows

    • OMV 3.x
    • Resolved
    • Hello All,

      This is bit urgent. My logs grows big... My usage of OS drive space (USB flash drive) was 26% on beginning by default. After installing SFTP and restart it started growing. to 47% then to 70% in a few days by itself. I ditched syslog as it was the biggest. but this is not solution.

      ls -lhatrS /var/log shows biggest once like this:

      Source Code

      1. ...
      2. -rw-r----- 1 root adm 477K Nov 3 13:33 messages
      3. -rw-r----- 1 root adm 1.1M Nov 3 13:33 auth.log
      4. -rw-r----- 1 root adm 1.1M Oct 31 08:04 daemon.log.1
      5. -rw-r----- 1 root adm 1.7M Oct 30 01:37 openmediavault-sftp.log
      6. -rw-r----- 1 root adm 13M Aug 20 07:16 mail.info.2.gz
      7. -rw-r----- 1 root adm 13M Aug 20 07:16 mail.log.2.gz
      8. -rw-r----- 1 root adm 131M Nov 3 13:33 daemon.log
      9. -rw-r----- 1 root adm 135M Aug 19 08:06 syslog.1
      10. -rw-r----- 1 root adm 355M Oct 31 08:04 mail.log.1
      11. -rw-r----- 1 root adm 355M Oct 31 08:04 mail.info.1
      12. -rw-r----- 1 root adm 853M Nov 3 13:33 syslog
      13. -rw-r----- 1 root adm 936M Nov 3 13:30 mail.log
      14. -rw-r----- 1 root adm 936M Nov 3 13:30 mail.info
      Display All

      Are these sizes normal? I guess not

      What I should do? What steps should I undergo?

      I cant access logs through OMV web interface... Thinking ditching sys log again and have a look why is growing so big so quick....

      Looking in logs it seems it is Notifications related issue. I wanted to turn Notifications off but I can't cause error message:

      Source Code

      1. Error #0:
      2. exception 'OMV\Exception' with message 'Failed to read file '/tmp/bgstatusX6EB59' (size=0).' in /usr/share/php/openmediavault/json/file.inc:199
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/json/file.inc(214): OMV\Json\File->getContents()
      5. #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(351): OMV\Json\File->read()
      6. #2 /usr/share/openmediavault/engined/rpc/exec.inc(151): OMV\Rpc\ServiceAbstract->getBgProcStatus('/tmp/bgstatusX6...')
      7. #3 [internal function]: OMVRpcServiceExec->isRunning(Array, Array)
      8. #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
      9. #5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('isRunning', Array, Array)
      10. #6 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Exec', 'isRunning', Array, Array, 1)
      11. #7 {main}
      Display All
      Any ideas?

      The post was edited 1 time, last by houndhunger ().

    • No, this is not normal. You need to have a look into it to find out what is spamming your syslog. If you delete the files, please keep in mind to restart the rsyslog service.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • OK, somehow I succeeded to turn Notifications off and syslog calm down watching it with command: tail -f -n 10 /var/log/syslog
      I'll let it for couple days to observe - if logs grows or not, and if not I'll try go through Notifications settings again...

      EDIT & SOLVED:
      So, after calming things down I have realized that Notifications does not have SSL/TLS ticked on, therefore error logs were written on attempting to send Notification messages.
      Recommendation to the others - make double sure that Notifications are set right and working by Sending a test mail and actually receiving it on Recipient side.

      The post was edited 1 time, last by houndhunger ().