Tickets :: [#10863] [ActiveSync] Sync not working when log file does not exist

6.0.0-beta1

7/4/25

Summary	[ActiveSync] Sync not working when log file does not exist
Queue	Synchronization
Queue Version	Git master
Type	Bug
State	Not A Bug
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	joniw (at) t-online (dot) de
Created	12/14/2011 (4951 days ago)
Due
Updated	12/14/2011 (4951 days ago)
Assigned	12/14/2011 (4951 days ago)
Resolved	12/14/2011 (4951 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/14/2011 11:03:45 PM	Michael Rubinsky	State ⇒ Not A Bug

12/14/2011 09:55:06 PM	joniw (at) t-online (dot) de	Comment #3	Reply to this comment
[Show Quoted Text - 11 lines][Hide Quoted Text] From the config page: "For debugging, it may be useful to send activesync-related log messages to a seperate log. If you want to do this, set this to Custom and enter the path to the log file to use. Horde will attempt to create device specific log files in the SAME DIRECTORY AS THE FILEPATH you provide here If it is unable to do so, all log entries will be sent to the filename you provide." This is necessary because not every ActiveSync message has the device id included in the headers e.g., the early messages in the provisioning process. OK now it is working. Just did not read right here. At first my logfiles were at /var/log and the www-user was not allowed to create a file here. But if the logfile can not be created, the "old" logfile is not used but the sync stops. It would be nice if in the horde_debug.txt is sent a warning if the file can not be created and the "old" logfile is used instead. Then the sync would not stop. Sorry again for not reading carefully the settingspage. with regards Jonathan

12/14/2011 09:08:20 PM	Michael Rubinsky	Comment #2 Assigned to Michael Rubinsky State ⇒ Feedback	Reply to this comment
With the commit fb3eb198ebf2168db801db653d9a7eb597ec0e5a a new logfile is used for every syncing device. Because the log file is not created Log file is created fine here. You'll have to find out why you are unable to create new files in this directory...though if this is the case, it would have failed previously with the single logfile as well. the sync is not working anymore. Also in the settings it is not said that the entry for the logging should be a folder. From the config page: "For debugging, it may be useful to send activesync-related log messages to a seperate log. If you want to do this, set this to Custom and enter the path to the log file to use. Horde will attempt to create device specific log files in the SAME DIRECTORY AS THE FILEPATH you provide here If it is unable to do so, all log entries will be sent to the filename you provide." This is necessary because not every ActiveSync message has the device id included in the headers e.g., the early messages in the provisioning process.

12/14/2011 08:34:26 PM	joniw (at) t-online (dot) de	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ [ActiveSync] Sync not working when log file does not exist Queue ⇒ Synchronization Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
With the commit fb3eb198ebf2168db801db653d9a7eb597ec0e5a a new logfile is used for every syncing device. Because the log file is not created the sync is not working anymore. Also in the settings it is not said that the entry for the logging should be a folder.