[jira] [Commented] (DAEMON-415) Log is not written to stdout and stderr Logfiles

2020-01-15 Thread Alexander Behrend (Jira) 


[ 
https://issues.apache.org/jira/browse/DAEMON-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015729#comment-17015729
 ] 

Alexander Behrend commented on DAEMON-415:
--

After rewatching other tickets i found out this issue has to do with ticket 
DAEMON-398.

> Log is not written to stdout and stderr Logfiles
> 
>
> Key: DAEMON-415
> URL: https://issues.apache.org/jira/browse/DAEMON-415
> Project: Commons Daemon
>  Issue Type: Bug
>  Components: Procrun
>Affects Versions: 1.2.2
> Environment: Windows Server 2016 Standard
> 64 Bit - OS
> x64 processor
> Intel(R) Xeon(R) CPU E5-2603 v4 @ 1.70 GHz
>  
>Reporter: Alexander Behrend
>Priority: Major
> Fix For: 1.2.3
>
>
> I updated my Procrun Version from 1.0.15 to 1.2.2.
> After Installing and starting the Service, logfiles where created at the 
> desired location but stayed empty during run. Loglevel is set to 'debug' like 
> in the version before. I rechecked the configuration documentation, but did 
> not find any changeable issues.   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (DAEMON-415) Log is not written to stdout and stderr Logfiles

2020-01-13 Thread Alexander Behrend (Jira) 
Alexander Behrend created DAEMON-415:


 Summary: Log is not written to stdout and stderr Logfiles
 Key: DAEMON-415
 URL: https://issues.apache.org/jira/browse/DAEMON-415
 Project: Commons Daemon
  Issue Type: Bug
  Components: Procrun
Affects Versions: 1.2.2
 Environment: Windows Server 2016 Standard

64 Bit - OS

x64 processor

Intel(R) Xeon(R) CPU E5-2603 v4 @ 1.70 GHz

 
Reporter: Alexander Behrend
 Fix For: 1.2.3


I updated my Procrun Version from 1.0.15 to 1.2.2.

After Installing and starting the Service, logfiles where created at the 
desired location but stayed empty during run. Loglevel is set to 'debug' like 
in the version before. I rechecked the configuration documentation, but did not 
find any changeable issues.   



--
This message was sent by Atlassian Jira
(v8.3.4#803005)