Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Php Agent on Ubuntu 18.04

welcome

#4

Hey @m.hannessen - I just got a ticket created for you!

I don’t have an ETA right now but I know that the teams are trying to get as much data as possible to replicate this behaviour! So we’re going to reach out in that ticket to get some information from you :slight_smile:


#5

The only pattern that we noticed: it fails at the time of calling newrelic_end_transaction -newrelic_start_transaction - newrelic_name_transaction


#6

Hi @skamz

Are you still seeing the segfaults happening in your server?

If yes, I’d be more than happy to create a ticket to better investigate it.

thanks,

Rodrigo


#7

Hi there,

We are also seeing this issue under PHP 7.2.24, Ubuntu0.18.04.3, NR Plugin: 9.7.0.258

Stacktrace looks like this for us:

(gdb) bt
#0 nr_segment_iterate_helper () at nr_segment.c:458
#1 nr_segment_iterate_helper () at nr_segment.c:470
#2 nr_segment_iterate_helper () at nr_segment.c:470
#3 nr_segment_iterate_helper () at nr_segment.c:470
#4 nr_segment_iterate_helper () at nr_segment.c:470
#5 nr_segment_iterate_helper () at nr_segment.c:470
#6 nr_segment_iterate_helper () at nr_segment.c:470
#7 nr_segment_iterate_helper () at nr_segment.c:470
#8 nr_segment_iterate_helper () at nr_segment.c:470
#9 0x00007f3f33842731 in nr_segment_iterate_helper () at nr_segment.c:470
#10 nr_segment_iterate_helper () at nr_segment.c:470
#11 nr_segment_iterate_helper () at nr_segment.c:470
#12 nr_segment_iterate_helper () at nr_segment.c:470
#13 nr_segment_iterate_helper () at nr_segment.c:470
#14 nr_segment_iterate_helper () at nr_segment.c:470
#15 nr_segment_iterate_helper () at nr_segment.c:470
#16 nr_segment_iterate_helper () at nr_segment.c:470
#17 nr_segment_iterate_helper () at nr_segment.c:470
#18 0x00007f3f3384343e in nr_segment_iterate_helper () at nr_segment.c:470
#19 nr_segment_iterate () at nr_segment.c:499
#20 0x00007f3f3385b010 in nr_segment_tree_finalise () at nr_segment_tree.c:64
#21 0x00007f3f338482be in nr_txn_end () at nr_txn.c:1368
#22 0x00007f3f33835083 in nr_php_txn_end () at /home/hudson/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_txn.c:1000
#23 0x00007f3f33831efb in nr_php_post_deactivate () at /home/hudson/workspace/php-release-agent/label/centos5-64-nrcamp/agent/php_rshutdown.c:108
#24 0x000055cdf370f6ca in zend_post_deactivate_modules ()
#25 0x000055cdf36a301d in php_request_shutdown ()
#26 0x000055cdf37bb914 in ?? ()
#27 0x000055cdf355166b in ?? ()
#28 0x00007f3f4280cb97 in __libc_start_main (main=0x55cdf3551250, argc=8, argv=0x7ffdfed8cdf8, init=, fini=, rtld_fini=, stack_end=0x7ffdfed8cde8) at …/csu/libc-start.c:310
#29 0x000055cdf355180a in _start ()

Hope this adds some info.

Regards,

-Zak


#8

No, our problem did not recur for several days. As I wrote, the problem was with end - start - name transaction.
We divided the transactions into separate processes in this cron task. We wanted to do this earlier, and we had the opportunity to speed up the implementation.
We use end - start - name transactions in other places, but this was the only place that worked for more than an hour. Other background tasks that use end - start - name transaction work for less than 10 minutes and there is no problem.

Ryan Veitch has already created a ticket. I provided all the requested information 3 days ago, when the last time we had a problem, on the same day we changed the principle of work.


#9

Hi @skamz

Yes, I just saw the ticket. If you need any additional help, just let us know.

thanks,

Rodrigo


#10

I’ve got the exact same error


#11

I’ve also got this issue, backtrace on the core dump reveals the same as zak3

#0 nr_segment_iterate_helper () at nr_segment.c:458
#1 nr_segment_iterate_helper () at nr_segment.c:470
#2 nr_segment_iterate_helper () at nr_segment.c:470
#3 nr_segment_iterate_helper () at nr_segment.c:470

#7 nr_segment_iterate() at nr_segment.c:499

@RyanVeitch


#12

Hi @ageffray

Would you have the logs with the complete dump of your error? You can send it here or even as a private message to me.

thanks,

Rodrigo


#13

Hi @Stephen.Rathbone

Can you share with us the complete dump of this error?

Thanks

Rodrigo


#14

hey @rcorgozinho - we have the same issue on production - here’s a link to download core dump: https://trive.digital/coredump-php.28371.gz


#15

Hi @lotar.mladen

I believe that the file that you have uploaded is invalid or corrupted. Would you mind to create a new one or even send it to me here?

thanks

Rodrigo


#16

How do I send it here, can’t directly upload unfortunately (filetype permissions)?

Besides that, I’ll ask for new core dump from our infrastructure team


#17

@lotar.mladen - I just created a ticket for you - you should hopefully be able to upload your logs there. :slight_smile:


#18

hey, I’m really new on discuss - so not sure where the ticket is - have checked my profile but don’t see it.


#19

Found it, but have another problem :smiley:


#20

Strange! Let me get that reported internally, for now you should be able to reply to that ticket with attachments via email. Could you try that?


#21

Hey @RyanVeitch unfortunately - gmail file attachments have filesize limit I’m hitting - file is ~150MB


#22

Hi @lotar.mladen -

I just DM’d you an attachment key, to use with NR Diagnostics to get information uploaded to the ticket.


#23

Cross-posting this for visibility: good news!

Version 9.8 of the PHP Agent has been released, and includes a fix for these segmentation faults! Let us know in the comments how it works out on the new version.