View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 7 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Mon May 20, 2019 1:08 pm 
Offline
Joined: Sun Nov 13, 2005 5:56 pm
Posts: 97
The topic sez it all. I just keep getting the same log entries repeated every 10 minutes or so.

Code:
2019-05-20T14:30:00.076855-04:00 mythbackend[3127]: N Scheduler scheduler.cpp:3273 (HandleIdleShutdown) Blocking shutdown because of a connected client
2019-05-20T14:30:13.588539-04:00 mythbackend[3127]: I ProcessRequest mainserver.cpp:1780 (HandleAnnounce) MainServer: MainServer::ANN Monitor
2019-05-20T14:30:13.588579-04:00 mythbackend[3127]: I ProcessRequest mainserver.cpp:1785 (HandleAnnounce) MainServer: adding: linhes(55bba9b93bb0) as a client (events: 0)
2019-05-20T14:30:14.289459-04:00 mythbackend[3127]: I MythSocketThread(55) mainserver.cpp:7928 (connectionClosed) Monitor sock(55bba9b93bb0) 'linhes' disconnected
2019-05-20T14:35:14.047972-04:00 mythbackend[3127]: I ProcessRequest mainserver.cpp:1780 (HandleAnnounce) MainServer: MainServer::ANN Monitor
2019-05-20T14:35:14.048020-04:00 mythbackend[3127]: I ProcessRequest mainserver.cpp:1785 (HandleAnnounce) MainServer: adding: linhes(55bba9b93bb0) as a client (events: 0)
2019-05-20T14:35:14.648714-04:00 mythbackend[3127]: I MythSocketThread(55) mainserver.cpp:7928 (connectionClosed) Monitor sock(55bba9b93bb0) 'linhes' disconnected
2019-05-20T14:40:14.408193-04:00 mythbackend[3127]: I ProcessRequest mainserver.cpp:1780 (HandleAnnounce) MainServer: MainServer::ANN Monitor
2019-05-20T14:40:14.408242-04:00 mythbackend[3127]: I ProcessRequest mainserver.cpp:1785 (HandleAnnounce) MainServer: adding: linhes(55bba9b93bb0) as a client (events: 0)
2019-05-20T14:40:15.109135-04:00 mythbackend[3127]: I MythSocketThread(55) mainserver.cpp:7928 (connectionClosed) Monitor sock(55bba9b93bb0) 'linhes' disconnected
2019-05-20T14:40:53.942712-04:00 mythbackend[3127]: N Expire autoexpire.cpp:261 (CalcParams) AutoExpire: CalcParams(): Max required Free Space: 50.0 GB w/freq: 15 min
2019-05-20T14:42:58.850623-04:00 mythbackend[3127]: I ProcessRequest mainserver.cpp:1780 (HandleAnnounce) MainServer: MainServer::ANN Monitor
2019-05-20T14:42:58.850670-04:00 mythbackend[3127]: I ProcessRequest mainserver.cpp:1785 (HandleAnnounce) MainServer: adding: linhes(55bba9b93bb0) as a client (events: 0)
2019-05-20T14:42:58.950850-04:00 mythbackend[3127]: I MythSocketThread(56) mainserver.cpp:7928 (connectionClosed) Monitor sock(55bba9b93bb0) 'linhes' disconnected


I have 63 GB free on the disk so I'm not sure what that entry is about. I see linhes is connecting and disconnecting but I am not sure where, how or why. I am running idle.py without the 'l' option. This is something that started in the last month or two.

sparks


Top
 Profile  
 
PostPosted: Mon May 20, 2019 6:59 pm 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 530
Do you have any remote frontends?
After upgrading a remote kodi box to 18, I started to have similar issues because it was blocking shutdown when idle, even when it wasn't supposed to.

This is the message that makes me wonder:
Code:
Blocking shutdown because of a connected client


Unfortunately I do not know of a way to interrogate which frontend is responsible, though.


Top
 Profile  
 
PostPosted: Mon May 20, 2019 7:26 pm 
Offline
Joined: Sun Nov 13, 2005 5:56 pm
Posts: 97
The only frontend client I have is a RPi box that is completely powered down, wall wart not even plugged in. I rarely use it. linhes is the name of my front/back end box so I figured it was something internal to my main box. Still stymied.

s


Top
 Profile  
 
PostPosted: Sun May 26, 2019 4:21 am 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 530
Sorry that I can't be of better help. I have had frustrating MythWelcome issues in the past and I find it difficult to troubleshoot, particularly with remote frontends in the mix. Since that is not an issue for you, can you provide more detail about your setup in hopes that it will resonate with somebody? Are you on 8.6.1? Are you manually exiting the frontend or are you letting the frontend go idle?

