Re: Setting PMWEB Dashboard

On Mon, Oct 24, 2016 at 04:05 am, Frank Ch. Eigler wrote:

> 
> 
> 
> Hi, Chandana -
> 
> That indicates a bug somewhere.
> 
> 

Yes, I think so

> 
> 
> 
> Unfortunately that log doesn't include anything problematic.
> 
> 

I am using -vv, should I increase that ?

> 
> 
> 
> What version of PCP are you running?
> 
> 

$ rpm -qa pcp pcp-webapi

pcp-webapi-3.11.4-1.fc24.x86_64

pcp-3.11.4-1.fc24.x86_64

> 
> 
> 
> Do you have any other observations 
> 
> 

None, other that it died almost hourly so far

> 
> 
> 
> core files? (There was a few months ago a serious memory leak in
> libpcp that could result in pmwebd running OOM after a while, but that
> was obvious from 'top' over time.)
> 
> 

You are correct. 

$ journalctl | grep -E "pmwebd.*oom"

Oct 24 12:30:53 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 24 16:36:28 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 24 21:40:14 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 24 23:04:29 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 25 03:32:07 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=2, oom_score_adj=0

Oct 25 07:04:32 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 25 10:52:50 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 25 11:57:32 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 25 12:54:34 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 25 14:37:54 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 25 15:55:26 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

Oct 25 16:31:30 pmlogf.inf.mel.mmd kernel: pmwebd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), order=0, oom_score_adj=0

> 
> 
> 
> 
> If running under systemd, pmwebd and similar daemons should be
> auto-restarted regardless.
> 
> 
> 

No, the "Restart" option is missing in the config file. I will submit a patch for this, if that is the intended behaviour

$ cat /usr/lib/systemd/system/pmwebd.service

[Unit]

Description=Performance Metrics Web Daemon

Documentation=man:pmwebd(8)

Wants=avahi-daemon.service

After=network.target avahi-daemon.service pmcd.service

 

[Service]

Type=oneshot

ExecStart=/usr/share/pcp/lib/pmwebd start

ExecStop=/usr/share/pcp/lib/pmwebd stop

RemainAfterExit=yes 

 

[Install]

WantedBy=multi-user.target