Mailing List Archive: MythTV: Users

Frontend submits hardware profile every startup

Index | Next | Previous | View Threaded

John.Veness.mythtv at pelago

Jun 15, 2012, 3:15 AM

Post #1 of 16 (1112 views)
Permalink

Frontend submits hardware profile every startup

Hi,

My mythfrontend seems to be submitting a hardware profile every time it
starts up. The relevant part of mythfrontend --v all would seem to be:

2012-06-13 07:54:28.829711 I [22447/22447] CoreContext
hardwareprofile.cpp:164 (NeedsUpdate) - Last hardware profile update was
> 30 days ago, update required...
2012-06-13 07:54:28.829806 I [22447/22447] CoreContext
mythmainwindow.cpp:2538 (LockInputDevices) - Locking input devices
2012-06-13 07:54:28.842664 I [22447/22447] CoreContext
system-unix.cpp:735 (Fork) - Managed child (PID: 22471) has started! *
command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
-a, timeout=0
2012-06-13 07:55:13.646857 I [22447/22460] SystemManager
system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
-a, status=256, result=1

As you'll see from the timestamps, this adds a 45-second or so delay to
mythfrontend starting up, during which time it looks like it's hung.

Any ideas why it's doing this every time? It looks from the log like it
should only be doing this every 30 days.

I'm running up-to-date 0.25-fixes from the mythbuntu repos. I've noticed
this problem for the last week or two.

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

newmank1 at asme

Jun 15, 2012, 6:41 AM

Post #2 of 16 (1071 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On Fri, Jun 15, 2012 at 3:15 AM, John Veness
<John.Veness.mythtv [at] pelago> wrote:
> Hi,
>
> My mythfrontend seems to be submitting a hardware profile every time it
> starts up. The relevant part of mythfrontend --v all would seem to be:
>
> 2012-06-13 07:54:28.829711 I [22447/22447] CoreContext
> hardwareprofile.cpp:164 (NeedsUpdate) - Last hardware profile update was >
> 30 days ago, update required...
> 2012-06-13 07:54:28.829806 I [22447/22447] CoreContext
> mythmainwindow.cpp:2538 (LockInputDevices) - Locking input devices
> 2012-06-13 07:54:28.842664 I [22447/22447] CoreContext system-unix.cpp:735
> (Fork) - Managed child (PID: 22471) has started! *
> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a,
> timeout=0
> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager system-unix.cpp:342
> (run) - Managed child (PID: 22471) has exited!
> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a,
> status=256, result=1
>
> As you'll see from the timestamps, this adds a 45-second or so delay to
> mythfrontend starting up, during which time it looks like it's hung.
>
> Any ideas why it's doing this every time? It looks from the log like it
> should only be doing this every 30 days.
>
> I'm running up-to-date 0.25-fixes from the mythbuntu repos. I've noticed
> this problem for the last week or two.
>
> Cheers,
>
> John

Just a "me too" here but my delay has been sometimes over a minute. I
thought it was hanging until I checked the logs.

Karl
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

keemllib at gmail

Jun 15, 2012, 10:29 AM

Post #3 of 16 (1071 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On 06/15/2012 05:15 AM, John Veness wrote:
> Hi,
>
> My mythfrontend seems to be submitting a hardware profile every time it starts up. The relevant part of mythfrontend --v all would seem to be:
>
> 2012-06-13 07:54:28.829711 I [22447/22447] CoreContext hardwareprofile.cpp:164 (NeedsUpdate) - Last hardware profile update was > 30 days ago,
> update required...
> 2012-06-13 07:54:28.829806 I [22447/22447] CoreContext mythmainwindow.cpp:2538 (LockInputDevices) - Locking input devices
> 2012-06-13 07:54:28.842664 I [22447/22447] CoreContext system-unix.cpp:735 (Fork) - Managed child (PID: 22471) has started! *
> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a, timeout=0
> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a, status=256, result=1
>
> As you'll see from the timestamps, this adds a 45-second or so delay to mythfrontend starting up, during which time it looks like it's hung.
>
> Any ideas why it's doing this every time? It looks from the log like it should only be doing this every 30 days.
>
> I'm running up-to-date 0.25-fixes from the mythbuntu repos. I've noticed this problem for the last week or two.

