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.
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.
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.”
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.
[quote=“RichardTSchaefer, post:67, topic:182683”]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.[/quote]That’s great news. Seems there’s a lot of misinformation about this spread throughout various threads.
[quote=“RichardTSchaefer, post:67, topic:182683”]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.[/quote]
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?
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.
[quote=“rigpapa, post:71, topic:182683”]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.[/quote]
Thanks. I am glad it is using RAM and not the flash memory.