portage broke, how do I repair?

[nellson]

Have 4 identical systems running Gentoo. Using one to learn Python on and when I logged into today.. python was coughing errors on class programs that were working yesterday.. started the python interpreter and could not even "import paramiko"

Though maybe it was paramiko at fault, so I tried to emerge --search paramiko to see if I could update it.. Emerge is broken.

Code: Select all

bertha portage-2.2.18 # emerge --sync
  File "/usr/lib/python-exec/python2.7/emerge", line 23
    from __future__ import print_function
       ^
SyntaxError: invalid syntax

Doing searching on this and it seems this is some pre-code to help between Python 2.x and 3.x? I am set to 3.4 in eselect, have been for a long while. Portage was happy using the still-installed 2.7.

bertha portage-2.2.18 # eselect python list
Available Python interpreters:
[1] python2.7 *
[2] python3.2
[3] python3.3
[4] python3.4

I even tried going back to 2.7 for all.. no help.

So, as I do have 4 identical hardware systems running Gentoo, and the other 3 seem fine, I am guessing my Python Class helped me do something bad? How do I fix portage? The whole binary package directions seem to still require a working portage on the receiving end.

[dol-sen]

Please post the file contents so we can see what is wrong with it. It should be a very small file, only 86 lines in it's original form. It will be the lines leading up to that error that are the most important.

[nellson]

Here is the contents..

Code: Select all

bertha ~ # cat /usr/lib/python-exec/python2.7/emerge
#!/usr/bin/python2.7 -b
# Copyright 2006-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

from __future__ import print_function

import platform
import signal
import sys

# This block ensures that ^C interrupts are handled quietly. We handle
# KeyboardInterrupt instead of installing a SIGINT handler, since
# exiting from signal handlers intermittently causes python to ignore
# the SystemExit exception with a message like this:
# Exception SystemExit: 130 in <function remove at 0x7fd2146c1320> ignored
try:

        def exithandler(signum, _frame):
                signal.signal(signal.SIGTERM, signal.SIG_I#!/usr/bin/python2.7 -b
# Copyright 2006-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

from __future__ import print_function

import platform
import signal
import sys

# This block ensures that ^C interrupts are handled quietly. We handle
# KeyboardInterrupt instead of installing a SIGINT handler, since
# exiting from signal handlers intermittently causes python to ignore
# the SystemExit exception with a message like this:
# Exception SystemExit: 130 in <function remove at 0x7fd2146c1320> ignored
try:

        def exithandler(signum, _frame):
                signal.signal(signal.SIGTERM, signal.SIG_IGN)
                sys.exit(128 + signum)

        signal.signal(signal.SIGTERM, exithandler)
        # Prevent "[Errno 32] Broken pipe" exceptions when
        # writing to a pipe.
        signal.signal(signal.SIGPIPE, signal.SIG_DFL)

        def debug_signal(_signum, _frame):
                import pdb
                pdb.set_trace()

        if platform.python_implementation() == 'Jython':
                debug_signum = signal.SIGUSR2 # bug #424259
        else:
                debug_signum = signal.SIGUSR1

        signal.signal(debug_signum, debug_signal)

        from os import path as osp
        if osp.isfile(osp.join(osp.dirname(osp.dirname(osp.realpath(__file__))), ".portage_not_installed")):
                sys.path.insert(0, osp.join(osp.dirname(osp.dirname(osp.realpath(__file__))), "pym"))
        import portage
        portage._internal_caller = True
        portage._disable_legacy_globals()
        from _emerge.main import emerge_main

        if __name__ == "__main__":
                from portage.exception import IsADirectory, ParseError, \
                                PermissionDenied
                try:
                        retval = emerge_main()
                except PermissionDenied as e:
                        sys.stderr.write("Permission denied: '%s'\n" % str(e))
                        sys.exit(e.errno)
                except IsADirectory as e:
                        sys.stderr.write("'%s' is a directory, but should be a file!\n"
                                        "See portage man page for information on "
                                        "which files may be directories.\n" %
                                        str(e))
                        sys.exit(e.errno)
                except ParseError as e:
                        sys.stderr.write("%s\n" % str(e))
                        sys.exit(1)
                ebertha ~ # 

[nellson]

WTH?? some strange double code at the top, my other systems do not have that... OK, I am only learning for loops in my class, no way I whacked up my system this badly.. :-O

And I did not do any system updates or world updates between Sat and Sunday..

The system does an "emerge --sync" once a night, but that shouldn't hork anything up, would it?

Nick

[nellson]

OK.. <sigh> system #2 can't create any packages, fails compiling.. on anything... Something has shaken the Gentoo tree while I wasn't updating every day and I seem to have dropped behind some curve that is proving a bit of a challenge to get passed..

How might I get python and portage re-imaged to a working state so I can start repairing the rest?

Nick

[krinn]

http://forums.gentoo.org/viewtopic-p-77 ... ml#7707196

That's not the only way, but clearly the easiest one for everyone and any package.

[dol-sen]

Might I suggest you check for bad memory and fsck your hard drive for any file corruption before you proceed any further.
while your at it, have you checked/cleaned the cpu fan & heatsink? Maybe some excess heat caused your cpu to do something strange.

[nellson]

I may have to do that. This system has no other boot media, I loaded it up using PXE Boot with sysrescueCD. I can do that again to use the memory and fsck tools, and sounds like that is how I am going to repair it anyway.

The systems are in a controlled data center (Re purposed Silver Peak WAN OPT head ends) for my own lab. Should be fairly dust free, but I will insure that.

Nick

[nellson]

So perhaps I was mistaken on the other 3 systems.. I have just one system that appears portage functional, three that are failing any form of portage command with python errors.

one seems to be somewhat happy...

Made a quickpkg and untar'ed it over the / dir, and recreated the /usr/bin/emerge symlink.. got a successfull "emerge --sync" out of it!!

Rebuilding portage again properly.. Here's hoping I can get this all repaired

[nellson]

OK, got things sorted out... on Sunday around 1 pm our computer room annex took a power hit and dropped all 4 of my systems. (Never thought to check "uptime" duh....

So that scrambled them good. system #3 was recoverable enough with a fresh tar of portage and "emerge -e system --keep-going" took around 5 washes through to get no errors.

Then I built binaries of gcc, bash, glibc, portage, and python2.7, and ssh'ed them to the other 3.

Split to tbz2 files out into the raw tar (emerge was totally non-functional on all 3) and untarred all 4 builds over the top of my / directory.

Fixed a missing symlink to /usr/lib/portage-exec/portage-exec2 and started in on the "emerge -e system --keep-going" and getting down to where I am almost through all 4 systems cleanly..

These systems use 4 160gig flash SAS drives as /dev/md0 for /, and I am thinking hard dropping power was.. erm.. bad?

Once they are all rebuilt for system, I'll go for the "-uDavN" on 'world' and get them back up to snuff. Then I will lobby to get my toys moved out of the lab annex and onto house UPS

Thanks all, hope this helps others with disaster.. though I did need at least one system of the set of 4 that had some of it's marbles intact.

Nick