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

Offline LucidOndine

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #60 on: December 23, 2016, 10:59:55 pm »
Just stumbled upon this after most recent firmware upgrade; I cannot even log in to the web portal as the device is in a tight spin/restart loop:
Code: [Select]
...snip...
02      12/23/16 21:56:39.266   UserData::TempLogFileSystemFailure start 0 <0x774f7520>
02      12/23/16 21:56:39.287   UserData::TempLogFileSystemFailure 5771 res:1
02      12/23/16 21:56:39.359   UserData::TempLogFileSystemFailure start 0 <0x774f7520>
02      12/23/16 21:56:39.382   UserData::TempLogFileSystemFailure 5682 res:1
02      12/23/16 21:56:39.978   UserData::TempLogFileSystemFailure start 0 <0x774f7520>
02      12/23/16 21:56:40.000   UserData::TempLogFileSystemFailure 5771 res:1
02      12/23/16 21:56:40.072   UserData::TempLogFileSystemFailure start 0 <0x774f7520>
02      12/23/16 21:56:40.095   UserData::TempLogFileSystemFailure 5682 res:1
02      12/23/16 21:56:41.572   UserData::TempLogFileSystemFailure start 0 <0x77ebe320>
02      12/23/16 21:56:41.594   UserData::TempLogFileSystemFailure 5771 res:1
02      12/23/16 21:56:41.662   UserData::TempLogFileSystemFailure start 0 <0x77ebe320>
02      12/23/16 21:56:41.684   UserData::TempLogFileSystemFailure 5682 res:1
02      12/23/16 21:56:43.395   UserData::TempLogFileSystemFailure start 0 <0x77ebe320>
02      12/23/16 21:56:43.416   UserData::TempLogFileSystemFailure 5771 res:1
02      12/23/16 21:56:43.480   UserData::TempLogFileSystemFailure start 0 <0x77ebe320>
02      12/23/16 21:56:43.501   UserData::TempLogFileSystemFailure 5682 res:1
02      12/23/16 21:56:45.045   UserData::TempLogFileSystemFailure start 1 <0x77737320>
02      12/23/16 21:56:45.147   UserData::TempLogFileSystemFailure 8655 res:1
02      12/23/16 21:56:52.926   UserData::TempLogFileSystemFailure start 0 <0x76d6f520>
02      12/23/16 21:56:52.948   UserData::TempLogFileSystemFailure 5771 res:1
02      12/23/16 21:56:53.018   UserData::TempLogFileSystemFailure start 0 <0x76d6f520>
02      12/23/16 21:56:53.043   UserData::TempLogFileSystemFailure 5682 res:1
02      12/23/16 21:56:55.170   UserData::TempLogFileSystemFailure start 0 <0x77737320>
02      12/23/16 21:56:55.191   UserData::TempLogFileSystemFailure 5771 res:1
02      12/23/16 21:56:55.258   UserData::TempLogFileSystemFailure start 0 <0x77737320>
02      12/23/16 21:56:55.280   UserData::TempLogFileSystemFailure 5682 res:1
02      12/23/16 21:56:59.880   UserData::TempLogFileSystemFailure start 0 <0x77737320>
02      12/23/16 21:56:59.900   UserData::TempLogFileSystemFailure 5771 res:1
02      12/23/16 21:56:59.964   UserData::TempLogFileSystemFailure start 0 <0x77737320>
02      12/23/16 21:56:59.985   UserData::TempLogFileSystemFailure 5682 res:1
02      12/23/16 21:57:01.571   UserData::TempLogFileSystemFailure start 1 <0x77144320>
02      12/23/16 21:57:01.674   UserData::TempLogFileSystemFailure 8006 res:1

Which is particularly frustrating, as the hub is completely useless in this capacity. I can't even login to enable the portal to have service check on it.

Offline moishaSPB

  • Sr. Newbie
  • *
  • Posts: 22
  • Karma: +1/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #61 on: March 18, 2017, 08:41:06 am »
My Vera Edge 7 month old unit loops in this UserData::TempLogFileSystemFailure restart on and off for the last couple of month.
Amazing how many folks experiencing this for the last 5+ years and Vera Ltd. offers no solution.

Offline moishaSPB

  • Sr. Newbie
  • *
  • Posts: 22
  • Karma: +1/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #62 on: March 23, 2017, 10:36:18 pm »
I sent mail to support (two actually) and received the following "we get paid by the word count" response :

"After checking the logs provided by the unit and with our developers, the TempLogFileSystemFailure is a function in the Vera engine used to log the WriteUserData function. This will check if the user_data configuration file has been saved correctly and save the output in a temporary file, and if it was it will delete it. The functions will verify periodically if the configuration file has been saved, no matter if you?ve made these changes yourself or the unit updated variables based on the connected devices output.
As long as you?ll see the ?WriteUserData saved? message you?ll know for sure the file has been saved correctly and the temporary file will be deleted. Each time the configuration file fails to save, it will log it in the alerts section of your Vera unit. Also keep in mind that this is one of the few safeties available for the user_data configuration file, which will backup the last 5 changes made to it so the Vera engine will be able to restore one of the earlier versions if necessary.
Please let me know if I can be of any other further assistance and I will get back to you asap."

My further requests for help are being ignored.

This is super frustrating.

02      03/23/17 21:34:15.437   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 21:40:15.429   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 21:40:15.630   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 21:46:15.337   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 21:46:15.444   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 21:52:15.322   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 21:52:15.420   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 21:58:15.323   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 21:58:15.423   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:04:15.332   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:04:15.430   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:10:15.324   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:10:15.420   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:16:15.402   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:16:15.597   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:22:15.323   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:22:15.432   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:28:15.334   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:28:15.437   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:34:15.323   UserData::TempLogFileSystemFailure start 0 <0x76de8520>
02      03/23/17 22:34:15.442   UserData::TempLogFileSystemFailure start 0 <0x76de8520>

Offline Explosive

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #63 on: March 24, 2017, 06:43:36 am »
I experience the exact same thing, every 6 minutes...


Offline moishaSPB

  • Sr. Newbie
  • *
  • Posts: 22
  • Karma: +1/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #64 on: March 24, 2017, 07:51:37 am »
Send an e-mail to support@getvera.com so we have a trail of Vera ignoring this data corruption issue for years.

Offline Dolphran

  • Jr. Member
  • **
  • Posts: 86
  • Karma: +1/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #65 on: December 20, 2017, 10:18:48 am »
I get the TempLogFileSystemFailure every 6 minutes on a recently purchased VeraPlus. I can't believe this has been happening on many systems for years without any response from MCV! I opened a support ticket.

Offline RichardTSchaefer

  • Master Member
  • *******
  • Posts: 10020
  • Karma: +758/-141
    • RTS Services Plugins
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #66 on: December 20, 2017, 10:26:32 am »
This is NOT an error ... it is MCV's logging looking for errors ...
There are a whole sequence of messages  that they are looking to capture some event.

They ignore this message ... because as I said ... it in itself is meaningless.



Offline Dolphran

  • Jr. Member
  • **
  • Posts: 86
  • Karma: +1/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #67 on: December 20, 2017, 06:36:02 pm »
This is NOT an error ... it is MCV's logging looking for errors ...
There are a whole sequence of messages  that they are looking to capture some event.

They ignore this message ... because as I said ... it in itself is meaningless.
That's great news. Seems there's a lot of misinformation about this spread throughout various threads.

Offline jchin

  • Sr. Newbie
  • *
  • Posts: 28
  • Karma: +0/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #68 on: December 30, 2017, 02:24:47 pm »
This is NOT an error ... it is MCV's logging looking for errors ...
There are a whole sequence of messages  that they are looking to capture some event.

They ignore this message ... because as I said ... it in itself is meaningless.


While I agree that the message itself is meaningless, I still want to know why it is constantly logging this same error message and directory dump?
This just takes up space and more wear on the flash drive.  No?

Offline RichardTSchaefer

  • Master Member
  • *******
  • Posts: 10020
  • Karma: +758/-141
    • RTS Services Plugins
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #69 on: December 31, 2017, 10:35:06 am »
Did you look at the "Second" statement in my answer!
I am usually pretty terse ... so if I take the time to say something ... it is meaningful.

Offline rigpapa

  • Sr. Member
  • ****
  • Posts: 338
  • Karma: +46/-0
    • toggledbits.com
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #70 on: December 31, 2017, 12:50:02 pm »
I agree with you, @JChin. The new WWN interface also logs a ton of useless data to the logs. That can mostly be controlled by modifying the logging settings (at some expense of other data that may be useful later), but those internal messages, directory and process dumps can't be controlled this way apparently. The excess of logged messages is one of Vera's quirks.

But, to your question, the good news is that the logs are stored on a temporary filesystem (tmpfs/ramfs), and that's RAM-based, so no wear occurs to the flash when writing them.
Author of Rachio, Deus Ex Machina II, Intesis WMP Gateway, SiteSensor, DelayLight, Auto Virtual Thermostat and VirtualSensor plugins. Vera Plus w/100+ Z-wave devices. Vera3 sandbox.

Offline jchin

  • Sr. Newbie
  • *
  • Posts: 28
  • Karma: +0/-0
Re: Basic Event Logging Problems - TempLogFileSystemFailure
« Reply #71 on: January 19, 2018, 11:05:34 pm »
I agree with you, @JChin. The new WWN interface also logs a ton of useless data to the logs. That can mostly be controlled by modifying the logging settings (at some expense of other data that may be useful later), but those internal messages, directory and process dumps can't be controlled this way apparently. The excess of logged messages is one of Vera's quirks.

But, to your question, the good news is that the logs are stored on a temporary filesystem (tmpfs/ramfs), and that's RAM-based, so no wear occurs to the flash when writing them.

Thanks.  I am glad it is using RAM and not the flash memory.