ATS 9.1.3 permission problems with run file on openEuler20_aarch64

[Tom-python0121]

hello，I meet a problem:ATS 9.1.3 permission problems with run file on openEuler20_aarch64

Steps to reproduce the issue

[root@localhost bin]#./traffic_manager
[E. Mgmt] log ==> [TrafficManager] using root directory '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver'
FATAL: Can't open server lockfile '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/server.lock' (Permission denied)
[root@localhost trafficserver-9.1.3]#cat var/log/trafficserver/traffic.out
[E. Mgmt] log ==> [TrafficManager] using root directory '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver'
FATAL: Can't open server lockfile '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/server.lock' (Permission denied)
[E. Mgmt] log ==> [TrafficManager] using root directory '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver'
FATAL: Can't open server lockfile '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/server.lock' (Permission denied)

Can you tell me how to solve the problem?
Run the sh -x bin/trafficserver start command:
test.log

[bneradt]

I assume this means there is a permissions issue with access to one of the directories in that path to the lock file. Can you check that each of your directories in /home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/ have the read and execute privilege granted to user nobody and that /home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/ itself also has write access so that the lock file can be written?

[Tom-python0121]

@bneradt Although I have assigned permissions to /home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver, the error is reported in openEuler_aarch64.

[root@localhost bin]# chmod 777 /home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/
[root@localhost bin]#
[root@localhost bin]#
[root@localhost bin]# ./traffic_manager
[E. Mgmt] log ==> [TrafficManager] using root directory '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver'
FATAL: Can't open server lockfile '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/server.lock' (Permission denied)

But in centos8_aarch64, it can be passed.

[root@bigdata bin]# ./traffic_manager
[E. Mgmt] log ==> [TrafficManager] using root directory '/home/spack/opt/spack/linux-centos8-aarch64/gcc-8.5.0/trafficserver'
Traffic Server 9.1.2 Dec 14 2022 16:41:04 bigdata
traffic_server: using root directory '/home/spack/opt/spack/linux-centos8-aarch64/gcc-8.5.0/trafficserver'

Do you have any good ideas?

[bneradt]

@bneradt Although I have assigned permissions to /home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver, the error is reported in openEuler_aarch64.

[root@localhost bin]# chmod 777 /home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/
[root@localhost bin]#
[root@localhost bin]#
[root@localhost bin]# ./traffic_manager
[E. Mgmt] log ==> [TrafficManager] using root directory '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver'
FATAL: Can't open server lockfile '/home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/server.lock' (Permission denied)

With the message "Permission denied" I still suspect some DAC issue for your path with the Traffic Manager process. Can you verify that each of the directories in the /home/spack/opt/spack/linux-openeuler20-aarch64/gcc-7.3.0/trafficserver/var/trafficserver/ path are readable/executable by the Traffic Manager process? Note that traffic_manager will run as the proxy.config.admin.user_id user (which defaults to user nobody). Using strace might be helpful to determine the specific cause of the EPERM.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.

[bryancall]

I'm closing this as a stale support request. The "Permission denied" error opening the server lockfile is a local filesystem permission issue, not an Apache Traffic Server defect: traffic_manager runs as the proxy.config.admin.user_id user (default nobody), and that user (or one of the parent directories along the var/trafficserver path) lacked the read, write, and execute access needed to create the lock file on your openEuler aarch64 install, even though the same build worked on CentOS 8. The recommended next step (verifying access along the full path, and using strace to pinpoint the EPERM) was never followed up on, so there is nothing actionable here. Note also that the traffic_manager process that produced this message was removed entirely in #8633, first shipped in the 10.0.0 release, so this code path no longer exists in current versions. Please open a new issue with a reproduction if you still see a problem on a supported release.