AWS CodeCommit & Git on OSX fatal unable to access returned error: 403

-
You had setup AWS CLI tools with AWS CodeCommit included and integrated it all to Git using the credential.helper config line. All was working correctly, then you tried to clone or push and got an error similar to:



*** fatal: unable to access 'https://git-codecommit.us-east-1.amazonaws.com/v1/repos/YOUR_REPO/': The requested URL returned error: 403 ***


Solution 1 :

Run in terminal

security delete-internet-password -l  git-codecommit.us-east-1.amazonaws.com

It's is not a permanent solution, now the clock is ticking down to the next password reset done on AWS.

Solution 2 :

As per Amazon Docs:
        1) Open the Keychain Access utility. (You can use Finder to locate it.)
        2) Search for git-codecommit.us-east-1.amazonaws.com . Highlight the row, open the context menu or right-click it, and then choose Get Info.
        3) Choose the Access Control tab.
        4) In Always allow access by these applications, choose git-credential-osxkeychain, and then choose the minus sign to remove it from the list.

 Solution 3 :

Install a version of Git that does not use the keychain by default.

!!!!!!!!!! just use SSH. !!!!!!!!!!!


Reference : https://docs.aws.amazon.com/codecommit/latest/userguide/troubleshooting-ch.html#troubleshooting-macoshttps

Comments

  1. Kevin Davidson11 July 2020 at 05:26

    It's very useful article with inforamtive and insightful content and i had good experience with this information.Enroll today to get free access to our live demo session which is a great opportunity to interact with the trainer directly which is a placement based Salesforce training India with job placement and certification . I strongly recommend my friends to join this Salesforce training institutes in hyderabad practical course, great curriculum Salesforce training institutes in Bangalore with real time experienced faculty Salesforce training institutes in Chennai. Never delay to enroll for a free demo at Salesforce training institutes in Mumbai who are popular for Salesforce training institutes in Pune.

    ReplyDelete
  2. for ict 9910 August 2020 at 11:55

    Great Article
    Cloud Computing Projects


    Networking Projects

    Final Year Projects for CSE


    JavaScript Training in Chennai

    JavaScript Training in Chennai

    The Angular Training covers a wide range of topics including Components, Angular Directives, Angular Services, Pipes, security fundamentals, Routing, and Angular programmability. The new Angular TRaining will lay the foundation you need to specialise in Single Page Application developer. Angular Training

    ReplyDelete

Post a comment

Popular posts from this blog

Datastax Error : Cannot start node if snitch's data center (dc1) differs from previous data center (dc2)

-
Image
This error occurs when the node try to start and see it has snitch information which differ from previous data center. In my case, i was using DseSimpleSnitch which name the datacenter based on workload type. Previously i had enabled solr in dse default
configuration file ( /etc/default/dse ) and datasenter name was Solr. Now i tried to start the dse with graph enabled, which change the name to datacenter SearchGraph which is default workload type name.

CassandraDaemon.java:698 - Cannot start node if snitch's data center (Solr) differs from previous data center (SearchGraph). Please fix the snitch configuration, decommission and rebootstrap this node or use the flag -Dcassandra.ignore_dc=true

Solution :

1) In the last line of cassandra-env.sh set in the jvm opts as given below :
JVM_OPTS="$JVM_OPTS -Dcassandra.ignore_dc=true"
2) If it starts successfully, execute:

nodetool repair nodetool cleanup
Continue Reading »»»»

Datastax Error : Cassandra - Saved cluster name Test Cluster != configured name

-
Image
While changing existing cluster name in datastax, i got name mismatch exception in log file. Process i followed was changed the cluster name in cassandra.yaml configuration file.

$ nano /etc/dse/cassandra/cassandra.yaml

cluster_name: 'Test Cluster1'








Solution : 


Change the cluster name  to "New Cluster Name" :

$ cqlsh `hostname -I`

cqlsh> UPDATE system.local SET cluster_name = 'New Cluster Name' where key='local';
cqlsh> exit;

$ nodetool flush system

Stop the cluster :

$ sudo service dse stop;sudo service datastax-agent stop

Edit the file :

$ sudo vi /etc/dse/cassandra/cassandra.yaml
cluster_name: 'New Cluster Name'

Start the cluster :

$ sudo service dse start;sudo service datastax-agent start

Check Installation log :

 $ cat /var/log/cassandra/output.log


