Phil,
Since you installed from a package you'll likely find xastir in
/usr/share/xastir. The "Debian" way is for packages to install in
/somewhere/somewhere/somewhere but programs compiled on the machine go
into /somewhere/local/somewhere/somewhere.
Unless it's changed very recently it's
On 2/6/20 10:02 am, Tom Russo wrote:
I forgot to mention that I had removed every instance of "local" from my
.xastir.cnf file. Doing so allowed xastir to start but on reboot xastir
rebuilt the .xastir.cnf file to again include /usr/local/share/xastir.
So, as I said in my first posting, I
On 2/6/20 10:02 am, Tom Russo wrote:
Thank you Tom,
If you're running from a package, that stuff is usually in /usr/share/xastir
instead, and getting this message means you probably have an xastir.cnf
file that is left over from a source-built install (that is, it contains
configuration for
The festival error will happen if you have not in fact started the
festival daemon. Did you?
It is not really a problem unless you are expecting text-to-speech.
As for your bitmap error:
Did you build Xastir from source, or are you installing from a package.
If you are running a build from
On 2/6/20 2:12 am, Curt Mills wrote:
Also: How are you shutting down Xastir? Are you doing it through the
menus or just killing it with the window controls?
From memory, file -> exit. I'd have to rename the config file and then
start again to make sure. I'm not clicking on the window corner
On 2/6/20 1:04 am, Jason Godfrey wrote:
Can you run "lsof -i :2023" as root and see if anything is using those
ports? This will look at the spider side of things.
I started Xastir this morning and the festival error was displayed. I
also ran the lsof command, see below.
Also: How are you shutting down Xastir? Are you doing it through the
menus or just killing it with the window controls?
Somehow Xastir appears to be dying in a poor manner, which leaves
processes running since it's a multi-threaded -and- multiprocessing
application.
On Mon, Jun 1, 2020 at 8:35
Can you run "lsof -i :2023" as root and see if anything is using those
ports? This will look at the spider side of things.
I'm not familiar with the festival side of things, so I won't be much
help there.
- Jason
On Mon, Jun 1, 2020 at 1:08 AM Phil wrote:
>
> telnet localhost 1314 results in
the xastir.cnf.N files are older versions of your configuration that were
saved when you updated the config.
-j
On Mon, Jun 1, 2020 at 6:12 AM Phil wrote:
> Further to the ongoing start problem.
>
> If I rename /.xastir/config/xastir.cnf, then Xastir will run. I can shut
> it down and restart
Aha! It was a rookie mistake. I tried to run the ".in" file from the
install script instead of the one in the xastir base directory.
Tom Henderson
On 5/30/20 4:28 PM, Tom Henderson wrote:
Just tried to run the script to get FCC callsigns on my raspberry pi
for the first time and got the
Further to the ongoing start problem.
If I rename /.xastir/config/xastir.cnf, then Xastir will run. I can shut
it down and restart without a problem. However, Xastir will not start
after a reboot. Does that suggest what the problem might be?
Also, I notice that there are multiple xastir.cnf
telnet localhost 1314 results in "connection refused"
/etc/hosts had a line that read "127.0.0.1 localhost" I added
"localhost.localdomain" to that line.
Running xastir after the addition results in the error messages:
x_spider: Can't bind local address for AF 2: 98 - Address already in use
12 matches
Mail list logo
