Configuration crash - can't start new thread

[Satish Balay]

> >  File "/nas/home/enduser/g0306332/python-2.4/lib/python2.5/threading.py",
> > line 434, in start
> >    _start_new_thread(self.__bootstrap, ())

No - its using the python - installed at
/nas/home/enduser/g0306332/python-2.4

What version of redhat? What do you have for:

cat /etc/redhat-release

The fact that you get the 'same thread' error with both python-2.5 and
python-2.2 - sugests that it could be glibc problem - not
python. [perhaps the OS is in a bad state]

I'll sugest using a different machine for install.

Matt,

Looks like this piece if code is ignoring the option '--useThreads=0'
- and attempting to use threads. Perhas this should be fixed?

Satish

On Thu, 7 Dec 2006, Ben Tay wrote:

> Hi,
> 
> It's Redhat. The administrator told me their python ver is 2.2.3. Is that
> the reason? However, I've already downloaded and installed the new version.
> but the same problem exist. I wonder if it is because petsc is still using
> the old version....
> 
> 
> On 12/6/06, Satish Balay <balay at mcs.anl.gov> wrote:
> > 
> > This is wierd. I don't think we've seen this error before. What kind
> > of linux is this running? I'm guessing there is a problem on the
> > system-software side.. [with threads]
> > 
> > Satish
> > 
> > On Wed, 6 Dec 2006, Ben Tay wrote:
> > 
> > > Hi,
> > >
> > > sorry, it still can't work. Installation of Python is ok though.
> > >
> > > the error msg is the same though:
> > >
> > >
> > >
> > =================================================================================
> > >             Configuring PETSc to compile on your
> > > system
> > >
> > =================================================================================
> > >
> > *********************************************************************************
> > >          CONFIGURATION CRASH  (Please send configure.log to
> > > petsc-maint at mcs.anl.gov)
> > >
> > *********************************************************************************
> > >
> > > can't start new thread
> > >  File "config/configure.py", line 172, in petsc_configure
> > >    framework = config.framework.Framework(sys.argv
> > [1:]+['--configModules=
> > > PETSc.Configure','--optionsModule=PETSc.compilerOptions'], loadArgDB =
> > 0)
> > >  File
> > > "/nas/hpctmp/g0306332/petsc-2.3.2-p7
> > /python/BuildSystem/config/framework.py",
> > > line 81, in __init__
> > >    self.argDB['debugSections'] = ['screen']
> > >  File "/nas/hpctmp/g0306332/petsc-2.3.2-p7/python/BuildSystem/RDict.py",
> > > line 219, in __setitem__
> > >    self.save()
> > >  File "/nas/hpctmp/g0306332/petsc-2.3.2-p7/python/BuildSystem/RDict.py",
> > > line 639, in save
> > >    self.saveTimer.start()
> > >  File "/nas/home/enduser/g0306332/python-2.4
> > /lib/python2.5/threading.py",
> > > line 434, in start
> > >    _start_new_thread(self.__bootstrap, ())
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 12/6/06, Satish Balay <balay at mcs.anl.gov> wrote:
> > > >
> > > > What linux is this? Just get python sources from http://python.org/
> > > > [sugest python-2.4] - and install your own copy - and try with it.
> > > >
> > > > configure python with:
> > > > ./configure --prefix=${HOME}/python-2.4
> > > > make
> > > > make install
> > > >
> > > > And configure PETSc with:
> > > > ${HOME}/python-2.4/bin/python config/configure.py
> > > >
> > > > Satish
> > > >
> > > >
> > > > On Wed, 6 Dec 2006, Ben Tay wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I just tried but it's the same error. Any other suggestion?
> > > > >
> > > > > thanks!
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 12/5/06, Matthew Knepley <knepley at gmail.com> wrote:
> > > > > >
> > > > > > You have a broken Python installation. You can work around this
> > using
> > > > > > the options --useThreads=0.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > >    Matt
> > > > > >
> > > > > > On 12/5/06, Ben Tay <zonexo at gmail.com> wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I tried to compile the library on a linux sys (xeon). It gives
> > the
> > > > error
> > > > > > > msg:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> > *********************************************************************************
> > > > > > >           CONFIGURATION CRASH  (Please send configure.log to
> > > > > > > petsc-maint at mcs.anl.gov)
> > > > > > >
> > > > > >
> > > >
> > *********************************************************************************
> > > > > > >
> > > > > > > can't start new thread
> > > > > > >
> > > > > > >   File "./config/configure.py", line 172, in petsc_configure
> > > > > > >     framework =
> > > > > > > config.framework.Framework(sys.argv[1:]+['--configModules=
> > > > > > PETSc.Configure','--optionsModule=PETSc.compilerOptions'],
> > > > > > > loadArgDB = 0)
> > > > > > >   File
> > > > > > > "/nas/hpctmp/g0306332/petsc-2.3.2-p7
> > > > > > /python/BuildSystem/config/framework.py",
> > > > > > > line 81, in __init__
> > > > > > >     self.argDB['debugSections'] = ['screen']
> > > > > > >   File "/nas/hpctmp/g0306332/petsc-2.3.2-p7
> > > > > > /python/BuildSystem/RDict.py",
> > > > > > > line 219, in __setitem__
> > > > > > >     self.save()
> > > > > > >   File "/nas/hpctmp/g0306332/petsc-2.3.2-p7
> > > > > > /python/BuildSystem/RDict.py",
> > > > > > > line 639, in save
> > > > > > >     self.saveTimer.start()
> > > > > > >   File "/usr/lib/python2.2/threading.py", line 396, in
> > > > > > > start
> > > > > > >     _start_new_thread(self.__bootstrap, ())
> > > > > > >
> > > > > > >
> > > > > > > May I know what's wrong? I also can't find any configure.logfile.
> > > > > > >
> > > > > > > Thank you.
> > > > > > >
> > > > > > > Regards
> > > > > >
> > > > > >
> > > > > > --
> > > > > > "Failure has a thousand explanations. Success doesn't need one" --
> > Sir
> > > > > > Alec Guiness
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > 
> > 
>