Jump to content


Member Since 11 Apr 2014
Offline Last Active Today, 11:52 AM

Posts I've Made

In Topic: New Perforce Ubuntu server won't start

05 February 2019 - 04:36 PM

The error you are seeing indicates that the address and port you are trying to use to start the server are being used by something eels.

The fact that you are able to run 'p4 info' indicates that you already have an instance of P4D running on

To stop this instance run:
  p4 -p localhost:1666 -u super admin stop

To get more information about your Perforce (Helix) environment, you can run:
  p4 set

You may also wish to contact our sales team to discuss setting up a free 30 day evaluation of the Helix (Perforce) server.

This will give you access to technical support, who can help get you up and running with the product.

Hope this helps,

In Topic: Ran out of space and can't log into workspace!

22 January 2019 - 04:08 PM


From your post I assume that you have run out of disk space on the Helix Server.

P4V itself does not store multiple revisions of the file, but if you have a personal server (DVCS) this
will store multiple revisions of files on your computer.

It will also need to create temporary files.

It sounds like the '/tmp' directory may be full.

If this is the case then you will have to either remove some data for it, or put '/tmp' on a larger volume.

You can use the command 'df -h' to check how much space is left on the disk, or use the 'Disk Utility' Mac

Also, this KB article provides some suggestions for what you can do if you run out of space:

Hope this helps,

In Topic: P4Python undefined symbol SSL_library_init

07 January 2019 - 04:49 PM


Thanks for bringing this to our attention.

I have tested here with Ubuntu 18.04 and have reproduced the behaviour you describe.

I have also had a look through the latest P4Python release notes, and do not see any mention of
Ubuntu 18.04 not being a supported Linux flavour.

I will check to see if we have an existing report of this issue.

If we do I will add details of your post to it.

If not I will log one and add details of the post to it.

Thanks again,

In Topic: Community help page "Moving Server Components on the Same Machine" ha...

31 December 2018 - 05:37 PM


Thanks for bringing this to our attention.

At the very least, the 'Solution' text needs to be changed, to make it clear that the article can be applied to either moving components on the same machine, or moving between machines who's OS, processor type, and
case handling do not differ.

We will review the article and make the necessary corrections.

Thanks again,

In Topic: Ignored sub folder still set "Read-only"

08 November 2018 - 05:40 PM

Hi Tgienger,

Setting 'allwrite' in the Helix Client specification may help.

When this option is set, files in the workspace are writable by default.

Hope this helps,