New MythWeb Trouble

[leejk]

Hello,

I've been using MythWeb flawlessly for about a year on El Capitan. Recently, tho, it's gotten to where I can only access it from localhost. Using the http://macmini.local/MythWeb method no longer works from any of the other computers in the house. If I reboot the machine, then a few minutes afterwards I can access it from my iPad, but the backend still hasn't started by then. However, say an hour later, it's no longer accessible from anything other than localhost. Does someone know where the logs live for MythWeb?

Thx

[pvr4me]

I've been using MythWeb flawlessly for about a year on El Capitan. Recently, tho, it's gotten to where I can only access it from localhost. Using the http://macmini.local/MythWeb method no longer works from any of the other computers in the house. If I reboot the machine, then a few minutes afterwards I can access it from my iPad, but the backend still hasn't started by then. However, say an hour later, it's no longer accessible from anything other than localhost. Does someone know where the logs live for MythWeb?

I would suspect that something has changed in your network. Is it possible that your backend machine is changing between wired and wireless?

Re the backend not starting at bootup, that has unfortunately become common for many of us. I believe the network is not available when launchd tries to start mythbackend. It does, however, try again in 5 minutes. I don't know of an elegant solution for this and I almost never restart my main backend so it seldom happens to me.

Web server logs are at:

Code: Select all

/opt/dvr/apache2/logs

BTW, when MythWeb isn't responding, can you access the backend at:

[url]http://<backend.ip>:6544[/url]

Craig

[leejk]

Hello,

No, the backend is wired only, as I have the wifi on it turned off. Today, it has stopped completely. Running the following commands, I can see no httpd process in Activity Monitor at all. I didn't see anything in the logs either that looked out of the ordinary either.

Code: Select all

sudo launchctl unload /Library/LaunchDaemons/org.macports.apache2.plist
sudo launchctl load -w /Library/LaunchDaemons/org.macports.apache2.plist

[leejk]

Oops... I did find something odd... somehow the hostname on the machine reverted back to the factory default. Fixing that has had a positive effect so far. Your suspicions where right

[leejk]

Hello,

Some new trouble has surfaced again. Mythweb seemingly no longer will start. I can manually start the apache web server from the command line, and it starts fine. I been looking at the logs on this machine and noticed something that was showing up in the system.log whenever I manually started myth web using the command "sudo launchctl load -w /Libray/LaunchDaemons/org.macports.apache2.plist".

Code: Select all

Nov  6 18:29:30 macmini com.apple.xpc.launchd[1] (org.macports.apache2): The Debug key is no longer respected. Please remove it.
Nov  6 18:29:30 macmini com.apple.xpc.launchd[1] (org.macports.apache2): This service is defined to be constantly running and is inherently inefficient.

I can find no other log information, so was wondering if this is contributing to the problem? The httpd process is not running whenever the above launch command is ran, so it appears it is silently dying somehow.

thx

[leejk]

Well, re-installing using the steps in the macports wiki seems to have resolved it... weird.

[pvr4me]

Some new trouble has surfaced again. Mythweb seemingly no longer will start. I can manually start the apache web server from the command line, and it starts fine. I been looking at the logs on this machine and noticed something that was showing up in the system.log whenever I manually started myth web using the command "sudo launchctl load -w /Libray/LaunchDaemons/org.macports.apache2.plist".

Code: Select all

Nov  6 18:29:30 macmini com.apple.xpc.launchd[1] (org.macports.apache2): The Debug key is no longer respected. Please remove it.
Nov  6 18:29:30 macmini com.apple.xpc.launchd[1] (org.macports.apache2): This service is defined to be constantly running and is inherently inefficient.

I can find no other log information, so was wondering if this is contributing to the problem? The httpd process is not running whenever the above launch command is ran, so it appears it is silently dying somehow.

I see you got it going again; just wanted to explain about those "error" messages. Neither one represents a real problem. There were some significant changes in recent versions of launchd but legacy features continue to be supported or tolerated. I'm waiting for smarter people than me to show a launchd plist that does "the right thing". Until then, these are just (more) noise in the logs.

Craig

[sfatula]

Hello,

Code: Select all

Nov  6 18:29:30 macmini com.apple.xpc.launchd[1] (org.macports.apache2): The Debug key is no longer respected. Please remove it.
Nov  6 18:29:30 macmini com.apple.xpc.launchd[1] (org.macports.apache2): This service is defined to be constantly running and is inherently inefficient.

Those are expected, and in fact you'll see those for other processes you did not create most likely. Constantly running may mean that it's inefficient, by someones definition. But that's the design of httpd (Apache). It's more efficient in this case than launching httpd on demand to service a request, which seems to be what Apple likes to suggest. Nothing to worry about. You can't get rid of the inefficient message unless you change it to launch on demand, and good luck with that.