0.0.3.Final pre-release - volunteers required to test

[jkandasa]

@Tetnobic fixed this restore issue on the slow environment too. Thanks to reporting this issue. This is a nice catch! Updated changes on SNAPSHOT build.

https://github.com/mycontroller-org/mycontroller/commit/14c791726b833905ce5ecc69853e2fca1b33b361

[Ghydda]

Hi,

Just downloaded latest snapshot uploaded today of 0.0.3-final.
I am unable to login. The login screen just sits there, reporting no errors.
Can somebody confirm this?

Thanks.

[jkandasa]

@Ghydda I do not face any issue. Working as expected. Can you check mycontroller/log/mycontroller.log, and clear your browser cache.

[rgavrilovic]

Hi
I have an issue with this 0.0.3-Final (snapshot from feb 13). My nodes are battery powered and on the node details the battery graph can only display the last 6 hours.
Changing the view to last week or last month does not change the graph.
Changing the default interval in the metrics configuration also has no impact.
On Alpha2 the dropdown list also had no action but the default interval from the metrics configuration was taken into account.
Thanks

[jkandasa]

@rgavrilovic Thanks to report this issue. This issue recently fixed on https://github.com/mycontroller-org/mycontroller/issues/359 Kindly download latest SNAPSHOT and test it.

[rgavrilovic]

Thanks, that fixed my issue.
After the update I could not login (wrong username/password) even with a cleared cache and browser restarted. I had to apply the password recovery solution from https://github.com/mycontroller-org/mycontroller/issues/233
I did not had that login problem when updating from 0.0.3Alpha2 to 0.0.3Final from feb 12.

[jkandasa]

@rgavrilovic I never face this issue. Can you share your backup database. I can test it locally.

[rgavrilovic]

I made again the same migration multiple times without facing the same issue. It does not seem to be related to the backup.
On my first migration I untar the snapshot then started mycontroller. I then remembered I have to disable https and change the default port so I stopped mycontroller a few seconds after.
I guess the database migration triggered on first launch was not finished and the database was altered. I see many database exceptions in the logs.
I have reproduced a database corruption with a fresh install. start then stop within 3 seconds. On my RPI3 the db migration left the database corrupted and mycontroller was unable to restart.
I don't know if you can prevent a shutdown during db initialization/migration. If you can't I take the full responsibility of this bad user behaviour !

[jkandasa]

@rgavrilovic We cannot hold stop. Hence user has to care this issue. Thanks to report in detail.

[edwardb]

How can I change the database to mysql?
there is no documentation for this yet?

[jkandasa]

@edwardb Yes, there is no document for this yet. But it is simple. You can change it on mycontroller/conf/mycontroller.properties.

In the recent version, I have introduced back-end metric support. Currently, supports for InfluxDB

[edwardb]

What would be the properties needed for mysql?
Could you give me an example?
Thanks,

[jkandasa]

@edwardb Example is on mycontroller/conf/mycontroller.properties file. Can you please have a look?

[edwardb]

Thanks, it is working for me now!