Good call John. I'm on 0.26-pre and seeing the same, if I manually run:

/usr/local/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a --debug,

The following prints:

Processing MythTV Data
smoon server URL: http://smolt.mythtv.org/
sendHostStr: {"default_runlevel": "2", "bogomips": "7233.01", much more data here ... }
Sending Host
Error contacting Server: HTTP Error 500: Internal error
Could not send - Exiting

In mythconverg, HardwareProfileLastUpdated = 2012-04-27T15:28:30.

Watching the protocol, the initial GET is accepted (smolt returns code 200 OK.)
But the following POST fails:

http://smolt.mythtv.org/client/add_json, POST /client/add_json HTTP/1.1
500 Internal error

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

thomas at mashos

Jun 15, 2012, 2:31 PM

Post #4 of 16 (1056 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On Fri, Jun 15, 2012 at 10:29 AM, Bill Meek <keemllib [at] gmail> wrote:
> On 06/15/2012 05:15 AM, John Veness wrote:
>>
>> Hi,
>>
>> My mythfrontend seems to be submitting a hardware profile every time it
>> starts up. The relevant part of mythfrontend --v all would seem to be:
>>
>> 2012-06-13 07:54:28.829711 I [22447/22447] CoreContext
>> hardwareprofile.cpp:164 (NeedsUpdate) - Last hardware profile update was >
>> 30 days ago,
>> update required...
>> 2012-06-13 07:54:28.829806 I [22447/22447] CoreContext
>> mythmainwindow.cpp:2538 (LockInputDevices) - Locking input devices
>> 2012-06-13 07:54:28.842664 I [22447/22447] CoreContext system-unix.cpp:735
>> (Fork) - Managed child (PID: 22471) has started! *
>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a,
>> timeout=0
>> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager
>> system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a,
>> status=256, result=1
>>
>> As you'll see from the timestamps, this adds a 45-second or so delay to
>> mythfrontend starting up, during which time it looks like it's hung.
>>
>> Any ideas why it's doing this every time? It looks from the log like it
>> should only be doing this every 30 days.
>>
>> I'm running up-to-date 0.25-fixes from the mythbuntu repos. I've noticed
>> this problem for the last week or two.
>
>
> Good call John. I'm on 0.26-pre and seeing the same, if I manually run:
>
> �/usr/local/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a
> --debug,
>
> The following prints:
>
> �Processing MythTV Data
> �smoon server URL: http://smolt.mythtv.org/
> �sendHostStr: {"default_runlevel": "2", "bogomips": "7233.01", �much more
> data here ... }
> �Sending Host
> �Error contacting Server: HTTP Error 500: Internal error
> �Could not send - Exiting
>
> In mythconverg, HardwareProfileLastUpdated = 2012-04-27T15:28:30.
>
> Watching the protocol, the initial GET is accepted (smolt returns code 200
> OK.)
> But the following POST fails:
>
> �http://smolt.mythtv.org/client/add_json, POST /client/add_json HTTP/1.1
> �500 Internal error
>
> --
> Bill
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users

So I've been working with a user in our Mythbuntu IRC channel and we
resolved this issue for him. In mythtv-setup, he needed to set a PIN
(his was blank). Please try setting the PIN and seeing if that
resolves the 500 error for you and let me know.

Thanks,

Thomas Mashos
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

keemllib at gmail

Jun 15, 2012, 5:19 PM

