Jump to content


After ubuntu update, "p4d service is running but not responding"

p4d ubuntu aws

  • Please log in to reply
3 replies to this topic

#1 SMGreenfield

SMGreenfield

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 23 October 2017 - 06:52 AM

I set up p4d to run on an Amazon AWS Ubuntu 16.04 instance and all WAS well.  Used an Elastic IP address so public address wouldn't change.  The p4 command line was working just fine on the ubuntu server. I was able to connect in remotely from the internet via P4V on macOS.  

Then I applied a series of ubuntu updates via:


[font=Arial][size=3]
sudo apt-get update && sudo apt-get upgrade[/size][/font]


When I did sudo reboot, I could no longer connect remotely, and even p4 help on the server returned:

Quote

Perforce client error:
SSL connect to ssl:172.31.53.19:1666 failed  (Connection reset by peer).
Remove SSL protocol prefix from P4PORT or fix the TLS settings.

sudo -u perforce p4dctl status -a
returned:


Quote

'wbi_perforce' p4d service is running but not responding.

So I must've messed something up but good.  But what?  Where?

Stephen

#2 P4Jen

P4Jen

    Advanced Member

  • Staff Moderators
  • 155 posts

Posted 23 October 2017 - 02:39 PM

Hi Stephen,

I have personally not seen this issue before.

I suggest first checking if P4D is actually running.

You can do this by running:
  ps -Aef | grep p4d

Note you will see your 'grep' process in this output.

If it is still up I suggest you run:
  p4 admin stop

to bring the server down safely, then check the health of your database by running:
  p4d -xv
and
  p4d -xx

If there are problems this will generate a 'jnl.fix' file, that will attempt to resolve them.

If you have support I strongly recommend you contact 'support@perforce.com', if a 'jnl.fix' file is generated.

We can tell you if it is safe to replay it.

If a 'jnl.fix' file is generated and you do not wish to replay it, you will need to restore from your most
recent checkpoint and backup of the depot files.

You can then replay journals up to and including the current journal.

More information about backup and recovery is located here:
  https://www.perforce...ter.backup.html

Hope this helps,
Jen.


#3 SMGreenfield

SMGreenfield

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 23 October 2017 - 06:08 PM

View PostP4Jen, on 23 October 2017 - 02:39 PM, said:

I suggest first checking if P4D is actually running.

It seems to be running:

perforce 1854 1 0 06:30 ? 00:00:00 p4d [wbi_perforce/ssl:1666]

Quote

If it is still up I suggest you run:
  p4 admin stop


Still getting this:

Perforce client error:
SSL connect to ssl:1666 failed (Connection reset by peer).
Remove SSL protocol prefix from P4PORT or fix the TLS settings.


​Somehow I messed something up, but good.  If I can't figure it out, I may have to create a new AWS EC2 instance, and install p4d from scratch -- there's nothing significant to lose at this point.

I DID attempt to obliterate the depot -- I had made a whole mess of bad decisions that created some undesirable changelists, and since I was at the beginning of the process, I thought I would start from scratch.

#4 P4Jen

P4Jen

    Advanced Member

  • Staff Moderators
  • 155 posts

Posted 24 October 2017 - 10:25 AM

Hi,

It does seem like something strange is going on with the networking on that machine.

This KB may provide some tips for diagnosing the issue:
  http://answers.perfo...rticles/KB/3785

Cheers,
Jen!





Also tagged with one or more of these keywords: p4d, ubuntu, aws

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users