1 |
On Wednesday 08 Jan 2014 11:28:36 Stefan G. Weichinger wrote: |
2 |
> Greetings, |
3 |
> |
4 |
> yesterday I started to upgrade an older gentoo server at a customer. It |
5 |
> has only been updated now and then as they tend to save money and rarely |
6 |
> contact me ... |
7 |
> |
8 |
> I recommended to at least apply the stuff mentioned in the GLSAs ... and |
9 |
> applied some updates today (remote, via ssh). |
10 |
> |
11 |
> Today glibc failed to merge: |
12 |
> >>> Installing (2 of 3) sys-libs/glibc-2.17 |
13 |
> |
14 |
> * Defaulting /etc/host.conf:multi to on |
15 |
> /usr/lib/portage/bin/phase-functions.sh: Zeile 87: 26924 |
16 |
> Speicherzugriffsfehler "${PORTAGE_PYTHON:-/usr/bin/python}" |
17 |
> "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" |
18 |
> * ERROR: sys-libs/glibc-2.11.3::gentoo failed (prerm phase): |
19 |
> * filter-bash-environment.py failed |
20 |
> * |
21 |
> * Call stack: |
22 |
> * ebuild.sh, line 480: Called __preprocess_ebuild_env |
23 |
> * phase-functions.sh, line 156: Called __filter_readonly_variables |
24 |
> '--filter-features' '--filter-locale' '--filter-path' '--filter-sandbox' |
25 |
> * phase-functions.sh, line 137: Called die |
26 |
> * The specific snippet of code: |
27 |
> * "${PORTAGE_PYTHON:-/usr/bin/python}" |
28 |
> "${PORTAGE_BIN_PATH}"/filter-bash-environment.py "${filtered_vars}" || |
29 |
> die "filter-bash-environment.py failed" |
30 |
> * |
31 |
> * If you need support, post the output of `emerge --info |
32 |
> '=sys-libs/glibc-2.11.3::gentoo'`, |
33 |
> * the complete build log and the output of `emerge -pqv |
34 |
> '=sys-libs/glibc-2.11.3::gentoo'`. |
35 |
> * The complete build log is located at |
36 |
> '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/temp/build.log'. |
37 |
> * The ebuild environment file is located at |
38 |
> '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/temp/environment'. |
39 |
> * Working directory: '/usr/lib/portage/pym' |
40 |
> * S: '/var/tmp/portage/._unmerge_/sys-libs/glibc-2.11.3/work/glibc-2.11.3' |
41 |
> /usr/lib/portage/bin/isolated-functions.sh: Zeile 109: 27001 |
42 |
> Speicherzugriffsfehler "$PORTAGE_BIN_PATH"/ebuild-ipc exit 1 |
43 |
> |
44 |
> But it seems that this is the consequence of problems with python. |
45 |
> There are various versions installed: |
46 |
> |
47 |
> # eselect python list |
48 |
> Available Python interpreters: |
49 |
> [1] python2.4 |
50 |
> [2] python2.5 |
51 |
> [3] python2.6 |
52 |
> [4] python2.7 * |
53 |
> [5] python3.1 |
54 |
> [6] python3.3 |
55 |
> |
56 |
> |
57 |
> But I get segfaults (german: Speicherzugriffsfehler) for all of them: |
58 |
> |
59 |
> mail ~ # python2.7 |
60 |
> Speicherzugriffsfehler |
61 |
> mail ~ # python3.1 |
62 |
> Speicherzugriffsfehler |
63 |
> mail ~ # python3.3 |
64 |
> Speicherzugriffsfehler |
65 |
> |
66 |
> dmesg shows lines: |
67 |
> |
68 |
> awk[28527]: segfault at 579e ip 0000579e sp bfc3006c error 4 in |
69 |
> gawk[8048000+4c000] |
70 |
> awk[28531]: segfault at 579e ip 0000579e sp bff3c8ec error 4 in |
71 |
> gawk[8048000+4c000] |
72 |
> find[28706]: segfault at 579e ip 0000579e sp bff21c3c error 4 in |
73 |
> find[8048000+21000] |
74 |
> find[28707]: segfault at 579e ip 0000579e sp bff42c9c error 4 in |
75 |
> find[8048000+21000] |
76 |
> find[28708]: segfault at 579e ip 0000579e sp bfe1a4ac error 4 in |
77 |
> find[8048000+21000] |
78 |
> find[28714]: segfault at 579e ip 0000579e sp bf82cb5c error 4 in |
79 |
> find[8048000+21000] |
80 |
> find[28715]: segfault at 579e ip 0000579e sp bfa0ef3c error 4 in |
81 |
> find[8048000+21000] |
82 |
> find[28716]: segfault at 579e ip 0000579e sp bfa4c4cc error 4 in |
83 |
> find[8048000+21000] |
84 |
> find[28720]: segfault at 579e ip 0000579e sp bfa1c83c error 4 in |
85 |
> find[8048000+21000] |
86 |
> find[28721]: segfault at 579e ip 0000579e sp bfcf9fbc error 4 in |
87 |
> find[8048000+21000] |
88 |
> eix[28731]: segfault at 579e ip 0000579e sp bfc028ec error 4 in |
89 |
> eix[8048000+114000] |
90 |
> python2.7[28732]: segfault at 579e ip 0000579e sp bfa1c9fc error 4 in |
91 |
> python2.7[8048000+1000] |
92 |
> python2.7[28733]: segfault at 579e ip 0000579e sp bf8a2c0c error 4 in |
93 |
> python2.7[8048000+1000] |
94 |
> python2.7[28746]: segfault at 579e ip 0000579e sp bfeb392c error 4 in |
95 |
> python2.7[8048000+1000] |
96 |
> python2.7[28747]: segfault at 579e ip 0000579e sp bfbfcd4c error 4 in |
97 |
> python2.7[8048000+1000] |
98 |
> python2.7[28749]: segfault at 579e ip 0000579e sp bfa1b71c error 4 in |
99 |
> python2.7[8048000+1000] |
100 |
> python2.7[28757]: segfault at 579e ip 0000579e sp bfeb8b0c error 4 in |
101 |
> python2.7[8048000+1000] |
102 |
> python2.7[28762]: segfault at 579e ip 0000579e sp bfeb479c error 4 in |
103 |
> python2.7[8048000+1000] |
104 |
> |
105 |
> |
106 |
> |
107 |
> This leads to not being able to emerge something :-( |
108 |
> |
109 |
> What can I do? quickpkg some python-version and copy over? |
110 |
> (sidenote: 32bit box ...) |
111 |
> |
112 |
> I would like to avoid to have to drive there so it would be great to be |
113 |
> able to fix that from here, via ssh. |
114 |
> |
115 |
> |
116 |
> Thanks for any help, Stefan |
117 |
|
118 |
The segfaults look scary and could point to hardware fault. I'd run a backup |
119 |
of any useful data to start with. |
120 |
|
121 |
Then run 'python-updater' to rebuild any packages that had their links broken. |
122 |
-- |
123 |
Regards, |
124 |
Mick |