-> Session permissions (Reapplied) - Printable Version +- Moode Forum (https://moodeaudio.org/forum) +-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3) +--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7) +--- Thread: -> Session permissions (Reapplied) (/showthread.php?tid=1799) |
-> Session permissions (Reapplied) - Cardone - 10-10-2019 Hi, since yesterday I have this error .... Excerpt is from today --------------------------- 20191010 090240 worker: Session permissions (OK) 20191010 090240 worker: Watchdog started 20191010 090240 worker: Ready 20191010 090241 watchdog: Session permissions (Reapplied) 20191010 090247 watchdog: Session permissions (Reapplied) 20191010 090254 watchdog: Session permissions (Reapplied) 20191010 090301 watchdog: Session permissions (Reapplied) 20191010 090307 watchdog: Session permissions (Reapplied) --------------------------- -> Moode 6.3.0 -> Linux moode 4.19.76-v8+ #1272 SMP PREEMPT Fri Oct 4 15:11:39 BST 2019 aarch64 GNU/Linux I could not find anything up to now ..... Thanks in advance for your help Zeferino RE: -> Session permissions (Reapplied) - Tim Curtis - 10-10-2019 Revert to a stock 6.3.0 build (4.19.75, 32-bit) RE: -> Session permissions (Reapplied) - Cardone - 10-10-2019 (10-10-2019, 11:33 AM)Tim Curtis Wrote: Revert to a stock 6.3.0 build (4.19.75, 32-bit) image set new and left on 32 bit .. Everything fits now ... Thank you Tim. RE: -> Session permissions (Reapplied) - Tim Curtis - 10-10-2019 Nice :-) The error "watchdog: Session permissions (Reapplied)" in theory should never happen but I recall during the development of moOde 6 series I would occasionally see incorrect permissions for the PHP session file. It was rare and only seemed to occur after loading updated development moOde sources and configs on the Pi then rebooting. A second reboot and no error. I added a bit of code to watchdog.sh script to check and reset the permissions if necessary which should correct the error after one occurrence. If it keeps reappearing in the log I may need to further investigate the issue. A new kernel or 64-bit should not cause the error. -Tim RE: -> Session permissions (Reapplied) - Cardone - 10-10-2019 (10-10-2019, 12:16 PM)Tim Curtis Wrote: Nice :-) I watch this for a while ... thanks again RE: -> Session permissions (Reapplied) - franz159 - 10-20-2019 I have this problem right now (on version 6.2.1): ...... 20191020 154950 watchdog: Session permissions (Reapplied) 20191020 154956 watchdog: Session permissions (Reapplied) 20191020 155002 watchdog: Session permissions (Reapplied) ....... I'm applying the in place update to 6.3.0.... RE: -> Session permissions (Reapplied) - TheOldPresbyope - 10-20-2019 I'm curious. How is this error manifested, e.g., what unexpected moOde behavior caused you to look at the log? And did it disappear on a reboot as Tim suggested it might? Regards, Kent RE: -> Session permissions (Reapplied) - TheOldPresbyope - 10-27-2019 (10-27-2019, 04:17 PM)liv_s Wrote: #1> Same error here: #1> Same questions I asked a week ago. What precipitated this error report? What had you done prior, what caused you to look at the log, and did it go away when you rebooted? #2> The shutdown command only stops Linux safely and puts the RPi into a low-power state. It does not turn off the power. Various people have posted power-on/power-off hacks to the Web. Google is your friend. #3> As Tim said before, this PHP behavior should not depend on the kernel. Regards, Kent RE: -> Session permissions (Reapplied) - TheOldPresbyope - 10-28-2019 @liv_s Ok, so item #1 was just something you observed along the way. Let's let Tim sort the PHP issue. Item #3 is a no-op, so we'll put it aside too. That leaves item #2. We should move any further discussion of this to a new support post. Nice repurposing of those Cisco boxes, by the way! Regards, Kent RE: -> Session permissions (Reapplied) - Tim Curtis - 10-28-2019 (10-27-2019, 04:17 PM)liv_s Wrote: Same error here: The symptoms suggest either the update did not complete successfully or there is some issue external to moOde. Either way there is breakage and not possible to troubleshoot. Start with a fresh image. |