[1.0RC3] XBMC keeps restarting

[palswim]

(30th Dec, 2014 08:39 AM)CurlyMo Wrote:  Can you guys try this:
http://forum.xbian.org/thread-2100-post-25847.html#pid25847

Thanks. Looks like your workaround has prevented the start/stop issue for the time being.

[CurlyMo]

Can you guys post the following output.

First enable the commented line again. Then

Code:

echo > /var/log/upstart/upstart-ev.log
service xbmc restart
cat /var/log/upstart/upstart-ev.log

Wait at least 2 minutes before posting the upstart log.

[min]

(21st Dec, 2014 01:14 AM)narotic Wrote:  In my case I solved the reboot issue by downgrading xbian-package-upstart-xbmc-bridge to version 1.1.3:

apt-get install xbian-package-upstart-xbmc-bridge=1.1.3

The problem occurs with versions 1.1.4 and 1.1.6 (and presumably also with 1.1.5) with the older xbmc package (13.2-RLS-1411559513).

On a related note, I noticed that I can get the newer xbmc packages (suffix 1418714780 and higher) by adding component "rpi-wheezy" to the apt.xbian.org repository. Is it recommended to add this component besides the standard "main"?

I have used this fix successfully for the xbmc-alsa package, thanks!

[palswim]

(30th Dec, 2014 07:53 PM)CurlyMo Wrote:  Can you guys post the following output.

First enable the commented line again. Then

Code:

echo > /var/log/upstart/upstart-ev.log
service xbmc restart
cat /var/log/upstart/upstart-ev.log

Wait at least 2 minutes before posting the upstart log.

Code:

