I have had my system set up to shutdown automatically between recordings
for years now, but for the last several days when the system comes up (or I
manually bring it up) I can't get Mythwelcome to connect to the backend,
nor can I get "mythbackend --printsched" to run except on rare occasions.
I have done nothing to the system. I have checked and confirmed that there
is plenty of room on all disks, including those used for recordings as well
as root and /var. Using "top" shows mythbackend is basically idle, but it
won't take connections as if it is bogged down. I see that the connection
dialogs switch from the server's IP address to the localhost IP address
(127.something -- 127.0.0.1?) on the standard port, but as far as I know
that's normal. For the life of me, I can't come up with what might have
changed to keep the backend from connecting or a way to chase down the
problem.
While waiting to see if anyone here has a suggestion, I will probably try
to see if there's an issue with the mysql daemon -- maybe it's bogged down
in a backup operation or some corruption in the database. I'll probably
try a manual run of the database checkup routine.
Any suggestions welcome.
--
Craig.
for years now, but for the last several days when the system comes up (or I
manually bring it up) I can't get Mythwelcome to connect to the backend,
nor can I get "mythbackend --printsched" to run except on rare occasions.
I have done nothing to the system. I have checked and confirmed that there
is plenty of room on all disks, including those used for recordings as well
as root and /var. Using "top" shows mythbackend is basically idle, but it
won't take connections as if it is bogged down. I see that the connection
dialogs switch from the server's IP address to the localhost IP address
(127.something -- 127.0.0.1?) on the standard port, but as far as I know
that's normal. For the life of me, I can't come up with what might have
changed to keep the backend from connecting or a way to chase down the
problem.
While waiting to see if anyone here has a suggestion, I will probably try
to see if there's an issue with the mysql daemon -- maybe it's bogged down
in a backup operation or some corruption in the database. I'll probably
try a manual run of the database checkup routine.
Any suggestions welcome.
--
Craig.