"Failed to issue method call: Unit name autofs is not valid"

This forum is dedicated to advanced help and support :

Ask here your questions about advanced usage of Mageia. For example you may post here all your questions about network and automated installs, complex server configurations, kernel tuning, creating your own Mageia mirrors, and all tasks likely to be touchy even for skilled users.

"Failed to issue method call: Unit name autofs is not valid"

Postby FiableDotBiz » Feb 17th, '13, 17:09

Hello.

I get this error message:
Code: Select all
# service autofs restart
Restarting autofs (via systemctl):  Job failed. See system journal and 'systemctl status' for details.
                                                                                                                                     [FAILED]
# systemctl status autofs
Failed to issue method call: Unit name autofs is not valid.


In my auto.master file, I have the line
Code: Select all
/-   /etc/autofs/auto.nfs

and, in the file auto.nfs:
Code: Select all
/mnt/Dell101   -fstype=nfs4   Dell101:/
/mnt/Dell-OptiPlex-390   -fstype=nfs4   Dell-OptiPlex-390:/
/mnt/Dell-graphist   -fstype=nfs4   Dell-graphist:/
/mnt/Fiable   -fstype=nfs4   Fiable:/

Some of these computers are turned off. Specially one of them which is a notebook. This is precisely the reason why I use autofs: so that they be mounted when they are turned on, while using fstab would only mount the file systems which would be on before the NFS client. Usually this method works. Sometimes, I don't know why, autofs doesn't mount a file system, so I launch "service autofs restart" and usually it works. But quite often I get the above error message, and if I launch it again, I get again the same error message.
Do you have any idea?
FiableDotBiz
 
Posts: 34
Joined: Oct 15th, '12, 10:00

Re: "Failed to issue method call: Unit name autofs is not va

Postby doktor5000 » Feb 17th, '13, 23:45

For systemctl the syntax is a bit different, instead of systemctl status autofs try
Code: Select all
systemctl status autofs.service

and please show the output.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18018
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: "Failed to issue method call: Unit name autofs is not va

Postby FiableDotBiz » Feb 19th, '13, 22:49

Thank you. I forgot that. By the way, the message "See system journal and 'systemctl status' for details." could be more explicit: Where is the journal, exactly what command to launch?
Here is the result:
Code: Select all
# systemctl status autofs.service
autofs.service - Automounts filesystems on demand
          Loaded: loaded (/lib/systemd/system/autofs.service; enabled)
          Active: failed (Result: signal) since Wed, 20 Feb 2013 04:35:33 +0800; 9min ago
         Process: 5413 ExecStart=/usr/sbin/automount ${OPTIONS} --pid-file /run/autofs.pid (code=killed, signal=KILL)
        Main PID: 3681 (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/autofs.service
FiableDotBiz
 
Posts: 34
Joined: Oct 15th, '12, 10:00

Re: "Failed to issue method call: Unit name autofs is not va

Postby alf » Feb 19th, '13, 23:09

FiableDotBiz wrote:Where is the journal, exactly what command to launch?


Code: Select all
journalctl
as root.
for the jounal of a specific day use
Code: Select all
journalctl --since <date>
(where date is in the form of yyyy-mm-dd).
for windows problems reboot; for linux problems be root
alf
 
Posts: 326
Joined: Apr 1st, '11, 23:07
Location: DE Paderborn


Return to Advanced support

Who is online

Users browsing this forum: No registered users and 1 guest