I’m tracking people, and I save their location (in my case, home, office, elsewhere) to trigger different actions (and adapt, ie when transitioning from home to elsewhere, then office).
All that said, it really depends on what you’d like to achieve.
I’m getting close to finishing my RoomMe plugin, but I’m no longer seeing log entries come in, I seem to be getting more of the following instead…
02 08/29/21 11:04:28.202 UserData::TempLogFileSystemFailure start 0 <0x76dae520>
02 08/29/21 11:04:28.230 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x76dae520>
Is this related ? If so is there anything I can do ?
I’m trying to troubleshoot some things, and could do with seeing the log entries coming in…
UPDATE : I’m also noticing the following in the logs too, shortly before the above TempLogFileSystemFailure messages…
02 08/29/21 16:04:28.146 UserData::CommitToDatabase data size 58810 58810 <0x76dae520>
01 08/29/21 16:04:28.166 UserData::WriteUserData saved--before move File Size: 16558 save size 16558 <0x76dae520>
Coincidence ? - I’m guessing related - perhaps resource constraints?
Here’s the full related section from my log…
02 08/29/21 16:28:28.148 UserData::CommitToDatabase data size 58808 58808 <0x76dae520>
01 08/29/21 16:28:28.167 UserData::WriteUserData saved--before move File Size: 16580 save size 16580 <0x76dae520>
02 08/29/21 16:28:28.168 UserData::TempLogFileSystemFailure start 0 <0x76dae520>
02 08/29/21 16:28:28.182 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x76dae520>
02 08/29/21 16:28:28.183 <0x1b>[33;1mUserData::TempLogFileSystemFailure 699 res:1
-rw-r--r-- 1 root root 504 Dec 4 2019 /etc/cmh/user_data.json.luup.lzo
-rw-r--r-- 1 root root 16564 Aug 29 16:10 /etc/cmh/user_data.json.lzo
-rw-r--r-- 1 root root 16558 Aug 29 16:04 /etc/cmh/user_data.json.lzo.1
-rw-r--r-- 1 root root 16586 Aug 29 15:58 /etc/cmh/user_data.json.lzo.2
-rw-r--r-- 1 root root 16587 Aug 29 15:46 /etc/cmh/user_data.json.lzo.3
-rw-r--r-- 1 root root 16599 Aug 29 15:40 /etc/cmh/user_data.json.lzo.4
-rw-r--r-- 1 root root 16592 Aug 29 15:28 /etc/cmh/user_data.json.lzo.5
-rw-r--r-- 1 root root 16580 Aug 29 16:28 /etc/cmh/user_data.json.lzo.new
<0x1b>[0m <0x76dae520>
02 08/29/21 16:28:28.244 UserData::TempLogFileSystemFailure start 0 <0x76dae520>
02 08/29/21 16:28:28.259 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x76dae520>
02 08/29/21 16:28:28.260 <0x1b>[33;1mUserData::TempLogFileSystemFailure 610 res:1
-rw-r--r-- 1 root root 504 Dec 4 2019 /etc/cmh/user_data.json.luup.lzo
-rw-r--r-- 1 root root 16580 Aug 29 16:28 /etc/cmh/user_data.json.lzo
-rw-r--r-- 1 root root 16564 Aug 29 16:10 /etc/cmh/user_data.json.lzo.1
-rw-r--r-- 1 root root 16558 Aug 29 16:04 /etc/cmh/user_data.json.lzo.2
-rw-r--r-- 1 root root 16586 Aug 29 15:58 /etc/cmh/user_data.json.lzo.3
-rw-r--r-- 1 root root 16587 Aug 29 15:46 /etc/cmh/user_data.json.lzo.4
-rw-r--r-- 1 root root 16599 Aug 29 15:40 /etc/cmh/user_data.json.lzo.5
<0x1b>[0m <0x76dae520>
UPDATE : Came across this on another post, which looks related, although no clear cause/fix
1 Like