openmediavault-WOL - standbyhour: The value "" is not an integer.
-
- gelöst
- OMV 6.x
- filipeaguiars
-
-
filipeaguiars
Hat den Titel des Themas von „openmediavault-WOL - standbyhour: The value "" is not an integer. openmediavault“ zu „openmediavault-WOL - standbyhour: The value "" is not an integer.“ geändert. -
-
votdev
Hat das Label OMV 6.x hinzugefügt. -
This is fixed in 6.1 in the repo now. I moved the rtcwake tab to a button on the datatable.
-
Thanks for the replies!
Please open a bug report here.
Nice, I`m going to open a bug report
.
This is fixed in 6.1 in the repo now. I moved the rtcwake tab to a button on the datatable.
Thanks for the update! I`ve upgraded to 6.1, but now I`m getting the following error:
I`m opening a bug report now.
Thank you so much, guys!
-
Just opened the ticket: https://github.com/OpenMediaVa…enmediavault-wol/issues/6
-
Thanks for the update! I`ve upgraded to 6.1, but now I`m getting the following error:
Actually I think I'm wrong here. I ran the update management but is now running 6.0.33-1 (Shaitan), and not 6.1.6.0.33 -1 (Shaitan)
I'm not sure how to upgrade to 6.1 haha
-
Hi
You have activated one question in the OMV GUI in the network interfaces and also in the bios?
-
The form problem has been fixed but I don't have a good system to test the actual rtcwake command on. So, if you could run the command in the error and see what needs to be tweaked, that would be helpful.
-
I ran the update management but is now running 6.0.33-1 (Shaitan), and not 6.1.6.0
Your OMV version is 6.0.33-1. The openmediavault-wol plugin version is 6.1.
-
Your OMV version is 6.0.33-1. The openmediavault-wol plugin version is 6.1.
Oh, gotcha! Thanks!
The form problem has been fixed but I don't have a good system to test the actual rtcwake command on. So, if you could run the command in the error and see what needs to be tweaked, that would be helpful.
Ok, after running that command I got the following message:
rtcwake: time doesn't go backward to Mon Aug 8 04:00:00 2022
The command was:
export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/loca l/sbin; export LANG=C.UTF-8; export LANGUAGE=; rtcwake -a -t 1659931200 -m memAm I missing something here? haha Sry, I'm a newbie
-
Am I missing something here? haha Sry, I'm a newbie
The plugin is using the literal time you enter. So, if it is 0800 and you enter 0400, the 0400 is not tomorrow. Can you enter a time that is after the current time of your system?
-
-
it will always try to set the time to -t 1659931200
ok. that is helpful. It seems doubtful that this feature has ever worked then. I will see what else I can do to fix.
-
it will always try to set the time to -t 1659931200
Are you sure? I just tried 1800 on my system and it did not fail. When I put in time before current (0800 and 0900), the time that is failing is changing. Did you hit ctrl-shift-R after installing the plugin?
-
Are you sure? I just tried 1800 on my system and it did not fail. When I put in the time before current (0800 and 0900), the time that is failing is changing. Did you hit ctrl-shift-R after installing the plugin?
Well, actually the value changes. My mistake!
Pressing ctrl-shift-R for some reason didn't work. I had to open OMV on another browser and now it seems I don't get this error when putting in a time after the current time.
If possible, to help newbies like myself, it would be good to display a message like "Insert a time after current time" or something better (English is not my first language haha)
Thank you a lot for your help and patience!
-
it would be good to display a message like "Insert a time after current time" or something bette
I think I will make it assume the next day if the time you enter is before the current time. Kind of hard to shut off the machine in the past lol
-
filipeaguiars
Hat das Label gelöst hinzugefügt.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!