Bug 1222815 - Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer
Summary: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: David Disseldorp
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-15 09:34 UTC by Dirk Mueller
Modified: 2024-07-16 06:00 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
ddiss: needinfo? (pdostal)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Mueller 2024-04-15 09:34:30 UTC
just installing pcp and pmlogger leads to:

# systemctl start pmlogger
Failed to start pmlogger.service: Unit pmlogger_daily.timer not found.


this unit is currently in pcp-zeroconf. however pmlogger.service is in pcp (main package). 

if zeroconf is supposed to be optional, then the pmlogger_daily.timer dependency is supposed to be made optional. otherwise the timer needs to be moved into the main package (like it appears to be upstream)
Comment 1 Pavel Dostál 2024-05-06 10:17:23 UTC
I just run into probably related issue:
> May 06 12:02:35 larry.prg2 systemd[1]: Starting Performance Metrics Archive Logger...
> May 06 12:02:35 larry.prg2 rc[6097]: /etc/pcp/pmlogger/rc: line 153: /var/lib/pcp/tmp/pmlogger_rc.P906AnP16/tmp: Permission denied
> May 06 12:02:35 larry.prg2 rc[6153]: /etc/pcp/pmlogger/rc: line 92: /var/lib/pcp/tmp/pmlogger_rc_start.tmWf9hnGa/pmcheck.out: Permission denied
> May 06 12:02:35 larry.prg2 systemd[1]: pmlogger.service: Main process exited, code=exited, status=1/FAILURE
> May 06 12:02:35 larry.prg2 systemd[1]: pmlogger.service: Failed with result 'exit-code'.
> May 06 12:02:35 larry.prg2 systemd[1]: Failed to start Performance Metrics Archive Logger.
Comment 2 David Disseldorp 2024-05-21 05:51:17 UTC
Thanks for the reports Dirk and Pavel...

(In reply to Pavel Dostál from comment #1)
> I just run into probably related issue:
> > May 06 12:02:35 larry.prg2 systemd[1]: Starting Performance Metrics Archive Logger...
> > May 06 12:02:35 larry.prg2 rc[6097]: /etc/pcp/pmlogger/rc: line 153: /var/lib/pcp/tmp/pmlogger_rc.P906AnP16/tmp: Permission denied
> > May 06 12:02:35 larry.prg2 rc[6153]: /etc/pcp/pmlogger/rc: line 92: /var/lib/pcp/tmp/pmlogger_rc_start.tmWf9hnGa/pmcheck.out: Permission denied
> > May 06 12:02:35 larry.prg2 systemd[1]: pmlogger.service: Main process exited, code=exited, status=1/FAILURE
> > May 06 12:02:35 larry.prg2 systemd[1]: pmlogger.service: Failed with result 'exit-code'.
> > May 06 12:02:35 larry.prg2 systemd[1]: Failed to start Performance Metrics Archive Logger.

This looks different to Dirk's report:

 86 _start_pmcheck()
 87 {
 88     bgstatus=0
 89     bgtmp=`mktemp -d "$PCP_TMPFILE_DIR/pmlogger_rc_start.XXXXXXXXX"` || exit 1     
 90     trap "rm -rf $tmp $bgtmp; exit \$bgstatus" 0 1 2 3 15
 91     
 92     pmlogger_check --quick $VFLAG $PMLOGGER_CHECK_PARAMS >$bgtmp/pmcheck.out 2>$bgtmp/pmcheck  

The $bgtmp directory is successfully created immediately prior to the writes at line#92, so I'm a little confused - do you have apparmor or selinux enabled?