OpenSuSE 11.4 Beta 5 NFS?

Hi–

I was using OpenSuSE 11.4 Beta 3 and decided to upgrade to Beta 5. The process worked more or less without a hitch, but my NFS mounts no longer works:

sudo /etc/init.d/nfs restart

Shutting down NFS client services: done
Starting NFS client services: sm-notify idmapd/usr/sbin/rpc.idmapd: symbol lookup error: /usr/sbin/rpc.idmapd: undefined symbol: conf_init
startproc: exit status of parent of /usr/sbin/rpc.idmapd: 127
failed

/usr/sbin/rpc.idmapd

/usr/sbin/rpc.idmapd: symbol lookup error: /usr/sbin/rpc.idmapd: undefined symbol: conf_init

I made sure the host is up and running to the latest and greatest versions and for kicks and giggles, did re-install the RPMs. This machine was upgraded via the Network option, if that makes any difference.

A few questions:

a). which rpm/DSO provides conf_init, conf_get_num, and conf_get_str so that I could get up and running again?
b). has this happened to anyone else?

===

rpm -qa | grep nfs

yast2-nfs-client-2.19.3-3.2.noarch
nfsidmap-0.23-10.1.x86_64
limal-nfs-server-perl-1.6.1-8.1.x86_64
limal-nfs-server-1.6.1-8.1.x86_64
yast2-nfs-common-2.18.1-7.4.noarch
nfs-client-1.2.3-3.1.x86_64

Thanks!

eyt*

In /etc/nfsmount, replace “#Defaultvers=4” by “Defaultvers=3”, IIRC that should do the trick. Of course you have to restart nfs

I have the same problem on M4-M5, and its impossibly to start nfs service manualy as well, the only repons I get is “service is not running”.
I tried with the solution “#Defaultvers=4” by “Defaultvers=3” and it dident do anything to help up the problem.
Otherwise M5 is running smothly on my testcomputer.

Hi @jodot, welcome here,

Are all (both) of you aware of the status of the Milestones? : experimental, just for testing, not for production use?

Of course I’m aware of the beta status! But there is nothing wrong to share information to others… Or do mean that the post shouldent be in the forum?
**
Information is … King!**

That’s not what I meant, please let me explain: we meet a lot of new users that go for “latest” which is supposed to be “greatest”, regardless the download’s development status. If not already in trouble during install, video card driver install, then during post install missing repos are being reported. Hence my warning question. I’d rather pop it and have a reply like yours, then doing so in the 30th post in a thread to find out the OP missed that info, and would rather have installed the latest stable release.

And … of course there’s nothing wrong with sharing this, IMO it’s the best you can do, no matter whether you’ve solved the issue or not. If you have the spare time, please post, this community driven distro needs you !!! It’s what keeps us alive.

Once again a warm welcome, enjoy

Yes, I am very well aware of the status of the builds and my question was more to see if you guys were aware of the problem or if the problem was unique to me and whether I should be filing a bug. Apologies if it looked somehow otherwise.

eyt*

No problem at all. Point is that the forums are for discussions/debate/getting+giving help etc. The forums are not a bug tracker. If you think you found a bug, report it through the appropriate channels, so that it will get to the devs. We here are just the forums, not some devs reading the forums to see what our users want.

Downloaded build 687(KDE) today from factory and NFS client is working in that build.

Regards

For the record, the buggy package was nfsidmap.rpm, with these changes:


Sat Dec 18 01:25:55 UTC 2010 - cristian.rodriguez@opensuse.org

  • revert the last change that exported only public symbols
    breaks loadable modules.

Sat Dec 11 03:52:09 UTC 2010 - cristian.rodriguez@opensuse.org

  • libnfsidmap: export only public symbols nfs4_*, in particular
    this avoids exporting strlcpy to calling applications…
  • openldap2-devel is not required in -devel package