http://newyork.cbslocal.com/2017/10/11/facebook-instagram-down/

@eddiejennings said in FreePBX - High Load Averages:

@dafyre said in FreePBX - High Load Averages:

@eddiejennings said in FreePBX - High Load Averages:

I failed to run sar in a timely fashion. When this spike occurs again, I'll know to run it.

If you don't have sar installed already, go ahead and install it so you know what "good" looks like too.

Yeah, I ran it and got a copy of the results. That how I knew I missed my opportunity.

Did you check the logs (usually stored in /var/log/sysstat/)?

Try sar -f /var/log/sysstat/sa02 to see the stats from yesterday.

North Korea hackers steal US-South Korea war plans

http://www.bbc.com/news/world-asia-41565281

http://www.rollingstone.com/culture/news/ralphie-may-last-comic-standing-comedian-dead-at-45-w507670

Last minute preparations for Nate....

Apparently that initial report was wrong. Now they're stating that Tom Petty is clinging to life.

@DustinB3403 Have you read the "something for everyone" link? Citrix has changed the rules regarding availability of updates.

After upgrading to Yarn 1.1.0, the majority of the warnings are gone. For me, all that remains is

[4/5] Linking dependencies...
warning "[email protected]" has unmet peer dependency "prop-types@^15.5.4".
warning The case-insensitive file /opt/xo-web/node_modules/react-bootstrap-4/node_modules shouldn't be copied twice in one bulk copy

and I haven't investigated those yet.

Tried updating to the latest version of XO earlier today and ran into a few issues, such as the following warning --

[4/5] Linking dependencies...
warning "[email protected]" has incorrect peer dependency "eslint@>=3.19.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-import@>=2.2.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-node@>=4.2.2".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-promise@>=3.5.0".
warning "[email protected]" has incorrect peer dependency "eslint-plugin-standard@>=3.0.0".

Reviewing the upgrade process, found the following error during apt-get update --

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E074D16EB6FF4DE3
W: Some index files failed to download. They have been ignored, or old ones used instead.

Turns out that the the Yarn public key was expiring soon and they've issued a new key as described here.

Haven't figured out the proper way to resolve this as part of the update script. However, I have tried both of the following with success --

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -

This just manually issues the command from the script to add the correct key.

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys E074D16EB6FF4DE3

This method works as well by retrieving the key directly from the key server.

But the remaining 5 drives aren't brand new. They have presumably seen a similar amount of activity as the failed drive, and therefore are more likely to fail during the rebuild.

@dustinb3403 I was wondering the same thing.

@marcinozga said in Best DNS choice for a financial institution?:

It's always been that way. Not that it's stopped anyone from using it anyway. I 2nd local Pi-hole installation. Add OpenDNS on top and you have a nice extra layer of filtering.

Actually, it was free for business at one time.

https://community.spiceworks.com/topic/197779-opendns-transitioning-to-paid-only-service-for-businesses?page=1#entry-1184863

@penguinwrangler said in Best DNS choice for a financial institution?:

@dashrender said in Best DNS choice for a financial institution?:

@reid-cooper said in Best DNS choice for a financial institution?:

OpenDNS is good. Or just use Google, it's not bad.

For pure DNS probably so - but the OP is claiming (and JB is refuting) that OpenDNS provides filtering for free that no one else does.

And from my own testing about 3 years ago, I agree with the OP, OpenDNS did provide a free level of filtering, but I don't recall what the limitations were.

IIRC the filtering was free for home use only.

Has that always been the case or did this change with the purchase by Cisco?

@dbeato Not sure I understand your point. Noone ever claimed that it was a firewall.

@dashrender Yes it is.

@jaredbusch said in Best DNS choice for a financial institution?:

@dave247 said in Best DNS choice for a financial institution?:

@coliver said in Best DNS choice for a financial institution?:

I don't see anything wrong with this. OpenDNS, Google DNS, Comodo DNS, are all big names that are very unlikely to fall victim to DNS poisoning attacks.

Yeah I was just trying OpenDNS out because someone mentioned that they seem to filter out some "bad"/spam sites and things of that nature. Example: I've had some people accidentally type the wrong URL (off by a letter) and it takes them to a malicious website.

They do no such thing.

How would you classify this functionality then?

@dustinb3403 said in Equifax Has 143 Million Americans Data Compromised:

@danp I'm not surprised.

Can we hang him now?

I say string him up by his nuts.

@scottalanmiller said in SFTP Server:

@danp said in SFTP Server:

Doesn't NextCloud support SFTP? Would that work for you?

Why all the extra effort?

IDK. Thought it might be an option since he indicated a desire to use a different method.

Doesn't NextCloud support SFTP? Would that work for you?

http://money.cnn.com/2017/09/26/investing/equifax-ceo-richard-smith-out/index.html