Server init fails with B`Tree Case Order Mismatch!`

[oskargargas]

Hi!

I'm trying to setup p4 inside docker on my Synology NAS. It's intel based linux. I'm running multiple apps on it without any problems.

With your container I'm running into the following issue.

perforce-p4-p4d-1  | Initializing configuration files in /etc/perforce
perforce-p4-p4d-1  | [INIT] Running 01-permissions.sh...
perforce-p4-p4d-1  | Checking permissions in /data/master/root
perforce-p4-p4d-1  | Checking permissions in /data/master/root/ssl
perforce-p4-p4d-1  | [INIT] Running 10-install-ssl-certificates.sh...
perforce-p4-p4d-1  | [INIT] Running 11-configure-tls-version.sh...
perforce-p4-p4d-1  | Running: set ssl.tls.version.min=12
perforce-p4-p4d-1  | Running: set ssl.tls.version.max=13
perforce-p4-p4d-1  | [INIT] Running 40-enable-unicode.sh...
perforce-p4-p4d-1  | [INIT] Running 45-database-upgrade.sh...
perforce-p4-p4d-1  | [INIT] Running 50-configure-helix-p4d.sh...
perforce-p4-p4d-1  | Initializing p4d server...
perforce-p4-p4d-1  | 
perforce-p4-p4d-1  | 
perforce-p4-p4d-1  | Service master not found. Creating...
perforce-p4-p4d-1  | 
perforce-p4-p4d-1  | Configuring p4d service 'master' with the information you specified...
perforce-p4-p4d-1  | 
perforce-p4-p4d-1  | Perforce server error:
perforce-p4-p4d-1  | 	Database open error on db.config!
perforce-p4-p4d-1  | 	BTree Case Order Mismatch! Check p4d -Cx flag usage.

Here is my docker-compose.yml

volumes:
  p4d_data: {}
services:
  p4d:
    image: hawkmothstudio/helix-p4d
    build: helix-p4d
    ports:
      - '1666:1666'
    environment:
      P4USER: 'p4admin'
      P4PASSWD: 'P@ssw0rd'
      P4D_USE_UNICODE: 'true'
      P4D_CASE_SENSITIVE: 'false'
    volumes:
      - p4d_data:/data

I've tried running it with volume, or mapped directly to the filesystem. With full config as in example and with minimal (just user name and pass). All to the same error BTree Case Order Mismatch.

The server only starts if I set P4D_CASE_SENSITIVE: 'true'. Am I missing something or is there some problem with initialisation, as in it starts somewhere without flag provided, inits the db and then, when it finally tries to run with flag correctly set it complains about case order mismatch?

[AllToBeNize]

Hi! I ran into the same issue while setting up the container and traced it to inconsistent case-sensitivity flags during initialization.

I opened PR #61 to fix it.

With P4D_CASE_SENSITIVE=false, every p4d invocation must consistently use -C1. Previously, some initialization commands and the final server command did not receive this flag, which could create or access the database with inconsistent case-order settings and cause the BTree Case Order Mismatch error.

You can try building an image from my fix/case-sensitivity-db branch to see whether it resolves the issue in your environment.

[oskargargas]

Thanks @AllToBeNize ! I've verified your fix, and it works correctly on my system. Hopefully it'll be merged into upstream.