Tue Dec 30 15:15:52 PST 2014 231859.92 31008876.92 stopped xbmc-screensaver                 0.63 0.38 0.30 5/159 28744
Tue Dec 30 15:15:52 PST 2014 231859.95 31008876.92 started xbian-xbmc-cpufreq               0.63 0.38 0.30 5/157 28745
Tue Dec 30 15:15:52 PST 2014 231860.43 31008876.92 started xbmc-priority                    0.63 0.38 0.30 3/156 28769
Tue Dec 30 15:15:53 PST 2014 231860.86 31008876.92 stopped xbmc-priority                    0.63 0.38 0.30 4/144 28783
Tue Dec 30 15:15:58 PST 2014 231865.81 32216838.46 stopping xbmc                            0.66 0.39 0.30 1/112 28848
Tue Dec 30 15:15:58 PST 2014 231866.28 32216838.46 starting xbmc-exits                      0.66 0.39 0.30 7/125 28878
Tue Dec 30 15:15:58 PST 2014 231866.29 32216838.46 started xbmc-changesettings              0.66 0.39 0.30 7/124 28878
Tue Dec 30 15:15:58 PST 2014 231866.30 32216838.46 stopped xbmc                             0.66 0.39 0.30 5/121 28878
Tue Dec 30 15:15:58 PST 2014 231866.44 32216838.46 stopped xbian-xbmc-cpufreq               0.66 0.39 0.30 3/116 28883
Tue Dec 30 15:15:59 PST 2014 231866.80 32216838.46 stopped tvonoff-xbmc                     0.66 0.39 0.30 3/113 28891
Tue Dec 30 15:15:59 PST 2014 231866.92 32216838.46 starting xbmc                            0.66 0.39 0.30 2/111 28898
Tue Dec 30 15:15:59 PST 2014 231867.17 32216838.46 stopped xbmc-changesettings              0.66 0.39 0.30 7/122 28918
Tue Dec 30 15:15:59 PST 2014 231867.18 32216838.46 started xbian-xbmc-cpufreq               0.66 0.39 0.30 6/121 28918
Tue Dec 30 15:15:59 PST 2014 231867.47 32216838.46 started xbmc-exits                       0.66 0.39 0.30 3/116 28936
Tue Dec 30 15:16:00 PST 2014 231868.44 32216838.49 started wait-for-state  xbmc-loaded      0.66 0.39 0.30 4/122 28983
Tue Dec 30 15:16:01 PST 2014 231868.93 32216838.49 stopped xbmc-exits                       0.76 0.42 0.31 2/116 29000
Tue Dec 30 15:17:41 PST 2014 231968.82 32216956.38 stopped wait-for-state  xbmc-loaded      0.52 0.48 0.35 3/144 29318
Tue Dec 30 15:17:41 PST 2014 231969.02 32216956.38 stopping xbmc                            0.52 0.48 0.35 1/141 29324
Tue Dec 30 15:17:41 PST 2014 231969.57 32216956.39 stopped xbmc                             0.52 0.48 0.35 7/123 29360
Tue Dec 30 15:17:41 PST 2014 231969.58 32216956.39 starting xbmc-exits                      0.52 0.48 0.35 6/120 29360
Tue Dec 30 15:17:41 PST 2014 231969.60 32216956.39 started xbmc-changesettings              0.52 0.48 0.35 5/117 29360
Tue Dec 30 15:17:42 PST 2014 231969.76 32216956.39 stopped xbian-xbmc-cpufreq               0.52 0.48 0.35 3/114 29365
Tue Dec 30 15:17:42 PST 2014 231970.02 32216956.39 stopped tvonoff-xbmc                     0.52 0.48 0.35 2/110 29372
Tue Dec 30 15:17:42 PST 2014 231970.16 32216956.39 stopped xbmc-changesettings              0.52 0.48 0.35 2/112 29383
Tue Dec 30 15:17:42 PST 2014 231970.29 32216956.39 started xbmc-exits                       0.52 0.48 0.35 2/111 29392
Tue Dec 30 15:17:42 PST 2014 231970.48 32216956.39 starting xbmc                            0.52 0.48 0.35 3/113 29404
Tue Dec 30 15:17:43 PST 2014 231970.68 32216956.39 started xbian-xbmc-cpufreq               0.52 0.48 0.35 3/117 29418
Tue Dec 30 15:17:43 PST 2014 231970.71 32216956.39 stopped xbmc-exits                       0.52 0.48 0.35 3/113 29419
Tue Dec 30 15:17:43 PST 2014 231971.62 32216956.39 started wait-for-state  xbmc-loaded      0.52 0.48 0.35 3/118 29470
Tue Dec 30 15:19:24 PST 2014 232071.97 32217078.51 stopped wait-for-state  xbmc-loaded      0.35 0.48 0.36 2/143 29728
Tue Dec 30 15:19:24 PST 2014 232072.11 32217078.51 stopping xbmc                            0.35 0.48 0.36 1/141 29734
Tue Dec 30 15:19:25 PST 2014 232072.67 32217078.53 stopped xbmc                             0.35 0.48 0.36 6/124 29770
Tue Dec 30 15:19:24 PST 2014 232072.68 32217078.53 starting xbmc-exits                      0.35 0.48 0.36 5/121 29770
Tue Dec 30 15:19:25 PST 2014 232072.66 32217078.53 started xbmc-changesettings              0.35 0.48 0.36 8/125 29770
Tue Dec 30 15:19:25 PST 2014 232072.81 32217078.53 stopped xbian-xbmc-cpufreq               0.35 0.48 0.36 4/116 29775
Tue Dec 30 15:19:25 PST 2014 232073.08 32217078.53 stopped tvonoff-xbmc                     0.35 0.48 0.36 2/114 29782
Tue Dec 30 15:19:25 PST 2014 232073.23 32217078.53 stopped xbmc-changesettings              0.35 0.48 0.36 2/115 29792
Tue Dec 30 15:19:25 PST 2014 232073.38 32217078.53 started xbmc-exits                       0.35 0.48 0.36 2/114 29804
Tue Dec 30 15:19:25 PST 2014 232073.58 32217078.53 starting xbmc                            0.35 0.48 0.36 3/112 29814
Tue Dec 30 15:19:26 PST 2014 232073.73 32217078.53 started xbian-xbmc-cpufreq               0.56 0.52 0.37 3/116 29825
Tue Dec 30 15:19:26 PST 2014 232073.76 32217078.53 stopped xbmc-exits                       0.56 0.52 0.37 2/114 29827
Tue Dec 30 15:19:26 PST 2014 232074.64 32250632.97 started wait-for-state  xbmc-loaded      0.56 0.52 0.37 3/118 29874
Tue Dec 30 15:21:07 PST 2014 232174.97 32250755.06 stopped wait-for-state  xbmc-loaded      0.69 0.64 0.43 3/141 30134
Tue Dec 30 15:21:07 PST 2014 232175.13 32250755.06 stopping xbmc                            0.69 0.64 0.43 1/139 30140
Tue Dec 30 15:21:07 PST 2014 232175.66 32250755.09 stopped xbmc                             0.69 0.64 0.43 6/122 30174
Tue Dec 30 15:21:08 PST 2014 232175.68 32250755.09 started xbmc-changesettings              0.69 0.64 0.43 5/119 30175
Tue Dec 30 15:21:08 PST 2014 232175.71 32250755.09 starting xbmc-exits                      0.69 0.64 0.43 5/118 30176
Tue Dec 30 15:21:08 PST 2014 232175.84 32250755.09 stopped xbian-xbmc-cpufreq               0.69 0.64 0.43 4/114 30181
Tue Dec 30 15:21:08 PST 2014 232176.10 32250755.09 stopped tvonoff-xbmc                     0.69 0.64 0.43 2/112 30188
Tue Dec 30 15:21:08 PST 2014 232176.25 32250755.09 stopped xbmc-changesettings              0.69 0.64 0.43 2/113 30198
Tue Dec 30 15:21:08 PST 2014 232176.40 32250755.09 started xbmc-exits                       0.69 0.64 0.43 2/111 30209
Tue Dec 30 15:21:08 PST 2014 232176.58 32250755.09 starting xbmc                            0.69 0.64 0.43 4/111 30220
Tue Dec 30 15:21:09 PST 2014 232176.78 32250755.09 started xbian-xbmc-cpufreq               0.69 0.64 0.43 3/116 30234
Tue Dec 30 15:21:09 PST 2014 232176.82 32250755.09 stopped xbmc-exits                       0.69 0.64 0.43 2/112 30235
Tue Dec 30 15:21:10 PST 2014 232177.64 32250755.11 started wait-for-state  xbmc-loaded      0.69 0.64 0.43 3/116 30277
Tue Dec 30 15:22:50 PST 2014 232277.99 32250877.58 stopped wait-for-state  xbmc-loaded      0.43 0.62 0.45 2/142 30547
Tue Dec 30 15:22:50 PST 2014 232278.15 32250877.58 stopping xbmc                            0.43 0.62 0.45 1/140 30553
Tue Dec 30 15:22:51 PST 2014 232278.68 32250877.60 starting xbmc-exits                      0.43 0.62 0.45 7/124 30588
Tue Dec 30 15:22:51 PST 2014 232278.73 32250877.60 started xbmc-changesettings              0.43 0.62 0.45 8/123 30592
Tue Dec 30 15:22:51 PST 2014 232278.70 32250877.60 stopped xbmc                             0.43 0.62 0.45 7/120 30592
Tue Dec 30 15:22:51 PST 2014 232278.82 32250877.60 stopped xbian-xbmc-cpufreq               0.72 0.67 0.47 4/115 30594
Tue Dec 30 15:22:51 PST 2014 232279.09 32250877.60 stopped tvonoff-xbmc                     0.72 0.67 0.47 2/113 30601
Tue Dec 30 15:22:51 PST 2014 232279.24 32250877.60 stopped xbmc-changesettings              0.72 0.67 0.47 4/115 30611
Tue Dec 30 15:22:51 PST 2014 232279.39 32250877.60 started xbmc-exits                       0.72 0.67 0.47 2/113 30623
Tue Dec 30 15:22:51 PST 2014 232279.58 32250877.60 starting xbmc                            0.72 0.67 0.47 3/112 30632
Tue Dec 30 15:22:52 PST 2014 232279.68 32250877.60 started xbian-xbmc-cpufreq               0.72 0.67 0.47 3/111 30639
Tue Dec 30 15:22:52 PST 2014 232279.82 32250877.60 stopped xbmc-exits                       0.72 0.67 0.47 2/114 30648
Tue Dec 30 15:22:53 PST 2014 232280.65 32250877.62 started wait-for-state  xbmc-loaded      0.72 0.67 0.47 3/117 30692