Reference  : https://support.datastax.com/hc/en-us/articles/205289825-Change-Cluster-Name-

Continue Reading »»»»

Configure Nagios plugin " check_logfiles " for scanning log file

-
I was checking for a nagios plugin which could filter the specified log file which i had mentioned and notify me whenever a warning or error appeared in log. Finally i get in hand check_logfilecreated by Gerhard Lausser. Check_logfiles is used to scan the lines of a file for regular expressions.

Install the plugin on client system : 

$ wget https://labs.consol.de/assets/downloads/nagios/check_logfiles-3.8.0.2.tar.gz

$ tar xvzf check_logfiles-3.8.0.2.tar.gz

$ cd check_logfiles-3.8.0.2/

$ ./configure

$ make

$ make install

check_logfiles executable file will get installed on location "/usr/local/nagios/libexec"


Configure Check Pattern :

$ nano  /etc/nagios-plugins/config/check_log.cfg

@searches = (
  {
    tag => 'Error',
    logfile => '/var/logs/error.log',
    criticalpatterns => 'Error',
  }
);

Here i am filtering pattern "Error" from log file which i had mentioned in logfile parameter section


Configure nrpe.cfg in client system :

$ nano /etc/nagio…
Continue Reading »»»»

Popular posts from this blog

Datastax Error : Cannot start node if snitch's data center (dc1) differs from previous data center (dc2)

-
Image
This error occurs when the node try to start and see it has snitch information which differ from previous data center. In my case, i was using DseSimpleSnitch which name the datacenter based on workload type. Previously i had enabled solr in dse default
configuration file ( /etc/default/dse ) and datasenter name was Solr. Now i tried to start the dse with graph enabled, which change the name to datacenter SearchGraph which is default workload type name.

CassandraDaemon.java:698 - Cannot start node if snitch's data center (Solr) differs from previous data center (SearchGraph). Please fix the snitch configuration, decommission and rebootstrap this node or use the flag -Dcassandra.ignore_dc=true

Solution :

1) In the last line of cassandra-env.sh set in the jvm opts as given below :
JVM_OPTS="$JVM_OPTS -Dcassandra.ignore_dc=true"
2) If it starts successfully, execute:

nodetool repair nodetool cleanup
Continue Reading »»»»

Datastax Error : Cassandra - Saved cluster name Test Cluster != configured name

-
Image
While changing existing cluster name in datastax, i got name mismatch exception in log file. Process i followed was changed the cluster name in cassandra.yaml configuration file.

$ nano /etc/dse/cassandra/cassandra.yaml

cluster_name: 'Test Cluster1'








Solution : 


Change the cluster name  to "New Cluster Name" :

$ cqlsh `hostname -I`

cqlsh> UPDATE system.local SET cluster_name = 'New Cluster Name' where key='local';
cqlsh> exit;

$ nodetool flush system

Stop the cluster :

$ sudo service dse stop;sudo service datastax-agent stop

Edit the file :

$ sudo vi /etc/dse/cassandra/cassandra.yaml
cluster_name: 'New Cluster Name'

Start the cluster :

$ sudo service dse start;sudo service datastax-agent start

Check Installation log :

 $ cat /var/log/cassandra/output.log


Reference  : https://support.datastax.com/hc/en-us/articles/205289825-Change-Cluster-Name-

Continue Reading »»»»

Configure Nagios plugin " check_logfiles " for scanning log file

-
I was checking for a nagios plugin which could filter the specified log file which i had mentioned and notify me whenever a warning or error appeared in log. Finally i get in hand check_logfilecreated by Gerhard Lausser. Check_logfiles is used to scan the lines of a file for regular expressions.

Install the plugin on client system : 

$ wget https://labs.consol.de/assets/downloads/nagios/check_logfiles-3.8.0.2.tar.gz

$ tar xvzf check_logfiles-3.8.0.2.tar.gz

$ cd check_logfiles-3.8.0.2/

$ ./configure

$ make

$ make install

check_logfiles executable file will get installed on location "/usr/local/nagios/libexec"


Configure Check Pattern :

$ nano  /etc/nagios-plugins/config/check_log.cfg

@searches = (
  {
    tag => 'Error',
    logfile => '/var/logs/error.log',
    criticalpatterns => 'Error',
  }
);

Here i am filtering pattern "Error" from log file which i had mentioned in logfile parameter section


Configure nrpe.cfg in client system :

$ nano /etc/nagio…
Continue Reading »»»»