Post #5 of 16 (1057 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On 06/15/2012 04:31 PM, Thomas Mashos wrote:
> On Fri, Jun 15, 2012 at 10:29 AM, Bill Meek<keemllib [at] gmail> wrote:
>> On 06/15/2012 05:15 AM, John Veness wrote:
...
>>> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager
>>> system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
>>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a,
>>> status=256, result=1
...
>> /usr/local/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a
>> --debug,
>>
>> The following prints:
>>
>> Processing MythTV Data
>> smoon server URL: http://smolt.mythtv.org/
>> sendHostStr: {"default_runlevel": "2", "bogomips": "7233.01", much more
>> data here ... }
>> Sending Host
>> Error contacting Server: HTTP Error 500: Internal error
>> Could not send - Exiting
...
>
> So I've been working with a user in our Mythbuntu IRC channel and we
> resolved this issue for him. In mythtv-setup, he needed to set a PIN
> (his was blank). Please try setting the PIN and seeing if that
> resolves the 500 error for you and let me know.

Hi;

That fixed it for me too. My Master Backend PIN was blank and my
Remote Frontend's PIN didn't exist. So, I added both (set to 0000)
and now result=0. And, HardwareProfileLastUpdated now has today's
date.

Running from the command line still fails, so that looks like an
invalid test.

--
Thanks,

Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

siliconfiend at gmail

Jun 15, 2012, 8:59 PM

Post #6 of 16 (1064 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On Fri, Jun 15, 2012 at 5:19 PM, Bill Meek <keemllib [at] gmail> wrote:
> On 06/15/2012 04:31 PM, Thomas Mashos wrote:
>>
>> On Fri, Jun 15, 2012 at 10:29 AM, Bill Meek<keemllib [at] gmail> �wrote:
>>>
>>> On 06/15/2012 05:15 AM, John Veness wrote:
>
> ...
>>>>
>>>> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager
>>>> system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
>>>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
>>>> -a,
>>>> status=256, result=1
>
> ...
>>>
>>> �/usr/local/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a
>>> --debug,
>>>
>>> The following prints:
>>>
>>> �Processing MythTV Data
>>> �smoon server URL: http://smolt.mythtv.org/
>>> �sendHostStr: {"default_runlevel": "2", "bogomips": "7233.01", �much more
>>> data here ... }
>>> �Sending Host
>>> �Error contacting Server: HTTP Error 500: Internal error
>>> �Could not send - Exiting
>
> ...
>>
>>
>> So I've been working with a user in our Mythbuntu IRC channel and we
>> resolved this issue for him. In mythtv-setup, he needed to set a PIN
>> (his was blank). Please try setting the PIN and seeing if that
>> resolves the 500 error for you and let me know.
>
>
> Hi;
>
> That fixed it for me too. My Master Backend PIN was blank and my
> Remote Frontend's PIN didn't exist. So, I added both (set to 0000)
> and now result=0. And, HardwareProfileLastUpdated now has today's
> date.
>
> Running from the command line still fails, so that looks like an
> invalid test.
>
> --
> Thanks,
>
> Bill

