[MacPorts] #30873: net/mrtg @2.17.2 rateup Lion crash - WARNING: rateup died from Signal 11

MacPorts noreply at macports.org
Thu Aug 18 21:21:37 PDT 2011


#30873: net/mrtg @2.17.2 rateup Lion crash - WARNING: rateup died from Signal 11
--------------------------------+-------------------------------------------
 Reporter:  randalla@…          |       Owner:  ricci@…           
     Type:  defect              |      Status:  new               
 Priority:  Normal              |   Milestone:                    
Component:  ports               |     Version:  2.0.1             
 Keywords:                      |        Port:  mrtg              
--------------------------------+-------------------------------------------
Changes (by macsforever2000@…):

 * cc: jberry@… (added)
  * owner:  macports-tickets@… => ricci@…
  * port:  net/mrtg => mrtg


Old description:

> mrtg in 10.7.1 is failing every run with the message:
>
> 2011-08-18 20:59:34: ERROR: Skipping webupdates because rateup did not
> return anything sensible
> 2011-08-18 20:59:34: WARNING: rateup died from Signal 11
>  with Exit Value 0 when doing router 'wlan0'
>  Signal was 11, Returncode was 0
>
> A crash report is being produced for /opt/local/bin/rateup, such as this:
>
> Process:         running job [19692]
> Path:            /opt/local/bin/rateup
> Identifier:      running job
> Version:         ??? (???)
> Code Type:       X86-64 (Native)
> Parent Process:  running job [19666]
>
> Date/Time:       2011-08-18 21:05:02.090 -0700
> OS Version:      Mac OS X 10.7.1 (11B26)
> Report Version:  9
>
> Crashed Thread:  0  Dispatch queue: com.apple.main-thread
>
> Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
> Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffd1052e068
>
> VM Regions Near 0xfffffffd1052e068:
> --> shared memory          00007fffffe00000-00007fffffe02000 [    8K]
> r-x/r-x SM=SHM
>

> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
> 0   rateup                              0x000000010252352d image + 3341
> 1   rateup                              0x0000000102529721 main + 3889
> 2   rateup                              0x00000001025221c4 start + 52
>
> Thread 0 crashed with X86 Thread State (64-bit):
>   rax: 0xffffffff81c005c9  rbx: 0x0000000000000000  rcx:
> 0x0000000081c005c9  rdx: 0x0000000000000000
>   rdi: 0x000000010252b220  rsi: 0xfffffffe8540115b  rbp:
> 0x00007fff62120ad0  rsp: 0x00007fff6211dfc0
>    r8: 0xaaaaaaaaaaaaaaab   r9: 0x000000000000000a  r10:
> 0x0000000000010000  r11: 0x00007fff892058f0
>   r12: 0xfffffffff88ca6c0  r13: 0x0000000000043f54  r14:
> 0x000000010252a723  r15: 0x000000010252a723
>   rip: 0x000000010252352d  rfl: 0x0000000000010213  cr2:
> 0xfffffffd1052e068
> Logical CPU: 1
>

>

> The only thing I can think of is that I am using the +no_x11 keyword,
> which affected gd, which mrtg does use.

New description:

 mrtg in 10.7.1 is failing every run with the message:

 {{{
 2011-08-18 20:59:34: ERROR: Skipping webupdates because rateup did not
 return anything sensible
 2011-08-18 20:59:34: WARNING: rateup died from Signal 11
  with Exit Value 0 when doing router 'wlan0'
  Signal was 11, Returncode was 0
 }}}

 A crash report is being produced for /opt/local/bin/rateup, such as this:

 {{{
 Process:         running job [19692]
 Path:            /opt/local/bin/rateup
 Identifier:      running job
 Version:         ??? (???)
 Code Type:       X86-64 (Native)
 Parent Process:  running job [19666]

 Date/Time:       2011-08-18 21:05:02.090 -0700
 OS Version:      Mac OS X 10.7.1 (11B26)
 Report Version:  9

 Crashed Thread:  0  Dispatch queue: com.apple.main-thread

 Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
 Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffd1052e068

 VM Regions Near 0xfffffffd1052e068:
 --> shared memory          00007fffffe00000-00007fffffe02000 [    8K]
 r-x/r-x SM=SHM


 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
 0   rateup                              0x000000010252352d image + 3341
 1   rateup                              0x0000000102529721 main + 3889
 2   rateup                              0x00000001025221c4 start + 52

 Thread 0 crashed with X86 Thread State (64-bit):
   rax: 0xffffffff81c005c9  rbx: 0x0000000000000000  rcx:
 0x0000000081c005c9  rdx: 0x0000000000000000
   rdi: 0x000000010252b220  rsi: 0xfffffffe8540115b  rbp:
 0x00007fff62120ad0  rsp: 0x00007fff6211dfc0
    r8: 0xaaaaaaaaaaaaaaab   r9: 0x000000000000000a  r10:
 0x0000000000010000  r11: 0x00007fff892058f0
   r12: 0xfffffffff88ca6c0  r13: 0x0000000000043f54  r14:
 0x000000010252a723  r15: 0x000000010252a723
   rip: 0x000000010252352d  rfl: 0x0000000000010213  cr2:
 0xfffffffd1052e068
 Logical CPU: 1
 }}}

 The only thing I can think of is that I am using the +no_x11 keyword,
 which affected gd, which mrtg does use.

--

-- 
Ticket URL: <https://trac.macports.org/ticket/30873#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list