*What steps will reproduce the problem?*
1. set the following log configuration:
log = {
{ levels = { min = "debug" }, to = "file", filename = "/var/log/prosody/prosody.log" };
{ levels = { min = "warn" }, to = "syslog" };
}
2. start prosody
3. change the log configuration to:
log = {
{ levels = { min = "warn" }, to = "syslog" };
}
4. killall -HUP prosody
*What is the expected output? What do you see instead?*
In the debug file /var/log/prosody/prosody.log, I see this:
Apr 13 11:47:22 mod_posix info Received SIGHUP
Apr 13 11:47:22 general info Reloading configuration file
Apr 13 11:47:22 general info Re-opening log files
Apr 13 11:47:25 s2sinc2c3c0 debug Received[s2sin]: <message id='130' type='groupchat' to='anarcat@koumbit.org/irssi-xmpp' from='prosody@conference.prosody.im/Zash'>
The last line shouldn't be there - I turned off debug logging!
I would like prosody to *really* reopen logfiles when it receives SIGHUP. Right now it says it does, but it doesn't: it doesn't close existing logfiles (as demonstrated above) and doesn't open up new ones (as #232 demonstrated, at least with syslog).
*What version of the product are you using? On what operating system?*
0.7-rc1 on Debian lenny.
*Please provide any additional information below.*
paul.aurich
on
As pointed out in the MUC, this has already been changed in newer versions...
theanarcat
on
Apparently, this works in 0.8, so maybe this bug can be closed, I can't do it myself (!).
MattJ
on
Yes, both logging reloading is implemented and the fix to not closing the old log files is already fixed in 0.8.
*What steps will reproduce the problem?* 1. set the following log configuration: log = { { levels = { min = "debug" }, to = "file", filename = "/var/log/prosody/prosody.log" }; { levels = { min = "warn" }, to = "syslog" }; } 2. start prosody 3. change the log configuration to: log = { { levels = { min = "warn" }, to = "syslog" }; } 4. killall -HUP prosody *What is the expected output? What do you see instead?* In the debug file /var/log/prosody/prosody.log, I see this: Apr 13 11:47:22 mod_posix info Received SIGHUP Apr 13 11:47:22 general info Reloading configuration file Apr 13 11:47:22 general info Re-opening log files Apr 13 11:47:25 s2sinc2c3c0 debug Received[s2sin]: <message id='130' type='groupchat' to='anarcat@koumbit.org/irssi-xmpp' from='prosody@conference.prosody.im/Zash'> The last line shouldn't be there - I turned off debug logging! I would like prosody to *really* reopen logfiles when it receives SIGHUP. Right now it says it does, but it doesn't: it doesn't close existing logfiles (as demonstrated above) and doesn't open up new ones (as #232 demonstrated, at least with syslog). *What version of the product are you using? On what operating system?* 0.7-rc1 on Debian lenny. *Please provide any additional information below.*
As pointed out in the MUC, this has already been changed in newer versions...
Apparently, this works in 0.8, so maybe this bug can be closed, I can't do it myself (!).
Yes, both logging reloading is implemented and the fix to not closing the old log files is already fixed in 0.8.
Changes