I believe that the added client and disconnected messages are normal because I see that all the time on my machine (which is also a hostname of linhes).


Top
 Profile  
 
PostPosted: Tue May 28, 2019 9:49 am 
Offline
Joined: Sun Nov 13, 2005 5:56 pm
Posts: 97
Thanks for the reply.

I am on the latest release of LinHES running on a an Intel motherboard with 8GB, H77 chipset, i7 cpu, a 220 GB SSD for LinHES, and a 1 GB HD for recordings. As far as usage goes, when I am done at night I manually backout of the frontend and let it sit with the mythwelcome screen. It's not unusal for backend jobs to be running at that time because I transcode all my recordings so I just expect it to shut down when it finishes. It used to until rececently (last month or two). When I check it the next day I find it still running, that it never shut down even though it sat idle for hours. I thought mythwelcome had a log but I haven't found it yet.

sparks


Top
 Profile  
 
PostPosted: Sun Jun 23, 2019 9:29 am 
Offline
Joined: Sun Nov 13, 2005 5:56 pm
Posts: 97
I was finally able to give this problem some attention again. I was able to get mythwelcome to produce a log that I set at DEBUG level. I get the same portion of log repeating. It shows mythshutdown returning a 0 status that I thought should be good. What ever picks up that status code isn't doing its job. I have no idea what the next link is. Any ideas?

sparks

