LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices



Reply
 
Search this Thread
Old 05-31-2011, 01:07 PM   #1
punt
Member
 
Registered: Jun 2001
Distribution: Fedora 21
Posts: 359

Rep: Reputation: 30
Fedora 15 - systemctl failures


Anyone know why these services aren't starting up? It would be awesome if the error messages would actually give some detail...

This all started when I upgraded to Fedora 15. Am hoping *not* to reinstall.

Code:
[root@server system]# systemctl status nfs.service
nfs.service - LSB: Start up the NFS server sevice
          Loaded: loaded (/etc/rc.d/init.d/nfs)
          Active: failed since Tue, 31 May 2011 11:26:47 -0400; 1h 39min ago
         Process: 1004 ExecStart=/etc/rc.d/init.d/nfs start (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/nfs.service
[root@server system]# systemctl status nfslock.service
nfslock.service - LSB: Start up the NFS file locking sevice
          Loaded: loaded (/etc/rc.d/init.d/nfslock)
          Active: failed since Tue, 31 May 2011 11:26:47 -0400; 1h 39min ago
         Process: 1005 ExecStart=/etc/rc.d/init.d/nfslock start (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/nfslock.service
[root@server system]# systemctl status systemd-kmsg-syslogd.service
systemd-kmsg-syslogd.service - Syslog Kernel Log Buffer Bridge
          Loaded: loaded (/lib/systemd/system/systemd-kmsg-syslogd.service)
          Active: failed since Tue, 31 May 2011 11:26:29 -0400; 1h 39min ago
         Process: 404 ExecStart=/lib/systemd/systemd-kmsg-syslogd (code=exited, status=218/CAPABILITIES)
          CGroup: name=systemd:/system/systemd-kmsg-syslogd.service
[root@server system]# systemctl status systemd-logger.service
systemd-logger.service - Stdio Syslog Bridge
          Loaded: loaded (/lib/systemd/system/systemd-logger.service)
          Active: failed since Tue, 31 May 2011 11:26:30 -0400; 1h 39min ago
         Process: 422 ExecStart=/lib/systemd/systemd-logger (code=exited, status=218/CAPABILITIES)
          CGroup: name=systemd:/system/systemd-logger.service
Here are some more details from /var/log/messages:

Code:
May 30 22:04:12 server kernel: <30>systemd[1]: systemd 26 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; fedora)
May 30 22:04:12 server kernel: <28>systemd[1]: /sbin/modprobe failed with error code 1.
May 30 22:04:12 server kernel: <30>systemd[1]: Set hostname to <servername>.
May 30 22:04:12 server kernel: <28>systemd[1]: /usr appears to be on a different file system than /. This is not supported anymore. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information.
May 30 22:04:12 server kernel: <28>systemd[1]: No control group support available, not creating root group.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit proc-sys-fs-binfmt_misc.automount entered failed state.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit dev-hugepages.automount entered failed state.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit sys-kernel-debug.automount entered failed state.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit sys-kernel-security.automount entered failed state.
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to open /dev/autofs: No such file or directory
May 30 22:04:12 server kernel: <27>systemd[1]: Failed to initialize automounter: No such file or directory
May 30 22:04:12 server kernel: <29>systemd[1]: Unit dev-mqueue.automount entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-kmsg-syslogd.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-kmsg-syslogd.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=218
May 30 22:04:12 server kernel: <29>systemd[1]: Unit systemd-logger.service entered failed state.
May 30 22:04:12 server kernel: <28>systemd[1]: systemd-logger.service start request repeated too quickly, refusing to start.
Code:
May 30 22:04:19 server systemd[1]: nfslock.service: control process exited, code=exited status=1
May 30 22:04:19 server systemd[1]: Unit nfslock.service entered failed state.
Code:
May 30 23:35:51 server systemd[1]: nfs.service: control process exited, code=exited status=1
May 30 23:35:52 server systemd[1]: Unit nfs.service entered failed state.
For a manual restart of nfs, here's the error:

Code:
May 31 13:19:25 server kernel: [ 6782.902700] svc: failed to register lockdv1 RPC service (errno 111).
May 31 13:19:25 server kernel: [ 6782.923573] svc: failed to register lockdv1 RPC service (errno 111).
May 31 13:19:25 server systemd[1]: nfs.service: control process exited, code=exited status=1
May 31 13:19:25 server systemd[1]: Unit nfs.service entered failed state.
And here's what it shows on the command line:

Code:
# /etc/rc.d/init.d/nfs start
Starting nfs (via systemctl):  Error: No space left on device
Job failed. See system logs and 'systemctl status' for details.
[FAILED]
uh, what?! I'm definitely NOT out of space on the device.

Last edited by punt; 05-31-2011 at 01:26 PM.
 
Old 05-31-2011, 01:50 PM   #2
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, Ubuntu, SLES, CentOS
Posts: 1,790

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324
@ Reply

Hi there,

Let us know the following information:

1. selinux status. You can check it by typing the following command: sestatus
2. Mount point and space on drive. Use df -h
3. Any exports configured on this server. If yes, Name of exports.
4. Any changes made to the system. Like recent upgrade or installed any packages.
 
Old 05-31-2011, 02:43 PM   #3
punt
Member
 
Registered: Jun 2001
Distribution: Fedora 21
Posts: 359

Original Poster
Rep: Reputation: 30
1. SELinux is off.

2. Mount points. Doesn't help that I use /usr on a separate FS...
Code:
rootfs                 39G  1.2G   37G   4% /
udev                  622M  4.0K  622M   1% /dev
tmpfs                 628M     0  628M   0% /dev/shm
/dev/sda3              39G  1.2G   37G   4% /
tmpfs                 628M  612K  627M   1% /run
tmpfs                 628M     0  628M   0% /sys/fs/cgroup
tmpfs                 628M     0  628M   0% /media
/dev/sdb1             147G  102G   38G  73% /backup
/dev/sda1             194M   77M  107M  42% /boot
/dev/sda2              39G  1.4G   36G   4% /var
tmpfs                 628M  612K  627M   1% /var/run
tmpfs                 628M  612K  627M   1% /var/lock
/dev/sdb1             147G  102G   38G  73% /var/www/html
/dev/sda6              39G  2.2G   35G   6% /home
/dev/sda7              39G  5.3G   32G  15% /usr
3. No idea what you mean in terms of exports.

4. Recent upgrade from Fedora 14 to Fedora 15 caused these headaches.

I think I should do a clean install of Fedora 15, hmm? I *really* didn't want to, but I'm left with little choice. So much stuff is wrong with this upgrade.
 
Old 05-31-2011, 03:07 PM   #4
T3RM1NVT0R
Senior Member
 
Registered: Dec 2010
Location: Internet
Distribution: Linux Mint, Ubuntu, SLES, CentOS
Posts: 1,790

Rep: Reputation: 324Reputation: 324Reputation: 324Reputation: 324
@ Reply

I think I have seen this issue before.

Try enabling selinux:

1. Edit /etc/selinux/config and edit as follows:

instead of using

SELINUX=disabled

Make it

SELINUX=permissive

save the file and reboot the system.

Remember it might take sometime for the system to come backup as selinux will be performing labeling on file system.

Once up try to start the services which you were trying before.

And yes by exports I mean did you configure any NFS shares on this server. You can find them by doing: cat /etc/exports
 
Old 05-31-2011, 03:59 PM   #5
punt
Member
 
Registered: Jun 2001
Distribution: Fedora 21
Posts: 359

Original Poster
Rep: Reputation: 30
nothing in exports. The only shares I have are cifs based and that's another issue entirely.

I'll see what SELinux does if anything but probably will look at a clean Fedora 15 install...
 
Old 05-31-2011, 04:01 PM   #6
punt
Member
 
Registered: Jun 2001
Distribution: Fedora 21
Posts: 359

Original Poster
Rep: Reputation: 30
Yeah, now I have no networking... at least no remote networking, and that's the only way I can interface with this computer. Time for a fresh install!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgraded to Fedora 15 now OpenVPN doesn't work ... systemctl issue? Hanse42 Linux - Newbie 10 05-29-2011 11:32 AM
Shut down failures GRS63 Linux - Software 1 03-14-2009 01:45 AM
Failures installing Fedora Core 5 on HP Lxr8500 Lenux78 Fedora - Installation 4 11-28-2006 09:35 AM
CD burning failures stevsom Linux - Software 1 07-26-2005 06:06 PM
slapt-get failures BroX Slackware 5 08-19-2004 03:19 AM


All times are GMT -5. The time now is 10:28 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration