<?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 cimserver and ssh root login in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112859#M313588</link>
    <description>&lt;!--!*#--&gt;We have a 4 node Service Guard cluster on HP-UX 11.23. No issues with the cluster but on one node&lt;BR /&gt;ps -aef | grep cim&lt;BR /&gt;    root 21350     1  0  Jun 21  ?         0:24 /opt/wbem/sbin/cimserverd&lt;BR /&gt;&lt;BR /&gt;On this node ssh login root works every time. On the remaining nodes&lt;BR /&gt;    root 27350     1  0  Nov 28  ?         0:03 /opt/wbem/sbin/cimserverd&lt;BR /&gt;    root 20970     1  0  Nov 29  ?         4:01 /opt/wbem/sbin/cimserver&lt;BR /&gt;    root  6299  6302  1 14:40:59 pts/3     0:00 grep cim&lt;BR /&gt;    root 20971 20970  0  Nov 29  ?         0:01 /opt/wbem/sbin/cimservera&lt;BR /&gt;&lt;BR /&gt;Remote ssh login for root always produces access denied, until reset at system console. My predecessor says it is an issue with cimserver. Can anyone shed light on this please&lt;BR /&gt;</description>
    <pubDate>Thu, 06 Dec 2007 14:43:04 GMT</pubDate>
    <dc:creator>Andrew Senior</dc:creator>
    <dc:date>2007-12-06T14:43:04Z</dc:date>
    <item>
      <title>cimserver and ssh root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112859#M313588</link>
      <description>&lt;!--!*#--&gt;We have a 4 node Service Guard cluster on HP-UX 11.23. No issues with the cluster but on one node&lt;BR /&gt;ps -aef | grep cim&lt;BR /&gt;    root 21350     1  0  Jun 21  ?         0:24 /opt/wbem/sbin/cimserverd&lt;BR /&gt;&lt;BR /&gt;On this node ssh login root works every time. On the remaining nodes&lt;BR /&gt;    root 27350     1  0  Nov 28  ?         0:03 /opt/wbem/sbin/cimserverd&lt;BR /&gt;    root 20970     1  0  Nov 29  ?         4:01 /opt/wbem/sbin/cimserver&lt;BR /&gt;    root  6299  6302  1 14:40:59 pts/3     0:00 grep cim&lt;BR /&gt;    root 20971 20970  0  Nov 29  ?         0:01 /opt/wbem/sbin/cimservera&lt;BR /&gt;&lt;BR /&gt;Remote ssh login for root always produces access denied, until reset at system console. My predecessor says it is an issue with cimserver. Can anyone shed light on this please&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Dec 2007 14:43:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112859#M313588</guid>
      <dc:creator>Andrew Senior</dc:creator>
      <dc:date>2007-12-06T14:43:04Z</dc:date>
    </item>
    <item>
      <title>Re: cimserver and ssh root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112860#M313589</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Probably the systems denying romote ssh login are configured that way.&lt;BR /&gt;&lt;BR /&gt;To prevent remote access to root and system hacks some people configure their systems to only permit console login, which normally requires access to a secure computer room.&lt;BR /&gt;&lt;BR /&gt;IT is also possible to block root login in /etc/opt/ssh/sshd_config of secure shell(ssh).&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 06 Dec 2007 15:30:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112860#M313589</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-12-06T15:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: cimserver and ssh root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112861#M313590</link>
      <description>Steven&lt;BR /&gt;&lt;BR /&gt;Once root is reset at the console this problem goes away for a period. Perhaps I ought to have added killing cimserver and cimservera (whatever that is) clears the problem. They are respawned by inittab but I don't want to tackle that till I understand the problem properly. How my ex-colleague stopped these processes respawning on the one node where they don't appear I don't know either since the cim1 entry is identical for both inittab nodes.&lt;BR /&gt;&lt;BR /&gt;It is not ssh configs that are denying access.</description>
      <pubDate>Thu, 06 Dec 2007 15:41:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112861#M313590</guid>
      <dc:creator>Andrew Senior</dc:creator>
      <dc:date>2007-12-06T15:41:29Z</dc:date>
    </item>
    <item>
      <title>Re: cimserver and ssh root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112862#M313591</link>
      <description>&amp;gt;I ought to have added killing cimserver  clears the problem. ... How my ex-colleague stopped these processes respawning on the one node&lt;BR /&gt;&lt;BR /&gt;I just did this recently.  See cimserver(1M):&lt;BR /&gt;# cimserver -s&lt;BR /&gt;&lt;BR /&gt;cimserver(1M) also says that there are belts and suspenders and backup suspenders to keep simserver going.  :-)&lt;BR /&gt;cimserver and cimserverd and inittab.</description>
      <pubDate>Fri, 07 Dec 2007 07:50:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cimserver-and-ssh-root-login/m-p/4112862#M313591</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2007-12-07T07:50:53Z</dc:date>
    </item>
  </channel>
</rss>

