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
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev

Reply via email to