UPS and drops

[mrbilky]

I installed a UPS (APC-NS1080G) and now noticed drops on eth0 received is that possible? it is a USB cabled device so not sure if it is responsible or not I have had to reinstall windows after the update screwed up several app drivers I also tried to install calibre but ran into a problem trying to install the script to the docker so I removed it and its appdata wondering if there are remnants of that causing the issue, any takers on where the problem might lie?

 

 

syslog.txt

[miniwalks]

Can you please elaborate on how this is to do with UnRaid?

Is this windows machine a VM on UnRaid with hardware pass through?

Make/Model
OS Ver
VM Specs
Etc

Please


Sent from my iPhone using Tapatalk

[mrbilky]

1 minute ago, miniwalks said:

Can you please elaborate on how this is to do with UnRaid?

Is this windows machine a VM on UnRaid with hardware pass through?

Make/Model
OS Ver
VM Specs
Etc

Please


Sent from my iPhone using Tapatalk

Well that's the question I don't know that it's an unraid issue but that's why the I posted in the hardware section in the event that this is a known issue with UPS's, My box is a supermicro mobo with 16 gigs of ddr4 2133 with a I7 6700 cpu no GPU no passthrough simply a 9TB NAS, my daily driver is an asus CH6 with 16gigs of ddr4 3200 an R7 1800x on windows 10 home I figured maybe with the UPS connected to USB it might be sending and receiving data causing the drops I only noticed it after a few days of being connected

[miniwalks]

So to confirm,
The UPS is plugged into UnRAID via USB? Or the Windows Machine, which I’m now assuming is a separate physical box?


Sent from my iPhone using Tapatalk

[mrbilky]

8 hours ago, miniwalks said:

So to confirm,
The UPS is plugged into UnRAID via USB? Or the Windows Machine, which I’m now assuming is a separate physical box?


Sent from my iPhone using Tapatalk

That is correct the unRAID server is connected to the UPS via USB and the windows machine is a separate unit on the network and the server is headless. I noticed the problem after installing the UPS and the windows unit crapped out with the fall update and I tried to install calibre, the server never gave me drops before this so I'm not sure what changed I guess it has to be something in the settings or an orphan script from when I tried to install calibre although I have deleted appdata through the plugin

[miniwalks]

This is getting really convoluted

In summary, it sounds like you haven’t done any significant testing, fault isolation, or even tried removing the UPS management from the equation

Post your diagnostics up, but this is sounding like you have a local issue in your own network.


Sent from my iPhone using Tapatalk

[mrbilky]

27 minutes ago, miniwalks said:

This is getting really convoluted

In summary, it sounds like you haven’t done any significant testing, fault isolation, or even tried removing the UPS management from the equation

Post your diagnostics up, but this is sounding like you have a local issue in your own network.


Sent from my iPhone using Tapatalk

 

To be clear I'm looking for information regarding my original post from someone who may have had or knows of a similar issue, so first off I have begun fault isolation and have set many parameters to default in the settings I have deleted or disabled a couple dockers i.e. calibre in the event that played a role and by the way I posted the syslog in my first post, tell you what how about you move along there is apparently nothing for you to see here other than to criticize what you perceive as me looking for someone to do the work for me

[miniwalks]

Wow.
I try to help you and get more information to assist in the troubleshooting and you have a go at me?

All I’m asking is if you’ve done any other isolation testing?
- plug in ups
— enable ups daemon
Does this cause issue y/n
Does disabling the daemon fix the issue y/n etc


Sent from my iPhone using Tapatalk

[unevent]

17 hours ago, mrbilky said:

I installed a UPS (APC-NS1080G) and now noticed drops on eth0 received is that possible? it is a USB cabled device so not sure if it is responsible or not I have had to reinstall windows after the update screwed up several app drivers I also tried to install calibre but ran into a problem trying to install the script to the docker so I removed it and its appdata wondering if there are remnants of that causing the issue, any takers on where the problem might lie?

 

 

syslog.txt

 

 

From your log:

