some errors from stderr.log FreeBSD x64 8.x

Discussion in 'Bug Reports' started by julian, Apr 25, 2014.

  1. julian

    julian New Member

    system is FreeBSD x64 8.x server running on 'chroot environment'
    I want to draw your attention to some errors of stderr.log. Full log https://gist.github.com/anonymous/7ab92bfd69a2270837f7
    Code:
    2014-04-13 13:31:03.702 [STDERR] Error Traversing Database for ipnum = 1211098133 - Perhaps database is corrupt?
    ....
    2014-04-14 07:17:01.001 [STDERR] Child process with pid: 34322 was killed by signal: 15, core dump: 0
    2014-04-18 11:14:33.317 [STDERR] Child process with pid: 2760 was killed by signal: 11, core dump: 128
    .....
    2014-04-18 19:12:14.004 [STDERR] sysctl: Failed to set 'kern.sugid_coredump', core dump may not be available!: Operation not permitted
    ....
    
    one more thing, about the log rotation. Server some reason ignores my settings, rotating logs every day, and not in size designation in the settings

    Code:
    Log Control  =>  Own Log File
    File Name  =>  $SERVER_ROOT/logs/$VH_NAME/access.log
    Piped Logger  =>  Not Set
    Log Format  =>  Not Set
    Log Headers  =>  Referrer  UserAgent  Host  None
    Rolling Size (bytes)  =>  1G
    Keep Days  =>  60
    Bytes log  =>  Not Set
    Compress Archive  =>  Yes
    
  2. mistwang

    mistwang LiteSpeed Staff

  3. julian

    julian New Member

    log is unreadable lines shifted, how can I trace what is this tool "sh: 1: lang: not found"
    at this time the system "debian 7.x and lsws 4.2.12"
    strerr.log AS IS
    Code:
    root at debian in Jail /lsws/logs on master*
    $ tail -n 20 stderr.log
    2014-08-03 01:46:23.144 [STDERR] sh: 1: lang: not found2014-08-03 01:46:23.144 [STDERR]
    sh: 1: 2014-08-03 01:51:57.932 [STDERR] lang: not found2014-08-03 01:51:57.932 [STDERR]
    sh: 1: lang: not found
    2014-08-03 02:16:32.337 [STDERR] sh: 1:
    2014-08-03 02:16:32.337 [STDERR] lang: not foundsh: 1: lang: not found
    sh: 1: lang: not found
    sh: 1: lang: not found
    2014-08-04 01:22:48.607 [STDERR] sh: 1: lang: not found
    2014-08-04 01:24:08.974 [STDERR] sh: 1: lang: not found
    2014-08-04 01:26:40.469 [STDERR] sh: 1: lang: not found
    sh: 1: lang: not found
    2014-08-04 01:30:26.282 [STDERR] sh: 1: 2014-08-04 01:30:26.282 [STDERR] lang: not found2014-08-04 01:30:26.282 [STDERR]
    
    sh: 1: lang: not found2014-08-04 01:44:41.679 [STDERR] sh: 1:
    2014-08-04 01:44:41.679 [STDERR] lang: not found2014-08-04 01:57:35.943 [STDERR] sh: 1: lang: not found2014-08-04 01:57:35.943 [STDERR]
    2014-08-04 02:12:08.847 [STDERR] sh: 1: lang: not found
    2014-08-04 02:13:14.114 [STDERR] sh: 1: lang: not found
    sh: 1: lang: not found
    Child process with pid: 31649 was killed by signal: 15, core dump: 0
    2014-08-04 03:45:25.000 [STDERR] Child process with pid: 32264 was killed by signal: 15, core dump: 0
    
  4. mistwang

    mistwang LiteSpeed Staff

    that's mean one CGI or php script try to execute a shell script trying to run command "lang", which is not available.
    You need to find the script doing that.

Share This Page