Log level don't seems to work

Discussion in 'Installation/Configuration' started by riverman, May 17, 2019.

  1. riverman

    riverman New Member

    Hi,
    I have problem with lot of Debug lines in system log even that I have Loglevel set to ERROR
    This is my loglevel: System -> Server Config -> Loglevel: Error
    Every 1 min I get this in System-Log:
    2019-05-17 01:46 web20.abc.com Debug Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock
    /Måns
     
  2. riverman

    riverman New Member

    Sorry, I posted this in worng forum! Should be: ISPConfig 3 -> Installation/Configuration
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Check the settings again to ensure that you set the right option, there are two options regarding log levels. One for log alerts by email and one that defines what get's logged.
     
  4. riverman

    riverman New Member

    I can find two optione:
    Loglevel: Error
    Send email to admin starting with the following level: No Notifications

    Is there another options that I have not found?
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    No, that's the two options. I checked it here and I don't get any debug messages in the current git-stable version of ISPConfig in system log when setting loglevel to error.
     
  6. riverman

    riverman New Member

    ok, but this IS the values in the web GUI. Can I check a config file for log settings?

    I'm running the version 3.1.13 but not the p1 update. Everything updated from web gui.
     
  7. riverman

    riverman New Member

    Its only "Debug Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_cron_lock" that is shown in the system log!

    Looking like this line in /usr/local/ispconfig/server/server.php :
    $app->log('Remove Lock: ' . $conf['temppath'] . $conf['fs_div'] . '.ispconfig_lock', LOGLEVEL_DEBUG);
     
  8. Taleman

    Taleman Well-Known Member HowtoForge Supporter

  9. riverman

    riverman New Member

    Server has been restarted and crontab looks like this:
    * * * * * /usr/local/ispconfig/server/server.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done
    * * * * * /usr/local/ispconfig/server/cron.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Try updating to git-stable with ispconfig_update.sh command. It might be that we fixed something for 3.1.14 that is not in 3.1.13p1.
     
  11. riverman

    riverman New Member

    I have now tried to change log level to DEBUG and I get lot of stuff i system log. If changed back to ERRORS I only get the Remove lock.

    This is a production server is it safe? I have not installed p1 update...
     
    Last edited: May 17, 2019
  12. riverman

    riverman New Member

    I have now update to p1 but not the git-stable, still the same problem.
     
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    This is to be expected as 3.1.13 and 3.1.13p1 differ only in a single patch which is not related to this problem, that's why I said to update to git-stable.
     
  14. riverman

    riverman New Member

    Till, I understand, that's why I asked if its safe because this is a production server. I'm not familiar with the difference between stable and git-stable.
     
  15. till

    till Super Moderator Staff Member ISPConfig Developer

    Stable is the released code. git-stable is the relesed code plus the bufixes of the next release. And yes, it's safe to install fit stable. Just ensure to not install the git master branch.
     

Share This Page