nfountou

Thanks Joe L! I fixed that as I saw the error under unmenu but it seems that 14.3 version of apcupsd is much more trouble free so I used the old one instead of 14.10. I have got some good news with the microlink protocol. Here is a response from APC staff: 2.) We realize that a SmartSlot card is not an ideal solution and we intend that it will only be a transition to products that would natively offer a publicly available protocol. We engaged with the apcupsd development community to try to find a better long term solution. While it took longer than anyone had hoped we have recently released a firmware update for certain Smart-UPS SMT models (UPS 09.1) which supports an open protocol that can be used by developers (including apcupsd) to communicate with the UPS. The documentation for this protocol should be available on our web site within a few weeks. Our intent is that all future Micro-Link based Smart-UPS will also include the open protocol described above. http://forums.apc.com/thread/5374?start=30&tstart=0 I ll check for a firmware update...

the main problem was with 3.14.10 version of apcupsd. 3.14.3 runs better and every value can be changed from UNMENU with no issues and no need of custom configuration. Unfortunately even with usb to serial still it doesnt work. If anyone connected successfully a ups of that series please let me know...

I am trying to setup a prolific 2303 usb to serial cable just to check if this will work. Server kernel: usbcore: registered new interface driver usbserial Server kernel: usbcore: registered new interface driver pl2303 Server kernel: usbserial: USB Serial support registered for pl2303 Server kernel: pl2303 4-2:1.0: pl2303 converter detected Server kernel: usb 4-2: pl2303 converter now attached to ttyUSB0 Everything seems to be ok. I changed the custom apcupsd unmenu conf file to: PACKAGE_INSTALLATION [ "${vDEVICE-NO}" = "YES" ] && sed -i -e "s/^UPSTYPE usb/UPSTYPE apcsmart/" /etc/apcupsd/apcupsd.conf PACKAGE_INSTALLATION sed -i -e "s/^DEVICE \/dev\/ttyUSB0/" /etc/apcupsd/apcupsd.conf PACKAGE_INSTALLATION sed -i -e "s/UPSCABLE usb/UPSCABLE smart/" /etc/apcupsd/apcupsd.conf PACKAGE_INSTALLATION sed -i -e "s/^MINUTES 3/MINUTES ${vMINUTES-5}/" /etc/apcupsd/apcupsd.conf PACKAGE_INSTALLATION sed -i -e "s/^BATTERYLEVEL 5/BATTERYLEVEL ${vBATTERYLEVEL-5}/" /etc/apcupsd/apcupsd.conf PACKAGE_INSTALLATION sed -i -e "s/^TIMEOUT 0/TIMEOUT ${vTIMEOUT-0}/" /etc/apcupsd/apcupsd.conf but ttyUSB0 doesnt get set. Instead it still tries to communicate with ttyS0...

Unfortunately I have already read the manual and already set UPSTYPE to apcsmart. I just came across to this link: http://apcupsd-ups-control-software.10985.n7.nabble.com/The-new-APC-SMT-series-UPS-td1178.html where people state about APCs new (not that new) standard called microlink and the issue with serial communication with apcupsd. Of course there is an option for buying a legacy communication card for about 50usd. the ups is an APC SMT1000I: http://www.apc.com/resource/include/techspec_index.cfm?base_sku=SMT1000I

thanks!!! that really did it! UPSCABLE was set to smart! but unfortunately apcupsd still doesnt work... I even set the UPSCABLE as the apc cable number i ve got but still nothing...

Hi, I ve got an APC smart 1000 ups connected on serial port installed from UNMENU an running 5.03 stable. Whatever settings I have got the UPSCABLE is set to usb (I checked it through apcupsd.conf) I ve made a custom unmenu install of apcupsd in which I altered the above line of the custom conf file i created (in package folder) to: PACKAGE_INSTALLATION sed -i -e "s/^UPSCABLE smart/UPSCABLE smart/" /etc/apcupsd/apcupsd.conf Still upscable not set to smart as its required to run from serial port. I have to mention that I m using an original APC network to serial cable that came with my ups and serial port is configured as ttyS0. ps: I am running the latest apcupsd 3.14.10

For an unknown reason ethtool wol option was changed to ug instead of g. for any similar case if wol not set to g use command: ethtool -s eth0 wol g

thats sounds like a good reason for stopping the script I had some issues with the network the last few days which now are fixed... I believe that this also had to do with my script not running from the web... disk doesnt show any reallocated sectors and everything was fine before the update. Just to be sure I virus checked my PC, I ran 13 hours of memtest, checked every network station and everything looks clear... For an unknown reason ethtool wol option was changed to ug instead of g and that was the reason for those sudden wake ups... I am parity testing at the moment with no errors till now... hope I ll get it running soon...

no but just realized that suspicious traffic was coming out from an old access point I have got... I replaced it with more advanced ap and mac filtered my wifi... I am sure that this was the problem as my unraid 5.03 no longer wakes up on its own (I had also this issue after the upgrade). I ll report when i double check everything...

hi! just updated from 4.7 to 5.03 stable and it seems like the system keeps waking up all the time when I shut it down after a few minutes or so... syslog.txt

just to mention that I am running the script locally (newperms execution) and the procedure seems to work pretty nice and fast... dont know though what causes this issue when I run it from the web interface.

I did run it again but unfortunately the procedure after a period of time stops... I memtesting at the moment ( i m pretty sure its ok. I did a couple of hours before the upgrade but I am retesting just to be sure) is there a way I can do the same procedure using the shell? is there a script available or something?

it seems ok to me... reallocated sectors 0... smart_disk1.txt

also my disks went to sleep and the procedure just stopped. Had to wake them up to continue..

hi! Just upgraded from 4.7 (after parity check and system check with 0 errors) and during the new permission script run, I got 19 errors on disk1 so far. Is that normal for this procedure? (upgraded to 5.03 stable) logs.txt