[gentoo-user] emerge stalls - what to do ?
Greetings, gentoo-users, I see a problem with emerge on my notebook. Whenever I try to emerge something, it starts off like: # emerge -1 libsexy Calculating dependencies... done! Verifying ebuild Manifests... Emerging (1 of 1) x11-libs/libsexy-0.1.11 to / and then just hangs there, doing nothing. It doesn't even generate load on the CPU or something, it just hangs and doesn't continue or finish (and is hard to kill ...). This is independent of the pkg emerged, at least until now it happened with every pkg I tried to emerge, also with world. I tried to clean the ccache, disable ccache, clean out /var/tmp/portage, and for sure I did some fresh eix-sync ... nothing helped so far. I tried to find something in the list-archives, in forums etc. but still couldn't find anything helpful. The system is up-to-date, I run updates every few days. I would be thankful for any help on this. Thanks in advance, Stefan -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge stalls - what to do ?
On Thu, Oct 25, 2007 at 07:01:26PM +0200, Stefan G. Weichinger wrote: Whenever I try to emerge something, it starts off like: # emerge -1 libsexy Calculating dependencies... done! Verifying ebuild Manifests... Emerging (1 of 1) x11-libs/libsexy-0.1.11 to / and then just hangs there, doing nothing. It doesn't even generate load on the CPU or something, it just hangs and doesn't continue or finish (and is hard to kill ...). This is independent of the pkg emerged, at least until now it happened with every pkg I tried to emerge, also with world. I have this happen with some specific packages which think it wise and necessary to prompt the operator with a configuration question and THEN WAIT FOR AN ANSWER! It annoys me so much that I use ps -el to find the offending program and kill it and let the config fail, and then I cross that package off my list. It has only happened two or three times, and I guess either someone else complained and it was fixed, or I didn't need the package enough to ever miss it. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman rocket surgeon / [EMAIL PROTECTED] GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge stalls - what to do ?
[EMAIL PROTECTED] schrieb: I have this happen with some specific packages which think it wise and necessary to prompt the operator with a configuration question and THEN WAIT FOR AN ANSWER! But it would wait for an answer than on my other machines as well, which it doesn't. Thanks, Stefan -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge stalls - what to do ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan G. Weichinger wrote:
Greetings, gentoo-users,
I see a problem with emerge on my notebook.
Whenever I try to emerge something, it starts off like:
# emerge -1 libsexy
Calculating dependencies... done!
Verifying ebuild Manifests...
Emerging (1 of 1) x11-libs/libsexy-0.1.11 to /
and then just hangs there, doing nothing.
That's right where it attempts to obtain a lock on the required
files in ${DISTDIR}. If that's on nfs and nfs isn't behaving
properly then it can cause problems like that. Check dmesg.
Zac
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHIOFe/ejvha5XGaMRAt3SAJ0Qh8sFGSMIDNCHGfa/f72bNmXiRQCgzKvp
4JKW3J4QLaU4127iEeng544=
=EoOm
-END PGP SIGNATURE-
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge stalls - what to do ?
Zac Medico schrieb:
Stefan G. Weichinger wrote:
Greetings, gentoo-users,
I see a problem with emerge on my notebook.
Whenever I try to emerge something, it starts off like:
# emerge -1 libsexy
Calculating dependencies... done!
Verifying ebuild Manifests...
Emerging (1 of 1) x11-libs/libsexy-0.1.11 to /
and then just hangs there, doing nothing.
That's right where it attempts to obtain a lock on the required
files in ${DISTDIR}. If that's on nfs and nfs isn't behaving
properly then it can cause problems like that. Check dmesg.
Correct, my ${DISTDIR} is normally mounted via nfs.
When I umount it, I can emerge ...
When mounted, dmesg gives me
lockd: cannot monitor ${IP_OF_NFS_SERVER}
lockd: failed to monitor ${IP_OF_NFS_SERVER}
What can I do to fix this? Restarting the nfs-service on the server did
not help yet.
Thanks a lot, Stefan
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge stalls - what to do ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan G. Weichinger wrote:
Emerging (1 of 1) x11-libs/libsexy-0.1.11 to /
and then just hangs there, doing nothing.
That's right where it attempts to obtain a lock on the required
files in ${DISTDIR}. If that's on nfs and nfs isn't behaving
properly then it can cause problems like that. Check dmesg.
Correct, my ${DISTDIR} is normally mounted via nfs.
When I umount it, I can emerge ...
When mounted, dmesg gives me
lockd: cannot monitor ${IP_OF_NFS_SERVER}
lockd: failed to monitor ${IP_OF_NFS_SERVER}
What can I do to fix this? Restarting the nfs-service on the server did
not help yet.
There are also nfs services that you need to run on the client side.
Maybe you need to do something like this:
emerge --noreplace nfs-utils
rc-update add nfs default
/etc/init.d/nfs start
If both client and server side services are running correctly then
should just work.
Zac
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHIQBD/ejvha5XGaMRAjscAKDtMwR9v/kk1si83X6Yw/bL8GscbgCdHGmC
t2spiSHCT+asZE7afFiJIHc=
=TrRr
-END PGP SIGNATURE-
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] emerge stalls - what to do ?
Zac Medico schrieb: There are also nfs services that you need to run on the client side. Maybe you need to do something like this: emerge --noreplace nfs-utils rc-update add nfs default /etc/init.d/nfs start If both client and server side services are running correctly then should just work. Hmm, I don't have nfs running on any of my other boxes (only nfsmount) and the nfs-mounted DISTDIR worked for a long time ... Anyway, I did what you recommended and now emerge runs fine. Might be that the reboot of the NFS-server also helped a bit. Thank you, Stefan -- [EMAIL PROTECTED] mailing list
