Обсуждение: pg_top error reporting?

Поиск
Список
Период
Сортировка

pg_top error reporting?

От
hvjunk
Дата:
Good day,

 I’m running into a problem with pg_top inside a LXC container (unprivileged on ProxMox).

1) Seems the pgtop “foundry” directory isn’t working?

http://ptop.projects.pgfoundry.org/

Forbidden
You don't have permission to access / on this server.

2) The error is a segmentation fault, looking at strace and ltrace we see the permission and array check error:

strace:
=======
open("5401/io", O_RDONLY)               = 4
read(4, 0x7ffd4c67c360, 4095)           = -1 EACCES (Permission denied)
close(4)                                = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x2} ---
+++ killed by SIGSEGV +++
Segmentation fault

ltrace:
=======

[pid 25433] open("5401/io", 0, 07332762347)                                                                          =
4
[pid 25433] read(4 <no return ...>
error: maximum array length seems negative
, "5401/io", 4095)                                                                                                   =
-1
[pid 25433] close(4)                                                                                                 =
0
[pid 25433] strchr("5401/io", ':')                                                                                   =
nil
[pid 25433]
strchr("\002\003\004\005\006\a\b\t\n\v\f\r\016\017\020\021\022\023\024\025\026\027\030\031\032\033\034\035\036\037
!"...,'\n' <no return ...> 
[pid 25433] --- SIGSEGV (Segmentation fault) ---
[pid 25433] +++ killed by SIGSEGV +++

Вложения

Re: pg_top error reporting?

От
Adrian Klaver
Дата:
On 12/13/18 4:23 AM, hvjunk wrote:
> Good day,
> 
>   I’m running into a problem with pg_top inside a LXC container (unprivileged on ProxMox).
> 
> 1) Seems the pgtop “foundry” directory isn’t working?
> 
> http://ptop.projects.pgfoundry.org/

Might want to try:

https://github.com/markwkm/pg_top

> 
> Forbidden
> You don't have permission to access / on this server.
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com