Error: Update could not be validated. Make sure network secure and try again. - updates

Current version of Mamp Pro is 5.04 (15996). The available updates window says "Mamp 5.0.0 > 5.1. Update fails with a message saying Error: Update could not be validated. Please make sure you are using a secure network and try again."
Is it odd that the update does not say 5.0.4 > 5.1??
I have no idea what secure network is referred to. Everything on my computer is as secure as I can make it. Especially the wireless network.
I'm running High Sierra 10.13.6 on a new iMac.

This issue has affected other updates in the past. Not sure what the exact cause is, however, the workaround is straight forward.
1, Download the latest version manually from MAMP here.
2, Run the installer, closing MAMP beforehand.
3, Once restarted, the option to 'upgrade' will present itself, click install and it should work no problem.
Edit: Since 5.3 -> 5.4, there is no need for step 3. Just the first 2.

Related

Openshift OKD Excessive Logging

So I installed a single host Openshift OKD v3.11 cluster. I installed it on a VM running Centos 7.8.2003.
It seems to have installed ok except that it continually streams verbose logs to /var/log/messages. Around 5 logs per second and all seem to be about throttling requests. Example of a typical log message:
******Jun 13 15:49:13 centos7 journal: I0613 14:49:13.011402 1 request.go:485] Throttling request took 196.341689ms, request: GET:https://172.30.0.1:443/api/v1/namespaces/openshift-service-cert-signer/serviceaccounts/service-serving-cert-signer-sa*****
The only reference I have managed to find is a question here but the access to the discussion is only available to those with deep pockets.
https://access.redhat.com/solutions/3348921
I assume these logs are nothing to worry about and so my main question is what is the "best"/cleanest/simplest/easiest way to ensure the Openshift cluster doesn't continue to fill up /var/log/messages but will still log any important messages there?
I would recommend looking at the root cause for this behavior. These messages indicate that there are a lot of requests coming to your API. Typically this is due to some application performing calls in a tight loop leading to this many messages. In your case check your openshift-service-cert-signer if you can see any warnings or an abnormal amount of log messages.
If you want to get rid of the throttling messages, you can increase the amount of Queries per second (QPS) for the API server: Recommended Practices for OKD Master Hosts (lower part).
The only reference I have managed to find is a question here but the access to the discussion is only available to those with deep pockets. https://access.redhat.com/solutions/3348921
I do not understand why you're saying that, as I can access that document with my free Red Hat account without any subscriptions. Have you tried with a free account as it says on the site?
Simon's answer was helpful but I've finally got to the bottom of this.
The problem was simply that the version of Docker I had installed was old. At the time of writing the latest version of Centos is 7.8.2003 and if you install that and then simply run "yum install docker" hoping that you'll get something at least reasonably new and certainly compatible with the rest of the linux installation, you'll probably be making a mistake.
The right thing to do is to follow the simple steps here:
https://docs.docker.com/engine/install/centos/
The reason I found the problem was because excessive logging of my openshift cluster wasn't the only issue. I started seeing strange behaviour of other containers. A process of trial and error narrowed down the issue to the default Centos version of docker. Once I followed the page above all my problem vanished including the original problem of /var/log/message getting hammered by openshift containers.
The main reason I decided to answer my own question was because surely someone else is going to be as impatient/thick as me and simply install Centos7 then try "yum install docker" without knowing they're about to enter a world of pain.

MacOS MySQL Gone Away and local networking issues due to GateKeeper

On MacOS Mojave 10.14.5, local services relying on TCP connections have connections randomly aborted, resulting in errors like "Mysql has gone away" and Nginx connection resets.
Seems like the Mojave OS is monitoring and blocking TCP connections, even if the firewall is disabled.
I managed to get MySQL working in a docker image, however this is much slower than native MySQL service. Same applies to NGinx.
A lot of blog articles online cover this issue with MySQL, recommending to increase wait_timeout and max_packet_size, which does not work in this case as the issue is most likely not with MySQL itself (in fact, local Nginx seems also to be affected).
Just spent 2.7K on a brand new MacBookPro and feel like I can't work with it...
Any help?
Chatted with Apple Support, who recommended to do an SMC reset, which I have done twice and it did not help... They don't really offer support for the OS issues... Was about to return the MacBookPro and buy a Linux laptop...
... and then figured it out!!!
As part of installation instructions for a third-party VPN software, I have been asked to run the following command on my MacOS Mojave 10.14.5:
sudo spctl --master-disable
This was to allow ALL applications to be installed on the system, bypassing System > Privacy settings (adding a third option "Allow all"), basically working around the GateKeeper service to allow for the VPN app to install.
This was meant to be disabling GateKeeper, so it won't interfere with the application, however it looks like GateKeeper is still doing something shady, and actually causing the networking issues.
Anyway, it was enough to switch it back and restart the MacBook:
sudo spctl --master-enable
in Terminal and reboot.

Xampp doesn't work on Mac X

So here is what happens when i run xampp by clicking on the manager-osx.
I click on "manager-osx".
Icon jumps in the dock as if it is starting the service.
Asks for admin password. I enter the password.
It accepts the password, and application keep jumping in the docs for 3-4 times.
The app disappear from the dock.
The issue started after i have quit few processes from the activity monitor.
I am not sure what has affected xampp and can't remember what services i have stopped as there were many.
Solution applied so far:
Restarted my MacBook Pro.
Exit all other application and tried to run xampp.
Made sure no other application is running on port 80.
Removed xampp from applications and tried to reinstalled. Same issue with re-installation process, It asks for admin password and then nothing happens.
search online for any help but nothing helpful found.
I haven't got any experience with XAMMP but MAMP works always fine for me. MAMP has everything I need in terms of functionality.
I would recommend MAMP
If MAMP is not the best solution for you. You can install manualy
APACHE + PHP + MYSQL (It's not so hard)
Just go step by step using tutorial like
This
Manual installation will give you much more controll on your enviroment.
And also you will have better output to attach it here if you can't find a problems.
Of course it's little bit longer than 3 clicks. But on all production servers you need to install environment manually. This knowledge you will use later much more times. You will better understand how all is works and how to find reason of bug.(error)

How to avoid that my server restarts every time I commit something?

I have 3 cartridges: PHP 5.4, MySQL 5.5 and phpMyAdmin 4.0. Every time I commit any change to my openshift, I see that my website is down because Apache is restarting but, is this really necessary? Is there any way to avoid it to restart everytime?
Thanks!
Today I discovered how to hot-deploy my application. Link: openshift.com/blogs/hot-deploying-php-on-openshift
Definition of hot-deploy: Hot-deployable services are those which can be added to or removed from the running server. It is the ability to change ON-THE-FLY what’s currently deployed without redeploying it.
Other information: openshift.com/kb/kb-e1057-how-can-i-deploy-my-application-without-having-to-restart-it

Windows Store App Cert Kit Fails to Start

The Windows Store App Cert kit fails to start.
Normally the flow is:
Start App Cert Kit
Choose Windows Store Application
Choose App
Choose Certs to Run
Run Certs
Save results
Currently, it fails just before 'Choose App'.
I get this result:
I have tried uninstalling and reinstalling, installed all updates, running appcert.exe reset. All to no avail.
I think it may have to do with the same issue I get with the Windows Store app. I have 38 languages installed (our app supports all of them) and the Windows Store app doesn't like it. I've had to escalate with customer support repeatedly for this, and have not had it resolved properly. I wonder if the same issue applies here.
So I was unable to start the UI, but I was still able to run the appcert by manually calling it on the command line as described here. It worked fine. One thing to note is that between each attempt, make sure to run appcert.exe reset.