June 20, 201511 yr Just noticed this, after restarting the array or a reboot. notifications are not starting up again till you change one, apply, change it back, apply... wasnt' this a problem before and was fixed? 6.0.0 and Dynamix 2015.06.15
June 22, 201511 yr Community Expert I am not seeing this issue - notifications seem to be starting up fine for me. I would suggest that you attach a diagnostics reports (Tools->Diagnostics) to see if any one can spot an issue. It might also be worth booting in Safe mode in case you have any plugins that might be causing problems.
June 23, 201511 yr Author soon as I can do a restart I will, it's busy moving 6tb of data around ......
June 25, 201511 yr Author OK here's the diagnostics zip.... situation is as follows 1. early in the morning lost connection to the webgui of the server (turned out to be an ISP'ish problem) so I putty'ed in and did a shutdown 2. Jun 25 05:26:41 - turned out to be an 'unclean' shutdown? (need to ask about that) 3. let it start the parity check (only 7 hours to go) 4. this looks interesting - Jun 25 05:31:47 PINEWOOD ntpd[1401]: kernel reports TIME_ERROR: 0x41: pll unsync Resource temporarily unavailable 5 waited about 10 minutes and zero notifications were forthcoming 6. went to the notifications setting and set one extra, apply, unset the same one. apply 7. Boom shacka lacka! Jun 25 05:42:51 PINEWOOD php: /usr/local/sbin/notify cron-init Jun 25 05:43:12 PINEWOOD sSMTP[13143]: Creating SSL connection to host Jun 25 05:43:12 PINEWOOD sSMTP[13143]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256 Jun 25 05:43:14 PINEWOOD sSMTP[13143]: Sent mail for ,,,,,,, this is consistent... if I stop the array (not just reboot or power down).. notifications stop until I tickle it (set/apply/unset/apply) diagnostics-20150625-0906.zip
June 25, 201511 yr Did you use to store your notifications on the array before? How does your [notify] section look like in /boot/config/plugins/dynamix/dynamx.plg ? Specifically the setting of path, mine is: path="/boot/config/plugins/dynamix/notifications"
June 25, 201511 yr Author Did you use to store your notifications on the array before? How does your [notify] section look like in /boot/config/plugins/dynamix/dynamx.plg ? Specifically the setting of path, mine is: path="/boot/config/plugins/dynamix/notifications" I have never touched any of the setting in any of plg/cfg files. I installed and set the ones I wanted and let it rip. "How does your [notify] section look like in /boot/config/plugins/dynamix/dynamx.plg ?" file does not appear to exist.... you mean "/boot/config/plugins/dynamix/dynamx.cfg" [notify] date="d-m-Y" time="H:i" position="top-right" path="/boot/config/plugins/dynamix/notifications" entity="0" normal="2" warning="2" alert="2" report="2" events="5|187|188|197|198" status="20 */2 * * *" custom="" plugin="2" system="*/1 * * * *" version="10 */6 * * *" docker_notify="2" docker_update="10 0 * * *" again, once I toggle any of the setings (change/apply/change back/apply) kicks off fine.
June 25, 201511 yr Sorry typo from my side, indeed the cfg file. All looks good at the settings side, so not sure what is happening cause I can't reproduce it... (I need to investigate more)
June 27, 201511 yr Author well same thing on the morning update 6.0.1... reboot, wait 10 minutes... nothing change anything/apply/change back/apply... notifications start the notify section BEFORE changing things [notify] date="d-m-Y" time="H:i" position="top-right" path="/boot/config/plugins/dynamix/notifications" entity="0" normal="2" warning="2" alert="2" report="2" events="5|187|188|197|198" status="20 */2 * * *" custom="" plugin="2" system="*/1 * * * *" version="10 */6 * * *" docker_notify="2" docker_update="10 0 * * *" [parity] cron="'0 0 1 * * /root/mdcmd check 1>/dev/null 2>&1'" mode="3" dotm="1" hour="0 0" write="" AFTER [notify] date="d-m-Y" time="H:i" position="top-right" path="/boot/config/plugins/dynamix/notifications" entity="0" normal="2" warning="2" alert="2" report="2" events="5|187|188|197|198" status="20 * * * *" custom="" plugin="2" system="*/1 * * * *" version="10 */6 * * *" docker_notify="2" docker_update="10 0 * * *" [parity] cron="'0 0 1 * * /root/mdcmd check 1>/dev/null 2>&1'" mode="3" dotm="1" hour="0 0" write=""
June 27, 201511 yr Your config file contains several depreciated settings, I guess this happened do to upgrades from earlier versions. Try the following: rename (or delete) the file /boot/config/plugins/dynamix/dynamix.cfg. Reboot your system, this will let it start with all default settings. Next apply your notification settings and rerun your test.
Archived
This topic is now archived and is closed to further replies.