| Summary: | The mmc-agent package installation (dnf and rpm) don't work properly | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Théo PORTIER <portier> |
| Component: | RPM Packages | Assignee: | Nicolas Lécureuil <mageia> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://www.dropbox.com/sh/d7bo5c4ux6iyito/AADRaSddtp6t-O_51C5tXbrka?dl=0 | ||
| Whiteboard: | |||
| Source RPM: | mmc-core-3.1.90-9.mg6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Théo PORTIER
2019-01-03 12:12:23 CET
Assigning to the registered maintainer. CC:
(none) =>
marja11 hi, can you provide the logs ? systemctl start mmc-agent.service and journalctl -u mmc-agent.service btw, can you try the packages from updates_testing ? ( mmc-agent 4.5.1 ( instead of released 3.1.90 ) in updates_testing we have: mmc-core-4.5-1.mga6 and pulse2-4.5-1.mga6 ( this is the name of the src.rpms ). The rpms created by them are: mmc-agent-4.5-1.mga6.x86_64.rpm mmc-web-backuppc-4.5-1.mga6.x86_64.rpm mmc-web-base-4.5-1.mga6.x86_64.rpm mmc-web-dashboard-4.5-1.mga6.x86_64.rpm mmc-web-dyngroup-4.5-1.mga6.x86_64.rpm mmc-web-glpi-4.5-1.mga6.x86_64.rpm mmc-web-imaging-4.5-1.mga6.x86_64.rpm mmc-web-inventory-4.5-1.mga6.x86_64.rpm mmc-web-kiosk-4.5-1.mga6.x86_64.rpm mmc-web-msc-4.5-1.mga6.x86_64.rpm mmc-web-pkgs-4.5-1.mga6.x86_64.rpm mmc-web-ppolicy-4.5-1.mga6.x86_64.rpm mmc-web-pulse2-4.5-1.mga6.x86_64.rpm mmc-web-report-4.5-1.mga6.x86_64.rpm mmc-web-services-4.5-1.mga6.x86_64.rpm mmc-web-support-4.5-1.mga6.x86_64.rpm pulse2-4.5-1.mga6.x86_64.rpm pulse2-common-4.5-1.mga6.x86_64.rpm pulse2-dlp-server-4.5-1.mga6.x86_64.rpm pulse2-inventory-server-4.5-1.mga6.x86_64.rpm pulse2-launchers-4.5-1.mga6.x86_64.rpm pulse2-package-server-4.5-1.mga6.x86_64.rpm pulse2-scheduler-4.5-1.mga6.x86_64.rpm pulse2-uuid-resolver-4.5-1.mga6.x86_64.rpm python-mmc-backuppc-4.5-1.mga6.x86_64.rpm python-mmc-base-4.5-1.mga6.x86_64.rpm python-mmc-connection-manager-4.5-1.mga6.x86_64.rpm python-mmc-core-4.5-1.mga6.x86_64.rpm python-mmc-dashboard-4.5-1.mga6.x86_64.rpm python-mmc-database-4.5-1.mga6.x86_64.rpm python-mmc-dyngroup-4.5-1.mga6.x86_64.rpm python-mmc-glpi-4.5-1.mga6.x86_64.rpm python-mmc-guacamole-4.5-1.mga6.x86_64.rpm python-mmc-imaging-4.5-1.mga6.x86_64.rpm python-mmc-inventory-4.5-1.mga6.x86_64.rpm python-mmc-kiosk-4.5-1.mga6.x86_64.rpm python-mmc-msc-4.5-1.mga6.x86_64.rpm python-mmc-pkgs-4.5-1.mga6.x86_64.rpm python-mmc-plugins-tools-4.5-1.mga6.x86_64.rpm python-mmc-ppolicy-4.5-1.mga6.x86_64.rpm python-mmc-pulse2-4.5-1.mga6.x86_64.rpm python-mmc-report-4.5-1.mga6.x86_64.rpm python-mmc-services-4.5-1.mga6.x86_64.rpm python-mmc-support-4.5-1.mga6.x86_64.rpm python-mmc-xmppmaster-4.5-1.mga6.x86_64.rpm python-pulse2-common-4.5-1.mga6.x86_64.rpm python-pulse2-common-database-4.5-1.mga6.x86_64.rpm python-pulse2-common-database-dyngroup-4.5-1.mga6.x86_64.rpm python-pulse2-common-database-imaging-4.5-1.mga6.x86_64.rpm python-pulse2-common-database-inventory-4.5-1.mga6.x86_64.rpm python-pulse2-common-database-msc-4.5-1.mga6.x86_64.rpm BTW can you try to start mmc-agent manually ? ( out of systemd by using mmc-agent -d ) (In reply to Nicolas Lécureuil from comment #3) > btw, can you try the packages from updates_testing ? ( mmc-agent 4.5.1 ( > instead of released 3.1.90 ) I will try the updated package (mmc-agent 4.5.1). i will tell you if it's work as soon as possible. (In reply to Nicolas Lécureuil from comment #5) > BTW can you try to start mmc-agent manually ? ( out of systemd by using > mmc-agent -d ) mmc-agent -d don't work, mageia don't know the command. > (In reply to Nicolas Lécureuil from comment #5)
> > BTW can you try to start mmc-agent manually ? ( out of systemd by using
> > mmc-agent -d )
>
> mmc-agent -d don't work, mageia don't know the command.
mageia can't know or ignore this command as this is provided by mmc-agent rpm.
/usr/sbin/mmc-agent is the binary used.
You must be root to use this command ( as it is installed in /usr/sbin and normal user does not have /usr/sbin in its path ).
(In reply to Nicolas Lécureuil from comment #7) > > (In reply to Nicolas Lécureuil from comment #5) > > > BTW can you try to start mmc-agent manually ? ( out of systemd by using > > > mmc-agent -d ) > > > > mmc-agent -d don't work, mageia don't know the command. > > mageia can't know or ignore this command as this is provided by mmc-agent > rpm. > > /usr/sbin/mmc-agent is the binary used. > > You must be root to use this command ( as it is installed in /usr/sbin and > normal user does not have /usr/sbin in its path ). With the new package, Mageia Know the command. The agent is working, but I have to add the "base.ini.local" file in /etc/mmc/plugins and I had to install the package "python-service-identity" who are not a dependence of the mmc-agent package. and I'm still not able to connect to the interface. The interface is saying that my agent is not correctly configured. I guess the problem for the agent about the fact he doesn't be correctly configured is that i don't have an xmpp server ? if it's true, can i get the package you use for the server ? mageia 6 is no longer supported. mmc-core will be added back in mageia when ported completly to python3 Status:
NEW =>
RESOLVED |