I'd be happy to upgrade them all, but they all need to be able to
synchronize carts, cuts, and logs with backup Rivendell machines at other
sites. This feature is mission-critical, as all of these stations run
largely unattended, so when there's a problem in the studio we need to be
able to s
On Feb 24, 2022, at 16:23, starrbuck1...@gmail.com wrote:
> And you really should upgrade them all. Fred shouldn't have to support much
> older versions. It's just not realistic.
And mostly I don’t, beyond recommending an upgrade to the latest-and-greatest
(currently v3.6.4). Bugs reported on
The only time I ever had crashes is when I overfilled the logs. With a few
hours of spare music. Running rivendell 2.10.3 on ubuntu 14.04.
Many thanks Geoff Barkman
On Fri, Feb 25, 2022, 8:34 AM Rob Landry <41001...@interpring.com> wrote:
>
> It's ancient, but I run it on at least half a dozen s
And you really should upgrade them all. Fred shouldn't have to support
much older versions. It's just not realistic.
On Thu, Feb 24, 2022 at 1:34 PM Rob Landry <41001...@interpring.com> wrote:
>
> It's ancient, but I run it on at least half a dozen stations, and have
> never encountered any cr
It's ancient, but I run it on at least half a dozen stations, and have
never encountered any crashes at log-loading time.
Rob
--
Не думай что всё пропели,
Что бури все отгремели;
Готовься к великой цели,
А слава тебя найдёт.
On Thu, 24 Feb 2022, Fred Gleason wrote:
On Feb 23, 2022, at 22
On Feb 23, 2022, at 22:32, Steve wrote:
> This is Rivendell 2.19.3 on CentOS 7.
That’s an ancient version. There have been literally hundreds of bug fixes and
feature enhancements made since in the v3.x tree. Your best bet would be to
upgrade.
See:
http://wiki.rivendellaudio.org/inde
Hi Fred,
This is Rivendell 2.19.3 on CentOS 7.
Steve
On Wed, Feb 23, 2022 at 09:50:31AM -0500, Fred Gleason wrote:
>On Feb 23, 2022, at 07:35, Steve <[1]riv...@braingia.org> wrote:
>
>We've seen a few crashes seemingly tied to the end of the log being
>reached and the next log being
On Feb 23, 2022, at 07:35, Steve wrote:
> We've seen a few crashes seemingly tied to the end of the log being
> reached and the next log being loaded. The only commonality that I've
> seen is that the logs had been manually edited, although they were
> manually edited several days prior.
Tha
Hello,
We've seen a few crashes seemingly tied to the end of the log being
reached and the next log being loaded. The only commonality that I've
seen is that the logs had been manually edited, although they were
manually edited several days prior.
I tried recreating the issue on another machi
