Author Topic: Basic Event Logging Problems - TempLogFileSystemFailure  (Read 10520 times)

Offline Ramias

  • Sr. Member
  • ****
  • Posts: 275
  • Karma: +7/-5
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #30 on: November 20, 2015, 09:05:29 pm »
Bump :D

Trying to resolve my frequent Vera Restarts (and missing triggers while restarting).

Offline RubbrDug

  • Newbie
  • *
  • Posts: 16
  • Karma: +0/-2
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #31 on: January 11, 2016, 07:08:20 am »
Wow, this error exists for a long time. Now I have it, too.

Maybe I should add that I did no programing or hacking whatsoever. Just installed a few Apps.
« Last Edit: January 11, 2016, 07:10:41 am by RubbrDug »

Offline mostlychris

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +0/-2
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #32 on: January 30, 2016, 08:10:52 pm »
Just going to throw my 2 cents in here as well.  I've had frequent lockups as of late and usually have to power cycle.  For the first time today, I had a failure of the Luup engine but was able to SSH into the box and restart it.  I am getting the dreaded failures as well.

Code: [Select]
01      01/30/16 14:17:11.707   UserData::WriteUserData failed result:1 size2:46740 vs 46740 <0x77519320>
02      01/30/16 14:17:11.708   UserData::TempLogFileSystemFailure start 1 <0x77519320>
02      01/30/16 14:17:11.975   UserData::TempLogFileSystemFailure 0 res:0
02      01/30/16 14:17:12.016   UserData::TempLogFileSystemFailure start 0 <0x77519320>
02      01/30/16 14:17:12.056   UserData::TempLogFileSystemFailure 0 res:0
02      01/30/16 18:56:05.523   UserData::TempLogFileSystemFailure start 1 <0x77f12320>
02      01/30/16 18:56:05.884   UserData::TempLogFileSystemFailure 7804 res:1
02      01/30/16 18:56:05.887   UserData::LoadUserData previous: 0 from *1.7.1707* <0x77f12320>

You can see that it failed at 14:17 and didn't come back (I didn't notice it broken) until I did a web page load at 18:56.  Vera responded to my phone call but said they would reply to my ticket in email.  It's been a week.  I ordered another unit for replacement because I can't wait.  I haven't put it in yet, hoping I can troubleshoot this issue myself.  I am using a USB stick for logging.

Code: [Select]
Filesystem                Size      Used Available Use% Mounted on
rootfs                    9.5M      3.8M      5.7M  40% /
/dev/root                 9.3M      9.3M         0 100% /rom
tmpfs                    61.9M      3.1M     58.8M   5% /tmp
/dev/mtdblock6            9.5M      3.8M      5.7M  40% /overlay
overlayfs:/overlay        9.5M      3.8M      5.7M  40% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mtdblock10          64.8M      7.4M     57.3M  11% /storage
/dev/mtdblock10          64.8M      7.4M     57.3M  11% /etc/cmh-firmware
/dev/mtdblock10          64.8M      7.4M     57.3M  11% /etc/cmh-backup
/dev/sda1               487.9M     25.0M    437.3M   5% /tmp/log/cmh
/dev/mtdblock9            5.8M      5.8M         0 100% /mios

Code: [Select]
             total         used         free       shared      buffers
Mem:        126688       107144        19544            0        16276
-/+ buffers:              90868        35820
Swap:            0            0            0

Offline mostlychris

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +0/-2
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #33 on: January 31, 2016, 05:19:11 am »
I was watching the logs via ssh just a bit ago and refreshed the web page at the same time.  I started getting the system failure errors again.  I wanted to do a reboot via ssh quickly before everything died and this is what I got:

Code: [Select]
root@MiOS_:/tmp/log/cmh# reboot
Segmentation fault
root@MiOS_:/tmp/log/cmh# df -h
Segmentation fault
root@MiOS_:/tmp/log/cmh# top
Segmentation fault
root@MiOS_:/tmp/log/cmh# tail -f LuaUPnP.log
Segmentation fault
root@MiOS_:/tmp/log/cmh# free -m
Segmentation fault


