View Issue Details

IDProjectCategoryView StatusLast Update
0002196XdebugUncategorizedpublic2023-08-23 16:21
Reporterdeveloper123 Assigned Toderick  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionunable to reproduce 
Summary0002196: DBGp Proxy no output to stdout when started as systemd process
Description

Hey,

we are using the DBGp proxy on our RockyLinux dev server.
This is the output of "ps -ef | grep dbgp"
apache 1619 1 0 Aug02 ? 00:02:47 /usr/local/bin/dbgpProxy -s 127.0.0.1:9074 -i 127.0.0.1:9010 >>/var/log/php/php74-xdebug.log 2>&1
apache 1623 1 0 Aug02 ? 00:02:48 /usr/local/bin/dbgpProxy -s 127.0.0.1:9080 -i 127.0.0.1:9001 >>/var/log/php/php80-xdebug.log 2>&1
apache 2508750 1 0 09:12 ? 00:00:01 /usr/local/bin/dbgpProxy -s 127.0.0.1:9082 -i 127.0.0.1:9182 >>/var/log/php/php82-xdebug.log 2>&1

The problem is that the log file is empty not even the messages on startup get logged. When doing it on console the file is written.

TagsNo tags attached.
Operating System
PHP Version8.2.0-8.2.9

Activities

derick

2023-08-23 11:45

administrator   ~0006640

Last edited: 2023-08-23 11:46

I can not reproduce this, and my log gets the messages:

$ /home/derick/dev/go/src/github.com/derickr/dbgp-tools/dbgpProxy/dbgpProxy >>/tmp/proxy.log 2>&1
^C 
$ 
$ cat /tmp/proxy.log 
Xdebug DBGp proxy (0.4.2-dev)
Copyright 2020 by Derick Rethans
2023-08-23 11:43:07.289 [warn] [SSL] The 'certs/fullchain.pem' file could not be found, not enabling SSL listeners
2023-08-23 11:43:07.289 [info] [dbgpProxy] Proxy started
2023-08-23 11:43:07.289 [info] [server] Started server server on 127.0.0.1:9003
2023-08-23 11:43:07.290 [info] [server] Started client server on 127.0.0.1:9001
2023-08-23 11:44:05.486 [warn] [dbgpProxy] Signal received: interrupt
2023-08-23 11:44:07.317 [info] [server] Shutdown server server
2023-08-23 11:44:07.317 [info] [server] Shutdown client server
2023-08-23 11:44:07.317 [info] [dbgpProxy] Proxy stopped
$ 

Are you sure that the apache user can create new files in /var/log/php and if these files already exist, they also allow writing by the apache user?

The dbgpProxy does not do anything specific here, and just writes to stdout/stderr. If there is anything odd, it's either your shell, or permissions.

developer123

2023-08-23 12:03

reporter   ~0006641

Hi derick,
thanks for the quick answer.

When executing it on the terminal like you did, then it works fine. We checked both the file and directory permission.
Maybe we need to check if there is a problem when executing it as system process.

You can close the ticket, I will reopen in case it is a dbgp problem.

Issue History

Date Modified Username Field Change
2023-08-23 08:22 developer123 New Issue
2023-08-23 11:45 derick Assigned To => derick
2023-08-23 11:45 derick Status new => feedback
2023-08-23 11:45 derick Note Added: 0006640
2023-08-23 11:46 derick Note Edited: 0006640
2023-08-23 12:03 developer123 Note Added: 0006641
2023-08-23 12:03 developer123 Status feedback => assigned
2023-08-23 16:21 derick Status assigned => resolved
2023-08-23 16:21 derick Resolution open => unable to reproduce