I'm running into a new and weird issue where my Perforce server depot - which was working fine until very recently (when I did some unrelated experiments with wiki.js and nginx) - has suddenly started refusing connections on port 1666, its default port. I'm getting this:
Code:
systemctl status helix-p4dctl.service
● helix-p4dctl.service - LSB: Starts all Perforce services
Loaded: loaded (/etc/init.d/helix-p4dctl; generated)
Active: failed (Result: exit-code) since Mon 2022-06-20 23:16:22 PDT; 8s ago
Docs: man:systemd-sysv-generator(8)
Process: 6914 ExecStart=/etc/init.d/helix-p4dctl start (code=exited, status=1/FAILURE)
Jun 20 23:16:21 War-mind p4dctl[6924]: error: Connect to server failed; check $P4PORT.
connect: 127.0.0.1:1666: Connection refused
Jun 20 23:16:21 War-mind p4dctl[6926]: error: Connect to server failed; check $P4PORT.
connect: 127.0.0.1:1666: Connection refused
Jun 20 23:16:21 War-mind p4dctl[6927]: error: Connect to server failed; check $P4PORT.
connect: 127.0.0.1:1666: Connection refused
Jun 20 23:16:21 War-mind p4dctl[6928]: error: Connect to server failed; check $P4PORT.
connect: 127.0.0.1:1666: Connection refused
Jun 20 23:16:22 War-mind p4dctl[6919]: error: 'PerforceServer' p4d: '/opt/perforce/sbin/p4d' exited with status
Jun 20 23:16:22 War-mind p4dctl[6919]: Started 0 services.
Jun 20 23:16:22 War-mind p4dctl[6919]: error: Not all services started successfully.
Jun 20 23:16:22 War-mind systemd[1]: helix-p4dctl.service: Control process exited, code=exited status=1
Jun 20 23:16:22 War-mind systemd[1]: helix-p4dctl.service: Failed with result 'exit-code'.
Jun 20 23:16:22 War-mind systemd[1]: Failed to start LSB: Starts all Perforce services.
The server responds to ping correctly, and services on other ports (80, 137, 445, 49152, etc) are functioning.
ifconfig is this:
Code:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.117 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::da16:9fa8:aff2:2aef prefixlen 64 scopeid 0x20<link>
ether 00:04:23:d3:d0:92 txqueuelen 1000 (Ethernet)
RX packets 396666 bytes 47266563 (47.2 MB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 11743 bytes 2353863 (2.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18 memory 0xb8820000-b8840000
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.116 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::659f:d321:8607:cc5f prefixlen 64 scopeid 0x20<link>
ether 00:04:23:d3:d0:93 txqueuelen 1000 (Ethernet)
RX packets 337457 bytes 23222306 (23.2 MB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 4922 bytes 339329 (339.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 19 memory 0xb8800000-b8820000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 6505 bytes 424432 (424.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6505 bytes 424432 (424.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
EDIT: I was able to get the helix-p4dctl.service started by resetting the environment variable for P4PORT to ssl:9000 instead of ssl:1666, but the service status is still griping about not being able to connect to 1666 - but it IS running. However: I get this when I try to run the config script (sudo /opt/perforce/sbin/configure-helix-p4d.sh)...
Code:
Perforce Service name [master]: PerforceServer
Perforce Server address (P4PORT) [ssl:1666]: ssl:9000
Configuring p4d service 'PerforceServer' with the information you specified...
FATAL: Need to be logged in as a superuser to perform this operation
I'm logged in as root when I ran that, not sure how much more superuser I can get. My admin account is obviously set up with sudo.
When I tried p4 admin after that, now it's griping about port 9000...
Code:
root@War-mind:/home/brandonadmin# p4 admin restart
Perforce client error:
Connect to server failed; check $P4PORT.
connect: 127.0.0.1:9000: Connection refused
So basically the server has stopped accepting perforce network requests from remote OR local clients? But I didn't touch a single thing with the Perforce configs when this started - I messed with nginx and apache2 and some net namespaces, but I tore all that back out. Did I not get something put back the way it needs to be? I'm in over my head here.
Ubuntu 18.04 LTS server (it's an old 2007 vintage rack server, dual Xenons or something). DNS nameserver is a PiHole doing DHCP and local DNS filtering for the whole local network. Perforce remote client is my workstation (Debian 11).
