damagedrepomd.xml

Mohamad.1996

Mohamad.1996

Member
Joined
Oct 5, 2019
Messages
40
Reaction score
2
Credits
242
Hi Friends I had ran into problem for a long time, I'm using Centos7 in Vmware and I can't do yum update or for example Install yum collectd but always receive damagedrepomd.xml
before that I was receiving no more mirrors!!
even I reverted snapshot I always should assign ip to my centos 7 by DHCP
I've done it but I Can't ping google....Why??
 


Are you retrieving your updates from centos mirrors or from your local satellite server? Can you reach your network gateway?
 
Mohamad.1996 said:
I can't ping google but yahoo and another websites I can
Click to expand...
No idea, I don't know your network setup. Can you show the output of:
Code: 
yum repolist
yum install collectd
yum install screen
 
Last edited:
[root@localhost shahin]# yum install collectd
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirror.centos.jt.iq
* extras: kozyatagi.mirror.guzel.net.tr
* updates: kozyatagi.mirror.guzel.net.tr
No package collectd available.
Error: Nothing to do
.......................................................................................................................................................


What does it mean??
 
collectd is a package from EPEL. You will need to install EPEL to install collectd
Code: 
yum install epel-release
yum install collectd
EPEL is a third party repository you may also want to have a look at the yum plugin protectbase.
 
ul 24 11:13:09 localhost.localdomain systemd[1]: Unit collectd.service entered failed state.
Jul 24 11:13:09 localhost.localdomain systemd[1]: collectd.service failed.
Jul 24 11:13:09 localhost.localdomain systemd[1]: collectd.service holdoff time over, scheduling restart.
Jul 24 11:13:09 localhost.localdomain systemd[1]: Stopped Collectd statistics daemon.
-- Subject: Unit collectd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit collectd.service has finished shutting down.
Jul 24 11:13:09 localhost.localdomain systemd[1]: start request repeated too quickly for collectd.service
Jul 24 11:13:09 localhost.localdomain systemd[1]: Failed to start Collectd statistics daemon.
-- Subject: Unit collectd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit collectd.service has failed.
--
-- The result is failed.
Jul 24 11:13:09 localhost.localdomain systemd[1]: Unit collectd.service entered failed state.
Jul 24 11:13:09 localhost.localdomain systemd[1]: collectd.service failed.
...................................................................................................................................................................................................





I can't start it!!! Why? What's the matter?
 
How did you start collectd? Can you show the output of:
Code: 
systemctl status collectd
journalctl -u collectd | tail -n 15
 
That's the screenshot the second one
 

Attachments

  • Screenshot (9).png
    Screenshot (9).png
    239.3 KB · Views: 401
If you're going to attach a file could you please attach at plain text file, and with the screenshot I can't read the full output.
 
The most important problem is ((Failed to start Collectd statistics daemon ))
when I restart it
 
Mohamad.1996 said:
The most important problem is ((Failed to start Collectd statistics daemon ))
when I restart it
Click to expand...
I want to see the output of the two commands I mentioned earlier or else I won't be able to see much. I can't just guess why collectd is failing to start.

(Failed to start Collectd statistics daemon) That just tells you it failed to start not why it failed to start.
 
