<?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[Failed to enable unit: Refusing to operate on alias name or linked unit.]]></title><description><![CDATA[<p dir="auto">New install on Debian Bookworm LXC on Proxmox-VE. Everything worked fine until I ran systemctl enable --now netxmsd.service. Returned: Failed to enable unit: Refusing to operate on alias name or linked unit file: netxmsd.service</p>
]]></description><link>https://forum.netxms.org/topic/7739/failed-to-enable-unit-refusing-to-operate-on-alias-name-or-linked-unit.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 11:37:38 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7739.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 27 Aug 2023 17:30:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Failed to enable unit: Refusing to operate on alias name or linked unit. on Thu, 31 Aug 2023 10:36:42 GMT]]></title><description><![CDATA[<p dir="auto">Try using<br />
systemctl enable --now netxms-server.service</p>
<p dir="auto">You can see unit names by issuing<br />
systemctl | grep netxms</p>
]]></description><link>https://forum.netxms.org/post/32706</link><guid isPermaLink="true">https://forum.netxms.org/post/32706</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Thu, 31 Aug 2023 10:36:42 GMT</pubDate></item></channel></rss>