<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Cant open Event Processing Policy in 2.2.15 via web ui or full client]]></title><description><![CDATA[<p dir="auto">I have a new install of 2.2.15 on Centos 7.5 running in a docker container. Same architecture I use everywhere aside from the netxms version. It ran fine at first while we imported our standard templates, events, epp, traps, etc etc. About 12 hours later I went to edit one of the epp rules and got a 'Cannot open event processing policy: Request timed out' error when trying to open the window in both the web ui and in the full client. I have 4 other 2.2.15 instances where this does not happen. There are some differences in the templates and epp rules but the other systems have more than this one. it only has a subset of the rules.</p>
<p dir="auto">I unmanaged everything in infrastructure (it only had the netxms server itself) and set debug to 9 but couldnt find anything in the logs at all that I was able to distinguish from the normal log noise.</p>
<p dir="auto">Any ideas how to proceed? further debug options? or a way to purge the rules without having access to the config options? I was able to export/import the rules still without issue and the file structure looks correctly formed.</p>
<p dir="auto">Thanks,</p>
<p dir="auto">Steve</p>
]]></description><link>https://forum.netxms.org/topic/6072/cant-open-event-processing-policy-in-2.2.15-via-web-ui-or-full-client</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 14:00:27 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6072.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 31 Jul 2019 22:33:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Cant open Event Processing Policy in 2.2.15 via web ui or full client on Sun, 11 Aug 2019 08:23:49 GMT]]></title><description><![CDATA[<p dir="auto">Depending on how you are using server it could be commit 3ab06f4e1c ("fixed server deadlock after action configuration import", 2019-06-19).</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/26267</link><guid isPermaLink="true">https://forum.netxms.org/post/26267</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Sun, 11 Aug 2019 08:23:49 GMT</pubDate></item><item><title><![CDATA[Reply to Cant open Event Processing Policy in 2.2.15 via web ui or full client on Fri, 09 Aug 2019 14:00:30 GMT]]></title><description><![CDATA[<p dir="auto">2.2.16 did correct the problem. Still not sure what triggered it however. I see no commits (based on the desc) in 2.2.16 that would explain how it fixed the issue.</p>
]]></description><link>https://forum.netxms.org/post/26254</link><guid isPermaLink="true">https://forum.netxms.org/post/26254</guid><dc:creator><![CDATA[scomoletti]]></dc:creator><pubDate>Fri, 09 Aug 2019 14:00:30 GMT</pubDate></item><item><title><![CDATA[Reply to Cant open Event Processing Policy in 2.2.15 via web ui or full client on Fri, 02 Aug 2019 08:08:39 GMT]]></title><description><![CDATA[<p dir="auto">Looks like internal lock. I recommend you to upgrade to 2.2.16. If issue remain, please take snapshot of the process threads (we bundle script capture_netxmsd_threads.sh for that).</p>
]]></description><link>https://forum.netxms.org/post/26212</link><guid isPermaLink="true">https://forum.netxms.org/post/26212</guid><dc:creator><![CDATA[alk]]></dc:creator><pubDate>Fri, 02 Aug 2019 08:08:39 GMT</pubDate></item></channel></rss>