Nov  1 14:36:02 homeNAS apcupsd[10300]: Power failure.
Nov  1 14:36:03 homeNAS dhcpcd[1757]: eth0: carrier lost
Nov  1 14:36:03 homeNAS kernel: e1000e: eth0 NIC Link is Down
Nov  1 14:36:03 homeNAS avahi-daemon[10333]: Withdrawing address record for 192.168.1.152 on eth0.
Nov  1 14:36:03 homeNAS avahi-daemon[10333]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.152.
Nov  1 14:36:03 homeNAS dhcpcd[1757]: eth0: deleting route to 192.168.1.0/24
Nov  1 14:36:03 homeNAS avahi-daemon[10333]: Interface eth0.IPv4 no longer relevant for mDNS.
Nov  1 14:36:03 homeNAS dhcpcd[1757]: eth0: deleting default route via 192.168.1.1
Nov  1 14:36:04 homeNAS ntpd[1815]: Deleting interface #2 eth0, 192.168.1.152#123, interface stats: received=133, sent=133, dropped=0, active_time=69257 secs
Nov  1 14:36:04 homeNAS ntpd[1815]: 74.82.59.150 local addr 192.168.1.152 -> <null>
Nov  1 14:36:08 homeNAS apcupsd[10300]: Running on UPS batteries.
Nov  1 14:36:08 homeNAS sSMTP[4877]: Unable to locate smtp.gmail.com
Nov  1 14:36:08 homeNAS sSMTP[4877]: Cannot open smtp.gmail.com:465
Nov  1 14:36:19 homeNAS apcupsd[10300]: Mains returned. No longer on UPS batteries.
Nov  1 14:36:19 homeNAS apcupsd[10300]: Power is back. UPS running on mains.
Nov  1 14:36:19 homeNAS sSMTP[5206]: Unable to locate smtp.gmail.com
Nov  1 14:36:19 homeNAS sSMTP[5206]: Cannot open smtp.gmail.com:465
Nov  1 14:36:25 homeNAS dhcpcd[1757]: eth0: carrier acquired
Nov  1 14:36:25 homeNAS kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Nov  1 14:36:26 homeNAS dhcpcd[1757]: eth0: rebinding lease of 192.168.1.152
Nov  1 14:36:31 homeNAS dhcpcd[1757]: eth0: probing for an IPv4LL address
Nov  1 14:36:31 homeNAS dhcpcd[1757]: eth0: DHCP lease expired
Nov  1 14:36:31 homeNAS dhcpcd[1757]: eth0: soliciting a DHCP lease
Nov  1 14:36:37 homeNAS dhcpcd[1757]: eth0: using IPv4LL address 169.254.251.87
Nov  1 14:36:37 homeNAS avahi-daemon[10333]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.251.87.
Nov  1 14:36:37 homeNAS dhcpcd[1757]: eth0: adding route to 169.254.0.0/16
Nov  1 14:36:37 homeNAS avahi-daemon[10333]: New relevant interface eth0.IPv4 for mDNS.
Nov  1 14:36:37 homeNAS avahi-daemon[10333]: Registering new address record for 169.254.251.87 on eth0.IPv4.
Nov  1 14:36:37 homeNAS dhcpcd[1757]: eth0: removing route to 169.254.0.0/16
Nov  1 14:36:38 homeNAS ntpd[1815]: Listen normally on 3 eth0 169.254.251.87:123
Nov  1 14:36:38 homeNAS ntpd[1815]: new interface(s) found: waking up resolver

 

Do you happen to have your Ethernet switch plugged into the 'Surge' only plug on the new UPS?  After your UPS went on battery your Ethernet went dead.  If power fails, or in the case of what looks like your plug-pull UPS test, the surge only outlets go dead.  Also, whatever is plugged into the 'Master' outlet when turned off or goes to sleep/standby it will cause the two gray surge-only  'controlled by master' outlets to turn off as well.  Another tidbit is to not plug in your gigabit Ethernet cable to the data protection ports.  The ports are only rated for 10/100 connections.

 

 

[mrbilky]

6 hours ago, unevent said:

 

 

From your log:

