After error message at boot time, I now come to run things in a terminal; here is what I get: root@moon_gen_2:~# /etc/init.d/nfs start * Service nfs starting rpc.gssd * ERROR: Some services needed are missing. Run * './nfs broken' for a list of those * services. nfs was not started. * ERROR: nfs failed to start root@moon_gen_2:~# ./nfs broken bash: ./nfs: No such file or directory root@moon_gen_2:~# /etc/init.d/nfs broken rpc.gssd root@moon_gen_2:~# - I complain about the fact the command proposed to be run does not work - I complain about the last command (that seems to be the one that I had to guess) does not help more than the first one. I personally dont need NFS at the moment; I dont need urgent fix. But these messages are not explanatory at all. My box worked fine for 2 years; I updated my system yesterday, and this morning I got this error (not harmfull for me). Things that have been updated yesterday: (last WE, my box was up to date; every saturday, I run esync && emerge -DaNuv world ) net-wireless/bluez-libs-3.24 dev-libs/mpfr-2.3.0_p4 net-dialup/minicom-2.2-r1 net-firewall/iptables-1.4.0 app-admin/eselect-opengl-1.0.6-r1 media-libs/tiff-3.8.2-r3 sys-apps/lshw-02.12.01b sys-apps/file-4.23 dev-libs/boost-1.34.1-r1 dev-python/pygobject-2.14.0-r1 sys-fs/e2fsprogs-1.40.3-r1 net-fs/nfs-utils-1.1.1 gnome-base/libbonobo-2.20.3 sys-kernel/genkernel-3.4.9_pre12 x11-terms/roxterm-1.8.1 dev-util/subversion-1.4.6 net-wireless/bluez-utils-3.24 app-emulation/wine-0.9.52 I give compleet list, cause breakage may not be just in net-fs/nfs-utils-1.1.1 Compile log file names, that will give you previously installed versions and dates ... net-fs:nfs-utils-1.1.0-r1:20071021-154213.log net-fs:nfs-utils-1.1.0-r1:20071113-180023.log net-fs:nfs-utils-1.1.1:20071230-023823.log
Created attachment 139623 [details] /tmp/emerge--info
revdep-rebuild did not find any problem (but it is known to be broken, and may not find all existing problems).
this has been fixed already in baselayout-2: ... Service `nfs' needs non existant service `rpc.gssd' ...
SpanKY ... I esynced yesterday, and here is what I have: root@moon_gen_2:~# emerge -va1 baselayout These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-apps/baselayout-1.12.10-r5 USE="unicode -bootstrap -build -static" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] n Quitting. so, where is baselayout-2 ? since when ? can you prmise me that other users wont meet the same bug as me ? what is `rpc.gssd' ? how do I fix my box ? I execpect emerge -DaNuv to maintain system stability, but, yesterday, it broke my box ... so, breakage came from weekly upgrade, and fix should also come throuh the same way !
baselayout-2 is in the works and in the tree ... we're not wasting time back porting trivial things to baselayout-1 if nfs thinks it needs rpc.gssd but you dont have it installed (because you didnt build nfs-utils with USE=kerberos), you probably have a /etc/exports file that is trying to use security features. post it as an attachment if you want me to look at it. running an unstable ~arch system and thinking a world upgrade will never break is just naive
since when is baselayout-2 in ? I am not that naive; I know it's dangerous; we are somhow the testing people for the Stable world. I do not criticise the fact there is a bug. I report, so that a fix can be establisehd for other users. root@moon_gen_2:~# /etc/init.d/nfs start * Service nfs starting rpc.gssd * ERROR: Some services needed are missing. Run * './nfs broken' for a list of those * services. nfs was not started. * ERROR: nfs failed to start root@moon_gen_2:~# ls /etc/expo* ls: cannot access /etc/expo*: No such file or directory root@moon_gen_2:~# emerge -vp net-fs/nfs-utils These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-fs/nfs-utils-1.1.1 USE="tcpd -kerberos -nonfsv4" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB root@moon_gen_2:~# So, you are right, I have kerberos OFF; but, since I dont have exports at all, never had ... And please, do not tell me I should not run nfs without having exports: it worked that way without any red star at startup for 2 years now. is baselayout-1 deprecated ? shall I upgrade to 2 ? how ?
if you read the ChangeLog, you'd see that baselayout-2 has been around for months for testing. the point is this: the error message you're complaining about has already been fixed. baselayout-1* will continue to have the crappy message forever. yes, running the nfs init.d script when you're not actually planning on exporting anything is a waste of time. there is a bug in the nfs init.d script when /etc/exports does not exist, i'll fix that.
is baselayout-1 deprecated ? shall I upgrade to 2 ? how ... seems I shall mask 1, and unmask 2 ... what trigers many problems that are out of topic. Still, after masking the 1, emerge world did not complain; is it normal for baselayout not to be registered in the world ?
if you simply do: touch /etc/exports /etc/init.d/nfs that should fix things for you yes it's normal for baselayout to not be in "world"
is baselayout-1 deprecated ? shall I upgrade to 2 ? anyway, if those red stars at boot get me on nerves, I think I can remove nfs at startup for now. root@moon_gen_2:~# touch /etc/exports ; /etc/init.d/nfs start * Service nfs starting rpc.gssd * ERROR: Some services needed are missing. Run * './nfs broken' for a list of those * services. nfs was not started. * ERROR: nfs failed to start root@moon_gen_2:~#
you didnt touch the nfs init.d script like i said which means you didnt force regeneration of init.d depcache