[Skywatch]

Min,

Thanks, that worked for me too! (problem only started after an upgrade today).

skywatch

[mk01]

(16th Dec, 2014 05:43 PM)mk01 Wrote:  anyhow with menakite we implemented a fix today. xbmc needs to be recompiled - any xbmc(rpi/imx6) or kodi(rpi/imx6) with suffix higher than -1418714780 (today) should have the fix included (without any additional job conf modding etc).

if anyone install new package and will still feel this issue be present, let us know.

I should have had been more precise - on that - the XBMC part was LAST of three fixes in three different packages

xbian-package-xbmc
xbian-package-upstart-bridge
xbian-package-xbmc-scripts

missing ANY of the 'chain' can retrigger/not solve the problem. but the other two packages been fixed & pushed before xbmc - developer (in that case myself) expects somehow automatically that other will have it - what of course mostly is not true.

so - so - lets correct / reconsolidate the info:

xbian-package-xbmc-scripts at minimum 1.1.4
xbian-package-upstart-xbmc-bridge 1.1.6
*xbmc* (that includes plain xbmc package, suffixed -6q, suffixed -nighly, suffixed -nightly-6q) with numbered suffix HIGHER than the date (16th Dec, 2014 08:43 AM) what translates to:

Code:

date --date="Dec 16, 2014 08:43" +%s

