I am new to Vera and DataYours. I have installed Akbooer’s Version3 Beta for UI7. I got Watcher and Cache devices created. But I a having trouble getting Graph and Dash to run. The Daemon value in DataYours device always revert back to “Watcher, Cache” after reboot.
I had the same problem with Watcher after getting DataYours created. So I just uploaded files for Watcher and Cache and then rebooted twice (maybe more times). Then both Watcher and Cache devices were created. Now have all files for Graph and Dash uploaded. But as just mentioned, the Daemon property values doesn’t seem to persist.
[quote=“dreamcryer, post:441, topic:181793”]I am new to Vera and DataYours. I have installed Akbooer’s Version3 Beta for UI7. I got Watcher and Cache devices created. But I a having trouble getting Graph and Dash to run. The Daemon value in DataYours device always revert back to “Watcher, Cache” after reboot.
I had the same problem with Watcher after getting DataYours created. So I just uploaded files for Watcher and Cache and then rebooted twice (maybe more times). Then both Watcher and Cache devices were created. Now have all files for Graph and Dash uploaded. But as just mentioned, the Daemon property values doesn’t seem to persist.
OK, glad to hear it. I was about to suggest that you just check that you had clicked outside the DAEMONS box and waited for the value to update before restarting.
I understand the technical reasons why two restarts are required, but four seems a bit excessive!
[quote=“akbooer, post:443, topic:181793”]OK, glad to hear it. I was about to suggest that you just check that you had clicked outside the DAEMONS box and waited for the value to update before restarting.
I understand the technical reasons why two restarts are required, but four seems a bit excessive![/quote]
My guess was that Dash depends on Graph. So rebooting twice was not enough for Dash to be configured. And since I had all files for Graph and Dash uploaded, the configuration for Dash probably failed and cleaned up the Daemon value somewhere when Luup engine loads up if I reload browser. Rebooting 4 times in a row without reloading the browser probably allowed all configuration to complete without interruption.
Sorry I did not have time to do more testing and debugging. If you are interested in ping-pointing the root cause, point me to the log entries that I should look for or add more logs to the log, I can probably do the investigation next weekend.
So, I installed ksmod-fs-cifs. I read here we need cifsmount which contradicts earlier posts I made about installing it: CIFS Client [Old OpenWrt Wiki].
Ironically I swear to you I tried opkg install cifsmount and it didn’t work. After installing the ksmod-fs-cifs I did eventually reboot and ran opkg install cifsmount.
So…whatever I guess…
Still didn’t work, only getting no file or directory exists.
Went back here: CIFS Client [Old OpenWrt Wiki]
I installed the special packages: opkg install kmod-nls-utf8 kmod-nls-base kmod-crypto-hmac kmod-crypto-md5 kmod-crypto-misc cifsmount
I then did mount.cifs //myip/share /tmp/tom -o user=myusername
You can put a password, I just let it prompt me.
So that actually worked. Now I go into /tmp/tom and do an ls. Another error…
Led me to this: GNU Core Utilities Frequently Asked Questions
So perhaps the share needs to be smaller…
Running out of time tonight but that’s progress I supose.
One quick update, also did it from /mnt/tom and it is working but still the exact same error.[/quote]
Try use --force-depends when installing the packages, then reboot. I have successfully mounted my NAS on VeraEdge.
Yes, I’m afraid that’s happened to all of us on the latest UI7 version(s).
Not sure if anyone has pursued this with the Vera folk?[/quote]
Ok… I have my CIFS mount back… I’m not sure what was done, but I logged a case with Vera about losing my mount after the upgrade. They replied on 2/24 and I enabled Tech Support. Got an email back today asking me to try again… Ran the following commands and my mount is working again…
