Dynamix - Web GUI


Recommended Posts

I think that if there is a default value (as you set it) and have an option to change the values as you see fit, then if a user is smart enough to change the default values then he should be smart enough to know and take responsibility for the values he enters and their consequences.

 

Understood  :)

Link to comment
  • Replies 1.3k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Note that starting from this version the new powerdown utlity - created by dlandon - is automatically installed together with the Dynamix webGui. This replaces the old powerdown version which came previously with Dynamix webGui, and is a much improved version which works on both unRAID v5 and v6.

 

Does this need any configuration by the user, or should pressing the power button result in a 'safe' shutdown automatically now?

 

Thanks again for all your hard work!

Link to comment

Note that starting from this version the new powerdown utlity - created by dlandon - is automatically installed together with the Dynamix webGui. This replaces the old powerdown version which came previously with Dynamix webGui, and is a much improved version which works on both unRAID v5 and v6.

 

Does this need any configuration by the user, or should pressing the power button result in a 'safe' shutdown automatically now?

 

Thanks again for all your hard work!

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

Link to comment

Note that starting from this version the new powerdown utlity - created by dlandon - is automatically installed together with the Dynamix webGui. This replaces the old powerdown version which came previously with Dynamix webGui, and is a much improved version which works on both unRAID v5 and v6.

 

Does this need any configuration by the user, or should pressing the power button result in a 'safe' shutdown automatically now?

 

Thanks again for all your hard work!

 

just curious, does this replace the one that lime-tech provides? If i unistall/remove dynamix, will the new powerdown remain?

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

Link to comment

 

just curious, does this replace the one that lime-tech provides? If i unistall/remove dynamix, will the new powerdown remain?

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

 

Yes it replaces the stock version.  It will be removed when Dynamix is removed because it is a package installed by Dynamix.

 

More information here: http://lime-technology.com/forum/index.php?topic=31735.0

Link to comment

I've been trying to keep up with all the posts about Dynamix, but I haven't seen this issue mentioned yet.  Sorry if it is a duplicate post.

 

When the black theme is selected, the status messages at the bottom of the screen do not show up when the array is stopped or started.

 

Black text on a black background?

Link to comment

I've been trying to keep up with all the posts about Dynamix, but I haven't seen this issue mentioned yet.  Sorry if it is a duplicate post.

 

When the black theme is selected, the status messages at the bottom of the screen do not show up when the array is stopped or started.

 

Black text on a black background?

 

You are the first to notice! Indeed black text on black background.

 

Thanks for your feedback, I'll have it corrected in a new version.

 

Link to comment

 

A very minor issue, the legend for an unassigned drive shows 2 blue balls, one for 'New disk' and one for 'Disk spun-down'.  Thanks for all your hard work!

 

Wait wait , nobody took this, two blue balls!

 

 

Sorry I had to.

 

 

Sent from my iPhone using Tapatalk

Link to comment

Yes it replaces the stock version.  It will be removed when Dynamix is removed because it is a package installed by Dynamix.

More information here: http://lime-technology.com/forum/index.php?topic=31735.0

 

Thanks!

 

Here's the bottom of my syslog - any clues here about why the system stats plugin fails?

 