Nov  1 14:36:02 homeNAS apcupsd[10300]: Power failure.
Nov  1 14:36:03 homeNAS dhcpcd[1757]: eth0: carrier lost
Nov  1 14:36:03 homeNAS kernel: e1000e: eth0 NIC Link is Down
Nov  1 14:36:03 homeNAS avahi-daemon[10333]: Withdrawing address record for 192.168.1.152 on eth0.
Nov  1 14:36:03 homeNAS avahi-daemon[10333]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.152.
Nov  1 14:36:03 homeNAS dhcpcd[1757]: eth0: deleting route to 192.168.1.0/24
Nov  1 14:36:03 homeNAS avahi-daemon[10333]: Interface eth0.IPv4 no longer relevant for mDNS.
Nov  1 14:36:03 homeNAS dhcpcd[1757]: eth0: deleting default route via 192.168.1.1
Nov  1 14:36:04 homeNAS ntpd[1815]: Deleting interface #2 eth0, 192.168.1.152#123, interface stats: received=133, sent=133, dropped=0, active_time=69257 secs
Nov  1 14:36:04 homeNAS ntpd[1815]: 74.82.59.150 local addr 192.168.1.152 -> <null>
Nov  1 14:36:08 homeNAS apcupsd[10300]: Running on UPS batteries.
Nov  1 14:36:08 homeNAS sSMTP[4877]: Unable to locate smtp.gmail.com
Nov  1 14:36:08 homeNAS sSMTP[4877]: Cannot open smtp.gmail.com:465
Nov  1 14:36:19 homeNAS apcupsd[10300]: Mains returned. No longer on UPS batteries.
Nov  1 14:36:19 homeNAS apcupsd[10300]: Power is back. UPS running on mains.
Nov  1 14:36:19 homeNAS sSMTP[5206]: Unable to locate smtp.gmail.com
Nov  1 14:36:19 homeNAS sSMTP[5206]: Cannot open smtp.gmail.com:465
Nov  1 14:36:25 homeNAS dhcpcd[1757]: eth0: carrier acquired
Nov  1 14:36:25 homeNAS kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Nov  1 14:36:26 homeNAS dhcpcd[1757]: eth0: rebinding lease of 192.168.1.152
Nov  1 14:36:31 homeNAS dhcpcd[1757]: eth0: probing for an IPv4LL address
Nov  1 14:36:31 homeNAS dhcpcd[1757]: eth0: DHCP lease expired
Nov  1 14:36:31 homeNAS dhcpcd[1757]: eth0: soliciting a DHCP lease
Nov  1 14:36:37 homeNAS dhcpcd[1757]: eth0: using IPv4LL address 169.254.251.87
Nov  1 14:36:37 homeNAS avahi-daemon[10333]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.251.87.
Nov  1 14:36:37 homeNAS dhcpcd[1757]: eth0: adding route to 169.254.0.0/16
Nov  1 14:36:37 homeNAS avahi-daemon[10333]: New relevant interface eth0.IPv4 for mDNS.
Nov  1 14:36:37 homeNAS avahi-daemon[10333]: Registering new address record for 169.254.251.87 on eth0.IPv4.
Nov  1 14:36:37 homeNAS dhcpcd[1757]: eth0: removing route to 169.254.0.0/16
Nov  1 14:36:38 homeNAS ntpd[1815]: Listen normally on 3 eth0 169.254.251.87:123
Nov  1 14:36:38 homeNAS ntpd[1815]: new interface(s) found: waking up resolver

 

Do you happen to have your Ethernet switch plugged into the 'Surge' only plug on the new UPS?  After your UPS went on battery your Ethernet went dead.  If power fails, or in the case of what looks like your plug-pull UPS test, the surge only outlets go dead.  Also, whatever is plugged into the 'Master' outlet when turned off or goes to sleep/standby it will cause the two gray surge-only  'controlled by master' outlets to turn off as well.  Another tidbit is to not plug in your gigabit Ethernet cable to the data protection ports.  The ports are only rated for 10/100 connections.

 

 

Thank you for the input and yes you are correct the router power brick was incorrectly installed on the surge protection side I have installed the ethernet directly into the router so far so good no drops, Do you know of any known issues running the coax into this unit I did because it was there? Thanks again that was what I was looking for! And that first power outage happen to be the real deal I did not do that so guess the investment has already showed some dividends between the utility company and my kids popping breakers this thing will serve me well!

[unevent]

4 hours ago, mrbilky said:

Thank you for the input and yes you are correct the router power brick was incorrectly installed on the surge protection side I have installed the ethernet directly into the router so far so good no drops, Do you know of any known issues running the coax into this unit I did because it was there? Thanks again that was what I was looking for! And that first power outage happen to be the real deal I did not do that so guess the investment has already showed some dividends between the utility company and my kids popping breakers this thing will serve me well!

 

Those UPS coax protections are typically not good for anything beyond analog antenna which is of no use these days.  The lightning protection typically consists of a poorly implemented gas discharge tube device and on most if not all consumer grade surge protectors/UPS they are typically not impedance matched for 75 ohm use and the higher frequencies involved with digital OTA, cable TV/Internet, and Satellite will suffer from signal reflections.  In the US it is NEC requirement for coax to be grounded at or near the service entrance for cable/satellite and antenna (as it requires a rather large ground wire, typically 10AWG or larger).  So if done right you should already be covered for outer conductor protection.  Inner conductor protection suggest a high quality lightning surge protector rated for 1GHz with low insertion and return loss such as Tii Technologies 212FF75F225-21 (here, here) or if you can find it, Extreme Broadband Engineering BB1SP.

[mrbilky]

7 hours ago, unevent said:

 

Those UPS coax protections are typically not good for anything beyond analog antenna which is of no use these days.  The lightning protection typically consists of a poorly implemented gas discharge tube device and on most if not all consumer grade surge protectors/UPS they are typically not impedance matched for 75 ohm use and the higher frequencies involved with digital OTA, cable TV/Internet, and Satellite will suffer from signal reflections.  In the US it is NEC requirement for coax to be grounded at or near the service entrance for cable/satellite and antenna (as it requires a rather large ground wire, typically 10AWG or larger).  So if done right you should already be covered for outer conductor protection.  Inner conductor protection suggest a high quality lightning surge protector rated for 1GHz with low insertion and return loss such as Tii Technologies 212FF75F225-21 (here, here) or if you can find it, Extreme Broadband Engineering BB1SP.

Wow good info I just switched from cable (comcast) to fibre (verizon) but I'll have to look now that you brought that to my attention as it's only fibre to the control panel