You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Syafiq Rokman <ms...@gmail.com> on 2016/02/01 02:41:18 UTC
Re: Authentication Error When Adding Host
Hi,
Yes.
$ nmap -p 8250 172.16.134.175
Starting Nmap 6.40 ( http://nmap.org ) at 2016-02-01 09:31 MYT
Nmap scan report for 172.16.134.175
Host is up (0.00029s latency).
PORT STATE SERVICE
8250/tcp open unknown
$ telnet 172.16.134.175 8250
Trying 172.16.134.175...
Connected to 172.16.134.175.
But when I try on the agent machine itself :
$ nmap -p 8250 172.16.134.246
Starting Nmap 6.40 ( http://nmap.org ) at 2016-02-01 09:34 MYT
Nmap scan report for syafiqrokman-HPCC.cloudstack (172.16.134.246)
Host is up (0.000017s latency).
PORT STATE SERVICE
8250/tcp closed unknown
$ telnet 172.16.134.246 8250
Trying 172.16.134.246...
telnet: Unable to connect to remote host: Connection refused.
I tried updating iptables and ufw to allow tcp through 8250. Still, no
luck.
On an off note, why is it trying to connect through this port? It wasn't
listed on the ports to be opened in the documentation.
On Fri, Jan 29, 2016 at 5:43 PM Nux! <nu...@li.nux.ro> wrote:
> Hello,
>
> Can you test manually if that agent machine can access the management one
> on that port?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Syafiq Rokman <ms...@gmail.com> wrote:
> > Hi, I'm new to Linux and CloudStack and would appreciate any support here
> >
> > CS 4.7 Ubuntu 14.04
> >
> > PC A - management server
> > PC B - host
> > PC C - host
> >
> > The management server managed to connect to PC B, making it a host.
> > But I'm getting an 'Authentication Error' when adding PC C. The
> > username/passwd should be correct already. (root , root passwd)
> >
> > ==== PC C agent.log ====
> > WARN [utils.nio.NioConnection] (main:null) (logid:) Unable to connect
> to
> > remote: is there a server running on port 8250
>
>
Re: Authentication Error When Adding Host
Posted by Syafiq Rokman <ms...@gmail.com>.
Hi,
Managed to get it working. The problem was in /etc/ssh/sshd_config :
Commented out : PermitRootLogin without-password and StrictModes yes
On Mon, Feb 1, 2016 at 9:41 AM Syafiq Rokman <ms...@gmail.com>
wrote:
> Hi,
>
> Yes.
>
> $ nmap -p 8250 172.16.134.175
>
> Starting Nmap 6.40 ( http://nmap.org ) at 2016-02-01 09:31 MYT
> Nmap scan report for 172.16.134.175
> Host is up (0.00029s latency).
> PORT STATE SERVICE
> 8250/tcp open unknown
>
> $ telnet 172.16.134.175 8250
> Trying 172.16.134.175...
> Connected to 172.16.134.175.
>
>
> But when I try on the agent machine itself :
>
>
> $ nmap -p 8250 172.16.134.246
>
> Starting Nmap 6.40 ( http://nmap.org ) at 2016-02-01 09:34 MYT
> Nmap scan report for syafiqrokman-HPCC.cloudstack (172.16.134.246)
> Host is up (0.000017s latency).
> PORT STATE SERVICE
> 8250/tcp closed unknown
>
> $ telnet 172.16.134.246 8250
> Trying 172.16.134.246...
> telnet: Unable to connect to remote host: Connection refused.
>
> I tried updating iptables and ufw to allow tcp through 8250. Still, no
> luck.
> On an off note, why is it trying to connect through this port? It wasn't
> listed on the ports to be opened in the documentation.
>
>
>
>
> On Fri, Jan 29, 2016 at 5:43 PM Nux! <nu...@li.nux.ro> wrote:
>
>> Hello,
>>
>> Can you test manually if that agent machine can access the management one
>> on that port?
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> ----- Syafiq Rokman <ms...@gmail.com> wrote:
>> > Hi, I'm new to Linux and CloudStack and would appreciate any support
>> here
>> >
>> > CS 4.7 Ubuntu 14.04
>> >
>> > PC A - management server
>> > PC B - host
>> > PC C - host
>> >
>> > The management server managed to connect to PC B, making it a host.
>> > But I'm getting an 'Authentication Error' when adding PC C. The
>> > username/passwd should be correct already. (root , root passwd)
>> >
>> > ==== PC C agent.log ====
>> > WARN [utils.nio.NioConnection] (main:null) (logid:) Unable to connect
>> to
>> > remote: is there a server running on port 8250
>>
>>