Ok, so I am an idiot.
The problem was neither with the database nor with the installation. I
absent mindedly made a change in /etc/hosts that affected the entry for
127.0.0.1.
That entry has to include "localhost localhost.localdomain", or else
Rivendell will misbehave exactly as it did for me these past three days.
You won't be able to see logs in rdlogedit, nor any audio files in
rdlibrary, and the user name will always be ''.
I'm posting this primarily for the benefit of the next person to
experience what I did, although at the rate I'm forgetting things these
days, that next person might well be me a few months from now.
Rob
--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.
On Wed, 20 Apr 2022, Rob Landry wrote:
I'm wrong. It's not a database problem.
It occurred to me that since I have two machines running the same version of
Rivendell, I should be able to backup the database from vipera (the machine
that doesn't have the problem) and restore it to farancia (the one that does
have the problem).
So, I did that. The problem persists even with the restored database from the
other machine, so it's not a database problem.
Next, I tried creating a new, blank Rivendell database on farancia using
rddbconfig. When I do that, rddbconfig crashes with a segmentation fault.
There must be something wrong with this Rivendell install. I'm going to blow
it out, reinstall Rivendell, and see if the problem is still there.
Rob
--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.
On Wed, 20 Apr 2022, Rob Landry wrote:
On Wed, 20 Apr 2022, Fred Gleason wrote:
I’d start by taking a look in RDAdmin->ManageUsers. Are all of the
expected
users there? Does the data look sane?
Yes.
(The data in those dialogs mostly live
in a table called ‘USERS’, but looking directly at that won’t be
particularly helpful without a good understanding of the schema design.
And,
remember, the schema has changed quite a bit between v2.1x and v2.19.x)!
I have actually looked at the USERS table on the machine (farancia)
exhibiting the problem and compared it with the USERS table on another
machine (vipera) I built for WZBC. Both are running 3.6.5 and have the same
schema. I looked for differences between the two that might explain why
farancia has the problem but vipera does not.
I did not see any differences in the USERS tables that might account for
the problem.
And then, take a look at the Station entry in RDAdmin. Does the default
user
exist?
I can't find a Station entry in rdadmin.
I did look at the STATIONS table in both machines' databases. Here, too, I
found no differences between the two tables that might account for the
problem. There were some fields like JACK_COMMAND_LINE that were blank in
one table but NULL in the other, but since I'm not using JACK on either
machine, I didn't think those differences were meaningful.
Rob
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