Code:
2019-06-23 11:21:29.732906 C [30265/30265] thread_unknown mythcommandlineparser.cpp:2607 (ConfigureLogging) - mythshutdown version: fixes/30 [v30.0-34-g81081957a0] www.mythtv.org
2019-06-23 11:21:29.732938 C [30265/30265] thread_unknown mythcommandlineparser.cpp:2609 (ConfigureLogging) - Qt version: compile: 5.10.1, runtime: 5.10.1
2019-06-23 11:21:29.732940 N [30265/30265] thread_unknown mythcommandlineparser.cpp:2611 (ConfigureLogging) - Enabled verbose msgs:  general
2019-06-23 11:21:29.733022 N [30265/30265] thread_unknown logging.cpp:734 (logStart) - Setting Log Level to LOG_DEBUG
2019-06-23 11:21:29.743403 I [30265/30268] Logger logging.cpp:296 (run) - Added logging to the console
2019-06-23 11:21:29.743808 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Interrupt handler
2019-06-23 11:21:29.743819 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Terminated handler
2019-06-23 11:21:29.743834 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Segmentation fault handler
2019-06-23 11:21:29.743842 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Aborted handler
2019-06-23 11:21:29.743851 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Bus error handler
2019-06-23 11:21:29.743857 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Floating point exception handler
2019-06-23 11:21:29.743867 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Illegal instruction handler
2019-06-23 11:21:29.743875 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Real-time signal 0 handler
2019-06-23 11:21:29.743886 I [30265/30265] thread_unknown signalhandling.cpp:194 (SetHandlerPrivate) - Setup Hangup handler
2019-06-23 11:21:29.743889 I [30265/30267] LogForward loggingserver.cpp:129 (FileLogger) - Added logging to /var/log/mythwelcome/mythshutdown.20190623152129.30265.log
2019-06-23 11:21:29.744007 N [30265/30265] thread_unknown mythdirs.cpp:203 (InitializeMythDirs) - Using runtime prefix = /usr
2019-06-23 11:21:29.744011 N [30265/30265] thread_unknown mythdirs.cpp:205 (InitializeMythDirs) - Using configuration directory = /home/mythtv/.mythtv
2019-06-23 11:21:29.744016 D [30265/30265] thread_unknown mythdirs.cpp:207 (InitializeMythDirs) - appbindir         = /usr/bin/
2019-06-23 11:21:29.744019 D [30265/30265] thread_unknown mythdirs.cpp:208 (InitializeMythDirs) - sharedir          = /usr/share/mythtv/
2019-06-23 11:21:29.744023 D [30265/30265] thread_unknown mythdirs.cpp:209 (InitializeMythDirs) - libdir            = /usr/lib/mythtv/
2019-06-23 11:21:29.744025 D [30265/30265] thread_unknown mythdirs.cpp:210 (InitializeMythDirs) - themedir          = /usr/share/mythtv/themes/
2019-06-23 11:21:29.744029 D [30265/30265] thread_unknown mythdirs.cpp:211 (InitializeMythDirs) - pluginsdir        = /usr/lib/mythtv/plugins/
2019-06-23 11:21:29.744032 D [30265/30265] thread_unknown mythdirs.cpp:212 (InitializeMythDirs) - translationsdir   = /usr/share/mythtv/i18n/
2019-06-23 11:21:29.744038 D [30265/30265] thread_unknown mythdirs.cpp:213 (InitializeMythDirs) - filtersdir        = /usr/lib/mythtv/filters/
2019-06-23 11:21:29.744042 D [30265/30265] thread_unknown mythdirs.cpp:214 (InitializeMythDirs) - cachedir          = /home/mythtv/.mythtv/cache
2019-06-23 11:21:29.744047 D [30265/30265] thread_unknown mythdirs.cpp:215 (InitializeMythDirs) - remotecachedir    = /home/mythtv/.mythtv/cache/remotecache
2019-06-23 11:21:29.744056 D [30265/30265] thread_unknown mythdirs.cpp:216 (InitializeMythDirs) - themebasecachedir = /home/mythtv/.mythtv/cache/themecache
2019-06-23 11:21:29.744058 D [30265/30265] thread_unknown mythdirs.cpp:217 (InitializeMythDirs) - thumbnaildir      = /home/mythtv/.mythtv/cache/thumbnails
2019-06-23 11:21:29.744132 I [30265/30265] CoreContext mythcorecontext.cpp:272 (Init) - Assumed character encoding: en_US.UTF-8
2019-06-23 11:21:29.744450 I [30265/30265] CoreContext mythcontext.cpp:641 (LoadDatabaseSettings) - Empty LocalHostName. This is typical.
2019-06-23 11:21:29.744459 I [30265/30265] CoreContext mythcontext.cpp:650 (LoadDatabaseSettings) - Using a profile name of: 'linhes' (Usually the same as this host's name.)
2019-06-23 11:21:29.744542 I [30265/30265] CoreContext mythcontext.cpp:900 (TestDBconnection) - Start up testing connections. DB 127.0.0.1, BE , attempt 0, status dbAwake, Delay: 2000
2019-06-23 11:21:29.744552 D [30265/30265] CoreContext portchecker.cpp:81 (checkPort) - PortChecker::checkPort(): host 127.0.0.1 port 3306 timeLimit 1000 linkLocalOnly 0
2019-06-23 11:21:30.245133 D [30265/30265] CoreContext portchecker.cpp:197 (checkPort) - PortChecker::checkPort(): socket state 3
2019-06-23 11:21:30.255251 D [30265/30265] CoreContext portchecker.cpp:81 (checkPort) - PortChecker::checkPort(): host 127.0.0.1 port 3306 timeLimit 30000 linkLocalOnly 1
2019-06-23 11:21:30.261061 D [30265/30265] CoreContext mythcontext.cpp:525 (FindDatabase) - FindDatabase() - Success!
2019-06-23 11:21:30.261138 D [30265/30265] CoreContext portchecker.cpp:81 (checkPort) - PortChecker::checkPort(): host 127.0.0.1 port 3306 timeLimit 30000 linkLocalOnly 1
2019-06-23 11:21:30.263158 N [30265/30265] CoreContext mythcorecontext.cpp:1864 (InitLocale) - Setting QT default locale to en_US
2019-06-23 11:21:30.263174 I [30265/30265] CoreContext mythcorecontext.cpp:1897 (SaveLocaleDefaults) - Current locale en_US
2019-06-23 11:21:30.263234 N [30265/30265] CoreContext mythlocale.cpp:123 (LoadDefaultsFromXML) - Reading locale defaults from /usr/share/mythtv//locales/en_us.xml
2019-06-23 11:21:30.266494 I [30265/30265] CoreContext main.cpp:240 (getStatus) - Mythshutdown: --status
2019-06-23 11:21:30.266990 I [30265/30295] SystemSignalManager mythsystemunix.cpp:509 (run) - Starting process signal handler
2019-06-23 11:21:30.266995 I [30265/30294] SystemManager mythsystemunix.cpp:276 (run) - Starting process manager
2019-06-23 11:21:30.268816 I [30265/30296] SystemIOHandlerR mythsystemunix.cpp:92 (run) - Starting IO manager (read)
2019-06-23 11:21:30.268847 I [30265/30297] SystemIOHandlerW mythsystemunix.cpp:92 (run) - Starting IO manager (write)
2019-06-23 11:21:30.467625 I [30265/30265] CoreContext main.cpp:369 (getStatus) - Mythshutdown: --status returned: 0


Top
 Profile  
 
PostPosted: Thu Jul 04, 2019 5:42 am 
Offline
Joined: Thu Sep 27, 2007 5:44 pm
Posts: 530
sparks, is that a mythwelcome or mythshutdown log? My mythshutdown ends with the line:
Code:
2019-07-03T22:12:22.620160-05:00 mythshutdown[32365]: I CoreContext main.cpp:369 (getStatus) Mythshutdown: --status returned: 0
which appears to match yours.
Is it possible that your shutdown command got corrupted somehow?


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu