Thank you for your donation!


-> Session permissions (Reapplied)
#1
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
Reply
#2
Revert to a stock 6.3.0 build (4.19.75, 32-bit)
Reply
#3
(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.
Reply
#4
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
Reply
#5
(10-10-2019, 12:16 PM)Tim Curtis Wrote: 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

I watch this for a while ...

thanks again
Reply


Forum Jump: