ratt-ru / meqtrees

A library for implementing radio astronomical Measurement Equations
http://meqtrees.net
10 stars 2 forks source link

Meqserver in ppa segfaults on startup #863

Open bennahugo opened 8 years ago

bennahugo commented 8 years ago

There is a problem with the meqtrees build on the PPA

Purged and installed latest set of meqtrees deb files from the radio astronomy ppa. Meqtrees GUI opens up, but as soon as I start a server I get a segfault.

Building meqtrees from source directly from the master branch seems to resolve the issue. Meqserver starts up successfully

gijzelaerr commented 8 years ago

hi, thanks for reporting this problem.

Are you using Ubuntu 14.04? What casacore version do you have installed? Is there anything else to report about your setup or is it just a plain Ubuntu 14.04 isntall with our repository enabled?

@o-smirnov do you know what may be causing this? Did you change things in the trunk?

bennahugo commented 8 years ago

Hi Gijs

Using Ubuntu 14.04 and I'm sticking to casacore and libcasacore-dev from radio astronomy ppa casacore-data/trusty,now 20150706-1trusty all [installed,automatic] casacore2/trusty,now 2.0.0-1trusty amd64 [installed] libcasacore-dev/trusty,now 1.7.0-2trusty amd64 [installed] libcasacore1/trusty,now 1.7.0-2trusty amd64 [installed,automatic] libcasacore2/trusty,now 2.0.0-1trusty amd64 [installed,automatic]

I've tested the meqtrees debs on 2 machines. Both fail.

gijzelaerr commented 8 years ago

What happens if you remove the casacore2 and libcasacore2 packages?

2015-07-09 10:56 GMT+02:00 bennahugo notifications@github.com:

Hi Gijs

Using Ubuntu 14.04 and I'm sticking to casacore and libcasacore-dev from radio astronomy ppa casacore-data/trusty,now 20150706-1trusty all [installed,automatic] casacore2/trusty,now 2.0.0-1trusty amd64 [installed] libcasacore-dev/trusty,now 1.7.0-2trusty amd64 [installed] libcasacore1/trusty,now 1.7.0-2trusty amd64 [installed,automatic] libcasacore2/trusty,now 2.0.0-1trusty amd64 [installed,automatic]

I've tested the meqtrees debs on 2 machines. Both fail.

— Reply to this email directly or view it on GitHub https://github.com/ska-sa/meqtrees/issues/863#issuecomment-119879912.

Gijs Molenaar http://pythonic.nl

bennahugo commented 8 years ago

Still the same seqfault.. have the following installed:

casacore-data/trusty,now 20150706-1trusty all [installed,automatic] libcasacore-dev/trusty,now 1.7.0-2trusty amd64 [installed] libcasacore1/trusty,now 1.7.0-2trusty amd64 [installed,automatic] libmeqtrees-timba0/trusty,now 1.3.4-1trusty amd64 [installed,automatic] meqtrees/trusty,now 1.3.3-2trusty amd64 [installed] meqtrees-timba/trusty,now 1.3.4-1trusty amd64 [installed,automatic] python-meqtrees-cattery/trusty,now 1.3.3-2trusty amd64 [installed,automatic] python-meqtrees-timba/trusty,now 1.3.4-1trusty amd64 [installed,automatic]

jfunction commented 8 years ago

Hello, I'm wondering if there is any progress on this? I am having the same issue.

The output of dmesg shows that the offending library is likely libcasa_synthesis.so as in:

[869144.655517] traps: meqserver[12677] general protection ip:7f932a63d598 sp:7fffecf90160 error:0 in libcasa_synthesis.so[7f932a251000+c07000]
gijzelaerr commented 8 years ago

what version are you using?

gijzelaerr commented 8 years ago

I can start meqbrowser.py on jake and with that a meqserver without segfault.

cattery 1.4.0 timba 1.5.0

jfunction commented 8 years ago

Does this help?

sudo apt-cache policy meqtrees
meqtrees:
  Installed: 1.4.0-0trusty
  Candidate: 1.4.0-0trusty
  Version table:
 *** 1.4.0-0trusty 0
        500 http://ppa.launchpad.net/radio-astro/main/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

I just installed meqtrees from the PPA on 14.04

jfunction commented 8 years ago

If I try install casarest it wants to remove libcasacore-dev and lwimager Also, I don't have meqtrees-timba - it wants to install casarest for that.

Should I try installing these?

gijzelaerr commented 8 years ago

meqtrees-timba is the actual browser. How do you install the browser?

casarest should replace lwimager. libcasacore-dev is depricated (by libcasacore2-dev).

jfunction commented 8 years ago

I can't remember how I installed it initially, but I installed meqtrees-timba now and am getting a new error:

/usr/bin/meqserver: symbol lookup error: /usr/bin/meqserver: undefined symbol: _ZN9MeqPython11use_memprofE
gijzelaerr commented 8 years ago

what is the md5sum of your meqserver binary

$ md5sum /usr/bin/meqserver
2ad75347e907c4306576149c710b8c22  /usr/bin/meqserver
jfunction commented 8 years ago

It seems to be the same as yours:

md5sum /usr/bin/meqserver
2ad75347e907c4306576149c710b8c22  /usr/bin/meqserver
gijzelaerr commented 8 years ago

_ZN9MeqPython11use_memprofE should be defined in /usr/lib/libmeqserver.so. Do you have a libmeqserver.so in /usr/local? Or are you fiddeling with your LD_LIBRARY_PATH?

jfunction commented 8 years ago

Ah, so that symbol is not defined in my /usr/lib/libmeqserver.so. I guess then that this is the wrong hash:

md5sum /usr/lib/libmeqserver.so
4e9dbefc9c41cec361feb96f68959f32  /usr/lib/libmeqserver.so

I don't have any other files called libmeqserver.so lying around and I'm not sure how to check my LD_LIBRARY_PATH. It's not an live environment variable in my shell. I'm using zsh, I don't think that's the problem though because the issue persists if I switch to bash.

gijzelaerr commented 8 years ago

/usr/lib/libmeqserver.so should be in the libmeqtrees-timba0 package, which is currently at version 1.5.0.

jfunction commented 8 years ago

Installing the above package seems to fix the problem for me. Thanks Gijs!

gijzelaerr commented 8 years ago

how did that file get there? You should never install software manually in /usr except for /usr/local.

if you are using my packages and manually compile/install stuff make sure what you are doing because otherwise you are just wasting my time.

jfunction commented 8 years ago

I'm can't be sure what I had done. I think I did install casapy manually into an optsoft folder in my home directory.

My apologies if this issue was a result of a manual install.