Rick Sanchez Posted January 3, 2016 Share Posted January 3, 2016 (edited) Fair enough. I seem to missing something? Any ideas? Edited May 10, 2018 by Rick Sanchez Quote Link to comment
Dimtar Posted January 3, 2016 Share Posted January 3, 2016 What does your log say? Quote Link to comment
CHBMB Posted January 3, 2016 Share Posted January 3, 2016 The pynab logs would be a better place to look... Quote Link to comment
Rick Sanchez Posted January 3, 2016 Share Posted January 3, 2016 I've refreshed the ones above, but which one are you referring to? As there are eight? Quote Link to comment
CHBMB Posted January 3, 2016 Share Posted January 3, 2016 I've refreshed the ones above, but which one are you referring to? As there are eight? I don't know, but why don't you look at them and see if you can see anything, looking at them may give some clues as to which one is best to post.. Quote Link to comment
CHBMB Posted January 3, 2016 Share Posted January 3, 2016 So I just loaded this up for s and g's Here's my log from the docker page webui... initialising empty databases in /data completed initialisation 2016-01-03 13:05:07,878 CRIT Supervisor running as root (no user in config file) 2016-01-03 13:05:07,882 INFO supervisord started with pid 86 2016-01-03 13:05:08,883 INFO spawned: 'postgres' with pid 90 2016-01-03 13:05:10,250 INFO success: postgres entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) setting up pynab user and database pynab user and database created building initial nzb import THIS WILL TAKE SOME TIME, DO NOT STOP THE DOCKER Quote Link to comment
Rick Sanchez Posted January 3, 2016 Share Posted January 3, 2016 This is above: 2016-01-02 21:29:31,991 INFO exited: postgres (exit status 2; not expected) 2016-01-02 21:29:32,991 INFO gave up: postgres entered FATAL state, too many start retries too quickly Quote Link to comment
Dimtar Posted January 3, 2016 Share Posted January 3, 2016 I never got mine working, it sounds like the same problem. The postgres DB just keeps restarting. Quote Link to comment
Rick Sanchez Posted January 3, 2016 Share Posted January 3, 2016 Did you use something else? It would be handy if all of the dockkers came with more detailed instructions & screenshots Quote Link to comment
Dimtar Posted January 3, 2016 Share Posted January 3, 2016 No I don't use something else. Not alot of people use this, it seems to work for some people and not for others, there is nothing we can really do about it. Quote Link to comment
CHBMB Posted January 3, 2016 Share Posted January 3, 2016 Remember it's marked beta for a reason.... Quote Link to comment
tooviral Posted January 3, 2016 Share Posted January 3, 2016 Does pynab have the webui installed by default?? If so than I'm unable to get to it, gives me a 502 bad gateway error. no noticeable errors in log Quote Link to comment
CHBMB Posted January 3, 2016 Share Posted January 3, 2016 Does pynab have the webui installed by default?? If so than I'm unable to get to it, gives me a 502 bad gateway error. no noticeable errors in log http://lime-technology.com/forum/index.php?topic=40216.msg430953#msg430953 Quote Link to comment
tkenn1s Posted January 16, 2016 Share Posted January 16, 2016 First, I have to say the pynab docker is awesome paired w/ Sick Beard. However, pynab will periodically stop updating. Checked the gui this morning and it hadn't updated the index in at least 2 days [all items were >= 2 days old]. I have to manually restart the docker for it to start updating again. Is this a known issue? What logs would be useful to help diagnose the problem? Quote Link to comment
CHBMB Posted July 21, 2016 Share Posted July 21, 2016 Where do we get the admin api key? I don't use this, but you tried reading the first post in the thread? Quote Link to comment
CHBMB Posted July 21, 2016 Share Posted July 21, 2016 I did read the first post and it states that it will generate an admin api key, and I've looked through the config.py and I don't see it. Want to read it again..... it generates a default api admin key of 303c5cd0b18e9ebe093e9b9dae3d3c74 Quote Link to comment
GreenEyedMonster Posted June 6, 2017 Share Posted June 6, 2017 Quote 2017-06-06 13:39:13,260 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:40:21,100 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:40:22,101 INFO spawned: 'prebot' with pid 31162017-06-06 13:40:23,102 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:40:55,044 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:40:56,048 INFO spawned: 'prebot' with pid 31212017-06-06 13:40:57,050 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:41:09,083 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:41:10,084 INFO spawned: 'prebot' with pid 31262017-06-06 13:41:11,086 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:42:12,829 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:42:13,831 INFO spawned: 'prebot' with pid 31332017-06-06 13:42:14,833 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:42:33,794 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:42:34,796 INFO spawned: 'prebot' with pid 31382017-06-06 13:42:35,797 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:43:07,092 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:43:08,094 INFO spawned: 'prebot' with pid 31472017-06-06 13:43:09,095 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:44:10,726 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:44:11,728 INFO spawned: 'prebot' with pid 31532017-06-06 13:44:12,729 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:45:20,946 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:45:21,948 INFO spawned: 'prebot' with pid 31592017-06-06 13:45:22,949 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:46:30,769 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:46:31,772 INFO spawned: 'prebot' with pid 31692017-06-06 13:46:32,774 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:46:34,853 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:46:35,856 INFO spawned: 'prebot' with pid 31742017-06-06 13:46:36,857 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:47:38,975 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:47:39,978 INFO spawned: 'prebot' with pid 31802017-06-06 13:47:40,981 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2017-06-06 13:48:49,507 INFO exited: prebot (exit status 1; not expected)2017-06-06 13:48:50,509 INFO spawned: 'prebot' with pid 31862017-06-06 13:48:51,510 INFO success: prebot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Can't seem to search for anything. Any ideas? This is the log from Pynab. Quote Link to comment
NewDisplayName Posted January 29, 2019 Share Posted January 29, 2019 (edited) does this still work? Seems so, but "api" doenst start automatic, i hat to use /opt/pynab# python3 pynab.py api pynab:api: started to be able to add it to nzbhydra. I bought nn+ and added it, its currently backfilling, but doenst show anything under stats (the webpage), prebot doenst seem to work (only reconnecting with new rnd names)... but for what is that used? Can it work without prebot? if we should/could/must buy nn+ why not use their client as docker? Anyway, in logs update i find many releases, but when i search for them, tehy dont appear, do i need to do anything else? How does he know what category rls are? (bc in webpage i have to specifiy rls categories) edit: nvm, just took longer then i expected to show anything, categories works and a quite a few things got added tried to disable tvrage and nfo, but then docker crashes , not expected false u cant add new groups, or delete old, they get just readded after restart.... (i tried via cmd line and via the groups.json) was really a pain, but not working. It doenst use that file, but created it..? Oo besides this it seems to work very fast and easy. Edited January 29, 2019 by nuhll Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.