PASSWD unset error

Hi,

I'm getting the following error somwhere inside
P4.save_client:

---------
ERROR: [P4#run] Errors during command execution( "p4
client -i" )

        [Error]: Perforce password (P4PASSWD) invalid or
unset.
--------

The "fun" thing is that if I execute "p4
login -s" everything looks
normal (number of hours left to expiration). This call is
hidden inside
my own classes (auto-generating temporary client specs) and
works a
treat on another very similar machine.

Details:

Platform: OpenSUSE 10.2
Compiler: g++ 4.1
p4api: 2005.1 (linux3x86)
P4Ruby: P4Ruby 1.5339
Ruby: 1.8.5

I originally tried using the latest stable release together
with the
2006.2 API, but when I got the above error I reverted to the
same
version I've got working on another OpenSUSE machine. The
other
machine's details:

Platform: OpenSUSE 10.0
Compiler: g++ 4.0.1
p4api: 2005.1 (linux3x86)
P4Ruby: P4Ruby 1.5339
Ruby: 1.8.2

Any hints on where to start troubleshooting?

/ Johan

_______________________________________________
p4ruby mailing list
p4rubyperforce.com

http://maillist.perforce.com/mailman/listinfo/p4ruby

Hi Johan

What's in the tickets file for that machine? I have had this
sort of problem
with a rogue ticket entry for the same P4Port.

Robert 

> -----Original Message-----
> From: p4ruby-bouncesperforce.com 
> [mailto:p4ruby-bouncesperforce.com] On Behalf Of
Johan Nilsson
> Sent: 11 May 2007 14:18
> To: p4rubyperforce.com
> Subject: [p4ruby] PASSWD unset error
> 
> Hi,
> 
> I'm getting the following error somwhere inside
P4.save_client:
> 
> ---------
> ERROR: [P4#run] Errors during command execution(
"p4 client -i" )
> 
>         [Error]: Perforce password (P4PASSWD) invalid
or unset.
> --------
> 
> The "fun" thing is that if I execute "p4
login -s" everything 
> looks normal (number of hours left to expiration). This
call 
> is hidden inside my own classes (auto-generating
temporary 
> client specs) and works a treat on another very similar
machine.
> 
> Details:
> 
> Platform: OpenSUSE 10.2
> Compiler: g++ 4.1
> p4api: 2005.1 (linux3x86)
> P4Ruby: P4Ruby 1.5339
> Ruby: 1.8.5
> 
> I originally tried using the latest stable release
together with the
> 2006.2 API, but when I got the above error I reverted
to the 
> same version I've got working on another OpenSUSE
machine. 
> The other machine's details:
> 
> Platform: OpenSUSE 10.0
> Compiler: g++ 4.0.1
> p4api: 2005.1 (linux3x86)
> P4Ruby: P4Ruby 1.5339
> Ruby: 1.8.2
> 
> Any hints on where to start troubleshooting?
> 
> / Johan
> 
> _______________________________________________
> p4ruby mailing list
> p4rubyperforce.com
> 
http://maillist.perforce.com/mailman/listinfo/p4ruby
> 
_______________________________________________
p4ruby mailing list
p4rubyperforce.com

http://maillist.perforce.com/mailman/listinfo/p4ruby

Hi Robert,

thanks for your reply.

> -----Original Message-----
> From: Robert Cowham [mailto:robertvaccaperna.co.uk] 
> Sent: den 11 maj 2007 16:02
> To: Johan Nilsson; p4rubyperforce.com
> Subject: RE: [p4ruby] PASSWD unset error
> 
> Hi Johan
> 
> What's in the tickets file for that machine? I have had
this 
> sort of problem with a rogue ticket entry for the same
P4Port.

The tickets file looks just fine. I also tried deleting it
and logging
in again, but the problem persists.

Do you know if it is possible to make P4Ruby output all
commands,
including options, when they are executed? I'm currently
relying on some
P4 parameters being set in the environment + config file and
I'd like to
check what is actually used.

/ Johan

_______________________________________________
p4ruby mailing list
p4rubyperforce.com

http://maillist.perforce.com/mailman/listinfo/p4ruby

Follow up, in case anyone's interested: 

> -----Original Message-----
> From: p4ruby-bouncesperforce.com 
> [mailto:p4ruby-bouncesperforce.com] On Behalf Of
Johan Nilsson
> Sent: den 15 maj 2007 13:12
> To: p4rubyperforce.com
> Subject: Re: [p4ruby] PASSWD unset error
> 
> Found it! 
> 
> I was using
P4PORT=<dotted-ip-address>:<port> in 
> .bash_profile and
P4PORT=<server-name>:<port> in my scripts, e.g:
> 

[snip]

> 
> As both the names and ip-address refer to the same
machine, 
> logically I think this should work - or? I'll try and
drop an 
> enhancement request to Perforce support.

I was too late. From the 2007.2 beta release notes:

    #117342 * **
	Different values of P4PORT for the same server instance
	e.g. (ip:port# vs host:port#) would result in multiple
	ticket entries in the Perforce ticket file. This has 
	been fixed so that the same server instance will always
	produce a single ticket entry that either P4PORT value can
	use.  (Bug #16707, #18349).

/ Johan

_______________________________________________
p4ruby mailing list
p4rubyperforce.com

http://maillist.perforce.com/mailman/listinfo/p4ruby