During 12.3 boot, my NFS clients fail to mount and spamassassin fails to load. I receive the errors:
Dependency failed for Remote File Systems.
Dependency failed for Daemonized version of spamassassin
Yet, after boot, I can go into Yast and start my remote shares by just entering the NFS client dialog and hitting OK and I can start the spamassassin daemon through the system services (runlevel) model with absolutely no problem. I have even checked the dependencies for these using Software management and it shows no problems. Since there are no dependency issues, why are these services failing to start during boot with a dependency error?
I have no clue and I’d love get this fixed. Thanks.
I had seen a similar problem with Samba until I made the following change. Don’t know if it will help you or not. See this portion from my Samba blog:
NMB Failing to Start on Reboot:
If, after you restart openSUSE, you notice that no one can find your PC on the network through your Samba share, it may be due to the fact that nmb is not starting. Its possible this is due to a failing of timing by systemd on bootup of your PC. One way to handle that issue to to allow it more time to find your network interfaces.
This is a YaST / System / /etc/sysconfig Editor Setting at:
/ etc / sysconfig / Network / General /** WAIT_FOR_INTERFACES** Default is 30, but I suggest you select 60 seconds instead and press OK and allow this change to be saved. It will be used then on your next openSUSE PC restart.
You get errors from spamassassin an email spam scanner, that its not working from systemd and you can’t get a NFS mount to work at bootup. Are these related problems? You show what looks like a systemd service file trying to run a mount command. Did you write this service file yourself? Based on the command I see, it can’t be loaded directly from your fstab file, you could add this same mount command into your boot.local bash script or activate the after.local using my guide here: systemd and using the after.local script in openSUSE 12.1 - Blogs - openSUSE Forums
I’m not actually doing anything myself. These are from files that were created by the installer when I updated from 12.2 to 12.3. The messages I receive in boot.log and during the boot process are
[1;32m OK [0m] Reached target Remote File Systems (Pre).
Mounting /opt/Cindy/usr...
Mounting /opt/Cindy/home...
Mounting /opt/Cindy/opt...
[1;31mFAILED[0m] Failed to mount /opt/Cindy/usr.
See 'systemctl status opt-Cindy-usr.mount' for details.
[1;33mDEPEND[0m] Dependency failed for Remote File Systems.
[1;33mDEPEND[0m] Dependency failed for Daemonized version of spamassassin.
[1;31mFAILED[0m] Failed to mount /opt/Cindy/home.
See 'systemctl status opt-Cindy-home.mount' for details.
......
As you can see, the log suggests running the systemctl status command which I did and which is the output I posted above. Also, I get a dependency failed notice for remote file systems followed immediately by a dependency failed notice for spamassassin. The line in fstab was written by Yast and is quite plain vanilla: 10.2.1.5:/usr /opt/Cindy/usr nfs defaults 0 0. The same line worked fine in the 12.2 fstab. It seems to me that the dependency failed for spamassassin, coming immediately after the dependency failed for remote file sytems in the middle of mount attempts for 3 different directories when neither nfs nor spamassassin have dependency problems suggests some relationship. I would think that if the problem were that the remote file systems themselves couldn’t be mounted, if I got another error message, it wouldn’t be a dependency error.
So let us see your fstab file (terminal command: cat /etc/fstab) to see how these mounts are being made there. Place all such text into a code # field.
So, if this works as a manual mount command and does not work in your fstab file, the network connection is not up yet when the command is being run. This is why I suggested you consider adding in a mount command to the boot.local or after.local files per my blog here: systemd and using the after.local script in openSUSE 12.1 - Blogs - openSUSE Forums
Now you have got to try some of my suggestions. Also, I wonder why you feel the need to make a permanent mount over the network? I use Samba myself in a mixed PC setup, and I use dolphin browse commands to make a connection only when needed. Have a look here: S.A.C.T. - Samba Automated Configuration Tool - Version 1.03 - Blogs - openSUSE Forums
Such constant mounts means all file manager actions are reading through these network connections and depending on the network speed can slow your system down. Now you may be moving files back and forth on every other command and in that case, a mount as you are wanting to use can make sense. But if you only interact with each mount a time or two per session, an on-fly-the-fly type connection might make more sense.
Thank you so much. I removed the remote directories from fstab and got rid of the dependency errors, including the spamassassin daemon, which now loads without problems. I didn’t quite understand what you were getting at, but after playing around a bit it is clear – a learning experience.
I take your point about constant mounts, and you are absolutely right. I only use the remote directories infrequently. It makes a lot more sense to have a couple of simple bash scripts to mount them when I want them and unmount them afterwards. Again thanks a lot - I appreciate all your help.