[Linux-HA] haclient.py requires a port to login ?

[Paulo F. Andrade]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Actually a similar thing happens on my Mac, the diference is that I  
do have to specify the correct port to connect. Anything else won't do.

On my Linux systems (running ubuntu and gentoo) I don't have to  
specify the port number, and it defaults to 5560.

Here's the output when I don't specify a port number:
Traceback (most recent call last):
   File "/sw/lib/heartbeat-gui/haclient.py", line 1598, in on_login
     if not manager.login(server, user, password):
   File "/sw/lib/heartbeat-gui/haclient.py", line 1943, in login
     ret = mgmt_connect(ip, username, password, port)
TypeError: mgmt_connect() argument 4 must be string, not None

It's no big deal, but it must be a bug.
Paulo F. Andrade 52439 at IST
mailto: pfca at mega.ist.utl.pt


On 2007/03/27, at 20:04, Alan Robertson wrote:

> Karl Hanzel wrote:
>>
>> 'Just upgraded to heartbeat-2.0.8-2.el4.centos, and it's new  
>> companion
>> RPMs.
>>
>> 'Found the new haclient.py under /usr/lib64/heartbeat-gui/.  It  
>> starts
>> up fine, but upon login to my running cluster and supplying these  
>> args
>> to the Login window: 127.0.0.1 / hacluster / hacluster's_pw (which
>> always worked previously), i'm now getting:
>>
>> -- 
>>   Traceback (most recent call last):
>>     File "/usr/lib64/heartbeat-gui/haclient.py", line 1598, in  
>> on_login
>>       if not manager.login(server, user, password):
>>     File "/usr/lib64/heartbeat-gui/haclient.py", line 1943, in login
>>       ret = mgmt_connect(ip, username, password, port)
>>   TypeError: mgmt_connect() argument 4 must be string, not None
>> -- 
>>
>> ...and it fails to login/connect.
>>
>> If in the "Server(:port):" field of the Login window i specify
>> "127.0.0.1:xyz" it makes the login without the above complaint.  That
>> "xyz" can be literal... i seem to be able to supply anything  
>> (including
>> a null string) there.
>>
>> So what's the rub ... why do i/we now have to specify a port?  And  
>> if we
>> do, what's the appropriate port to specify?
>
> You don't have to supply a port...  You _can_ specify a port if you  
> like...
>
> You can check out the screencast here, and see what I mean...
> 	http://linux-ha.org/Education/Newbie/IPaddrScreencast
>
> In other words It Works For Me (tm)  ;-)
>
>
>
> -- 
>     Alan Robertson <alanr at unix.sh>
>
> "Openness is the foundation and preservative of friendship...  Let me
> claim from you at all times your undisguised opinions." - William
> Wilberforce
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFGCYPT7Pu4LhNRtw4RAtVHAJ9QyaZXIH7empl0CKTDklw1K0jNNACeNCp3
V5S2OmJ+w3e2QeeFdbh1j/o=
=asr2
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFGCYPm7Pu4LhNRtw4RAkANAJ4twLLO+K4qSIeHuYk3xhmoVhe0kQCg+pOr
66Qa2xhS/fN0hFepci2s7gE=
=fGmb
-----END PGP SIGNATURE-----