| View previous topic :: View next topic |
| Author |
Message |
joanandk
Apprentice
Joined: 12 Feb 2017
Posts: 169
|
 Posted: Wed May 15, 2019 7:02 am Post subject: [Workaround] emerge fails on some packages |
 |
|
Hi,
I am unable to update gcc from 8.2 to 8.3, update virtualbox, update thunderbird, update firefox and update samba (seen so far) on one laptop and one desktop. On another laptop, no issues!
The emerge process quits with
| Quote: |
* ERROR: app-emulation/virtualbox-5.2.26::gentoo failed (install phase):
* !!! newins: /var/tmp/portage/app-emulation/virtualbox-5.2.26/files/virtualbox-4-config does not exist
|
| Quote: |
* ERROR: sys-devel/gcc-8.3.0-r1::gentoo failed (install phase):
* /var/tmp/portage/sys-devel/gcc-8.3.0-r1/files/awk/fixlafiles.awk-no_gcc_la does not exist
|
| Quote: |
* ERROR: net-fs/samba-4.8.6-r2::gentoo failed (install phase):
* !!! newinitd: /var/tmp/portage/net-fs/samba-4.8.6-r2/files/4.4/samba4.initd-r1 does not exist
|
Firefox and Thunderbird quits with "Too many symbolic links"
If I cd into the directory, I see the file and can read it. I have also checked the file system and it still does not work.
I have two systems (at the moment) where I have seen similar issues. On three other systems, emerge works fine and without issues.
Does anyone have a clue what the cause is?
Thanks and BR
Edit:
The system uses autofs to mount portage-tree, distfiles and package directory. They are located on a central server and saves bandwidth and space. I never suspected the autofs as the source of the problem, as the emerge fails at the installation stage.
The workaround: I only had to turn off autofs, mount the shares manually. I first suspected nfs and synced the portage tree to the local system. This worked on the laptop. The destkop I tried to manuall mount the shares which worked too. So it seems to be an autofs issue.
Thanks @Ant P. for asking the correct question.
BR
Last edited by joanandk on Sat May 18, 2019 7:57 pm; edited 1 time in total |
|
| Back to top |
|
 |
guitou
Guru
Joined: 02 Oct 2003
Posts: 534
Location: France
|
| Posted: Wed May 15, 2019 11:44 am Post subject: |
|
|
Hello.
Maybe you are simply running out of disk space |
|
| Back to top |
|
|
joanandk
Apprentice
Joined: 12 Feb 2017
Posts: 169
|
| Posted: Wed May 15, 2019 12:22 pm Post subject: |
|
|
| guitou wrote: | | Maybe you are simply running out of disk space |
No, there is more than enough space (over 90GB on the root). The confusing part is:
but I can see and edit the file.
| Quote: | >>> Install firefox-60.6.2 into /var/tmp/portage/www-client/firefox-60.6.2/image/ category www-client
cp: cannot stat '/var/tmp/portage/www-client/firefox-60.6.2/files/gentoo-default-prefs.js-2': Too many levels of symbolic links
* ERROR: www-client/firefox-60.6.2::gentoo failed (install phase):
* (no error message)
|
I have in the meantime recompiled python and perl. Both were emerged sucessfully, but I still cannot compile virtualbox or firefox. I am still stuck with the issue.
Thanks and BR |
|
| Back to top |
|
|
guitou
Guru
Joined: 02 Oct 2003
Posts: 534
Location: France
|
| Posted: Thu May 16, 2019 11:41 am Post subject: |
|
|
Well... might have been a matter of inodes, rather than actual space, but provided file is there, I guess I was just wrong in my suggestion.
| Quote: | | Too many levels of symbolic links |
For this one, you may check along the path for symlinks and/or search this string on the web for a similar problem.
++
Gi) |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Thu May 16, 2019 3:07 pm Post subject: |
|
|
| Are you using autofs? |
|
| Back to top |
|
|
joanandk
Apprentice
Joined: 12 Feb 2017
Posts: 169
|
| Posted: Fri May 17, 2019 5:18 am Post subject: |
|
|
| Ant P. wrote: | | Are you using autofs? |
Yes, the systems which fails to emerge are using autofs to mount the portage tree, distfiles, package dir and my custom overlay. All these are on a NFS share to minimize download bandwidth and local disk usage.
I have already taken one system off and was able successfully update.
Do you know why this is the cause of the issue?
Thanks and BR |
|
| Back to top |
|
|
zerocool_australia
n00b
Joined: 31 Jul 2003
Posts: 58
|
| Posted: Fri May 31, 2019 3:15 pm Post subject: |
|
|
I had this problem with autofs as well. Increasing timeout= and dismount_interval in autofs.conf seemed to help. I set them to 10000 for now and I have gotten past a couple of previously failing emerges, but I think you'd have to set it to the maximum possible time that an emerge could take on your system. On my system with chromium it could be days.
I think the portion of portage trying to install the initrd and other components times out rapidly and doesn't give autofs enough time to remount the share, and just fails immediately. |
|
| Back to top |
|
|
|
Portage & Programming
