[solved] Issues with chrooted pipedLogger

[chipus]

Hi,
I have pipedLogger configured for remote logging (config as in ).
The server is running in a chroot environment.
Version: LiteSpeed Web Server Enterprise 5.2.6

In chroot does not started the logger. In stderr.log there are many lines:
2018-04-16 11:20:29.559 [STDERR] lscgid: chdir():: No such file or directory
.......


I did some research and found that:
without chroot, logger started as:

7383  setgroups(1, [99])                = 0
7383  setuid(99)                        = 0
7383  chdir("/usr/bin/")                = 0
7383  getpid()                          = 7383
7383  write(1, "\327\34\0\0", 4)        = 4
7374  <... read resumed> "\327\34\0\0", 4) = 4
7383  execve("/usr/bin/logger", ["/usr/bin/logger", "-t", "lsws", "-i", "-p", "local6.notice", "-T", "-P", "514", "-n", "X.X.X.X"], [/* 1 var */] <unfinished ...>
7374  close(53)                         = 0
7374  close(52)                         = 0

with chroot, logger started as

7855  setgroups(1, [2])                 = 0
7855  setuid(2)                         = 0
7855  chdir("")                         = -1 ENOENT (No such file or directory)
7855  write(2, "lscgid: chdir():: No such file o"..., 44) = 44
7830  <... poll resumed> )              = 1 ([{fd=10, revents=POLLIN}])
7855  write(1, "l\376\377\377", 4 <unfinished ...>
7830  read(10,  <unfinished ...>
7855  <... write resumed> )             = 4
7837  <... read resumed> "l\376\377\377", 4) = 4
7855  exit_group(123)                   = ?
7830  <... read resumed> "lscgid: chdir():: No such file o"..., 4063) = 44
7837  close(63)                         = 0
7830  write(6, "2018-04-16 11:23:13.991 [STDERR]"..., 77 <unfinished ...>
7837  close(62)                         = 0

For an unknown reason, the path to the executable file ( 7855 chdir("") ) is lost.


Best regards.

 

[chipus]

I found a solution to my problem. The logger should be placed inside $SERVER_ROOT. In this scenario, the binary file starts normally.