Jump to content


Member Since 30 Jun 2014
Offline Last Active Yesterday, 01:43 AM

Topics I've Started

Basic backup/recovery question

16 February 2017 - 07:35 PM

I'm about ready to upgrade our server from the ancient 2012.1 to the current 2016.2. I've read several KB articles on backup, recovery, and upgrade (as well as several manual pages). Even so, there is one item I'm not completely clear on.

When you create a checkpoint using p4d -jc, it will also save and truncate the journal. When I'm recovering from that checkpoint using p4d -jr, do I also need to recover from the journal file too or does the checkpoint contain a complete and up to date backup of the server?


EDIT:  Just in case it wasn't clear, my intent is to stop p4d before creating the checkpoint.

Automated user deletion by admin

19 December 2016 - 08:45 PM

I am needing to clean up many user accounts that are no longer being used. I would like to automate this process as much as I can (I have a lot of users I need to clean up).

Just a simple p4 user -f -d someuser is not sufficient, because the command fails if the user has opened or shelved files.

I've been able to automate most of the process and have cleaned up several of the old accounts. I'm stuck now with the users that have files checked out. Is there a way to revert the files in a change list without having to log in to each and every user?

What about clients that are locked to a specific host? Do I have to edit each of those clients to remove the Host field, before logging into the user to revert the opened files?

It seems like there are a lot of steps that can't easily be automated.

Any suggestions?

Using P4DTG with multiple bug tracking packages

07 November 2016 - 08:30 PM

We are in the process of migrating from Bugzilla to Jira. We've had P4DTG running between Bugzilla and Perforce for several years now. We are going to need to keep P4DTG running between Perforce and Bugzilla for a while after Jira is up and running (the use of Bugzilla and Jira will overlap for a while).

I'm setting up a second instance of P4DTG to manage the Jira<->Perforce integration. That seems to be functioning fine, except when there are changes to the Perforce jobs that may need to be sent back to the bug tracking software. Whenever a Perforce job gets updated, the DTG_ERROR field gets set to "DTG_MAPID does not match current map".

How can I have P4DTG maps set up for both Perforce<->Bugzilla and Perforce<->Jira without them stepping on each others toes?

Swarm worker queue hangs

05 October 2016 - 11:22 PM

Both yesterday and today, we've had our worker queue in Swarm stop processing requests. We're running Swarm 2016.1 and Perforce server version 2012.1. We've had Swarm up and running on 2016.1 since May without any issues. The last config file change was in August, to update the email server. I have configured the max number of workers to five.

When I discovered that the queue processing has stopped (this was a couple of hours after the earliest queue entry still present), I performed an "apachectl stop" followed by "apachectl start". This unblocked the backup and the queue resumed processing.

Any thoughts regarding why this is happening? I don't see any errors or unusual messages in any of the logs I've looked at (I've looked at the Swarm log, the Apache logs, and the system log).