so the number suffix MUST be higher than this 1418715780.

this is full info.
also unfortunately all that mixes with the repo problem we had & restructuring it as part of recovery process.
so to put that as answer to @palswim

new structure is the way like Debian defined it - meaning platforms are horizontal dimension - meaning specifically:

Code:

deb mirror://apt.xbian.org/mirror.txt      stable  main imx6-jessie
deb mirror://apt.xbian.org/mirror.txt     staging   main    imx6-jessie
deb mirror://apt.xbian.org/mirror.txt     devel   main    imx6-jessie

(THIS IS EXAMPLE FROM IMX6, RPI USERS MUST HAVE RPI-WHEEZY instead of IMX6-JESSIE)

also the specs "stable main imx6-jessie" doesn't mean 1st OR 2nd OR 3rd. correct ENTRY for STABLE repo must contain ALL three levels/specs in the line - because only then it makes meaning -

Code:

packages considered STABLE
installable to all platforms so from MAIN (shared packages)
and also the platform specific for IMX6-JESSIE

missing any of the levels will WORK technically, but will never distribute full scale of what needs to be distributed.
to HAVE the correct entries there - user doesn't need to retype all that info manually ! XBIAN-PACKAGE-REPO since version 1.0.6-1 WILL DO THAT CORRECTLY (ALSO AUTOMATICALLY CONSIDERING platform and BASE OS) - but all the info is in the FAQ of http://www.xbian.org

ALSO BOTH files /etc/apt/sources.list and /etc/apt/sources.list.d/xbian.list MUST exists. the first one we are leaving completely for system (and user) - so that defines the upstream debian/raspbian sources - 99% of packages in system comes from there. the rest is coming from xbian repos defined in xbian.list.
ALSO three lines (stable,staging,devel) is provided AS template. currently for RPI only STABLE is requirement. for IMX6 STABLE+STAGING is requirement due to the nature of DEBIAN/Jessie itself - not still stable release.
"Requirement MEANS the line MUST NOT BE commented - starting with #"
@palswim
is this clear now? does it make sense ?