Well, the PIN on mine was blank (I assume you mean
mythtv-setup->General->Security PIN (required)), but setting it to
0000 did NOT fix the problem for me. I still have the delayed start of
the frontend, and every time I see "[mythfrontend] I CoreContext
hardwareprofile.cpp:164 (NeedsUpdate) Last hardware profile update was
> 30 days ago, update required..." in the log. This was after
restarting the backend a couple times and the frontend a few more
times. Running the command manually as above gives an error about
failing to connect to the backend as such:
2012-06-15 20:50:20.672719 C [12069] Python Backend Connection
Couldn't connect to backend [192.168.1.5]:6543
Traceback (most recent call last):
File "/usr/share/mythtv/hardwareprofile/sendProfile.py", line 420, in <module>
main()
File "/usr/share/mythtv/hardwareprofile/sendProfile.py", line 403, in main
profile = read_profile(gate, smolt.read_uuid())
File "/usr/share/mythtv/hardwareprofile/sendProfile.py", line 299,
in read_profile
profile = smolt.create_profile(gate, uuid)
File "/usr/share/mythtv/hardwareprofile/smolt.py", line 1251, in
create_profile
return create_profile_nocatch(gate, uuid)
File "/usr/share/mythtv/hardwareprofile/smolt.py", line 1243, in
create_profile_nocatch
return _HardwareProfile(gate, uuid)
File "/usr/share/mythtv/hardwareprofile/smolt.py", line 517, in __init__
self.distro_specific = self.get_distro_specific_data(gate)
File "/usr/share/mythtv/hardwareprofile/smolt.py", line 530, in
get_distro_specific_data
d.gather(gate, debug=True)
File "/usr/share/mythtv/hardwareprofile/distros/mythtv_data/main.py",
line 39, in gather
from data_mythtv import create_mythtv_data
File "/usr/share/mythtv/hardwareprofile/distros/mythtv_data/data_mythtv.py",
line 35, in <module>
_BE = MythTV.MythBE(db=_DB)
File "/usr/lib64/python2.7/site-packages/MythTV/mythproto.py", line
119, in __init__
self._conn.command = self._newcmdconn()
File "/usr/lib64/python2.7/site-packages/MythTV/mythproto.py", line
142, in _newcmdconn
self.blockshutdown)
File "/usr/lib64/python2.7/site-packages/MythTV/connections.py",
line 207, in __init__
raise MythBEError(MythError.PROTO_CONNECTION, self.host, self.port)
MythTV.exceptions.MythBEError: Failed to connect to backend at 192.168.1.5:6543

The address and port number are correct for the backend, and I ran the
test as the user that runs mythbackend and mythfrontend. Any other
ideas why this isn't working?

Karl
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

siliconfiend at gmail

Jun 15, 2012, 9:34 PM

