Horde - unable to read globals.json from perforce P4PASSWD invalid or unset

Development Pipeline & Plugins
, ,
1

This question was created in reference to: [Horde - Perforce Password error when configuring globals.json location in [Content removed]

I’m getting “Failed: Perforce password (P4PASSWD) invalid or unset. (Generic=Config)” in Horde. Familiar error to anyone who uses perforce but I don’t understand why I’m getting it because the password value is correct (I’ve tried it 100 times or so just to be sure I’m not going mad)

Horde is running in ECS, checked environment from shell, checked environment from /api/v1/debug/environment

Docker image is latest. Relevant config bits (which I think match https://github.com/EpicGames/UnrealEngine/blob/5\.5/Engine/Source/Programs/Horde/Docs/Deployment/ServerSettings.md\#perforcecredentials)

Horde__configPath=//horde/globals.json

Horde__perforce__0__credentials__password=notrealpassword

Horde__perforce__0__credentials__userName=hordeserver

Horde__perforce__0__id=default

Horde__perforce__0__serverAndPort=ssl:perforce.domain.co.uk:1666

Any ideas what I’m doing wrong?

2

Confirmed the creds are fine in globals.json when referenced by file system path for configPath. Issue only occurs when setting configPath is in perforce and variables set. I suspect its bad error handling from perforce and its actually nothing to do with password, just need to find out what

3

Realised I was using server.json and documentation for 5.4 and not 5.5. So

Horde__perforce__0__id=default

Horde__perforce__0__serverAndPort=ssl:perforce.domain.co.uk:1666

now appears to be

Horde__plugins__build__perforce__0__id=default

Horde__plugins__build__perforce__0__ServerAndPort=ssl:perforce.domain.co.uk:1666

However this hasn’t solved the issue and actually seems worse

(logs) System.Exception: Unknown Perforce cluster ‘Default’

(UI) Failed: Connect to server failed; check $P4PORT. TCP connect to perforce:1666 failed. Name or service not known

At least with the 5.4 convention I got (and resolved) p4trust warning so definitely talking to the right server

Going to set useLocalPerforceEnv to true and see how that goes.

4

I feel like I’m just getting further and further down a totally un-necessary rabbit hole

Unable to read perforce://default/app/Defaults/default.global.json. No matching files found.This was after p4client error which is to be expected if I’m using the environment. Where on earth is that depot coming from? I have configPath set as follows

Horde__configPath=//horde/globals.json

I’ll just put my globals.json and other configs onto filesystem for now

5

[Content removed]

This looks very similar, suspect root cause could be Unreal Engine Issues and Bug Tracker (UE\-254494)

6

Right all sorted, if configPath EV is set to a perforce path make sure the includes to other configs are perforce paths and not $(HordeDir) like in default globals.json if you just copied it for reference to get started

7

Glad you found the root cause. Closing this issue.