If the file got deleted, then Linux will let you continue to log to the
FD, tossing the contents to dev null.
Do you have log rotation setup, alternately, you can configure the log
to syslog option.
Basically if you run a production broker with logging on, then you need
to select a log management strategy based on the mechanism used. These
are well documented practices for logs in Linux.
Logging sink options:
--log-to-stderr yes|no (1) Send logging output to stderr
--log-to-stdout yes|no (0) Send logging output to stdout
--log-to-file FILE Send log output to FILE.
--log-to-syslog yes|no (0) Send logging output to syslog;
customize using --syslog-name and
--syslog-facility
--syslog-name NAME (lt-qpidd) Name to use in syslog messages
--syslog-facility LOG_XXX (LOG_DAEMON)
Facility to use in syslog messages
Carl.
On 04/08/2011 10:34 AM, Lahiru Gunathilake wrote:
> Hi Devs,
>
> We have a critical situation with out client deployment since we do not see
> any logging in a production system ?
>
> If someone can provide some input it would be great for us.
>
> Lahiru
>
> On Thu, Apr 7, 2011 at 12:54 PM, Lahiru Gunathilake <[email protected]>wrote:
>
>> Hi all,
>>
>> We have configured Qpid C++ broker to write the logs to a file using qpidd
>> arguments. After running couple of hours it stops logging anything ?
>>
>> What is the default logging level (We have not specified any logging level
>> ) ?
>>
>> Can someone give any clue why this is happening ? Qpid works without any
>> issue but there are not logs available.
>>
>> Lahiru
>>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