Post #7 of 16 (1052 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On Fri, Jun 15, 2012 at 8:59 PM, Karl Newman <siliconfiend [at] gmail> wrote:
> On Fri, Jun 15, 2012 at 5:19 PM, Bill Meek <keemllib [at] gmail> wrote:
>> On 06/15/2012 04:31 PM, Thomas Mashos wrote:
>>>
>>> On Fri, Jun 15, 2012 at 10:29 AM, Bill Meek<keemllib [at] gmail> �wrote:
>>>>
>>>> On 06/15/2012 05:15 AM, John Veness wrote:
>>
>> ...
>>>>>
>>>>> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager
>>>>> system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
>>>>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
>>>>> -a,
>>>>> status=256, result=1
>>
>> ...
>>>>
>>>> �/usr/local/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -a
>>>> --debug,
>>>>
>>>> The following prints:
>>>>
>>>> �Processing MythTV Data
>>>> �smoon server URL: http://smolt.mythtv.org/
>>>> �sendHostStr: {"default_runlevel": "2", "bogomips": "7233.01", �much more
>>>> data here ... }
>>>> �Sending Host
>>>> �Error contacting Server: HTTP Error 500: Internal error
>>>> �Could not send - Exiting
>>
>> ...
>>>
>>>
>>> So I've been working with a user in our Mythbuntu IRC channel and we
>>> resolved this issue for him. In mythtv-setup, he needed to set a PIN
>>> (his was blank). Please try setting the PIN and seeing if that
>>> resolves the 500 error for you and let me know.
>>
>>
>> Hi;
>>
>> That fixed it for me too. My Master Backend PIN was blank and my
>> Remote Frontend's PIN didn't exist. So, I added both (set to 0000)
>> and now result=0. And, HardwareProfileLastUpdated now has today's
>> date.
>>
>> Running from the command line still fails, so that looks like an
>> invalid test.
>>
>> --
>> Thanks,
>>
>> Bill
>
> Well, the PIN on mine was blank (I assume you mean
> mythtv-setup->General->Security PIN (required)), but setting it to
> 0000 did NOT fix the problem for me. I still have the delayed start of
> the frontend, and every time I see "[mythfrontend] I CoreContext
> hardwareprofile.cpp:164 (NeedsUpdate) Last hardware profile update was
>> 30 days ago, update required..." in the log. This was after
> restarting the backend a couple times and the frontend a few more
> times. Running the command manually as above gives an error about
> failing to connect to the backend as such:
> 2012-06-15 20:50:20.672719 C [12069] Python Backend Connection
> Couldn't connect to backend [192.168.1.5]:6543
> Traceback (most recent call last):
> �File "/usr/share/mythtv/hardwareprofile/sendProfile.py", line 420, in <module>
> � �main()
> �File "/usr/share/mythtv/hardwareprofile/sendProfile.py", line 403, in main
> � �profile = read_profile(gate, smolt.read_uuid())
> �File "/usr/share/mythtv/hardwareprofile/sendProfile.py", line 299,
> in read_profile
> � �profile = smolt.create_profile(gate, uuid)
> �File "/usr/share/mythtv/hardwareprofile/smolt.py", line 1251, in
> create_profile
> � �return create_profile_nocatch(gate, uuid)
> �File "/usr/share/mythtv/hardwareprofile/smolt.py", line 1243, in
> create_profile_nocatch
> � �return _HardwareProfile(gate, uuid)
> �File "/usr/share/mythtv/hardwareprofile/smolt.py", line 517, in __init__
> � �self.distro_specific = self.get_distro_specific_data(gate)
> �File "/usr/share/mythtv/hardwareprofile/smolt.py", line 530, in
> get_distro_specific_data
> � �d.gather(gate, debug=True)
> �File "/usr/share/mythtv/hardwareprofile/distros/mythtv_data/main.py",
> line 39, in gather
> � �from data_mythtv import create_mythtv_data
> �File "/usr/share/mythtv/hardwareprofile/distros/mythtv_data/data_mythtv.py",
> line 35, in <module>
> � �_BE = MythTV.MythBE(db=_DB)
> �File "/usr/lib64/python2.7/site-packages/MythTV/mythproto.py", line
> 119, in __init__
> � �self._conn.command = self._newcmdconn()
> �File "/usr/lib64/python2.7/site-packages/MythTV/mythproto.py", line
> 142, in _newcmdconn
> � �self.blockshutdown)
> �File "/usr/lib64/python2.7/site-packages/MythTV/connections.py",
> line 207, in __init__
> � �raise MythBEError(MythError.PROTO_CONNECTION, self.host, self.port)
> MythTV.exceptions.MythBEError: Failed to connect to backend at 192.168.1.5:6543
>
> The address and port number are correct for the backend, and I ran the
> test as the user that runs mythbackend and mythfrontend. Any other
> ideas why this isn't working?
>
> Karl

Stupid me. I had killed the backend and forgot to restart. Now when I
run it from the command line it connects but I'm still getting the
HTTP Error 500 as the other reporters, and the frontend still runs the
script on every start.

Karl
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

keemllib at gmail

Jun 15, 2012, 10:23 PM

Post #8 of 16 (1044 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On 06/15/2012 11:34 PM, Karl Newman wrote:
...
>> Well, the PIN on mine was blank (I assume you mean
>> mythtv-setup->General->Security PIN (required)), but setting it to
>> 0000 did NOT fix the problem for me.

Hi;

