Search found 107 matches

by pinnerite
Sat May 11, 2019 2:30 pm
Forum: Troubleshooting
Topic: cannot restart following system seizure.
Replies: 14
Views: 240
Great Britain

Re: cannot restart following system seizure.

Unbelievable. It worked!
Thank you all so much.
Alan
by pinnerite
Sat May 11, 2019 12:23 pm
Forum: Troubleshooting
Topic: cannot restart following system seizure.
Replies: 14
Views: 240
Great Britain

Re: cannot restart following system seizure.

I can now gain access from a remote machine. So /var/log/mysql/error.log was empty so used the preceding file: alan@albury:~/Upload$ cat error.log.1 2019-05-10 10:03:48 140052356955264 [Note] CONNECT: Version 1.06.0008 October 06, 2018 2019-05-10 10:03:48 140052356955264 [Note] InnoDB: innodb_empty_...
by pinnerite
Fri May 10, 2019 5:43 pm
Forum: Troubleshooting
Topic: cannot restart following system seizure.
Replies: 14
Views: 240
Great Britain

Re: cannot restart following system seizure.

I am using a tiny keyboard that has a tracker pad on its reverse making moving windows impossible. So apologies for piecemeal reply. thelma@origen ~ $ systemctl list-unit-files "*myth*" UNIT FILE STATE mythtv-backend.service enabled mythtv-status.service generated 2 unit files listed. I will need ac...
by pinnerite
Fri May 10, 2019 2:18 pm
Forum: Troubleshooting
Topic: cannot restart following system seizure.
Replies: 14
Views: 240
Great Britain

Re: cannot restart following system seizure.

It is possible that my state of health at the time led me to do more damage than I thought. thelma@origen ~ $ systemctl cat "myth*" | egrep 'After|Requires|Wants' After=mysql.service network.target After=remote-fs.target After=nss-lookup.target After=mythtv-backend.service After=motd.service RemainA...
by pinnerite
Fri May 10, 2019 9:38 am
Forum: Troubleshooting
Topic: cannot restart following system seizure.
Replies: 14
Views: 240
Great Britain

Re: cannot restart following system seizure.

I did reboot but the logs looked much the same following a restart. $ sudo service mysqld status revealed that mysqld was not running. I had not done anything to change any operations on this machine other than to make some space on the root partition by deleting temporary files, the only logs delet...
by pinnerite
Thu May 09, 2019 4:17 pm
Forum: Troubleshooting
Topic: cannot restart following system seizure.
Replies: 14
Views: 240
Great Britain

Re: cannot restart following system seizure.

Thank you. I was able to generate two logs, in the pastebin page:

https://pastebin.com/s71Ddpx5

Apologies for brevity.
by pinnerite
Wed May 08, 2019 5:21 pm
Forum: Troubleshooting
Topic: cannot restart following system seizure.
Replies: 14
Views: 240
Great Britain

cannot restart following system seizure.

My dedicated backend and frontend system was working fine until the end of March and then its root partition filled up. I then fell ill and have just left hospital. Brain left behind I think. To gain access to the system I deleted the logs only to find the cause was the root .trash folders holding n...
by pinnerite
Mon Apr 22, 2019 1:07 pm
Forum: Troubleshooting
Topic: Remote Frontend
Replies: 8
Views: 121
Great Britain

Re: Remote Frontend

libqt5sql5-mysql appears to already be installed. You are correct, I did inadvertently configure the frontend as root. Can I reverse that? I have discovered that my / partition is full. It shouldn't be. It will take me a while to sort that out. I cannot attempt that right now as I am currently tryin...
by pinnerite
Sun Apr 21, 2019 5:46 pm
Forum: Troubleshooting
Topic: Remote Frontend
Replies: 8
Views: 121
Great Britain

Re: Remote Frontend

by pinnerite
Sun Apr 21, 2019 4:19 pm
Forum: Troubleshooting
Topic: Remote Frontend
Replies: 8
Views: 121
Great Britain

Re: Remote Frontend

It is now on pastebin, under pinnerite.
Do I need to send you the password?
It is the only item held.
by pinnerite
Sat Apr 20, 2019 12:19 pm
Forum: Troubleshooting
Topic: Remote Frontend
Replies: 8
Views: 121
Great Britain

Remote Frontend

I have one Linux Mint 19.1 system running both Mythtv 29.0 back and frontends. I also have a remote frontend, also on a Mint 19.1 machine. The remote frontend is a wired machine, the bnackend/frontend machine is wirelessly connected to wireless router. Both run reasonably well. I wanted to add an ad...
by pinnerite
Fri Mar 15, 2019 10:37 am
Forum: Troubleshooting
Topic: [Solved] Unexpected Recording Conflicts
Replies: 18
Views: 371
Great Britain

[SOLVED] Unexpected Recording Conflicts

By chance I found the answer on another thread. The advice there was that after compiling new drivers for the DVB-TV adapter, installing them and rebooting the op should delete the tuners in mythtv-setup and reinstall them. I had not taken that last step. After doing so I up six or seven proposed re...
by pinnerite
Mon Mar 11, 2019 11:17 am
Forum: Troubleshooting
Topic: [Solved] Unexpected Recording Conflicts
Replies: 18
Views: 371
Great Britain

Re: Unexpected Recording Conflicts

Firstly, the prime purpose of this computer is to run MythTV. Since formatting the root partition to install Mint 19.1 and Mythtv 29 in place of Mageia 5 and MythTV 28, it is always powered down while it is not functioning properly. This means that the normal process is to cold-boot it. The only tim...
by pinnerite
Sun Mar 10, 2019 11:51 pm
Forum: Troubleshooting
Topic: [Solved] Unexpected Recording Conflicts
Replies: 18
Views: 371
Great Britain

Re: Unexpected Recording Conflicts

The status page tells me all tuners are not recording.

I rebooted anyway and set up 6 items to record contemporaneously as previously.

As before all but one were highlighted in red!

I am going to delete the backend and frontend logs and shutdown until tomorrow.
by pinnerite
Sun Mar 10, 2019 2:31 pm
Forum: Troubleshooting
Topic: [Solved] Unexpected Recording Conflicts
Replies: 18
Views: 371
Great Britain

Re: Unexpected Recording Conflicts

Mm. I changed the ownership of /home/mythtv and everything beneath and shutdown.

I waited about 15 minutes before making a cold boot and again set six broadcasts to record at the same time.

Only one made it. The others are marked as conflicting.