zhaozuowu opened a new issue, #10345:
URL: https://github.com/apache/skywalking/issues/10345

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Apache SkyWalking Component
   
   OAP server (apache/skywalking)
   
   ### What happened
   
           php.ini setting
   
   [skywalking]
   extension=skywalking_agent.so
   
   # Enable skywalking extension or not.
   skywalking_agent.enable = On
   
   # Log file path.
   skywalking_agent.log_file = /usr/local/etc/skywalking-php.log
   
   # Log level: one of `OFF`, `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`.
   skywalking_agent.log_level = INFO
   
   # Address of skywalking oap server.
   skywalking_agent.server_addr =http://127.0.0.1:11800
   
   
   # Application service name.
   skywalking_agent.service_name = gateway-uat
   
   # Skywalking version.
   skywalking_agent.skywalking_version = 8
   
   # Skywalking worker threads, 0 will auto set as the cpu core size.
    #skywalking_agent.worker_threads = 3
   
   ______________________________________
   
   Error in php-error.log
   
   zend_mm_heap corrupted
   [05-Feb-2023 13:46:05] WARNING: [pool www] child 115 exited with code 1 
after 1350.514043 seconds from start
   [05-Feb-2023 13:46:05] NOTICE: [pool www] child 157 started
   
   
   
         
   
   ### What you expected to happen
   
   我希望能修复这个问题
   
   ### How to reproduce
   
   fix
   
   ### Anything else
   
   fix
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to