[p4] (2) Problems with P4WEB

Sweeney, Tony sweeney at ea.com
Mon Jun 19 07:20:09 PDT 2006 

Andrés,
	The second invocation will try to connect on the 'localhost' loopback address -- the packets never leave the local machine and do not appear on the wire.  In the first, they go out over the wire, and, depending on the implementation, are either read back from the wire or are short-circuited via the hardware driver.  What does '/sbin/ifconfig' tell you?

Tony.

quis custodiet ipsos custodes -- Juvenal VI, 347-8 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com [mailto:perforce-user-
> bounces at perforce.com] On Behalf Of Andres Fuentes
> Sent: 19 June 2006 14:24
> To: steve at vance.com; perforce-user at perforce.com
> Subject: Re: [p4] (2) Problems with P4WEB
> 
> Hello Steve (& all)
> 
> First, I started the p4d with : p4d -p myserver:1666 -r
> /usr/local/perforceroot/ -d
> After that IU typed : p4d -r /usr/local/perforceroot -J /var/log/journal -
> L /var/log/p4err -p 1666
> 
> I don't undertand why with the first option didn't run the P4WEB
> successful. It was strange, because I could see the P4WEB
> header...but with an error message. And when I started the configuration
> time with this new server, p4web runs fine when I started the p4d with the
> first option....any idea about it? ...maybe (?) any (involuntary)change
> into O.S. configuration (Suse v.10)
> 
> 
> 
> 
> Regards
> 
> 
> Andrés
> 
> 
> 
> -----Mensaje original-----
> De: steve at vance.com [mailto:steve at vance.com]
> Enviado el: lunes, 19 de junio de 2006 14:55
> Para: Andres Fuentes; perforce-user at perforce.com
> Asunto: Re: [p4] (2) Problems with P4WEB
> 
> 
> So what was the change in arguments?
> 
> Steve
> 
> Original Message:
> -----------------
> From: Andres Fuentes andres.fuentes at altana.es
> Date: 	Mon, 19 Jun 2006 11:18:19 +0200
> To: lee at marzke.net, perforce-user at perforce.com
> Subject: Re: [p4] (2)    Problems with P4WEB
> 
> 
> Thanks Lee,
> 
> Because we had dns problems sometimes I was working with Ip's .
> 
> The p4web is in the same machine as p4d...In this server the client p4
> (linux) doesn't work, to use client commands I use other windows machine
> (?) .
> 
> I was trying all posibilities what I know...and, after a restart of
> Perforce server (p4d) with differents arguments the P4WEB runs fine (? I
> don't known why)
> 
> 
> Regards,
> 
> 
> Andrés
> 
> 
> -----Mensaje original-----
> De: Lee Marzke [mailto:lee at marzke.net]
> Enviado el: viernes, 16 de junio de 2006 20:05
> Para: Andres Fuentes
> CC: perforce-user at perforce.com
> Asunto: Re: (2) [p4] Problems with P4WEB
> 
> 
> If the firewall is off and windows clients connect, seems like a DNS issue
> 
> Does the windows client work with   P4PORT=10.10.10.190:1666  ?
> 
> Is p4web on the same machine as p4d?  If not you need to trace the
> problem,  e.g  try running a command line client on the p4web machine
> and/or moving the client closer to the server until you find the problem.
> 
> Work with IP addresses first,  when  that works, you can switch back
> to DNS.  Again,   this is standard TCP/IP debugging, not really related
> to Perforce. Perhaps asking your network admin to help if your not
> strong in networking ?
> 
> Regards,
> 
> Lee Marzke
> 
> 
> Andres Fuentes wrote:
> > Hello all
> > (and Thanks Lee).
> >
> >
> > The windows client connects successsfully to Perforce server, which runs
> fine.
> > Whe I start the p4web on Linux server :
> > -------------------------------
> > nuevoperforce:/etc # p4web -w 8080 -B -p nuevoperforce:1666 &
> > [1] 13423
> > nuevoperforce:/etc #
> > P4Web started on host nuevoperforce.
> > User: root, Client: nuevoperforce, Port: nuevoperforce:1666
> > Version: P4Web/2003.2/LINUX24X86/65591
> >
> > If your web browser is running on nuevoperforce,
> >  for speed purposes, please point your browser to:
> >   http://localhost:8080/
> >
> > but if your web browser is running on a machine other than
> nuevoperforce,
> > please point your browser to:
> >   http://nuevoperforce:8080/
> > -------------------------------
> >
> > But when I try to access to p4web from my web-browser I can see the
> P4WEB
> header...but the follow message appears :
> >
> > Connect to server failed; check $P4PORT. TCP connect to
> nuevoperforce:1666 failed. connect: nuevoperforce:1666: Connection refused
> >
> > The running process :
> >
> > root     13423  0.0  0.0   2772   580 pts/2    S    16:30   0:00 p4web -
> w
> 8080 -B -p nuevoperforce:1666
> >
> >
> > Same days ago, whe I installed the p4web and it runs ok, I had
> configured
> the firewall and all was fine. Today, after server restart, p4web isn't
> ok...also I'm trying with the firewall disconected. (?)
> >
> > I'm testing with  http://nuevoperforce & http://10.10.10.190 &
> http://nuevoperforce.dns.altana.es  and always have the same mistake. (?)
> >
> >
> >
> > Any idea?
> >
> >
> >
> >
> >
> > Thanks in advance
> >
> >
> >
> >
> > Andrés
> >
> >
> >
> >
> > -----Mensaje original-----
> > De: Lee Marzke [mailto:lee at marzke.net]
> > Enviado el: viernes, 16 de junio de 2006 16:17
> > Para: Andres Fuentes
> > CC: perforce-user at perforce.com
> > Asunto: Re: [p4] Problems with P4WEB
> >
> >
> > Can clients connect to the server successfully ?
> > Is a firewall running on the new server ?
> >
> > You also could have a DNS problem.    Try using the IP of the server
> instead
> >
> > P4PORT=xxx.xxx.xxx.xxx:1666
> >
> > Use standard network debugging techniques to determine why the
> > connection fails.
> >
> > Lee Marzke
> >
> >
> > Andres Fuentes wrote:
> >
> >> 	Hello all,
> >>
> >> I'm working with a new server which I installed Perforce and defect
> tracker (Bugzilla).........I'm in testing time, for that I restarted the
> server and...now the Perforce work fine, but I've problems with the client
> web (P4WEB) which was ok before restart (?)
> >>
> >> When I consult a bug (Bugzilla) and try to see it's information with
> P4WEB...I can see the main page of P4WEB but don't appears the information
> related, because an error :
> >> Connect to server failed; check $P4PORT. TCP connect to
> nuevoperforce:1666 failed. connect: nuevoperforce:1666: Connection refused
> >>
> >>
> >> But the $P4PORT is correct! ...if don't the Perforce doesn't work, and
> it's fine.....
> >>
> >> Please, anybody could help me with an idea?
> >>
> >>
> >>
> >> Thanks in advance
> >>
> >>
> >>
> >> Andrés
> >>
> >>
> >> _______________________________________________
> >> perforce-user mailing list  -  perforce-user at perforce.com
> >> http://maillist.perforce.com/mailman/listinfo/perforce-user
> >>
> >>
> >
> >
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> 
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
> 
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

More information about the perforce-user mailing list