#529 Processes still be running from a previous run of Xastir
[W8JSA@w8jsa ~]$ xastir
Built-in map types:
gnis USGS GNIS Datapoints
map APRSdos Maps
map WinAPRS/MacAPRS/X-APRS Maps
pdb PocketAPRS Maps
Support for these additional map types has been compiled in:
geo Image Map (ImageMagick/GraphicsMagick library, many formats allowed)
geo URL (Internet maps via wget)
shp ESRI Shapefile Maps (Shapelib library)
x_spider: Can't bind local address
Could some processes still be running from a previous run of Xastir?
Error: BindingCould some processes still be running from a previous run of Xastir?
UDP_Server process died.
x_spider: Couldn't set read-end of pipe_udp_server_to_xastir non-blocking
Could some processes still be running from a previous run of Xastir?
festival_client: connect to server failed
festival_client: connect to server failed
SayText: Couldn't open socket to Festival
SayText: Couldn't open socket to Festival
Error: Can't open display:
Indexing maps...
Finished indexing maps
Reading WX Alert log files
Done with WX Alert log files
No DBFAWK signature for ba28mr06.shp! Using default.
bash: [5245: 2] tcsetattr: Interrupted system call
Segmentation fault
[W8JSA@w8jsa ~]$
OS: Fedora 8 x86_64
Computer: HP Media Centre
RAM: 2G
I had it setup to run under every users login. It ran fine under 32 bit but since upgrading to 64 bit it seems to crash under every login. There are other applications where I need to run a native 64 bit environment. I have checked under each login for any running process of Xastir and have found none. I'd really like to get this back up and running soon. Any suggestions?
Logged In: NO
Submitted by Jeff W8JSA
I have it running on OpenSuSE-11.0 64-bit just fine. Did you recompile it on the 64-bit machine or did you try running the 32-bit compile that you were running before? The x-spider messages show that it can't snag the ports it wants to use for the TCP and UDP servers, port 2023, so something else must have those? Try disabling the server ports in the config file, plus also try bringing it up in debug mode to see if you can find out more about when the segfault happens: "xastir -v 4095"
To minimize troubleshooting efforts edit '~/.xastir/config/xastir.cnf' to set 'ENABLE_SERVER_PORT:0'. This will remove the error messages about the processes running. I think this is probably not the problem but need to test in a minimal configuration to attempt to narrow down the problem.
I have been working in a 64 bit environment for years and have never had any difficulties with running xastir. Have you compiled for this platform?
The Xastir project no longer uses sourceforge for issue tracking and I am closing all open issues (all of which are very old).
If this issue is still important, please open a new one on https://github.com/Xastir/Xastir.