Ask Your Question
0

fedora 19 systemctl failed to issue method call no such file or directory

asked 2013-12-06 01:27:01 -0500

Tedd gravatar image

Hello,

The Error Message:

systemctl -f disable exim.service

Failed to issue method call: No such file or directory

or

chkconfig exim.service off

error reading information on service exim.service: No such file or directory

The Problem:

Fifty percent of the time now, when I boot into fedora, it hangs before it gets to the login screen, at the starting sendmail service. I have to hard-power off my computer and try it again. The second attempt usually works.

There are 17 services, sockets, and targets that error or fail that I do not need to load at start up and want to stop.

System Background/Background Information:

I have been using fedora 16 for years and just did a fresh upgrade to fedora 19. I installed and ran all the updates. I have not installed any additional software on it other than Google Chrome.

I tried to install KDE, but half way through the install, it crashed. So I gave up and stuck with Gnome. When I run Software, it says that no KDE has been installed other than: A helper that makes system-config-printer use PolicyKit, Firewall configuration application, and Helps troubleshoot SELinux problems. I have left these alone.

I have read 20+ articles on the web and so far, I cannot find a solution to this problem. Surely there is a cure for this outside simply re-installing the OS!

Thank You!

edit retag flag offensive close merge delete

Comments

systemctl disable sendmail.service returns error: Failed to issue method call: No such file or directory. I cannot use the systemctl command at all, to disable any services at all without it returning that exact same error message. All I want to do is go through and disable the services that are in the error failed state in hopes that this will stop this pesky bootup problem. However, the only way I know how to do this is with systemctl and systemctl seems to not allow me to do this, and I am doing it as su and as my normal sysadmin account and neither work.

Tedd gravatar imageTedd ( 2013-12-08 23:11:03 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2013-12-07 07:46:14 -0500

jmt gravatar image

If sendmail seems to be the culprit, why don't you deactivate that.

systemctl disable sendmail.service

Sendmail is know to cause problems if not configured properly.

After that you can figure out whether you can start sendmail after booting up your system or whether you need sendmail at all.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2013-12-06 01:27:01 -0500

Seen: 3,751 times

Last updated: Dec 07 '13