Mar  2 15:18:29 Tower kernel: piix4_smbus 0000:00:07.3: Host SMBus controller not enabled!
Mar  2 15:18:29 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo 127.0.0.1
Mar  2 15:18:29 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
Mar  2 15:18:29 Tower logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 mtu 9000
Mar  2 15:18:29 Tower kernel: e1000: eth0 changing MTU from 1500 to 9000
Mar  2 15:18:29 Tower logger: /etc/rc.d/rc.inet1:  Polling for DHCP server on interface eth0:
Mar  2 15:18:29 Tower logger: /etc/rc.d/rc.inet1:  /sbin/dhcpcd -t 10 -h Tower -L eth0
Mar  2 15:18:29 Tower dhcpcd[1008]: version 5.2.7 starting
Mar  2 15:18:29 Tower dhcpcd[1008]: forked to background, child pid 1009
Mar  2 15:18:29 Tower logger: /etc/rc.d/rc.inet1:  /sbin/route add default gw 192.168.1.1 metric 1
Mar  2 15:18:29 Tower logger: SIOCADDRT: Network is unreachable
Mar  2 15:18:29 Tower rpc.statd[1037]: Version 1.2.2 starting
Mar  2 15:18:29 Tower sm-notify[1039]: Version 1.2.2 starting
Mar  2 15:18:29 Tower rpc.statd[1037]: Failed to read /var/lib/nfs/state: Success
Mar  2 15:18:29 Tower kernel: e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Mar  2 15:18:29 Tower rpc.statd[1037]: Initializing NSM state
Mar  2 15:18:29 Tower rpc.statd[1037]: Running as root.  chown /var/lib/nfs to choose different user
Mar  2 15:18:29 Tower dhcpcd[1009]: eth0: broadcasting for a lease
Mar  2 15:18:29 Tower acpid: starting up with proc fs 
Mar  2 15:18:29 Tower acpid: skipping conf file /etc/acpi/events/. 
Mar  2 15:18:29 Tower acpid: skipping conf file /etc/acpi/events/.. 
Mar  2 15:18:29 Tower acpid: 1 rule loaded 
Mar  2 15:18:29 Tower acpid: waiting for events: event logging is off 
Mar  2 15:18:29 Tower crond[1073]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel notice 
Mar  2 15:18:29 Tower logger: Installing system plugins
Mar  2 15:18:29 Tower logger: installing plugin: dynamix.webGui-2.2.2-noarch-bergware
Mar  2 15:18:29 Tower logger:  file /tmp/plugin-startup: successfully wrote INLINE file contents
Mar  2 15:18:30 Tower dhcpcd[1009]: eth0: offered 192.168.1.251 from 192.168.1.1
Mar  2 15:18:30 Tower dhcpcd[1009]: eth0: acknowledged 192.168.1.251 from 192.168.1.1
Mar  2 15:18:30 Tower dhcpcd[1009]: eth0: checking for 192.168.1.251
Mar  2 15:18:35 Tower dhcpcd[1009]: eth0: leased 192.168.1.251 for 86400 seconds
Mar  2 15:18:36 Tower logger:   /bin/bash /tmp/plugin-startup ... success
Mar  2 15:18:36 Tower logger:  file /boot/config/plugins/dynamix/dynamix.webGui.cfg: already exists
Mar  2 15:18:36 Tower logger:  file /boot/plugins/dynamix.webGui-2.2.2-i486-1.txz: already exists
Mar  2 15:18:36 Tower logger:   upgradepkg --install-new /boot/plugins/dynamix.webGui-2.2.2-i486-1.txz ... 
Mar  2 15:18:36 Tower logger: +==============================================================================
Mar  2 15:18:36 Tower logger: | Installing new package /boot/plugins/dynamix.webGui-2.2.2-i486-1.txz
Mar  2 15:18:36 Tower logger: +==============================================================================
Mar  2 15:18:36 Tower logger: 
Mar  2 15:18:37 Tower logger: Verifying package dynamix.webGui-2.2.2-i486-1.txz.
Mar  2 15:18:37 Tower logger: Installing package dynamix.webGui-2.2.2-i486-1.txz:
Mar  2 15:18:37 Tower logger: PACKAGE DESCRIPTION:
Mar  2 15:18:38 Tower logger: Package dynamix.webGui-2.2.2-i486-1.txz installed.
Mar  2 15:18:38 Tower logger: 
Mar  2 15:18:38 Tower logger: 
Mar  2 15:18:38 Tower logger: success
Mar  2 15:18:38 Tower logger:  file /boot/config/plugins/images/dynamix.webGui.png: already exists
Mar  2 15:18:38 Tower logger:  file /usr/local/emhttp/plugins/webGui/images/dynamix.webGui.png: successfully copied LOCAL file
Mar  2 15:18:38 Tower logger:  file /boot/packages/powerdown-2.06-noarch-unRAID.tgz: already exists
Mar  2 15:18:38 Tower logger:   CTRLALTDEL=YES upgradepkg --install-new /boot/packages/powerdown-2.06-noarch-unRAID.tgz ... 
Mar  2 15:18:38 Tower logger: +==============================================================================
Mar  2 15:18:38 Tower logger: | Installing new package /boot/packages/powerdown-2.06-noarch-unRAID.tgz
Mar  2 15:18:38 Tower logger: +==============================================================================
Mar  2 15:18:38 Tower logger: 
Mar  2 15:18:38 Tower logger: Verifying package powerdown-2.06-noarch-unRAID.tgz.
Mar  2 15:18:38 Tower logger: Installing package powerdown-2.06-noarch-unRAID.tgz:
Mar  2 15:18:38 Tower logger: PACKAGE DESCRIPTION:
Mar  2 15:18:38 Tower logger: #
Mar  2 15:18:38 Tower logger: # powerdown  Control scripts for the unRAID server Environment.
Mar  2 15:18:38 Tower logger: #
Mar  2 15:18:38 Tower logger: # Copyright (C) 2008-2014 by Robert Cotrone & Dan Landon
Mar  2 15:18:38 Tower logger: #
Mar  2 15:18:38 Tower logger: # Adds /sbin/powerdown script to assist with quick unRAID poweroff
Mar  2 15:18:38 Tower logger: #
Mar  2 15:18:38 Tower logger: # Install Variable options:
Mar  2 15:18:38 Tower logger: # CTRLALTDEL=yes set ctrl-alt-del to do powerdown instead of reboot
Mar  2 15:18:38 Tower logger: # SYSLOG=YES     do initial syslog saving upon installation
Mar  2 15:18:38 Tower logger: # STATUS=YES     Show status upon installation
Mar  2 15:18:38 Tower logger: # START=YES      do initial start upon installation
Mar  2 15:18:38 Tower logger: # 
Mar  2 15:18:38 Tower logger: # Install with VAR's as defined above like:
Mar  2 15:18:38 Tower logger: # VAR=YES OTHERVAR=YES installpkg powerdown-2.06-noarch-unRAID.tgz
Mar  2 15:18:38 Tower logger: # Like Like: 
Mar  2 15:18:38 Tower logger: # CTRLALTDEL=yes installpkg powerdown-2.06-noarch-unRAID.tgz
Mar  2 15:18:38 Tower logger: # 
Mar  2 15:18:38 Tower logger: # /etc/rc.d/rc.unRAID script has basic pre-power down functions
Mar  2 15:18:38 Tower logger: # Hooks are placed in /etc/rc.d/rc.local_shutdown
Mar  2 15:18:38 Tower logger: # to allow normal poweroff/shutdown commands do a graceful shutdown
Mar  2 15:18:38 Tower logger: # 
Mar  2 15:18:38 Tower logger: # Diagnostic mode for quick syslog dump/save to /boot/logs
Mar  2 15:18:38 Tower logger: # call as /etc/rc.d/ec.unRAID diag
Mar  2 15:18:38 Tower logger: # call as /etc/rc.d/rc.unRAID syslog 
Mar  2 15:18:38 Tower logger: #
Mar  2 15:18:38 Tower logger: Executing install script for powerdown-2.06-noarch-unRAID.tgz.
Mar  2 15:18:38 Tower init: Re-reading inittab
Mar  2 15:18:38 Tower logger: kernel.poweroff_cmd = /sbin/powerdown
Mar  2 15:18:38 Tower logger: Package powerdown-2.06-noarch-unRAID.tgz installed.
Mar  2 15:18:38 Tower logger: 
Mar  2 15:18:38 Tower logger: 
Mar  2 15:18:38 Tower logger: success
Mar  2 15:18:38 Tower logger:  file /tmp/plugin-install: successfully wrote INLINE file contents
Mar  2 15:18:38 Tower logger:   /bin/bash /tmp/plugin-install ... executing !
Mar  2 15:18:38 Tower logger: 
Mar  2 15:18:38 Tower logger: -----------------------------------------------------------
Mar  2 15:18:38 Tower logger:  dynamix.webGui has been installed.
Mar  2 15:18:38 Tower logger: 
Mar  2 15:18:38 Tower logger:  Created by Bergware International
Mar  2 15:18:38 Tower logger:  Dynamic graphical interface for unRAID media server
Mar  2 15:18:38 Tower logger:  Copyright 2014, Bergware International
Mar  2 15:18:38 Tower logger:  Version: 2.2.2
Mar  2 15:18:38 Tower logger: -----------------------------------------------------------
Mar  2 15:18:38 Tower logger: 
Mar  2 15:18:38 Tower logger: success
Mar  2 15:18:38 Tower logger:  file /var/log/plugins/dynamix.webGui: successfully wrote INLINE file contents
Mar  2 15:18:38 Tower logger:  plugin successfully installed
Mar  2 15:18:38 Tower logger: Installing user plugins
Mar  2 15:18:38 Tower logger: installing plugin: dynamix.plugin.control-2.1.1-noarch-bergware
Mar  2 15:18:38 Tower logger:  file /tmp/plugin-startup: successfully wrote INLINE file contents
Mar  2 15:18:38 Tower logger:   /bin/bash /tmp/plugin-startup ... success
Mar  2 15:18:38 Tower logger:  file /boot/config/plugins/dynamix/dynamix.plugin.control.cfg: already exists
Mar  2 15:18:38 Tower logger:  file /boot/config/plugins/dynamix/dynamix.plugin.control-2.1.1-i486-1.txz: already exists
Mar  2 15:18:39 Tower logger:   upgradepkg --install-new /boot/config/plugins/dynamix/dynamix.plugin.control-2.1.1-i486-1.txz ... 
Mar  2 15:18:39 Tower logger: +==============================================================================
Mar  2 15:18:39 Tower logger: | Installing new package /boot/config/plugins/dynamix/dynamix.plugin.control-2.1.1-i486-1.txz
Mar  2 15:18:39 Tower logger: +==============================================================================
Mar  2 15:18:39 Tower logger: 
Mar  2 15:18:39 Tower logger: Verifying package dynamix.plugin.control-2.1.1-i486-1.txz.
Mar  2 15:18:39 Tower logger: Installing package dynamix.plugin.control-2.1.1-i486-1.txz:
Mar  2 15:18:39 Tower logger: PACKAGE DESCRIPTION:
Mar  2 15:18:39 Tower logger: Package dynamix.plugin.control-2.1.1-i486-1.txz installed.
Mar  2 15:18:39 Tower logger: 
Mar  2 15:18:39 Tower logger: 
Mar  2 15:18:39 Tower logger: success
Mar  2 15:18:39 Tower logger:  file /boot/config/plugins/images/dynamix.plugin.control.png: already exists
Mar  2 15:18:39 Tower logger:  file /usr/local/emhttp/plugins/dynamix/images/dynamix.plugin.control.png: successfully copied LOCAL file
Mar  2 15:18:39 Tower logger:  file /tmp/plugin-install: successfully wrote INLINE file contents
Mar  2 15:18:39 Tower logger:   /bin/bash /tmp/plugin-install ... executing !
Mar  2 15:18:39 Tower logger: 
Mar  2 15:18:39 Tower logger: -----------------------------------------------------------
Mar  2 15:18:39 Tower logger:  dynamix.plugin.control has been installed.
Mar  2 15:18:39 Tower logger:  This plugin requires Dynamix webGui to operate
Mar  2 15:18:39 Tower logger:  Copyright 2014, Bergware International
Mar  2 15:18:39 Tower logger:  Version: 2.1.1
Mar  2 15:18:39 Tower logger: -----------------------------------------------------------
Mar  2 15:18:39 Tower logger: 
Mar  2 15:18:39 Tower logger: success
Mar  2 15:18:39 Tower logger:  file /var/log/plugins/dynamix.plugin.control: successfully wrote INLINE file contents
Mar  2 15:18:39 Tower logger:  plugin successfully installed
Mar  2 15:18:39 Tower logger: installing plugin: dynamix.system.stats-2.1.2-noarch-bergware
Mar  2 15:18:39 Tower logger:  file /tmp/plugin-startup: successfully wrote INLINE file contents
Mar  2 15:18:39 Tower logger:   /bin/bash /tmp/plugin-startup ... success
Mar  2 15:18:39 Tower logger:  file /tmp/plugin-packages: successfully wrote INLINE file contents
Mar  2 15:18:39 Tower logger:  file /boot/config/plugins/dynamix/dynamix.system.stats.cfg: already exists
Mar  2 15:18:39 Tower logger:  file /boot/config/plugins/dynamix/dynamix.system.stats-2.1.2-i486-1.txz: already exists
Mar  2 15:18:39 Tower logger:   upgradepkg --install-new /boot/config/plugins/dynamix/dynamix.system.stats-2.1.2-i486-1.txz ... 
Mar  2 15:18:39 Tower logger: +==============================================================================
Mar  2 15:18:39 Tower logger: | Installing new package /boot/config/plugins/dynamix/dynamix.system.stats-2.1.2-i486-1.txz
Mar  2 15:18:39 Tower logger: +==============================================================================
Mar  2 15:18:39 Tower logger: 
Mar  2 15:18:39 Tower logger: Verifying package dynamix.system.stats-2.1.2-i486-1.txz.
Mar  2 15:18:40 Tower logger: Installing package dynamix.system.stats-2.1.2-i486-1.txz:
Mar  2 15:18:40 Tower logger: PACKAGE DESCRIPTION:
Mar  2 15:18:40 Tower logger: Package dynamix.system.stats-2.1.2-i486-1.txz installed.
Mar  2 15:18:40 Tower logger: 
Mar  2 15:18:40 Tower logger: 
Mar  2 15:18:40 Tower logger: success
Mar  2 15:18:40 Tower logger:  file /boot/config/plugins/images/dynamix.system.stats.png: already exists
Mar  2 15:18:40 Tower logger:  file /usr/local/emhttp/plugins/dynamix/images/dynamix.system.stats.png: successfully copied LOCAL file
Mar  2 15:18:40 Tower logger:  file /etc/rc.d/rc.sysstat: successfully wrote INLINE file contents
Mar  2 15:18:40 Tower logger:   successfully changed file mode
Mar  2 15:18:40 Tower logger:  file /tmp/plugin-install: successfully wrote INLINE file contents
Mar  2 15:18:40 Tower logger:   /bin/bash /tmp/plugin-install ... executing !
Mar  2 15:43:36 Tower in.telnetd[2167]: connect from 192.168.1.129 (192.168.1.129)

