dista commented on issue #11822:
URL:
https://github.com/apache/trafficserver/issues/11822#issuecomment-3349580802
> > I see something similar with 10.0.6 when doing a systemctl restart under
AlmaLinux 9, just less information in the crash logs.
> >
> > ```
> > Process: [TS_MAIN] [65855]
> > Version: Traffic Server 10.0.6
> > System Version: Linux x86_64 #1 SMP PREEMPT_DYNAMIC Fri Nov 1
14:58:02 EDT 2024 5.14.0-427.42.1.el9_4.x86_64
> > Date: Thu, 10 Jul 2025 12:28:20 -0400
> >
> > No target signal information
> >
> > No target CPU registers
> >
> > Thread 65855, [TS_MAIN]:
> >
> > Thread 65923, [ACCEPT 5:80]:
> >
> >
> > Process Status:
> > Name: [TS_MAIN]
> > State: Z (zombie)
> > Tgid: 65855
> > Ngid: 0
> > Pid: 65855
> > PPid: 1
> > TracerPid: 0
> > Uid: 1001 1001 1001 1001
> > Gid: 1001 1001 1001 1001
> > FDSize: 0
> > Groups: 1001
> > NStgid: 65855
> > NSpid: 65855
> > NSpgid: 65855
> > NSsid: 65855
> > Threads: 1
> > SigQ: 0/6940
> > SigPnd: 0000000000000000
> > ShdPnd: 0000000000000000
> > SigBlk: 0000000000000000
> > SigIgn: 0000000000001001
> > SigCgt: 0000000100004efe
> > CapInh: 0000000000000000
> > CapPrm: 0000000000000000
> > CapEff: 0000000000000000
> > CapBnd: 000001ffffffffff
> > CapAmb: 0000000000000000
> > NoNewPrivs: 0
> > Seccomp: 0
> > Seccomp_filters: 0
> > Speculation_Store_Bypass: thread vulnerable
> > SpeculationIndirectBranch: conditional enabled
> > Cpus_allowed: 3
> > Cpus_allowed_list: 0-1
> > Mems_allowed:
00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001
> > Mems_allowed_list: 0
> > voluntary_ctxt_switches: 90
> > nonvoluntary_ctxt_switches: 290
> >
> > Process Limits:
> > Limit Soft Limit Hard Limit
Units
> > Max cpu time unlimited unlimited
seconds
> > Max file size unlimited unlimited
bytes
> > Max data size unlimited unlimited
bytes
> > Max stack size unlimited unlimited
bytes
> > Max core file size unlimited unlimited
bytes
> > Max resident set unlimited unlimited
bytes
> > Max processes 6940 6940
processes
> > Max open files 1000000 1000000
files
> > Max locked memory 8388608 8388608
bytes
> > Max address space unlimited unlimited
bytes
> > Max file locks unlimited unlimited
locks
> > Max pending signals 6940 6940
signals
> > Max msgqueue size 819200 819200
bytes
> > Max nice priority 0 0
> > Max realtime priority 0 0
> > Max realtime timeout unlimited unlimited us
> >
> > Memory Regions:
> > ```
> >
> > The systemd service being used, being based on the one in tools/package
with adaptations for the install prefix I'm using.
>
> 请问你解决了吗？我现在10.0.6也是遇到了这个问题。
> 我也是自定义的安装前缀，使用systemd启动。
> 每次 执行 systemctl top 或者 systemctl restart .
>
> 都有很大概率提示
> ```
> Sep 25 03:13:43 debian traffic_server[28222]: [Sep 25 03:13:43.953]
traffic_crashlo NOTE: crashlog started, target=28222, debug=false syslog=true,
uid=0 euid=0
> Sep 25 03:13:43 debian traffic_server[28222]: [Sep 25 03:13:43.953]
traffic_crashlo NOTE: logging to 0x1a19c50
> Sep 25 03:13:43 debian traffic_server[28222]: [Sep 25 03:13:43.953]
traffic_crashlo NOTE: readlink failed with No such file or directory
> Sep 25 03:13:43 debian traffic_crashlog[28223]: traffic_crashlo NOTE:
crashlog started, target=28222, debug=false syslog=true, uid=0 euid=0
> Sep 25 03:13:43 debian traffic_crashlog[28223]: traffic_crashlo NOTE:
logging to 0x1a19c50
> Sep 25 03:13:43 debian traffic_crashlog[28223]: traffic_crashlo NOTE:
readlink failed with No such file or directory
> Sep 25 03:13:43 debian traffic_server[28222]: [Sep 25 03:13:43.955]
traffic_crashlo ERROR: wrote crash log to
/opt/cdn/logs/ats/crash-2025-09-25-031343.log
> Sep 25 03:13:43 debian traffic_crashlog[28223]: traffic_crashlo ERROR:
wrote crash log to /opt/cdn/logs/ats/crash-2025-09-25-031343.log
> ```
we now using 9.2.x, not using 10
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