[root@localhost shahin]# systemctl status collectd
● collectd.service - Collectd statistics daemon
Loaded: loaded (/usr/lib/systemd/system/collectd.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Docs: man:collectd(1)
man:collectd.conf(5)
[root@localhost shahin]# systemctl start collectd
Job for collectd.service failed because the control process exited with error code. See "systemctl status collectd.service" and "journalctl -xe" for details.
-----------------------------------------------------------------------------------------------------------
[root@localhost shahin]# journalctl -xe
Jul 24 11:57:54 localhost.localdomain collectd[3152]: Read the logs for details.
Jul 24 11:57:54 localhost.localdomain systemd[1]: collectd.service: main process exited, code=exited, status=1/FAILURE
Jul 24 11:57:54 localhost.localdomain systemd[1]: Failed to start Collectd statistics daemon.
-- Subject: Unit collectd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit collectd.service has failed.
--
-- The result is failed.
Jul 24 11:57:54 localhost.localdomain systemd[1]: Unit collectd.service entered failed state.
Jul 24 11:57:54 localhost.localdomain systemd[1]: collectd.service failed.
Jul 24 11:57:55 localhost.localdomain systemd[1]: collectd.service holdoff time over, scheduling restart.
Jul 24 11:57:55 localhost.localdomain systemd[1]: Stopped Collectd statistics daemon.
-- Subject: Unit collectd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit collectd.service has finished shutting down.
Jul 24 11:57:55 localhost.localdomain systemd[1]: start request repeated too quickly for collectd.service
Jul 24 11:57:55 localhost.localdomain systemd[1]: Failed to start Collectd statistics daemon.
-- Subject: Unit collectd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit collectd.service has failed.
--
-- The result is failed.
Jul 24 11:57:55 localhost.localdomain systemd[1]: Unit collectd.service entered failed state.
Jul 24 11:57:55 localhost.localdomain systemd[1]: collectd.service failed.
--------------------------------------------------------------------------------------------------
[root@localhost shahin]# journalctl -u collectd | tail -n 15
Jul 24 11:57:54 localhost.localdomain collectd[3152]: plugin_load: plugin "rrdtool" successfully loaded.
Jul 24 11:57:54 localhost.localdomain collectd[3152]: plugin_load: Could not find plugin "smart" in /usr/lib64/collectd
Jul 24 11:57:54 localhost.localdomain collectd[3152]: plugin_load: plugin "statsd" successfully loaded.
Jul 24 11:57:54 localhost.localdomain collectd[3152]: Error: Reading the config file failed!
Jul 24 11:57:54 localhost.localdomain collectd[3152]: Read the logs for details.
Jul 24 11:57:54 localhost.localdomain systemd[1]: collectd.service: main process exited, code=exited, status=1/FAILURE
Jul 24 11:57:54 localhost.localdomain systemd[1]: Failed to start Collectd statistics daemon.
Jul 24 11:57:54 localhost.localdomain systemd[1]: Unit collectd.service entered failed state.
Jul 24 11:57:54 localhost.localdomain systemd[1]: collectd.service failed.
Jul 24 11:57:55 localhost.localdomain systemd[1]: collectd.service holdoff time over, scheduling restart.
Jul 24 11:57:55 localhost.localdomain systemd[1]: Stopped Collectd statistics daemon.
Jul 24 11:57:55 localhost.localdomain systemd[1]: start request repeated too quickly for collectd.service
Jul 24 11:57:55 localhost.localdomain systemd[1]: Failed to start Collectd statistics daemon.
Jul 24 11:57:55 localhost.localdomain systemd[1]: Unit collectd.service entered failed state.
Jul 24 11:57:55 localhost.localdomain systemd[1]: collectd.service failed.
 
It can't read the configuration file. Does it exist, can you check by doing:
Code: 
ls -l /etc/collectd.conf
 rpm -ql collectd | grep conf
 
Last edited:
[root@localhost shahin]# ls -l /etc/collectd.conf
-rw-r--r--. 1 root root 42083 Jul 24 11:22 /etc/collectd.conf
 
[root@localhost shahin]# rpm -ql collectd | grep conf
/etc/collectd.conf
/usr/lib64/pkgconfig/libcollectdclient.pc
/usr/share/man/man5/collectd.conf.5.gz
 
Weird your configuration file does exist. Could try turning temporarily turning selinux off.
Code: 
setenforce 0
Then try starting collectd again:
Code: 
systemctl start collectd
What happens then?
 
[root@localhost shahin]# setenforce 0
[root@localhost shahin]# systemctl start collectd
Job for collectd.service failed because the control process exited with error code. See "systemctl status collectd.service" and "journalctl -xe" for details.
 
You must log in or register to reply here.

Members online

Total: 452 (members: 5, guests: 447)

Latest posts

Top