gunbunny wrote: ↑Sun Oct 16, 2022 2:30 pm
Odd situation today. Running 1.1.0 on DSM 6. Haven't changed the config in a while, everything just ran like it should. Until today.
Football game was set to record and I had planned to timeshift it. Little red dot was showing up in the UI and everything normal. Sit down to watch it... no recording. So I log into my Synology, click the Package Center, hit the HDHR DVR Manager, click Open... and it 404's. Okay, that's odd. So I check here, then SSH into my box and there's no files in the www folder. So I re-download the SPK and reinstall it. Still 404s. Still nothing in the www folder. So I open the SPK and manually copy the files into www. Okay, now we're getting somewhere. The web interface comes up, and most of the config stuff is blank:
- Version:TO BE SET
- Record Engine Version: Unable to discover DVR version
- Config File Location: /
- RecordPath: Path not Set
- Port: Path not Set
- RecordStreamsMax: 16
- StorageID: StorageID not Set
- RunAs: not set
- BetaEngine: 0
I check the config file with
Code: Select all
cat /volume1/@appstore/HDHomeRunDVR/etc/HDHomeRunDVR.conf
and I get:
- RecordPath=/volume1/HDHomeRunDVR
- Port=59090
- RecordStreamsMax=16
- BetaEngine=0
- RunAs=hdhomerundvr
- StorageID=8633275D-***********
So... what now?
Permissions issue.
the web interface user is ran as user which is in the group 'http'
As part of the install the permissions of the .conf file are changed to be owned by the dvr user and the 'http' group.
If for some reason an update or something else gets those permissions screwed up then the DVR Manager can't read the .conf file or get the status of the engine.
However - the fact that you had to copy the www pages over means something else is probably go on
But it reminded me of something and I found my old post here
viewtopic.php?p=376952#p376952
Which was in response to another user installing 1.1.0 on DSM6 and it not creating the web folder.
For DSM6 1.0.2 and 1.1.0 are functionally the same - might be worth just running 1.0.2
As to suddenly why it might change - sounds like an update was made and/or a restart and on the boot the new policies kicked in.
And finally - just reminder - the SPKs are EOL for the last year - so I've no idea if the 2022 updates to DSM6 introduced something