Your message dated Wed, 22 Jan 2014 11:08:56 +0100
with message-id <[email protected]>
and subject line fixed
has caused the Debian Bug report #735874,
regarding aborts with exception in log if users.txt refresh fails due to
permissions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
735874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735874
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: resiprocate-turn-server
If the users.txt permissions do not allow reading (which is possible if
the file was originally read before reTurn dropped root permissions or
if it is recreated by mistake), the process completely stops.
INFO | 20140117-195557.026 | reTurnServer | RETURN | 140559005935392 |
ReTurnConfig.cxx:435 | HUP signal received, scheduling a users.txt reload
INFO | 20140117-195558.159 | reTurnServer | RETURN | 140558953101056 |
ReTurnConfig.cxx:412 | change in user database detected, reloading...
DEBUG | 20140117-195558.159 | reTurnServer | RESIP | 140558953101056 |
BaseException.cxx:21 | BaseException at ReTurnConfig.cxx:162 Error
opening/reading user database file!
--- End Message ---
--- Begin Message ---
fixed - 1.9.0~rc1
stop
--- End Message ---