I'm throwing this in there in case it helps to troubleshoot the issue.  I'm wondering again if I have hardware failure.

Here are the logs right at failure:

Code: [Select]
01      01/31/16 4:11:18.454    UserData::WriteUserData saved--before move File Size: 46161 save size 46161 <0x74556520>
02      01/31/16 4:11:18.454    UserData::TempLogFileSystemFailure start 0 <0x74556520>
02      01/31/16 4:11:18.491    UserData::TempLogFileSystemFailure 0 res:0
01      01/31/16 4:11:18.667    UserData::WriteUserData failed File Size: 46161 save size 45973 <0x74556520>
02      01/31/16 4:11:18.668    UserData::TempLogFileSystemFailure start 1 <0x74556520>
02      01/31/16 4:11:19.449    UserData::TempLogFileSystemFailure 0 res:0
01      01/31/16 4:11:19.668    UserData::WriteUserData failed result:1 size2:46161 vs 46161 <0x74556520>
02      01/31/16 4:11:19.668    UserData::TempLogFileSystemFailure start 1 <0x74556520>
02      01/31/16 4:11:19.999    UserData::TempLogFileSystemFailure 0 res:0
02      01/31/16 4:11:20.039    UserData::TempLogFileSystemFailure start 0 <0x74556520>
02      01/31/16 4:11:20.125    UserData::TempLogFileSystemFailure 0 res:0
06      01/31/16 4:11:20.127    Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusID was: 1 now: 2 #hooks: 0 upnp: 0 skip: 0 v:0x975618/NONE duplicate:0 <0x74556520>
06      01/31/16 4:11:20.128    Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusText was: OK now: Resetting ZWave Network #hooks: 0 upnp: 0 skip: 0 v:0xba4208/NONE duplicate:0 <0x74556520>
01      01/31/16 4:11:20.177    RAServerSync::SendAlert notification lost for time 17420660 type 7 code user_data <0x77997520>
01      01/31/16 4:11:20.691    UserData::WriteUserData saved--before move File Size: 46220 save size 46220 <0x77ef9320>
02      01/31/16 4:11:20.692    UserData::TempLogFileSystemFailure start 0 <0x77ef9320>
02      01/31/16 4:11:20.728    UserData::TempLogFileSystemFailure 0 res:0
01      01/31/16 4:11:20.919    UserData::WriteUserData failed File Size: 46220 save size 46161 <0x77ef9320>
02      01/31/16 4:11:20.920    UserData::TempLogFileSystemFailure start 1 <0x77ef9320>
02      01/31/16 4:11:21.246    UserData::TempLogFileSystemFailure 0 res:0
01      01/31/16 4:11:21.469    UserData::WriteUserData failed result:1 size2:46220 vs 46220 <0x77ef9320>
02      01/31/16 4:11:21.470    UserData::TempLogFileSystemFailure start 1 <0x77ef9320>
02      01/31/16 4:11:21.713    UserData::TempLogFileSystemFailure 0 res:0
02      01/31/16 4:11:21.751    UserData::TempLogFileSystemFailure start 0 <0x77ef9320>
02      01/31/16 4:11:21.791    UserData::TempLogFileSystemFailure 0 res:0
01      01/31/16 4:11:21.795    Mongoose XXX-mg_stop1 0x9e2cf8 1 2 <0x77ef9320>
06      01/31/16 4:11:23.181    Device_Variable::m_szValue_set device: 107 service: urn:demo-ted-striker:serviceId:PingSensor1 variable: CurrentFailureCount was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76397520>
50      01/31/16 4:11:23.183    luup_log:107: PingSensor #107 ping failed, failure = 1/10 <0x76397520>
06      01/31/16 4:11:23.223    Device_Variable::m_szValue_set device: 105 service: urn:demo-ted-striker:serviceId:PingSensor1 variable: CurrentFailureCount was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76597520>
50      01/31/16 4:11:23.225    luup_log:105: PingSensor #105 ping failed, failure = 1/10 <0x76597520>
01      01/31/16 4:11:23.811    Mongoose XXX-mg_stop2 0x9e2cf8 2 2 <0x77ef9320>
01      01/31/16 4:11:23.811    Mongoose XXX-mg_stop3 0x9e2cf8 2 2 <0x77ef9320>
01      01/31/16 4:11:23.812    Mongoose XXX-mg_stop4 0x9e2cf8 16742528 2 <0x77ef9320>
01      01/31/16 4:11:24.439    UserData::WriteUserData saved--before move File Size: 46214 save size 46214 <0x77ef9320>
02      01/31/16 4:11:24.440    UserData::TempLogFileSystemFailure start 0 <0x77ef9320>
02      01/31/16 4:11:24.474    UserData::TempLogFileSystemFailure 0 res:0

