At the time of writing, the best course of action in order to stop further service failures for this bug is to disable automatic timezone adjustment on Windows.
For this, you can use the following workaround: 1. Open Control Panel and edit the Date and Time settings 2. Click "Change time zone" 3. Ensure your time zone is set correctly [For example: UTC -08:00 Pacific Time (US & Canada)] 4. Uncheck "Automatically adjust clock for Daylight Saving Time" 5. Confirm this is now set correctly according to MarkLogic - In Query Console run: fn:current-dateTime() => 2015-11-03T14:29:29.371-08:00 - i.e. make sure time zone offset values are correct (for example -08:00 for PST). If the time zone offset values don't match, try restarting MarkLogic.exe and testing again. The only downside of this workaround is that it will think all implicit dateTimes are in standard time, even ones from the summer, but that's better than your cluster being unavailable between 11pm and 12 midnight. Thanks, Rick Pelton Director, Global Support Services MarkLogic Corporation [email protected]<mailto:[email protected]> Phone: +1 650 287-2548 www.marklogic.com<http://www.marklogic.com/> This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communication by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies. Thank you for your cooperation. From: [email protected] [mailto:[email protected]] On Behalf Of John Chertudi Sent: Tuesday, November 03, 2015 10:42 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] MarkLogic 7.0.5.2 crash Thanks for the feedback all! Even a host restart did not seem to allow my Mark Logic servers to come up normally Sunday night. we waited until after midnight, then the service would start normally. After the first failure on November 1 at 11pm Pacific Standard time, they all failed again at 11pm on November 2. Makes sense if this is a problem with log rotation, since all of my logs are zeroed out when this occurs. My work around was to change the server's Time Zone to Arizona (-7:00 GMT), and then start Mark Logic. We'll see if that works tonight when 11pm approaches. John Chertudi From: [email protected] [mailto:[email protected]] On Behalf Of Rick Pelton Sent: Tuesday, November 03, 2015 9:44 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] MarkLogic 7.0.5.2 crash MarkLogic Engineering has reproduced this bug in our labs and are treating this bug with the highest priority. It appears to only affect MarkLogic Server running on Windows and we have reports that it exists on all supported versions of MarkLogic Server (v6, v7 & v8). Rick Pelton Director, Global Support Services MarkLogic Corporation [email protected]<mailto:[email protected]> www.marklogic.com<http://www.marklogic.com/> This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communication by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies. Thank you for your cooperation. From: [email protected] [mailto:[email protected]] On Behalf Of Dunlap, Zachariah Sent: Tuesday, November 03, 2015 7:42 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] MarkLogic 7.0.5.2 crash Thanks for the information Yun. We had the same issue here with our machine last night at 11 p.m. EST and the night before at the same time as well. Look forward to a bug fix for this. Regards, Zach From: [email protected] [mailto:[email protected]] On Behalf Of Yang, Yun Sent: Tuesday, November 03, 2015 10:38 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] MarkLogic 7.0.5.2 crash We had the same issue two days in the roll started 11 PM CST, According to Support, this is a known issue with bug 36052 related with daylight saving time changes. We had to restart the ML services on all hosts to get it back online. I assume this will continue to happen at 11 PM CST at night until there is a patch to address the issue. We are running ML 8.0-3.2 on Windows 2008R2 system. Best, Yun From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chavez, Robert Sent: Tuesday, November 03, 2015 8:34 AM To: [email protected]<mailto:[email protected]> Subject: Re: [MarkLogic Dev General] MarkLogic 7.0.5.2 crash Adding our voice to the thread: We experienced a similar issue last night around the same time as everyone else on the thread — in our case it was a log rotation issue that locked up our cluster (MarkLogic v.8.0-3.2 on Windows 2012 Server). We have to reboot all the Windows servers in the cluster to get back online. We sent a ticket into Support and they are investigating. From our perspective, it seems to be a problem with the Daylight Savings time change not being handled correctly by MarkLogic. Best Wishes, Rob Robert Chavez | Senior Content Solutions Architect | NEJM Group 860 Winter Street, Waltham, MA 02451 | 781-434-7537 | r<mailto:[email protected]>[email protected]<mailto:[email protected]>
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
