Dal1980

Members
  • Posts

    72
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Dal1980's Achievements

Rookie

Rookie (2/14)

2

Reputation

  1. Hi JDGJr I might have deleted the container and setup Plex again. I don't think it effects anything as long as the same directories are used since that's where all the settings/media files are kept. It seemed that the update knocked out something in the instance. I also restarted the server before I deleted the container and after I think if I remember correctly. Hope this helps
  2. I thought I'd bump this one last time before it end up in the boneyard (there was recent activity on another post so hoping someone has an answer *cough* 😛) Just asked BotFather to show my /mybots again and the response was Here is the token for bot unRAIDBOT @Z*******Bot: 1*******02:A******-******-*******************Q Just tried https://api.telegram.org/bot1*******02:A******-******-*******************Q/getUpdates and got back the following response: {"ok":true,"result":[]} Simply amazing stuff (obviously everything that is a * is blanked out data and not actual data) I'm not sure what I'm supposed to hide and what I can safely show so it may have been excessive to hide my bot chat name or whatever that @Z***... name was for my bot (been around in so many circles I'm confused with the whole thing to be honest)
  3. I thought I'd include the diagnostics file. borg-diagnostics-20200608-0820.zip
  4. It's been 4 hours. Strangely the apps tab now works but I'm still getting the Retry unmounting disk share(s) message. Is this safe to reboot or is there a console command I should use to stop this array before rebooting?
  5. I tried stopping the array so I could just try a restart but I'm getting problems doing that too Jun 7 19:01:06 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 19:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 19:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 19:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 19:49:09 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 19:53:31 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 20:06:38 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 20:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 20:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 20:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 20:54:41 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 20:54:41 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 21:12:10 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 21:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 21:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 21:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 21:22:11 borg webGUI: Successful login user root from 192.168.1.10 Jun 7 21:25:41 borg nginx: 2020/06/07 21:25:41 [error] 1166#1166: *2229798 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.10, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "761e316f08274ef9fba996156abd3dc403fc9243.unraid.net", referrer: "https://761e316f08274ef9fba996156abd3dc403fc9243.unraid.net/Apps" Jun 7 21:32:14 borg nginx: 2020/06/07 21:32:14 [error] 1166#1166: *2229798 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.10, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "761e316f08274ef9fba996156abd3dc403fc9243.unraid.net", referrer: "https://761e316f08274ef9fba996156abd3dc403fc9243.unraid.net/Apps" Jun 7 21:55:51 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 22:00:14 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 22:00:16 borg crond[2076]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Jun 7 22:08:58 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 22:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 22:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 22:20:45 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 22:22:05 borg emhttpd: shcmd (6055): /usr/sbin/hdparm -y /dev/sdb Jun 7 22:22:05 borg root: Jun 7 22:22:05 borg root: /dev/sdb: Jun 7 22:22:05 borg root: issuing standby command Jun 7 22:22:05 borg emhttpd: shcmd (6056): /usr/sbin/hdparm -y /dev/sdc Jun 7 22:22:05 borg root: Jun 7 22:22:05 borg root: /dev/sdc: Jun 7 22:22:05 borg root: issuing standby command Jun 7 22:57:01 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 23:01:24 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 23:04:38 borg kernel: mdcmd (120): nocheck cancel Jun 7 23:04:39 borg emhttpd: Spinning up all drives... Jun 7 23:04:39 borg emhttpd: shcmd (6061): /usr/sbin/hdparm -S0 /dev/sdb Jun 7 23:04:39 borg kernel: mdcmd (121): spinup 0 Jun 7 23:04:39 borg kernel: mdcmd (122): spinup 1 Jun 7 23:04:39 borg kernel: mdcmd (123): spinup 2 Jun 7 23:04:39 borg kernel: mdcmd (124): spinup 29 Jun 7 23:04:39 borg root: Jun 7 23:04:39 borg root: /dev/sdb: Jun 7 23:04:39 borg root: setting standby to 0 (off) Jun 7 23:04:39 borg emhttpd: shcmd (6062): /usr/sbin/hdparm -S0 /dev/sdc Jun 7 23:04:39 borg root: Jun 7 23:04:39 borg root: /dev/sdc: Jun 7 23:04:39 borg root: setting standby to 0 (off) Jun 7 23:04:55 borg emhttpd: Stopping services... Jun 7 23:04:55 borg root: Stopping docker_load Jun 7 23:04:55 borg emhttpd: shcmd (6065): /etc/rc.d/rc.docker stop Jun 7 23:04:55 borg root: stopping dockerd ... Jun 7 23:04:56 borg root: waiting for docker to die ... Jun 7 23:04:57 borg avahi-daemon[6661]: Interface docker0.IPv4 no longer relevant for mDNS. Jun 7 23:04:57 borg avahi-daemon[6661]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jun 7 23:04:57 borg avahi-daemon[6661]: Withdrawing address record for 172.17.0.1 on docker0. Jun 7 23:04:57 borg emhttpd: shcmd (6066): umount /var/lib/docker Jun 7 23:04:57 borg root: umount: /var/lib/docker: target is busy. Jun 7 23:04:57 borg emhttpd: shcmd (6066): exit status: 32 Jun 7 23:04:57 borg unassigned.devices: Unmounting All Devices... Jun 7 23:04:57 borg emhttpd: shcmd (6067): /etc/rc.d/rc.samba stop Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 23:04:57 borg emhttpd: shcmd (6068): rm -f /etc/avahi/services/smb.service Jun 7 23:04:57 borg avahi-daemon[6661]: Files changed, reloading. Jun 7 23:04:57 borg avahi-daemon[6661]: Service group file /services/smb.service vanished, removing services. Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a6, vlan:0) Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a5, vlan:0) Jun 7 23:04:57 borg emhttpd: Stopping mover... Jun 7 23:04:57 borg emhttpd: shcmd (6071): /usr/local/sbin/mover stop Jun 7 23:04:57 borg root: mover: not running Jun 7 23:04:57 borg emhttpd: Sync filesystems... Jun 7 23:04:57 borg emhttpd: shcmd (6072): sync Jun 7 23:04:57 borg emhttpd: shcmd (6073): umount /mnt/user0 Jun 7 23:04:57 borg emhttpd: shcmd (6074): rmdir /mnt/user0 Jun 7 23:04:57 borg emhttpd: shcmd (6075): umount /mnt/user Jun 7 23:04:57 borg emhttpd: shcmd (6076): rmdir /mnt/user Jun 7 23:04:57 borg emhttpd: shcmd (6077): rm -f /boot/config/plugins/dynamix/mover.cron Jun 7 23:04:57 borg emhttpd: shcmd (6078): /usr/local/sbin/update_cron Jun 7 23:04:57 borg emhttpd: Unmounting disks... Jun 7 23:04:57 borg emhttpd: shcmd (6079): umount /mnt/disk1 Jun 7 23:04:57 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 23:04:58 borg kernel: XFS (md1): Unmounting Filesystem Jun 7 23:05:04 borg emhttpd: shcmd (6080): rmdir /mnt/disk1 Jun 7 23:05:04 borg emhttpd: shcmd (6081): umount /mnt/disk2 Jun 7 23:05:05 borg kernel: XFS (md2): Unmounting Filesystem Jun 7 23:05:11 borg emhttpd: shcmd (6082): rmdir /mnt/disk2 Jun 7 23:05:11 borg emhttpd: shcmd (6083): umount /mnt/cache Jun 7 23:05:11 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:11 borg emhttpd: shcmd (6083): exit status: 32 Jun 7 23:05:11 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:16 borg emhttpd: Unmounting disks... Jun 7 23:05:16 borg emhttpd: shcmd (6084): umount /mnt/cache Jun 7 23:05:16 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:16 borg emhttpd: shcmd (6084): exit status: 32 Jun 7 23:05:16 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:21 borg emhttpd: Unmounting disks... Jun 7 23:05:21 borg emhttpd: shcmd (6085): umount /mnt/cache Jun 7 23:05:21 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:21 borg emhttpd: shcmd (6085): exit status: 32 Jun 7 23:05:21 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:26 borg emhttpd: Unmounting disks... Jun 7 23:05:26 borg emhttpd: shcmd (6086): umount /mnt/cache Jun 7 23:05:26 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:26 borg emhttpd: shcmd (6086): exit status: 32 Jun 7 23:05:26 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:31 borg emhttpd: Unmounting disks... Jun 7 23:05:31 borg emhttpd: shcmd (6087): umount /mnt/cache Jun 7 23:05:31 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:31 borg emhttpd: shcmd (6087): exit status: 32 Jun 7 23:05:31 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:36 borg emhttpd: Unmounting disks... Jun 7 23:05:36 borg emhttpd: shcmd (6088): umount /mnt/cache Jun 7 23:05:36 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:36 borg emhttpd: shcmd (6088): exit status: 32 Jun 7 23:05:36 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:41 borg emhttpd: Unmounting disks... Jun 7 23:05:41 borg emhttpd: shcmd (6089): umount /mnt/cache Jun 7 23:05:41 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:41 borg emhttpd: shcmd (6089): exit status: 32 Jun 7 23:05:41 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:46 borg kernel: net_ratelimit: 2 callbacks suppressed Jun 7 23:05:46 borg kernel: br0: received packet on eth1 with own address as source address (addr:00:26:55:d1:76:a7, vlan:0) Jun 7 23:05:46 borg emhttpd: Unmounting disks... Jun 7 23:05:46 borg emhttpd: shcmd (6090): umount /mnt/cache Jun 7 23:05:46 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:46 borg emhttpd: shcmd (6090): exit status: 32 Jun 7 23:05:46 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:51 borg emhttpd: Unmounting disks... Jun 7 23:05:51 borg emhttpd: shcmd (6091): umount /mnt/cache Jun 7 23:05:51 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:51 borg emhttpd: shcmd (6091): exit status: 32 Jun 7 23:05:51 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:05:56 borg emhttpd: Unmounting disks... Jun 7 23:05:56 borg emhttpd: shcmd (6092): umount /mnt/cache Jun 7 23:05:56 borg root: umount: /mnt/cache: target is busy. Jun 7 23:05:56 borg emhttpd: shcmd (6092): exit status: 32 Jun 7 23:05:56 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:06:01 borg emhttpd: Unmounting disks... Jun 7 23:06:01 borg emhttpd: shcmd (6093): umount /mnt/cache Jun 7 23:06:01 borg root: umount: /mnt/cache: target is busy. Jun 7 23:06:01 borg emhttpd: shcmd (6093): exit status: 32 Jun 7 23:06:01 borg emhttpd: Retry unmounting disk share(s)... Jun 7 23:06:06 borg emhttpd: Unmounting disks... Jun 7 23:06:06 borg emhttpd: shcmd (6094): umount /mnt/cache Jun 7 23:06:06 borg root: umount: /mnt/cache: target is busy. Jun 7 23:06:06 borg emhttpd: shcmd (6094): exit status: 32 Jun 7 23:06:06 borg emhttpd: Retry unmounting disk share(s)... I don't know what to do at this point
  6. Hi I've just clicked to update Plex on Docker and it downloaded the update and took ages to install. I thought I'd just close the box and let it do it in the background but it's still going 15 minutes later and it's blocking access to the GUI with the unRAID wavy loading icon in the centre of the screen and there must be a div covering the whole screen as no buttons are clickable. When I go back to the IP of my server again I can access stuff but as soon as I go to Apps I get completely bricked again. Docker tab shows the loading graphic too and doesn't load in Plex again. Edit: This has since morphed into another issue (hence updated thread title Retry unmounting disk share(s)).
  7. Thanks Squid, I read about that plugin. To be honest this might be something I'd look at in the future but for now I might just switch it to check parity every month instead of every week if that is an appropriate timescale.
  8. I run my parity check every Monday morning at about 2am. I'm interested to know if this is based on the amount of changed data or if parity checks all the data each week? What I mean is, if I switched to doing a parity check every night would it take as long as doing it once a week or once a month? Also what is an appropriate schedule for parity? My data doesn't change that much... ie maybe there's new data added every once in a while but data is never removed if that information helps.
  9. Dal1980

    What UPS

    Thanks so much 😀 After all of this I felt confident enough to push that test button (held for 5 seconds). It jumped over the battery and then presumably passed it's own test and went back to normal running. Cool, well I learnt some stuff, thanks again 🤗
  10. Dal1980

    What UPS

    247.6 v Edit: It's gone up to 250.5 but then came back down o 249.1
  11. Dal1980

    What UPS

    Cool - HITRANSFER setting has taken a hold using their web gui. Thanks @Benson
  12. Dal1980

    What UPS

    oops - I did read what you had wrote, then forgot by the time I researched how to restart services in slackware 😳😁 Charging my laptop so I can install this PowerChute Thing
  13. Dal1980

    What UPS

    Hmm after making the changes to HITRANSFER 265 (without the # comment character) Saved in nano and went back in to check it had saved. Tried both restarting the daemon via the gui (settings->UPS Settings->Start APC UPS Daemon: no, then applied, waited 20 seconds or so and changed it back to Start APC UPS Daemon: yes and hit apply) /etc/rc.d/rc.apcupsd restart Stopping apcupsd power management.. Starting apcupsd power management: /sbin/apcupsd Also tried this. Both attempts have not changed this reporting "HITRANS 253.0 Volts" on the UPS Details Anything else I can try?
  14. Dal1980

    What UPS

    In my /etc/apcupsd/apcupsd.conf config file I see the HITRANSFER setting is not actually set so I'm presuming it's either 253 or 0 (I'm reading the comment as if it means it would be 0 if the setting was not supported or couldn't be changed). # High line voltage causing transfer to batteries # The permitted values depend on your model as defined by last letter # of FIRMWARE or APCMODEL. Some representative values are: # D 127 130 133 136 # M 229 234 239 224 # A 108 110 112 114 # I 253 257 261 265 (default = 0 => not valid) #HITRANSFER 253 Wasn't sure how to get the firmware via unRAID terminal but UPS settings in the GUI does show it as "FIRMWARE619.3.I USB FW:8.1" Since that's an I then that makes sense as the other rows are completely different power ratings.... ok so if row (i) supports all of them values then I presume I'd just change the config to #HITRANSFER 265 Correct? I've also include the rest of the conf file if there's any other recommendations. (UPS APC manual : http://apcupsd.org/manual/manual.html) ## apcupsd.conf v1.1 ## # # for apcupsd release 3.14.14 (31 May 2016) - slackware # # "apcupsd" POSIX config file # # Note that the apcupsd daemon must be restarted in order for changes to # this configuration file to become active. # # # ========= General configuration parameters ============ # # UPSNAME xxx # Use this to give your UPS a name in log files and such. This # is particulary useful if you have multiple UPSes. This does not # set the EEPROM. It should be 8 characters or less. #UPSNAME # UPSCABLE <cable> # Defines the type of cable connecting the UPS to your computer. # # Possible generic choices for <cable> are: # simple, smart, ether, usb # # Or a specific cable model number may be used: # 940-0119A, 940-0127A, 940-0128A, 940-0020B, # 940-0020C, 940-0023A, 940-0024B, 940-0024C, # 940-1524C, 940-0024G, 940-0095A, 940-0095B, # 940-0095C, 940-0625A, M-04-02-2000 # UPSCABLE usb # To get apcupsd to work, in addition to defining the cable # above, you must also define a UPSTYPE, which corresponds to # the type of UPS you have (see the Description for more details). # You must also specify a DEVICE, sometimes referred to as a port. # For USB UPSes, please leave the DEVICE directive blank. For # other UPS types, you must specify an appropriate port or address. # # UPSTYPE DEVICE Description # apcsmart /dev/tty** Newer serial character device, appropriate for # SmartUPS models using a serial cable (not USB). # # usb <BLANK> Most new UPSes are USB. A blank DEVICE # setting enables autodetection, which is # the best choice for most installations. # # net hostname:port Network link to a master apcupsd through apcupsd's # Network Information Server. This is used if the # UPS powering your computer is connected to a # different computer for monitoring. # # snmp hostname:port:vendor:community # SNMP network link to an SNMP-enabled UPS device. # Hostname is the ip address or hostname of the UPS # on the network. Vendor can be can be "APC" or # "APC_NOTRAP". "APC_NOTRAP" will disable SNMP trap # catching; you usually want "APC". Port is usually # 161. Community is usually "private". # # netsnmp hostname:port:vendor:community # OBSOLETE # Same as SNMP above but requires use of the # net-snmp library. Unless you have a specific need # for this old driver, you should use 'snmp' instead. # # dumb /dev/tty** Old serial character device for use with # simple-signaling UPSes. # # pcnet ipaddr:username:passphrase:port # PowerChute Network Shutdown protocol which can be # used as an alternative to SNMP with the AP9617 # family of smart slot cards. ipaddr is the IP # address of the UPS management card. username and # passphrase are the credentials for which the card # has been configured. port is the port number on # which to listen for messages from the UPS, normally # 3052. If this parameter is empty or missing, the # default of 3052 will be used. # # modbus /dev/tty** Serial device for use with newest SmartUPS models # supporting the MODBUS protocol. # modbus <BLANK> Leave the DEVICE setting blank for MODBUS over USB # or set to the serial number of the UPS to ensure # that apcupsd binds to that particular unit # (helpful if you have more than one USB UPS). # UPSTYPE usb DEVICE # POLLTIME <int> # Interval (in seconds) at which apcupsd polls the UPS for status. This # setting applies both to directly-attached UPSes (UPSTYPE apcsmart, usb, # dumb) and networked UPSes (UPSTYPE net, snmp). Lowering this setting # will improve apcupsd's responsiveness to certain events at the cost of # higher CPU utilization. The default of 60 is appropriate for most # situations. #POLLTIME 60 # LOCKFILE <path to lockfile> # Path for device lock file. This is the directory into which the lock file # will be written. The directory must already exist; apcupsd will not create # it. The actual name of the lock file is computed from DEVICE. # Not used on Win32. LOCKFILE /var/lock # SCRIPTDIR <path to script directory> # Directory in which apccontrol and event scripts are located. SCRIPTDIR /etc/apcupsd # PWRFAILDIR <path to powerfail directory> # Directory in which to write the powerfail flag file. This file # is created when apcupsd initiates a system shutdown and is # checked in the OS halt scripts to determine if a killpower # (turning off UPS output power) is required. PWRFAILDIR /etc/apcupsd # NOLOGINDIR <path to nologin directory> # Directory in which to write the nologin file. The existence # of this flag file tells the OS to disallow new logins. NOLOGINDIR /etc # # ======== Configuration parameters used during power failures ========== # # The ONBATTERYDELAY is the time in seconds from when a power failure # is detected until we react to it with an onbattery event. # # This means that, apccontrol will be called with the powerout argument # immediately when a power failure is detected. However, the # onbattery argument is passed to apccontrol only after the # ONBATTERYDELAY time. If you don't want to be annoyed by short # powerfailures, make sure that apccontrol powerout does nothing # i.e. comment out the wall. ONBATTERYDELAY 6 # # Note: BATTERYLEVEL, MINUTES, and TIMEOUT work in conjunction, so # the first that occurs will cause the initation of a shutdown. # # If during a power failure, the remaining battery percentage # (as reported by the UPS) is below or equal to BATTERYLEVEL, # apcupsd will initiate a system shutdown. BATTERYLEVEL 30 # If during a power failure, the remaining runtime in minutes # (as calculated internally by the UPS) is below or equal to MINUTES, # apcupsd, will initiate a system shutdown. MINUTES 10 # If during a power failure, the UPS has run on batteries for TIMEOUT # many seconds or longer, apcupsd will initiate a system shutdown. # A value of 0 disables this timer. # # Note, if you have a Smart UPS, you will most likely want to disable # this timer by setting it to zero. That way, you UPS will continue # on batteries until either the % charge remaing drops to or below BATTERYLEVEL, # or the remaining battery runtime drops to or below MINUTES. Of course, # if you are testing, setting this to 60 causes a quick system shutdown # if you pull the power plug. # If you have an older dumb UPS, you will want to set this to less than # the time you know you can run on batteries. TIMEOUT 0 # Time in seconds between annoying users to signoff prior to # system shutdown. 0 disables. ANNOY 300 # Initial delay after power failure before warning users to get # off the system. ANNOYDELAY 60 # The condition which determines when users are prevented from # logging in during a power failure. # NOLOGON <string> [ disable | timeout | percent | minutes | always ] NOLOGON disable # If KILLDELAY is non-zero, apcupsd will continue running after a # shutdown has been requested, and after the specified time in # seconds attempt to kill the power. This is for use on systems # where apcupsd cannot regain control after a shutdown. # KILLDELAY <seconds> 0 disables KILLDELAY 0 # # ==== Configuration statements for Network Information Server ==== # # NETSERVER [ on | off ] on enables, off disables the network # information server. If netstatus is on, a network information # server process will be started for serving the STATUS and # EVENT data over the network (used by CGI programs). NETSERVER on # NISIP <dotted notation ip address> # IP address on which NIS server will listen for incoming connections. # This is useful if your server is multi-homed (has more than one # network interface and IP address). Default value is 0.0.0.0 which # means any incoming request will be serviced. Alternatively, you can # configure this setting to any specific IP address of your server and # NIS will listen for connections only on that interface. Use the # loopback address (127.0.0.1) to accept connections only from the # local machine. NISIP 0.0.0.0 # NISPORT <port> default is 3551 as registered with the IANA # port to use for sending STATUS and EVENTS data over the network. # It is not used unless NETSERVER is on. If you change this port, # you will need to change the corresponding value in the cgi directory # and rebuild the cgi programs. NISPORT 3551 # If you want the last few EVENTS to be available over the network # by the network information server, you must define an EVENTSFILE. EVENTSFILE /var/log/apcupsd.events # EVENTSFILEMAX <kilobytes> # By default, the size of the EVENTSFILE will be not be allowed to exceed # 10 kilobytes. When the file grows beyond this limit, older EVENTS will # be removed from the beginning of the file (first in first out). The # parameter EVENTSFILEMAX can be set to a different kilobyte value, or set # to zero to allow the EVENTSFILE to grow without limit. EVENTSFILEMAX 10 # # ========== Configuration statements used if sharing ============= # a UPS with more than one machine # # Remaining items are for ShareUPS (APC expansion card) ONLY # # UPSCLASS [ standalone | shareslave | sharemaster ] # Normally standalone unless you share an UPS using an APC ShareUPS # card. UPSCLASS standalone # UPSMODE [ disable | share ] # Normally disable unless you share an UPS using an APC ShareUPS card. UPSMODE disable # # ===== Configuration statements to control apcupsd system logging ======== # # Time interval in seconds between writing the STATUS file; 0 disables STATTIME 0 # Location of STATUS file (written to only if STATTIME is non-zero) STATFILE /var/log/apcupsd.status # LOGSTATS [ on | off ] on enables, off disables # Note! This generates a lot of output, so if # you turn this on, be sure that the # file defined in syslog.conf for LOG_NOTICE is a named pipe. # You probably do not want this on. LOGSTATS off # Time interval in seconds between writing the DATA records to # the log file. 0 disables. DATATIME 0 # FACILITY defines the logging facility (class) for logging to syslog. # If not specified, it defaults to "daemon". This is useful # if you want to separate the data logged by apcupsd from other # programs. #FACILITY DAEMON # # ========== Configuration statements used in updating the UPS EPROM ========= # # # These statements are used only by apctest when choosing "Set EEPROM with conf # file values" from the EEPROM menu. THESE STATEMENTS HAVE NO EFFECT ON APCUPSD. # # UPS name, max 8 characters #UPSNAME UPS_IDEN # Battery date - 8 characters #BATTDATE mm/dd/yy # Sensitivity to line voltage quality (H cause faster transfer to batteries) # SENSITIVITY H M L (default = H) #SENSITIVITY H # UPS delay after power return (seconds) # WAKEUP 000 060 180 300 (default = 0) #WAKEUP 60 # UPS Grace period after request to power off (seconds) # SLEEP 020 180 300 600 (default = 20) #SLEEP 180 # Low line voltage causing transfer to batteries # The permitted values depend on your model as defined by last letter # of FIRMWARE or APCMODEL. Some representative values are: # D 106 103 100 097 # M 177 172 168 182 # A 092 090 088 086 # I 208 204 200 196 (default = 0 => not valid) #LOTRANSFER 208 # High line voltage causing transfer to batteries # The permitted values depend on your model as defined by last letter # of FIRMWARE or APCMODEL. Some representative values are: # D 127 130 133 136 # M 229 234 239 224 # A 108 110 112 114 # I 253 257 261 265 (default = 0 => not valid) #HITRANSFER 253 # Battery charge needed to restore power # RETURNCHARGE 00 15 50 90 (default = 15) #RETURNCHARGE 15 # Alarm delay # 0 = zero delay after pwr fail, T = power fail + 30 sec, L = low battery, N = never # BEEPSTATE 0 T L N (default = 0) #BEEPSTATE T # Low battery warning delay in minutes # LOWBATT 02 05 07 10 (default = 02) #LOWBATT 2 # UPS Output voltage when running on batteries # The permitted values depend on your model as defined by last letter # of FIRMWARE or APCMODEL. Some representative values are: # D 115 # M 208 # A 100 # I 230 240 220 225 (default = 0 => not valid) #OUTPUTVOLTS 230 # Self test interval in hours 336=2 weeks, 168=1 week, ON=at power on # SELFTEST 336 168 ON OFF (default = 336) #SELFTEST 336