Your best friend for file transfer.

Fetch application logoFetch

"ConsoleLogger has encountered a fatal error..." on every start (6 posts)

  • Started 4 years ago by Shawn
  • Latest reply 4 years ago from Scott McGuire
  • Shawn Member

    Starting today, both with Fetch 5.3 and 5.5, every time I start Fetch, a process ConsoleLogger crashes with the following message:
    -----
    ConsoleLogger has encountered a fatal error, and will now terminate.
    An uncaught exception was raised during execution of the main script:
    ImportError: No module named os
    This may mean that an unexpected error has occurred, or that you do not have all of the dependencies for this application.
    -----
    And the console log shows this:
    -----
    'import site' failed; use -v for traceback
    Traceback (most recent call last):
    File "/Applications/Fetch.app/Contents/Resources/ConsoleLogger.app/Contents/Resources/__boot__.py", line 4, in ?
    _chdir_resource()
    File "/Applications/Fetch.app/Contents/Resources/ConsoleLogger.app/Contents/Resources/__boot__.py", line 2, in _chdir_resource
    import os
    ImportError: No module named os
    2009-07-09 14:39:20.472 ConsoleLogger[560] Could not execute __error__.sh: launch path not accessible
    2009-07-09 14:39:20.488 ConsoleLogger[560] An uncaught exception was raised during execution of the main script:
    ImportError: No module named os
    This may mean that an unexpected error has occurred, or that you do not have all of the dependencies for this application.
    -----
    I don't know why this problem started today. I have used the same version of Fetch before without any problems. I hadn't changed any settings.
    Not knowing much of anything about python programming, it seems like a bad thing that a python script can't find a module named os, since it looks like a very useful and universal module, looking at http://pydoc.org/1.6/os.html
    When I create a simple GoodbyeWorld program in python, it runs, and it still runs when I include an "import os" command to the script, the following:
    -----
    import os
    print "Goodbye, world..."
    print os.name
    -----
    outputs
    -----
    Goodbye, world...
    posix
    -----
    I guess Fetch's python script, or rather Fetch's ConsoleLogger's script is supposed to set up an environment for its python scripts and it isn't doing it right.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Shawn,

    Have you restarted your Mac since this problem began? If not, please give that a try just to see if it fixes the problem.

    Next, could you tell us which version of Mac OS X you are using?

    And finally, could you please do the following?

    * Open the Terminal application.
    * Type "python" (without quotes).
    * Copy the first two lines that appear (containing various version numbers), and paste it into a reply to this message.

    That information will help us figure out what to do next to investigate the problem.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Shawn Member

    Scott,
    I've restarted since yesterday, and the problem still occurs. Also tried 5.5.1
    Here's my version of python you requested:
    Python 2.5.1 (r251:54869, Apr 18 2007, 22:08:04)
    [GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin
    I'm using Tiger with all the updates. That would be 10.4.11, running on a Quad G5. I have Apple's developer's kit installed.
    I have two instances of the file os.py (and its compiled versions), one at /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/os.py
    /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/os.pyc
    /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/os.pyo
    and another for 2.3 at
    /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/os.py
    /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/os.pyc
    /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/os.pyo

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Shawn,

    Thanks for the information.

    Python 2.5.1 is not the standard version of Python on Mac OS X 10.4.11; it looks like you have a third party Python installed (the one in /Library/Frameworks/) in addition to the standard one (the one in /System/Library/Frameworks/).

    In theory this should work - we have several 10.4.11 machines with Python 2.5 installed on them, and Fetch 5.3 and 5.5 run fine on them - but it looks like something from the extra Python install on your Mac is causing problems with the standard Python install, and this results in Fetch having problems.

    The first thing to try is moving the Python.framework in /Library/Frameworks to someplace else (like a folder on your desktop), restart your Mac, and see if that fixes the problem. Let us know, and we'll go from there, depending on the result.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Shawn Member

    I moved Python 2.5 away from /Library/Frameworks/, as Scott suggested; the error is different now, but still annoying:
    Console Logger, launched by Fetch on startup, crashes with the following message:
    'import site' failed; use -v for traceback
    Traceback (most recent call last):
    File "/Applications/Fetch.app/Contents/Resources/ConsoleLogger.app/Contents/Resources/__boot__.py", line 31, in ?
    _run('ConsoleLogger.py')
    File "/Applications/Fetch.app/Contents/Resources/ConsoleLogger.app/Contents/Resources/__boot__.py", line 21, in _run
    site.addsitedir(base)
    AttributeError: 'module' object has no attribute 'addsitedir'
    2009-08-11 16:23:31.682 ConsoleLogger[270] Could not execute __error__.sh: launch path not accessible
    2009-08-11 16:23:31.713 ConsoleLogger[270] An uncaught exception was raised during execution of the main script:
    AttributeError: 'module' object has no attribute 'addsitedir'
    This may mean that an unexpected error has occurred, or that you do not have all of the dependencies for this application.

    My computer seems to have Python 2.3 in /System/Library/Frameworks. So, I try installing 2.5.1 from Python.org, which failed during postflight, but did put the 2.5 folder back in /Library/Frameworks. Interestingly, even after restart, the problem above persists, but not the issue in my first post.
    Same deal after installing Python 2.6.4, just for fun. Also, python 2.6.4 installer package failing. A nice chain of unsolvables here, practically nothing to do with the functionality of Fetch.
    -Shawn

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Shawn,

    The fact that the Python installers are failing when you try to install them probably isn't a good sign. It's unlikely you got a complete install either time.

    Unfortunately, it sounds like the original Python installation that came with Mac OS X has gotten corrupted somehow, and probably the only solution to the problem is to reinstall Mac OS X. (Note that Fetch does not make any changes to the Python installed on your Mac; it only attempts to use what's there.)

    Sorry, I wish I had a better answer for you.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.