missing neatx.app?

[afrobavarian]

from /var/log/messages on our CentOS 5.3 server:

Jul 14 11:40:28 foofighter nxserver-login-wrapper[7597]: Traceback
(most recent call last):
Jul 14 11:40:28 foofighter nxserver-login-wrapper[7597]: File "/usr/
local/lib/neatx/nxserver-login", line 3, in ?
Jul 14 11:40:28 foofighter nxserver-login-wrapper[7597]: from
neatx.app import nxserver_login
Jul 14 11:40:28 foofighter nxserver-login-wrapper[7597]: ImportError:
No module named neatx.app

is something missing from the install process?

[Stephen Shirley]

On Tue, Jul 14, 2009 at 21:13, afrobavarian<di...@fastersilicon.com> wrote:
> Jul 14 11:40:28 foofighter nxserver-login-wrapper[7597]: ImportError:
> No module named neatx.app
>
> is something missing from the install process?

The issue there is about where the neatx python modules got installed.
I'm guessing it might be somewhere like
/usr/local/lib/python2.5/site-packages/neatx. Neatx expects the
modules to be available to python, if you can do:

diamond@asher:~(0:0)$ python
Python 2.5.2 (r252:60911, Jul 31 2008, 17:28:52)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import neatx.constants
>>> neatx.constants.AUTH_METHOD_DEFAULT
'su'

then python is happy. I expect what'll happen in your case though is
that you'll get the same error as from your log. Can you tell me where
the neatx python packages are?

Steve
--
"You are technically correct, the best kind of correct."
- Bureaucrat 1.0, Futurama

[Stephen Shirley]

On Tue, Jul 14, 2009 at 22:01, Stephen Shirley<kor...@gmail.com> wrote:
> the neatx python packages are?

Er, python *modules*, sorry.

[Thomas Hamel]

I had the same probem, you can work around it by putting this line in your nxserver-login-wrapper:

export PYTHONPATH=<change to your prefix>/lib/python<your python version>/site-packages

I used /opt/neatnx as prefix and here is mine:

#!/bin/bash

# Copyright (C) 2009 Google Inc.

# This file is automatically generated, do not edit!

# Log all stderr output from nxserver-login and children

# (should only be critical errors)

PROGNAME=$(basename "$0")

PRIORITY=""

log() {

  logger -t "$PROGNAME[$$]" -p "user.${PRIORITY:-crit}" -- "$@"

}

export PYTHONPATH=${PYTHONPATH}:/opt/neatnx/lib/python2.6/site-packages

# Duplicate stdout to fd 3

exec 3>&1

exec /opt/neatnx/lib/neatx/nxserver-login "$@" 2>&1 >&3 | {

  PRIORITY=debug log "Started"

  while read; do

    log "$REPLY"

  done

  PRIORITY=debug log "EOF on stderr, exiting"

}

--

Thomas

[Stephen Shirley]

On Tue, Jul 14, 2009 at 22:30, Thomas Hamel<hame...@gmail.com> wrote:
> I had the same probem, you can work around it by putting this line in your
> nxserver-login-wrapper:

Nice