Link to comment

 

just curious, does this replace the one that lime-tech provides? If i unistall/remove dynamix, will the new powerdown remain?

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

 

Yes it replaces the stock version.  It will be removed when Dynamix is removed because it is a package installed by Dynamix.

 

More information here: http://lime-technology.com/forum/index.php?topic=31735.0

 

Hi.

Currently I'm using a few addons from unMenu (apcupsd, ssmtp, scheduled email notifications, monthly check, powerdown on overtemp and clean powerdown).

Does your version, been installed with dynamic, replace the package I install from unMenu ?

Should I stop installing the "powerdown on overtemp" from unMenu (if I read correctly in your link, dynamix has it built-in) ?

Thanks

Link to comment

 

just curious, does this replace the one that lime-tech provides? If i unistall/remove dynamix, will the new powerdown remain?

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

 

Yes it replaces the stock version.  It will be removed when Dynamix is removed because it is a package installed by Dynamix.

 

More information here: http://lime-technology.com/forum/index.php?topic=31735.0

 

Hi.

Currently I'm using a few addons from unMenu (apcupsd, ssmtp, scheduled email notifications, monthly check, powerdown on overtemp and clean powerdown).

Does your version, been installed with dynamic, replace the package I install from unMenu ?

Should I stop installing the "powerdown on overtemp" from unMenu (if I read correctly in your link, dynamix has it built-in) ?

