Kodi Community Forum
[WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - Printable Version

Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Supplementary Tools for Kodi (https://forum.kodi.tv/forumdisplay.php?fid=116)
--- Thread: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app (/showthread.php?tid=126297)



RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - Jeremy White - 2014-03-25

Still not working.

Could it be because my install directory is in /home/xbmc/HTPC-Manager?

The user name is xbmc that I ssh in under.

'sudo service htpc start' works fine if I ssh in.


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - ylafont - 2014-03-25

depends if you logon as xbmc on boot, check you /var/log/syslog for messages.

Set permissions on your HTPC-manager directory to 777

also (forgot to mention) type

initctl reload-configuration


and reboot. should work


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - Jeremy White - 2014-03-25

This still isn't autostarting.

'sudo service htpc start' works fine.

Two ideas....

Is my directory '/home/xbmc/HTPC-Manager/' a directory the startup script can't for some reason access?

Is it possible my script is running to early, before something necessary has started up?

Thanks!


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - ylafont - 2014-03-25

not that complicated, as long as you placed the .conf file in /etc/init.

executed
initctl reload-configuration

and
sudo chmo -R 777 /home/xbmc/HTPC-Manager/


Check you /var/log/upstart folder. there should be a log file for each service started with upstart. in particular htpc.log (if you named your file htpc.conf)

...check your /var/log/boot.log for an entry of htpc service.
...check your upper and lower case with files names. I know if seems obvious, but it happens to me all the time. .

that should give you an idea of what is going on.


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - Jeremy White - 2014-03-25

I'll note that it looks like it tries to start more then once, but each time this is the error I get.



******************************************************
Starting HTPC Manager on port 8099.
Start your browser and go to http://localhost:8099/
******************************************************
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Listening for SIGHUP.
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Listening for SIGTERM.
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Listening for SIGUSR1.
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Bus STARTING
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Started monitor thread '_TimeoutMonitor'.
2014-03-25 14:56:49 :: cherrypy.error :: ERROR :: [25/Mar/2014:14:56:49] ENGINE Error in HTTP server: shutting down
Traceback (most recent call last):
File "/home/xbmc/HTPC-Manager/libs/cherrypy/process/servers.py", line 187, in _start_http_thread
self.httpserver.start()
File "/home/xbmc/HTPC-Manager/libs/cherrypy/wsgiserver/wsgiserver2.py", line 1824, in start
raise socket.error(msg)
error: No socket could be created

2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Bus STOPPING
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('192.168.4.101', 8099)) already shut do
wn
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Stopped thread '_TimeoutMonitor'.
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Bus STOPPED
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Bus EXITING
2014-03-25 14:56:49 :: cherrypy.error :: INFO :: [25/Mar/2014:14:56:49] ENGINE Bus EXITED


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - Jeremy White - 2014-03-25

Edit : Thought I had it working and it isn't. I'm out of ideas.

I tried various sleeps just for a test.

I tried 'start on started networking' and it was insufficient.


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - ylafont - 2014-03-25

(2014-03-25, 10:37)Jeremy White Wrote: Edit : Thought I had it working and it isn't. I'm out of ideas.

I tried various sleeps just for a test.

I tried 'start on started networking' and it was insufficient.

At least you know the service is starting on reboot.

I see it is starting on a port that is not the default, is that port already being used by something else?
try adding the --port 8085 to the exec line.

maybe hellow or styxit can share their thoughts on the error you are receiving.


[WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - hellow - 2014-03-25

I'm afraid I can't assist you I know nothing about Linux, infact init and permissions is the main reason I stay away :p


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - ylafont - 2014-03-25

(2014-03-25, 08:59)Jeremy White Wrote: 2014-03-25 14:56:49 :: cherrypy.error :: ERROR :: [25/Mar/2014:14:56:49] ENGINE Error in HTTP server: shutting down
Traceback (most recent call last):
File "/home/xbmc/HTPC-Manager/libs/cherrypy/process/servers.py", line 187, in _start_http_thread
self.httpserver.start()
File "/home/xbmc/HTPC-Manager/libs/cherrypy/wsgiserver/wsgiserver2.py", line 1824, in start
raise socket.error(msg)
error: No socket could be created


I lam leading to say the port is already in use. but hey i don't call my self and expert.


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - guy_smiley:) - 2014-03-26

(2014-03-25, 19:33)ylafont Wrote:
(2014-03-25, 08:59)Jeremy White Wrote: error: No socket could be created


I lam leading to say the port is already in use. but hey i don't call my self and expert.

I would second that, saying no socket could be created is generally the case of the port being in use. BTW that has nothing to do with Linux and is a Python output.


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - Jeremy White - 2014-03-29

It certainly has nothing to do with a port being in use.

Well, no port will work. It's like the network isn't there yet!?


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - ylafont - 2014-03-29

(2014-03-29, 04:28)Jeremy White Wrote: It certainly has nothing to do with a port being in use.

Well, no port will work. It's like the network isn't there yet!?

i tested it and got the same error.- 99% sure it is the port in use.

try turning off the firewall. sudo ufw disable


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - Jeremy White - 2014-04-05

Actually didn't have ufw installed.

I installed it, and then disabled it.

I also flushed -F the iptables.

No change.... still stuck. Any other ideas?


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - ylafont - 2014-04-06

(2014-04-05, 10:38)Jeremy White Wrote: Actually didn't have ufw installed.

I installed it, and then disabled it.

I also flushed -F the iptables.

No change.... still stuck. Any other ideas?

I got nothing else, maybe someone with more experience can assist.


RE: [WIP] HTPC-Manager Beta, Manage XBMC, Sabnzbd, SickBeard with one app - MadClicker - 2014-04-06

You might try putting this in your init.d file:

Code:
# Should-Start:      $NetworkManager
# Should-Stop:       $NetworkManager

Can't say it will fix your problem, but it does sound to me like the system is trying to start your script before the network.