Offline pwlivewire

  • Jr. Member
  • **
  • Posts: 58
  • Karma: +0/-1
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #34 on: February 21, 2016, 06:25:56 pm »
Just got a New Vera Plus, added a few devices, noticed the interface and app is slow. Low and behold.. Log is full of Templogfilesystemfailure events. Emailed support then I'm gona return the device if I don't get a fix, huge waste of none responsive cash..
 >:(
Paul

Offline George

  • Administrator
  • Full Member
  • *****
  • Posts: 116
  • Karma: +6/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #35 on: February 22, 2016, 03:42:41 am »
Hi Paul,

Can you send me your ticket id number so we could look into it ? As for the "TempLogFileSystemFailure" this is just a function in the UI which does exactly what it says, logs any errors saving the user configuration data and as long as the user configuration data is saved successfully ("WriteUserData saved") there shouldn't be any issues.

Offline pwlivewire

  • Jr. Member
  • **
  • Posts: 58
  • Karma: +0/-1
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #36 on: February 22, 2016, 05:12:57 am »
I haven't got a ticket number back yet, e-mailed yesterday and had no reply. Sent to 'support at getvera.com' . Is there somewhere or someone i can send it to direct?
Paul

Offline mano

  • Jr. Member
  • **
  • Posts: 76
  • Karma: +0/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #37 on: February 24, 2016, 10:55:49 am »
Seeing the same here every 6 mins or so, luup restarting.
01   02/24/16 14:31:09.208   UserData::WriteUserData saved--before move File Size: 53490 save size 53490 <0x76e8a520>
01   02/24/16 14:37:09.217   UserData::WriteUserData saved--before move File Size: 53513 save size 53513 <0x76e8a520>
01   02/24/16 14:43:09.203   UserData::WriteUserData saved--before move File Size: 53506 save size 53506 <0x76e8a520>
01   02/24/16 14:49:09.257   UserData::WriteUserData saved--before move File Size: 53592 save size 53592 <0x76e8a520>
01   02/24/16 14:55:09.207   UserData::WriteUserData saved--before move File Size: 53527 save size 53527 <0x76e8a520>
01   02/24/16 15:01:09.211   UserData::WriteUserData saved--before move File Size: 53474 save size 53474 <0x76e8a520>
01   02/24/16 15:07:09.205   UserData::WriteUserData saved--before move File Size: 53587 save size 53587 <0x76e8a520>
01   02/24/16 15:13:09.205   UserData::WriteUserData saved--before move File Size: 53473 save size 53473 <0x76e8a520>
01   02/24/16 15:19:09.203   UserData::WriteUserData saved--before move File Size: 53530 save size 53530 <0x76e8a520>
01   02/24/16 15:25:09.216   UserData::WriteUserData saved--before move File Size: 53579 save size 53579 <0x76e8a520>

Raised a Support ticket few mins ago.

Offline trouty00

  • Full Member
  • ***
  • Posts: 205
  • Karma: +2/-1
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #38 on: February 24, 2016, 12:11:08 pm »
watching with interest as i have it every 6 minutes and seems to take between 3 and 15 seconds to complete the task - if its doing what it should be then great but if its doing this every 6 minutes and then has an impact on me trying to launch a scene or dim a light at exactly that time then I'd rather not be impacted by it. why every 6 minutes? why not daily in the dark hours?

Stu

Offline RichardTSchaefer

  • Master Member
  • *******
  • Posts: 9202
  • Karma: +695/-127
    • RTS Services Plugins
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #39 on: February 24, 2016, 12:31:50 pm »
This is Vera saving it's state in case it restarts because of a failure ...
In general Vera tries to save the current state before it restarts. Depending on the failure it might not be able to.

When vera reloads, it reverts to the last save point (within 6 min of the current time)
 

Offline trouty00

  • Full Member
  • ***
  • Posts: 205
  • Karma: +2/-1
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #40 on: February 24, 2016, 03:00:15 pm »
This is Vera saving it's state in case it restarts because of a failure ...
In general Vera tries to save the current state before it restarts. Depending on the failure it might not be able to.

When vera reloads, it reverts to the last save point (within 6 min of the current time)

ok - that makes sense i guess, maybe worrying about nothing in terms of resource use then, although should we be worried that they feel the need to do this so regular, are vera that worried about it falling over. I guess they cant win but its just my brain ticking..

Offline mano

  • Jr. Member
  • **
  • Posts: 76
  • Karma: +0/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #41 on: February 24, 2016, 03:10:38 pm »
This is Vera saving it's state in case it restarts because of a failure ...
In general Vera tries to save the current state before it restarts. Depending on the failure it might not be able to.

When vera reloads, it reverts to the last save point (within 6 min of the current time)
Thanks for the insight....
hmm. so design intent !

Offline xeinth

  • Full Member
  • ***
  • Posts: 136
  • Karma: +1/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #42 on: February 25, 2016, 03:56:50 pm »
Mano,

The saving of the state every 6 minutes is a design intent, getting a restart every 6 minutes is not.

I remember fondly when this was my problem.  My VeraPlus doesn't save the state for PLEG and then it crashes =).

x

Offline mano

  • Jr. Member
  • **
  • Posts: 76
  • Karma: +0/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #43 on: February 26, 2016, 05:21:29 am »
Hi xenith, Richard,
 Bit more details..
I updated my V-Lite to the latest firmware with no config and it aso restarts every 31 minutes also.
Now the real issue, is eventually the restarts leads to Lua and scene errors where some scenes do not run at all and becoming un-reliable.

Following a luup.restart using the http://192.168.0.101:3480/data_request?id=reload, all the scenes can be triggered and used without any errors being reported by luup. Eventualy the erros start creeping in. So my "suspicion" is each of these restarts builds up the degradation as time goes on, may be the save point at which is restarts is incomplete or corrupting....

Offline RichardTSchaefer

  • Master Member
  • *******
  • Posts: 9202
  • Karma: +695/-127
    • RTS Services Plugins
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #44 on: February 26, 2016, 05:11:06 pm »
There is definitely some type of system corruption going on. The fact that MCV has all of these diagnostics in the log file is an indication that they have a problem and do not have a good handle on the exact problem and as a result do not have a solution.

It might only effect a fraction of a percent ... But that is a lot of people if you consider the number of units they sell.

Possible problems can be the RAM used as a disk drive randomly failing. That might be why they dump a listing of files in the etc directory.

It can also be a lack of program memory (This is different memory than the memory used for disk space, although the log files use this space if you do not have a thumb drive installed.)
A lack of program memory can  cause havoc with all kinds of operations. And this is definitely the weak spot for a Vera Light.
« Last Edit: February 26, 2016, 05:16:33 pm by RichardTSchaefer »