06-19-2020, 03:45 PM
I got diverted onto something else, and never managed to resolve this, though I did fix the errors (in my code) that were causing me to want to look for the log file in the first place.
But, while tinkering I thought I'd try something with upmpdcli. I kill the instance that moode runs, and start one from the command line
Oddly, the log information goes to the console (rather than to the one specified in the config file) and I've been able to redirect it to a file and tail that. So result of a sort.
So then I thought I'd try adding the parameters to the command line. Logging still goes to the console and no log file is created. I had already created the logs directory and given the world and their grannie write access to it.
So, finally, I went back to the config file and commented out the logfile and log level entries and started it again, same commandline as above. Still no logfile created, output goes to stdout.
So I'm confused, but wondering if that's why I'm not seeing a logfile with the instance started by Moode, that no matter what, the logfile goes to stdout...
Ideas would be appreciated. The reason I've gone back to this is that my Upnp control point is seeing occasional EarlyEOF errors reported when sending commands to the OhNetPlaylist service that's part of upmpdcli. Neither the upnp stack not the jetty stack underneath it are being very helpful, so I thought I'd look at upmpdcli.
I think I can get by on starting upmpdcli and backgrounding from the commandline, but you know, completeness...
But, while tinkering I thought I'd try something with upmpdcli. I kill the instance that moode runs, and start one from the command line
Code:
sudo upmpdcli -c /etc/upmpdcli.confOddly, the log information goes to the console (rather than to the one specified in the config file) and I've been able to redirect it to a file and tail that. So result of a sort.
So then I thought I'd try adding the parameters to the command line. Logging still goes to the console and no log file is created. I had already created the logs directory and given the world and their grannie write access to it.
Code:
sudo /usr/bin/upmpdcli -c /etc/upmpdcli.conf -l 4 -d /home/pi/logs/upmpdcli.logSo, finally, I went back to the config file and commented out the logfile and log level entries and started it again, same commandline as above. Still no logfile created, output goes to stdout.
So I'm confused, but wondering if that's why I'm not seeing a logfile with the instance started by Moode, that no matter what, the logfile goes to stdout...
Ideas would be appreciated. The reason I've gone back to this is that my Upnp control point is seeing occasional EarlyEOF errors reported when sending commands to the OhNetPlaylist service that's part of upmpdcli. Neither the upnp stack not the jetty stack underneath it are being very helpful, so I thought I'd look at upmpdcli.
I think I can get by on starting upmpdcli and backgrounding from the commandline, but you know, completeness...
