SOLVED UPS Setup Fails

Status
Not open for further replies.

NasKar

Guru
Joined
Jan 8, 2016
Messages
739
I'm trying to setup the UPS service. My UPS is a APC Backup -UPS Pro 1000. When I plug it into the Freenas box it says ugen0.7<American Power Conversion> at usbus0. Here is my setup which errors when I try to turn the service on. Seems to not like the username and pw. I've also tried the Freenas box username and pw without success. I've checked the manual which didn't help and look at other threats about UPS setup but I'm still lost.
Code:
Feb 27 21:39:50 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).
Feb 27 21:39:50 freenas notifier: nut_upsmon not running? (check /var/db/nut/upsmon.pid).
Feb 27 21:39:50 freenas notifier: nut_upslog not running? (check /var/db/nut/upslog.pid).
Feb 27 21:39:50 freenas notifier: Cannot 'restart' nut. Set nut_enable to YES in /etc/rc.conf or use 'onerestart' instead of 'restart'.
Feb 27 21:39:50 freenas notifier: Cannot 'restart' nut_upsmon. Set nut_upsmon_enable to YES in /etc/rc.conf or use 'onerestart' instead of 'restart'.
Feb 27 21:39:51 freenas notifier: Cannot 'restart' nut_upslog. Set nut_upslog_enable to YES in /etc/rc.conf or use 'onerestart' instead of 'restart'.
Feb 27 21:39:56 freenas notifier: tcgetattr(/dev/ugen0.7): Inappropriate ioctl for device
Feb 27 21:39:56 freenas notifier: Network UPS Tools - APC Smart protocol driver 3.1 (2.7.3)
Feb 27 21:39:56 freenas notifier: APC command table version 3.1
Feb 27 21:39:56 freenas notifier: Driver failed to start (exit status=1)
Feb 27 21:39:56 freenas notifier: Network UPS Tools - UPS driver controller 2.7.3
Feb 27 21:39:56 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Feb 27 21:39:56 freenas notifier: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Feb 27 21:39:56 freenas notifier: Starting nut_upsmon.
Feb 27 21:39:56 freenas notifier: kill: No such process
Feb 27 21:39:56 freenas notifier: UPS: ups (master) (power value 1)
Feb 27 21:39:56 freenas notifier: Using power down flag file /etc/nokillpower
Feb 27 21:39:56 freenas upsmon[29034]: UPS [ups]: connect failed: Connection failure: Connection refused
Feb 27 21:39:56 freenas upsmon[29034]: Communications with UPS ups lost
Feb 27 21:39:56 freenas notifier: Starting nut_upslog.
Feb 27 21:39:56 freenas notifier: Warning: initial connect failed: Connection failure: Connection refused
Feb 27 21:39:57 freenas notifier: Stopping nut_upslog.
Feb 27 21:39:57 freenas notifier: Waiting for PIDS: 29054.
Feb 27 21:39:57 freenas notifier: Stopping nut_upsmon.
Feb 27 21:40:07 freenas find_alias_for_smtplib.py: [common.system:294] Failed to send email: (535, '5.7.8 Username and Password not accepted. Learn more at\n5.7.8  https://support.google.com/mail/?p=BadCredentials u54sm192160qtu.35 - gsmtp')
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/common/system.py", line 275, in send_mail
    server = _get_smtp_server(timeout, local_hostname=local_hostname)
  File "/usr/local/www/freenasUI/common/system.py", line 208, in _get_smtp_server
    em.em_pass.encode('utf-8'))
  File "/usr/local/lib/python2.7/smtplib.py", line 622, in login
    raise SMTPAuthenticationError(code, resp)
SMTPAuthenticationError: (535, '5.7.8 Username and Password not accepted. Learn more at\n5.7.8  https://support.google.com/mail/?p=BadCredentials u54sm192160qtu.35 - gsmtp')
Feb 27 21:40:08 freenas kernel: arp: 192.168.1.3 moved from 00:7f:28:29:aa:1e to 00:1f:90:7d:09:e4 on epair3b
Feb 27 21:40:21 freenas kernel: arp: 192.168.1.3 moved from 00:1f:90:7d:09:e4 to 00:7f:28:29:aa:1e on epair3b
Feb 27 21:40:21 freenas upsmon[29033]: upsmon parent: read
Feb 27 21:40:22 freenas notifier: Waiting for PIDS: 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034, 29034.
Feb 27 21:40:22 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).

ups service setup.jpg
 
Joined
Jan 7, 2015
Messages
1,155
I think APC UPS' user/pass are apc:apc. See if that gets you anywhere.
 
Joined
Jan 7, 2015
Messages
1,155
Alternatively you can look HERE and see if this gets you anywhere. Seems apcuser:apc is another one that is widely used for APC devices.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
This error is telling you it can't send an email. Check your email settings and your google passwords.
 

NasKar

Guru
Joined
Jan 8, 2016
Messages
739
I think APC UPS' user/pass are apc:apc. See if that gets you anywhere.
Got it working by changing the driver to "APC UPS 2 BACKUP_UPS PRO USB USB (usbhid-ups)", apcmon:apc but I'm not sure if the username/pw was the issue as it failed with the other driver.
 
Status
Not open for further replies.
Top