Thanks

 

If you install Dynamix you don't need to install the powerdown package from unMenu.  Dynamix does all the things you are adding from unMenu.  Email notifications, monthly parity check, powerdown on overtemp, and clean powerdown are all a part of Dynamix.

Link to comment

 

just curious, does this replace the one that lime-tech provides? If i unistall/remove dynamix, will the new powerdown remain?

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

 

Yes it replaces the stock version.  It will be removed when Dynamix is removed because it is a package installed by Dynamix.

 

More information here: http://lime-technology.com/forum/index.php?topic=31735.0

 

Hi.

Currently I'm using a few addons from unMenu (apcupsd, ssmtp, scheduled email notifications, monthly check, powerdown on overtemp and clean powerdown).

Does your version, been installed with dynamic, replace the package I install from unMenu ?

Should I stop installing the "powerdown on overtemp" from unMenu (if I read correctly in your link, dynamix has it built-in) ?

Thanks

 

If you install Dynamix you don't need to install the powerdown package from unMenu.  Dynamix does all the things you are adding from unMenu.  Email notifications, monthly parity check, powerdown on overtemp, and clean powerdown are all a part of Dynamix.

I still use unMenu pkgs to have the option of renaming all my plugins for a clean reboot of the server (don't have a keyboard or monitor connected), so using the unMenu pkgs makes apcupsd and email notifications with clean powerdown available.

My question is - if I leave my unMenu configuration as-is, does the "clean powerdown" that dynamix install replace the one installed via unmenu  ?

Link to comment

 

just curious, does this replace the one that lime-tech provides? If i unistall/remove dynamix, will the new powerdown remain?

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

 

Yes it replaces the stock version.  It will be removed when Dynamix is removed because it is a package installed by Dynamix.

 

More information here: http://lime-technology.com/forum/index.php?topic=31735.0

 

Hi.

Currently I'm using a few addons from unMenu (apcupsd, ssmtp, scheduled email notifications, monthly check, powerdown on overtemp and clean powerdown).

Does your version, been installed with dynamic, replace the package I install from unMenu ?

Should I stop installing the "powerdown on overtemp" from unMenu (if I read correctly in your link, dynamix has it built-in) ?

Thanks

 

If you install Dynamix you don't need to install the powerdown package from unMenu.  Dynamix does all the things you are adding from unMenu.  Email notifications, monthly parity check, powerdown on overtemp, and clean powerdown are all a part of Dynamix.

I still use unMenu pkgs to have the option of renaming all my plugins for a clean reboot of the server (don't have a keyboard or monitor connected), so using the unMenu pkgs makes apcupsd and email notifications with clean powerdown available.

My question is - if I leave my unMenu configuration as-is, does the "clean powerdown" that dynamix install replace the one installed via unmenu  ?

 

Not necessarily.  It depends on the sequence of installation.  This is a case of the last one there wins.  The last powerdown package installed will be the active one.

Link to comment

 

just curious, does this replace the one that lime-tech provides? If i unistall/remove dynamix, will the new powerdown remain?

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

 

Yes it replaces the stock version.  It will be removed when Dynamix is removed because it is a package installed by Dynamix.

 

More information here: http://lime-technology.com/forum/index.php?topic=31735.0

 

Hi.

Currently I'm using a few addons from unMenu (apcupsd, ssmtp, scheduled email notifications, monthly check, powerdown on overtemp and clean powerdown).

Does your version, been installed with dynamic, replace the package I install from unMenu ?

Should I stop installing the "powerdown on overtemp" from unMenu (if I read correctly in your link, dynamix has it built-in) ?

Thanks

 

If you install Dynamix you don't need to install the powerdown package from unMenu.  Dynamix does all the things you are adding from unMenu.  Email notifications, monthly parity check, powerdown on overtemp, and clean powerdown are all a part of Dynamix.

I still use unMenu pkgs to have the option of renaming all my plugins for a clean reboot of the server (don't have a keyboard or monitor connected), so using the unMenu pkgs makes apcupsd and email notifications with clean powerdown available.

My question is - if I leave my unMenu configuration as-is, does the "clean powerdown" that dynamix install replace the one installed via unmenu  ?

 

Not necessarily.  It depends on the sequence of installation.  This is a case of the last one there wins.  The last powerdown package installed will be the active one.

 

The best way to get around this would be to install the new script that dlandon wrote as well.  It's better than the one you're getting from unMENU anyway, and if you do require support you won't have to figure out which version of the script is running/causing issues.

Link to comment

Some observations, a bit long, hope you don't mind!

 

1. I was a bit dismayed by the automatic installation of the new powerdown, as it caused the deletion of a number of syslogs, but I realize that is an issue probably isolated to only me.  Originally, I took one of Rob's (WeeboTech) early powerdown scripts and modified it for my use, and it has worked perfectly all this time.  Among other things, I removed the syslog files pruning, as I wanted all of them kept, in the logs folder.  The powerdown script from its earliest days includes a loop to delete all but the most recent 10 syslogs, which is probably fine with almost everyone (except me!).  I would like to request that you (or dlandon) add a little configurability to the powerdown, as some users may want the ability to control CTRLALTDEL, possibly LOGDIR (where the logs are saved), and LOGSAVE (how many syslogs to keep).  I would like to turn off the log file limiting function completely, but others may want to save only the last 3 or perhaps the last 20.  At present, I don't quite know how to get around this, attempt to go back to Dynamix 2.2.1, or perhaps try to create a modified powerdown txz, placed in /boot/config/plugins so it runs last, but that would mean it has to be modified with each update of powerdown, which is somewhat inconvenient.  I did find the deleted syslogs in my backup of the folder, but that means the backup is not a real backup any longer since it held the only copies.  So it was time to update my backup processes, probably needed anyway.  By the way, the pruning did not quite work right (thankfully for me!), as it only deleted 10 to 13 syslogs, leaving about 70 others untouched, no idea why.  Also, it would be good if powerdown would check for other installations of powerdown, and only install itself if it's a newer version, but I should probably mention that in dlandon's Powerdown thread, not here.

 

2. For me, the Dashboard has been of only marginal help, though a good idea for most.  I have no Shares and there's no other user, so those areas are not useful to me.

  a. What to me would be useful in their place is a syslog tail of perhaps 20 lines.

  b. It would also be nice in the Parity Check monitoring section to display the current speed.

  c. During the Parity Check, 3 drives raised the red heat flag, with temps (only visible on the Main page) of 40 to 42.  Here in Florida, those are not hot, just warm, very normal working temps, so I'll add my vote for configurability of the temp warning levels.  I would probably set 40 and up as Warm and 47 and up as Hot, 52 as perhaps too hot.

  d. I would be more likely to use the Dashboard if the actual temps were shown, not just flags, but perhaps that's just me.

  e. For Memory size, Physical, it says '(max. )'.  It's not clear to me what that means.

 

3. I would really like a configurable refresh interval, perhaps a slider with click points? (You probably have much better ideas!)  Perhaps with choices of Off, 10 seconds, 30 secs, 1 min, 5 min, 15 min, and 30 min.  Or Off, Low, Medium, and High with each of those configurable.  Then allow us to configure the standard default value as well as the default value when a parity check or sync or drive rebuild was running.  I'd like to see this clickable refresh tool on each of the main tabs, especially the Dashboard, Array Devices, and Array Operation.

 

4. With a Parity Check currently running, a Refresh button appeared.  It works fine on most tabs, but does not on the Unassigned Devices tab.  Upon clicking Refresh, the screen returns to the Array Devices tab, and does not refresh the drives on the Unassigned Devices tab.  I had a spun up drive with temp on that page (verified using UnMENU), but it always showed as spun down with no temp, no matter how I tried to refresh the page.

 

5. I'd like to see more network info, within the System Info stuff (I'm a bit spoiled by the UnMENU Network plugin!)  You currently are only showing the 'ethtool eth0' info, which shows the network connection speed (be nice to highlight it!), the coded WOL status, and whether we currently have a link or not, all very useful but there is quite a bit more that also is useful.  The UnMENU network tool also shows:

  a. 'ethtool -i eth0' (the network driver and its version)

  b. 'ifconfig eth0' (Ethernet config and error info, such as the MAC address, the MTU, and RX and TX packet issues)

  c. 'cat /boot/config/network.cfg' (DHCP use, netmask, gateway, and DNS addresses)

  d. 'cat /boot/config/ident.cfg' (machine and workgroup names and comment, local master switch, timezone, and ntp use and servers)

  e. 'cat /etc/resolv.conf' (the nameserver)

  f. 'cat /etc/hosts' (host file with all comments removed)

 

6. UnMENU had other technical info available, for more advanced users (sorry(!), UnMENU is what many of us are used to):

  a. PS info, from 'ps -eaf'

  b. Fuser info, from 'fuser -mv /mnt/disk* /mnt/user/* 2>&1'

  c. Uptime plus load average, 'uptime'  (I know you have Uptime displayed, but some also like the load averages easily available)

  d. Top processes and system status numbers, from 'top -b -n1'

  e. Open files, from 'lsof /dev/md*'

  f. Device list, from 'lsdev'

  g. UPS status, from 'apcaccess status' (if APC stuff is installed)

  h. PCI devices, from 'lspci -v'

  i. Loaded modules, from 'lsmod'

  j. Run a drive speed test, using 'hdparm -tT' with a selected drive symbol (eg. hdparm -tT /dev/sdk)

  k. Dupe files, a tool to list duplicate files in the Shares on parallel drive paths

 

7. Just a cosmetic item, concerning the line for the Parity drive on the Array Devices tab, I would prefer to leave blank the dark bars under Used and Free, and remove the folder icon under View.

 

Think I've caused enough trouble now!  You are welcome to ignore everything!  But thanks again for all the time you have put into this.

Link to comment

 

just curious, does this replace the one that lime-tech provides? If i unistall/remove dynamix, will the new powerdown remain?

 

There is no configuration required.  This is a newer version of powerdown that was previously installed by Dynamix.  It permits a clean shutdown when the power button is pressed, or Ctrl-Alt-Del keys are pressed.

 

Yes it replaces the stock version.  It will be removed when Dynamix is removed because it is a package installed by Dynamix.

 

More information here: http://lime-technology.com/forum/index.php?topic=31735.0

 

Hi.

Currently I'm using a few addons from unMenu (apcupsd, ssmtp, scheduled email notifications, monthly check, powerdown on overtemp and clean powerdown).

Does your version, been installed with dynamic, replace the package I install from unMenu ?

Should I stop installing the "powerdown on overtemp" from unMenu (if I read correctly in your link, dynamix has it built-in) ?

Thanks

 

If you install Dynamix you don't need to install the powerdown package from unMenu.  Dynamix does all the things you are adding from unMenu.  Email notifications, monthly parity check, powerdown on overtemp, and clean powerdown are all a part of Dynamix.

I still use unMenu pkgs to have the option of renaming all my plugins for a clean reboot of the server (don't have a keyboard or monitor connected), so using the unMenu pkgs makes apcupsd and email notifications with clean powerdown available.

My question is - if I leave my unMenu configuration as-is, does the "clean powerdown" that dynamix install replace the one installed via unmenu  ?

 

Not necessarily.  It depends on the sequence of installation.  This is a case of the last one there wins.  The last powerdown package installed will be the active one.

 

The best way to get around this would be to install the new script that dlandon wrote as well.  It's better than the one you're getting from unMENU anyway, and if you do require support you won't have to figure out which version of the script is running/causing issues.

Can you post a link to dlandon's script? Or are you referring to the one integrated into dynamix?

 

Sent from my GT-I9500 using Tapatalk

 

 

Link to comment

I cannot get this installed at all, I've followed your instructions to the letter.  Can you confirm  that this is going in flash/boot/plugins?

 

Telnet/console cannot see/find any directories

 

you can't get Dynamix installed?

 

if you are on telnet, you cd to /boot/plugins

 

if you download it via the browser link on GITHUB go to your servers flash\plugins directory so something like \\tower\flash\plugins

 

note the difference in the paths... because /boot/ is what's exported as \flash

 

i'm no Linux guy, but i think what i said above makes sense.

 

 

Link to comment

That is what I thought.

 

 

....... login: root

Linux 3.9.11p-unRAID.

root@Atlantis:~# cd /boot/plugins

-bash: cd: /boot/plugins: No such file or directory

root@Atlantis:~# cd boot

-bash: cd: boot: No such file or directory

root@Atlantis:~# cd flash

-bash: cd: flash: No such file or directory

root@Atlantis:~# dir

mdcmd*  powerdown@  samba@

root@Atlantis:~# cd cd /boot/plugins

-bash: cd: cd: No such file or directory

root@Atlantis:~# cd /flash/

-bash: cd: /flash/: No such file or directory

root@Atlantis:~#

 

I downloaded and copied it across to /flash/boot/plugins/ and rebooted and nothing.  Do I need to do something else?

Link to comment

So by adding this new user account and setting the shares to Private, I cut off access for my XBMC machine. Oops. I'll attack this issue later. Back to default...

 

Using "private" requires an interactive login procedure. You can use "secure" mode to make shares read-only for all users except those which you have given explicit write access.

 

 

Can you expand on this? If I understand you correctly, will secure mode require an account for ALL computers who will access the share?

 

How can I test the settings of other machines or users once the secure mode is set and users are added?

Link to comment
  • Squid locked this topic
Guest
This topic is now closed to further replies.