If you've got a remote frontend, you need to run mythtv-setup there too
(I didn't and still got the failure until I did.)

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

newmank1 at asme

Jun 15, 2012, 10:37 PM

Post #9 of 16 (1044 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On Fri, Jun 15, 2012 at 10:23 PM, Bill Meek <keemllib [at] gmail> wrote:
> On 06/15/2012 11:34 PM, Karl Newman wrote:
> ...
>
>>> Well, the PIN on mine was blank (I assume you mean
>>> mythtv-setup->General->Security PIN (required)), but setting it to
>>> 0000 did NOT fix the problem for me.
>
>
> Hi;
>
> If you've got a remote frontend, you need to run mythtv-setup there too
> (I didn't and still got the failure until I did.)
>
> --
> Bill

No, that's not the case here. It's a combined frontend/backend (it's
the only machine).

Karl
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

John.Veness.mythtv at pelago

Jun 20, 2012, 2:21 AM

Post #10 of 16 (989 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On 15/06/2012 22:31, Thomas Mashos wrote:
> So I've been working with a user in our Mythbuntu IRC channel and we
> resolved this issue for him. In mythtv-setup, he needed to set a PIN
> (his was blank). Please try setting the PIN and seeing if that
> resolves the 500 error for you and let me know.

I've just set a PIN in mythtv-setup on my combined BE/FE. (By the way, I
wasn't even aware of the option, and I've never needed to set a PIN
before, even on my separate FE - it has always just connected fine).
Anyway, this doesn't seem to have made a difference and it is still
trying to submit a hardware profile every startup of mythfrontend.

Also, I've gone into the Setup Wizard in mythfrontend and tried to
submit a profile there, but (after a long delay) it says that there is
an error in submitting the profile. Trying to delete my profile from the
same screen also gives an error message. If I run
"/usr/local/share/mythtv/hardwareprofile/sendProfile.py --submitOnly -d"
manually it says "500 Internal error".

Are we sure the problem isn't at the smolt.mythtv.org end?

Cheers,

John
--
John Veness, MythTV user, UK, DVB-T

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

John.Veness.mythtv at pelago

Jul 9, 2012, 1:38 AM

Post #11 of 16 (868 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On 15/06/2012 11:15, John Veness wrote:
> Hi,
>
> My mythfrontend seems to be submitting a hardware profile every time it
> starts up. The relevant part of mythfrontend --v all would seem to be:
>
> 2012-06-13 07:54:28.829711 I [22447/22447] CoreContext
> hardwareprofile.cpp:164 (NeedsUpdate) - Last hardware profile update was
> > 30 days ago, update required...
> 2012-06-13 07:54:28.829806 I [22447/22447] CoreContext
> mythmainwindow.cpp:2538 (LockInputDevices) - Locking input devices
> 2012-06-13 07:54:28.842664 I [22447/22447] CoreContext
> system-unix.cpp:735 (Fork) - Managed child (PID: 22471) has started! *
> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
> -a, timeout=0
> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager
> system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
> -a, status=256, result=1
>
> As you'll see from the timestamps, this adds a 45-second or so delay to
> mythfrontend starting up, during which time it looks like it's hung.
>
> Any ideas why it's doing this every time? It looks from the log like it
> should only be doing this every 30 days.
>
> I'm running up-to-date 0.25-fixes from the mythbuntu repos. I've noticed
> this problem for the last week or two.
>
> Cheers,
>
> John

Further to this, setting a PIN didn't make a difference. Eventually I
deleted (well, renamed just in case) the folder
~/.mythtv/HardwareProfile and that has got rid of the delay so I assume
it isn't submitting the hardware profile every startup. I'll keep an eye
on it.

Does anyone want to see the previous contents of the HardwareProfile
folder in case that helps them troubleshoot what the problem was?

Cheers,

John
--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

thomas at mashos

Jul 9, 2012, 6:07 AM

Post #12 of 16 (865 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On Mon, Jul 9, 2012 at 1:38 AM, John Veness
<John.Veness.mythtv [at] pelago> wrote:
> On 15/06/2012 11:15, John Veness wrote:
>>
>> Hi,
>>
>> My mythfrontend seems to be submitting a hardware profile every time it
>> starts up. The relevant part of mythfrontend --v all would seem to be:
>>
>> 2012-06-13 07:54:28.829711 I [22447/22447] CoreContext
>> hardwareprofile.cpp:164 (NeedsUpdate) - Last hardware profile update was
>> > 30 days ago, update required...
>> 2012-06-13 07:54:28.829806 I [22447/22447] CoreContext
>> mythmainwindow.cpp:2538 (LockInputDevices) - Locking input devices
>> 2012-06-13 07:54:28.842664 I [22447/22447] CoreContext
>> system-unix.cpp:735 (Fork) - Managed child (PID: 22471) has started! *
>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
>> -a, timeout=0
>> 2012-06-13 07:55:13.646857 I [22447/22460] SystemManager
>> system-unix.cpp:342 (run) - Managed child (PID: 22471) has exited!
>> command=/usr/share/mythtv/hardwareprofile/sendProfile.py --submitOnly
>> -a, status=256, result=1
>>
>> As you'll see from the timestamps, this adds a 45-second or so delay to
>> mythfrontend starting up, during which time it looks like it's hung.
>>
>> Any ideas why it's doing this every time? It looks from the log like it
>> should only be doing this every 30 days.
>>
>> I'm running up-to-date 0.25-fixes from the mythbuntu repos. I've noticed
>> this problem for the last week or two.
>>
>> Cheers,
>>
>> John
>
>
> Further to this, setting a PIN didn't make a difference. Eventually I
> deleted (well, renamed just in case) the folder ~/.mythtv/HardwareProfile
> and that has got rid of the delay so I assume it isn't submitting the
> hardware profile every startup. I'll keep an eye on it.
>
> Does anyone want to see the previous contents of the HardwareProfile folder
> in case that helps them troubleshoot what the problem was?
>
> Cheers,
>
> John
> --
> John Veness, MythTV user, UK, DVB-T
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users

If you are using Mythbuntu and submitting the Whoopsie report then the
issue is that sendprofile.py cannot reach your backend, as that is
what all of the whoopsie reports for sendprofile.py have been for the
last month. If you aren't using Ubuntu and/or aren't submitting the
whoopsie report then I don't know what the issue is. I think it's
probably safe to say that it isn't submitting the hardware profile
every time, but rather failing to send the hardware profile and thus
trying to send it every time.

Thanks,

Thomas Mashos
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

John.Veness.mythtv at pelago

Jul 9, 2012, 6:18 AM

Post #13 of 16 (861 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On 09/07/2012 14:07, Thomas Mashos wrote:
> If you are using Mythbuntu and submitting the Whoopsie report then the
> issue is that sendprofile.py cannot reach your backend, as that is
> what all of the whoopsie reports for sendprofile.py have been for the
> last month. If you aren't using Ubuntu and/or aren't submitting the
> whoopsie report then I don't know what the issue is. I think it's
> probably safe to say that it isn't submitting the hardware profile
> every time, but rather failing to send the hardware profile and thus
> trying to send it every time.

Hi Thomas,

I'm running Ubuntu with 0.25-fixes from your mythbuntu repos, which I
assume is close enough to what you're talking about. The machine in
question is a combined FE/BE and works fine in general, other than this
mythfrontend startup delay. I don't know what a Whoopsie report is.

If you can tell me what to type to troubleshoot whether sendprofile.py
can or cannot reach the backend, or whatever other troubleshooting you
wish me to try, then let me know.

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

thomas at mashos

Jul 9, 2012, 6:36 AM

Post #14 of 16 (861 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On Mon, Jul 9, 2012 at 6:18 AM, John Veness
<John.Veness.mythtv [at] pelago> wrote:
> On 09/07/2012 14:07, Thomas Mashos wrote:
>>
>> If you are using Mythbuntu and submitting the Whoopsie report then the
>> issue is that sendprofile.py cannot reach your backend, as that is
>> what all of the whoopsie reports for sendprofile.py have been for the
>> last month. If you aren't using Ubuntu and/or aren't submitting the
>> whoopsie report then I don't know what the issue is. I think it's
>> probably safe to say that it isn't submitting the hardware profile
>> every time, but rather failing to send the hardware profile and thus
>> trying to send it every time.
>
>
> Hi Thomas,
>
> I'm running Ubuntu with 0.25-fixes from your mythbuntu repos, which I assume
> is close enough to what you're talking about. The machine in question is a
> combined FE/BE and works fine in general, other than this mythfrontend
> startup delay. I don't know what a Whoopsie report is.
>
> If you can tell me what to type to troubleshoot whether sendprofile.py can
> or cannot reach the backend, or whatever other troubleshooting you wish me
> to try, then let me know.
>
> Cheers,
>
> John
>
> --
> John Veness, MythTV user, UK, DVB-T
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users

A whoopsie report is when the dialog box pops up and says that
something has stopped working and asks you to send information to the
ubuntu developers. A better/fuller explanation can be found in the
first answer here

http://askubuntu.com/questions/135540/what-is-the-whoopsie-process-and-how-can-i-remove-it

The error report it sends is attached to a guid rather than any
identifiable information. I'm looking to see if that guid is kept
anywhere on the system for you to find. If it is and you tell me what
it is I can look up your specific error report and see the exact error
message (although all of them are backend connectivity issues).

You might also want to see if there are any files in /var/crash/

Thanks,

Thomas Mashos
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

John.Veness.mythtv at pelago

Jul 9, 2012, 7:06 AM

Post #15 of 16 (864 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On 09/07/2012 14:36, Thomas Mashos wrote:
> A whoopsie report is when the dialog box pops up and says that
> something has stopped working and asks you to send information to the
> ubuntu developers. A better/fuller explanation can be found in the
> first answer here
>
> http://askubuntu.com/questions/135540/what-is-the-whoopsie-process-and-how-can-i-remove-it
>
> The error report it sends is attached to a guid rather than any
> identifiable information. I'm looking to see if that guid is kept
> anywhere on the system for you to find. If it is and you tell me what
> it is I can look up your specific error report and see the exact error
> message (although all of them are backend connectivity issues).
>
> You might also want to see if there are any files in /var/crash/
>
> Thanks,
>
> Thomas Mashos

Thanks Thomas. I've never seen any dialog box pop up and I don't seem to
have whoopsie installed. At least, typing "whoopsie" just says command
not found. No files in /var/crash. I'm running Ubuntu 11.10, by the way.

Cheers,

John

--
John Veness, MythTV user, UK, DVB-T
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

thomas at mashos

Jul 9, 2012, 7:39 AM

Post #16 of 16 (861 views)
Permalink

Re: Frontend submits hardware profile every startup [In reply to]

On Mon, Jul 9, 2012 at 7:06 AM, John Veness
<John.Veness.mythtv [at] pelago> wrote:
> On 09/07/2012 14:36, Thomas Mashos wrote:
>>
>> A whoopsie report is when the dialog box pops up and says that
>> something has stopped working and asks you to send information to the
>> ubuntu developers. A better/fuller explanation can be found in the
>> first answer here
>>
>>
>> http://askubuntu.com/questions/135540/what-is-the-whoopsie-process-and-how-can-i-remove-it
>>
>> The error report it sends is attached to a guid rather than any
>> identifiable information. I'm looking to see if that guid is kept
>> anywhere on the system for you to find. If it is and you tell me what
>> it is I can look up your specific error report and see the exact error
>> message (although all of them are backend connectivity issues).
>>
>> You might also want to see if there are any files in /var/crash/
>>
>> Thanks,
>>
>> Thomas Mashos
>
>
> Thanks Thomas. I've never seen any dialog box pop up and I don't seem to
> have whoopsie installed. At least, typing "whoopsie" just says command not
> found. No files in /var/crash. I'm running Ubuntu 11.10, by the way.
>
>
> Cheers,
>
> John
>
> --
> John Veness, MythTV user, UK, DVB-T
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users

Ah, I think it was added in 12.04.

Thanks,

Thomas Mashos
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads