<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart. in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68013#M6152</link>
    <description>&lt;P&gt;In my case it’s an AP7522 version 5.8.4.0-03R causing problems.&lt;/P&gt; &lt;P&gt;I contacted GTAC, sent them my log and received this answer:&lt;/P&gt; &lt;P&gt;“&lt;EM&gt;I am contacting you in regards to Extreme support case 01979225. AP7522 in a boot loop. Based on your description of the issue it appears that the issue is hardware related and will need RMA. You can try rebooting the device and see if you can get to a login prompt, if the AP does not boot to a login prompt then it is definitely hardware related.”&lt;/EM&gt;&lt;/P&gt; &lt;P&gt;Well, no login prompt at all in my case, so I guess I will have to send the AP for repair.&lt;/P&gt;</description>
    <pubDate>Mon, 03 Feb 2020 21:26:54 GMT</pubDate>
    <dc:creator>Seban</dc:creator>
    <dc:date>2020-02-03T21:26:54Z</dc:date>
    <item>
      <title>%DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68007#M6146</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;&lt;P&gt;Site running VC with AP7532 5.9.4.1 with repeated messages: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.&lt;/P&gt;&lt;P&gt;There is well known bug in this firmware version?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2019 20:13:21 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68007#M6146</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-11-10T20:13:21Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68008#M6147</link>
      <description>&lt;P&gt;Aviv, looking through the 5.9.4.1 through 5.9.6 release notes, I’m not seeing any bugs that were either marked as ‘fixed’ or as ‘known issues’ - that match this error message.&amp;nbsp; This is likely an unknown issue and should be reported to GTAC.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2019 22:52:56 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68008#M6147</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2019-11-10T22:52:56Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68009#M6148</link>
      <description>&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 10 Nov 2019 23:05:20 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68009#M6148</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-11-10T23:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68010#M6149</link>
      <description>&lt;P&gt;Any progress/ new finding in this case? Presently having the same problem. AP connected via console port. Device is totally unresponsive (restart loop). Any hint how to proceed?&lt;/P&gt; &lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 20:20:39 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68010#M6149</guid>
      <dc:creator>Seban</dc:creator>
      <dc:date>2020-01-30T20:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68011#M6150</link>
      <description>&lt;P&gt;Seban, don’t know if Aviv contacted GTAC or not or got any resolution, but I’ll make the same suggestion for you as well.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 22:29:14 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68011#M6150</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2020-01-30T22:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68012#M6151</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt; &lt;P&gt;Nope.&lt;/P&gt; &lt;P&gt;Seems there is some kind of bug/limitation.&lt;/P&gt; &lt;P&gt;EDIT:&lt;/P&gt; &lt;P&gt;In the site:&lt;/P&gt; &lt;P&gt;AP6562 version 5.9.3.3 - have the&amp;nbsp;issue&lt;/P&gt; &lt;P&gt;AP7532 version 5.9.3.3 - working well&lt;/P&gt; &lt;P&gt;AP7502&amp;nbsp;version 5.9.3.3 - MNG process is freezing sometimes&lt;/P&gt; &lt;P&gt;There is running some AP detection with this routine:&lt;/P&gt; &lt;P&gt;&lt;U&gt;%SYSTEM-3-LOGIN_FAIL: Log-in failed for user 'root' from 'ssh'&lt;/U&gt;&lt;/P&gt; &lt;P&gt;It’s possibly can cause the problem, seems the low memory devices cant open many sessions?&lt;/P&gt; &lt;P&gt;What can you advice to minimize the affect?&amp;nbsp;&lt;/P&gt; &lt;P&gt;Same&amp;nbsp; mng config in all the aps:&lt;/P&gt; &lt;BLOCKQUOTE&gt; &lt;P&gt;show running-config management-policy default&amp;nbsp;&lt;BR /&gt; management-policy default&lt;BR /&gt; &amp;nbsp;telnet&lt;BR /&gt; &amp;nbsp;no http server&lt;BR /&gt; &amp;nbsp;https server&lt;BR /&gt; &amp;nbsp;no rest-server&lt;BR /&gt; &amp;nbsp;ssh&lt;BR /&gt; &amp;nbsp;user fgdsg&amp;nbsp;password 1 a157f5337bdf9689c6ae3123546dacb4dc1b60ed8a4ea1e7cdc302cba7948b3a role superuser access all&lt;BR /&gt; &amp;nbsp;no snmp-server manager v3&lt;BR /&gt; &amp;nbsp;&lt;/P&gt; &lt;/BLOCKQUOTE&gt; &lt;P&gt;Thanks&lt;/P&gt; &lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2020 19:27:34 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68012#M6151</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2020-02-03T19:27:34Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68013#M6152</link>
      <description>&lt;P&gt;In my case it’s an AP7522 version 5.8.4.0-03R causing problems.&lt;/P&gt; &lt;P&gt;I contacted GTAC, sent them my log and received this answer:&lt;/P&gt; &lt;P&gt;“&lt;EM&gt;I am contacting you in regards to Extreme support case 01979225. AP7522 in a boot loop. Based on your description of the issue it appears that the issue is hardware related and will need RMA. You can try rebooting the device and see if you can get to a login prompt, if the AP does not boot to a login prompt then it is definitely hardware related.”&lt;/EM&gt;&lt;/P&gt; &lt;P&gt;Well, no login prompt at all in my case, so I guess I will have to send the AP for repair.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2020 21:26:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68013#M6152</guid>
      <dc:creator>Seban</dc:creator>
      <dc:date>2020-02-03T21:26:54Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68014#M6153</link>
      <description>&lt;P&gt;Hello Chris,&lt;/P&gt; &lt;P&gt;Any suggestions will be appreciated&lt;/P&gt; &lt;P&gt;Thanks&lt;/P&gt; &lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Tue, 04 Feb 2020 15:56:22 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68014#M6153</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2020-02-04T15:56:22Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68015#M6154</link>
      <description>&lt;P&gt;Hello Chris,&lt;/P&gt; &lt;P&gt;Any suggestions will be appreciated&lt;/P&gt; &lt;P&gt;Thanks&lt;/P&gt; &lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2020 15:23:41 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68015#M6154</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2020-02-12T15:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: %DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 502) exited. Scheduling for restart.</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68016#M6155</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt; &lt;P&gt;This topic is not solved.&lt;/P&gt; &lt;P&gt;Please provide some recommendations .&lt;/P&gt; &lt;P&gt;Thanks&lt;/P&gt; &lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Tue, 18 Feb 2020 15:29:26 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/daemon-1-alert-init-process-usr-sbin-rim-d-pid-502-exited/m-p/68016#M6155</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2020-02-18T15:29:26Z</dc:date>
    </item>
  </channel>
</rss>