now - all that text - its purpose is not any blame to anyone - it is trying to say that natural way of communication works EXACTLY as defined by other philosophers centuries ago. from my brain (100% of info) - only 80% gets passed to 1st user, 60% to 2nd, 40% to third. that's why - if there is at least ONE user not understanding the message, the message wasn't said/written correctly (yes, my case mostly ;-)). but the user needs to ASK, to tell US. there is no shame in that. only if we are told (like someone here told - he doesn't get it from the FAQ) - only then we can change it. TELL US - there are not stupid questions - only stupid answers.
I will rather (and happier) be answering 3x in a row "YES, YOU UNDERSTAND IT CORRECTLY", comparing to for instance situation with trying to fix a BUGXYZ to find at the end that I created it myself BY improper FAQ entry or Forum message not being detailed enough. so AGAIN, if you-user don't get the text, ASK, TELL us. and be sure, you immediately helped 100 others who don't ask or simply skip that info as it makes no sense.

It will happen regularly that we - people around project - will loose the right user vocabulary - because we understand each other so we forget now and then that it doesn't work for user. TELL me, or us - that hey man! this info was not much useful from user perspective - ask for rewrite or call it rubbish. tell the author that he is slowly sliding off into the tech zone. author might not be AWARE of that.

back to xbmc looping:
- if the above conditions (the three RIGHT versions of debs ARE installed on your XBian and you still have XBMC looping - try to change TIMEOUT=100 to TIMEOUT=99999 on line 43 of /etc/init/xbmc.conf . few days BACK i have seen PROPER UNBROKEN RPI machine running XBIan & all the nice downloader packages etc which was starting XBMC for 3.5 minutes! it was also mounting 3TB disks, file indexes etc.
in the last version of xbian-package-xbmc-scripts we changed from 100s to 150s. what is 2minutes and 30s. 99% of users MUST be below that (maybe we even may move the VALUE into /etc/default/xbmc to be user editable and script will load it from there.

But let's consider the fact that this timeout=100 is there since XBian Beta2. more than 1Y of usage behind. the actual loops have been caused by combination of two other bugs introduced - together causing this FAIL to start). I'm confident about the code again - still if the three debs updates DO NOT SOLVE the issue - report to this thread and I will personally go user by user to track what ever else could by the issue.
Also because never before this happened at MASS scale - we neither users ever considered the looping itself for a BUG. the looping is alone a FEATURE - to auto restart XBMC in case of crash. but if XBMC doesn't start AT ALL (to HOME SCREEN) as part of BOOT and is killed on timeout - it is not logical to try loop it again and again. only today I named as BUG and fixed in xbian-package-xbmc-scripts v1.1.5.
(i have the feeling @palswim challenged that looping few msgs back as well -and clearly - reload AFTER xbmc running & crashing later is the feature we want to havel. useless restarting of XBMC which never make it to display on TV is an attack on user.

last but not least !
I WISH ALL the BEST in 2015 to all fans/users/coworkers/anyone involved !

[funky]

downgrading from xbian-package-upstart-xbmc-bridge 1.1.6 to 1.1.3 did the trick! thank you.

EDIT: I've just seen a dev had just replied in this thread talking about the issue, also after downgrading I've found out there's 3 new packages to update (one of them is obviously xbian-package-upstart-xbmc-bridge), I'm pretty sure the other two were not there yesterday.
Although everything is working fine right now, I'm pondering to update all of them and see what happens if mk01 thinks it would work.

BTW, these are the packages to be updated:

The following packages will be upgraded:
xbian-package-upstart-xbmc-bridge xbian-package-xbianhome xbian-package-xbmc-scripts
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

as note aside, this is the date of xbmc I have:
xbian ~ $ date --date='@1411559513'
Wed Sep 24 13:51:53 CEST 2014

[t1k]

I had the restarting problem since yesterday after upgrading routinely with apt-get. Last update was weeks ago.

I applied the apt fix mentioned in the FAQ, but trying upgrading again didn't solve the problem. After the updates XBMC dropped me to terminal login instead of restarting after the timeout period. Changing the timeout (as mentioned in some earlier posts) would just delay the problems and also prevented SSH login during the timeout period.

(31st Dec, 2014 08:59 PM)mk01 Wrote:  xbian-package-xbmc-scripts at minimum 1.1.4
xbian-package-upstart-xbmc-bridge 1.1.6
*xbmc* (that includes plain xbmc package, suffixed -6q, suffixed -nighly, suffixed -nightly-6q) with numbered suffix HIGHER than the date (16th Dec, 2014 08:43 AM) -- so the number suffix MUST be higher than this 1418715780.

This was what seems to have been the problem: My xbmc package was older than 1418715780 (I checked with dpkg --list). There were no updates though. Then I noticed my /etc/apt/sources.list.d/xbian.list did not have the rpi-wheezy ending mentioned in mk01's post. The FAQ does not have it either. I added it:

Code:

deb mirror://apt.xbian.org/mirror.txt      stable  main rpi-wheezy

Then did sudo apt-get update. Some newer packages were found, including a newer xbmc package. After installing them XBMC did not die after the timeout period. I did not have much time to test it yet, but hopefully my RPi will run smoother now.

[CurlyMo]

The rpi-wheezy will be added if you follow all steps described in the FAQ.

[palswim]

(31st Dec, 2014 08:59 PM)mk01 Wrote:  ALSO BOTH files /etc/apt/sources.list and /etc/apt/sources.list.d/xbian.list MUST exists. the first one we are leaving completely for system (and user) - so that defines the upstream debian/raspbian sources - 99% of packages in system comes from there. the rest is coming from xbian repos defined in xbian.list.
ALSO three lines (stable,staging,devel) is provided AS template. currently for RPI only STABLE is requirement. for IMX6 STABLE+STAGING is requirement due to the nature of DEBIAN/Jessie itself - not still stable release.
"Requirement MEANS the line MUST NOT BE commented - starting with #"
@palswim
is this clear now? does it make sense ?

I think that makes sense. You're saying I shouldn't change the contents of my sources.list file, but match the contents of my sources.list.d/xbian.list file to the lines you posted.

Code:

deb mirror://apt.xbian.org/mirror.txt stable main rpi-wheezy

[palswim]

(31st Dec, 2014 08:59 PM)mk01 Wrote:  Also because never before this happened at MASS scale - we neither users ever considered the looping itself for a BUG. the looping is alone a FEATURE - to auto restart XBMC in case of crash. but if XBMC doesn't start AT ALL (to HOME SCREEN) as part of BOOT and is killed on timeout - it is not logical to try loop it again and again. only today I named as BUG and fixed in xbian-package-xbmc-scripts v1.1.5.
(i have the feeling @palswim challenged that looping few msgs back as well -and clearly - reload AFTER xbmc running & crashing later is the feature we want to havel. useless restarting of XBMC which never make it to display on TV is an attack on user.

I'm not sure I understand what you mean here. Are you saying that you added the XBMC auto-restart as a feature, but I provided an argument as to why a user may not desire that behavior?

[CurlyMo]

Simple:
1. XBian checks if XBMC fails or crashes and auto-restarts it.
2. If point 1. fails you get a restart loop.

Little more technical:
It REALLY difficult to check if XBMC actually started properly. XBMC didn't implement this logic, so we hacked it in ourselves. That was what has changed in the latest versions. All packages involved need to be the right version to work or else you get conflicts between "XBMC started?" checks. If they are out-of-sync, it fails and you get the behavior as you described as the reboot loop.

[palswim]

(1st Jan, 2015 03:15 AM)CurlyMo Wrote:  The rpi-wheezy will be added if you follow all steps described in the FAQ.

Not quite. The installation of the xbian-package-repo package added rpi-jessie (which didn't exist) for me the first time instead. It seems to try to do something clever and determine your Debian distribution.

I tried altering lines in the /etc/apt/sources.list file to target the wheezy repositories instead of jessie, but then, the xbian-package-repo added neither rpi-wheezy nor rpi-jessie.

I have since manually added rpi-wheezy, but I'm adding my experience just to say that following everything in the FAQ will not always result in the correct setup (at this moment).

[CurlyMo]

If that's indeed the case, then you found a bug that needs to be solved For the quickest solution, report it to our github issues next time.

[funky]

I've followed the instructions in the FAQ, and now everything is working fine. I've got xbian-package-upstart-xbmc-bridge 1.1.6 running with no issues, xbmc has been updated also, now I'm running version 13.2-RLS-1419734381, which is quite recent.

Thank you guys for the support and happy new year.