I am trying to install the redmine Git Hosting plugin for redmine 3.3.2.
I have followed the steps at (http://redmine-git-hosting.io/get_started/) but when i try the 9th step, which is to login to the git, I get asked for a password. There is no password on the GIT user, and just entering a blank password also doesn't work...
I can confirm that there's no password on the user:
[root#RedmineZonderDocker2 ~]# passwd -S git
git NP 2018-12-16 0 99999 7 -1 (Empty password.)
The log of the plugin does state this:
2018-12-16 20:16:47 +0000 [INFO] Testing if Redmine user 'redmine' can sudo to Gitolite user 'git'...
2018-12-16 20:16:47 +0000 [INFO] OK!
2018-12-16 20:16:47 +0000 [ERROR] Error while getting Gitolite infos, check
your SSH keys (path, permissions) or your Git user.
I clearly have no idea where the problem lays, and as you might notice, i'm quite new to all this. Any help would be appreciated.
If you need other config files or logs, please let me know and i'll gladly provide them.
Kind regards
Make sure you have completed all the settings described in step 9 and restarting Redmine after changing said settings, as some of them are put in cache.
The password is only asked if the SSH key is not found or not properly register. In both instances, double-check "Gitolite - ssh troubleshooting and tips".
I found the problem, and the plugin is functional now.
Related
tldr; I think I need to add a github token. I have a token from github, but I have no idea how to implement it at the stage that I'm at.
I am trying to deploy an angular 13 app to github pages. Right now, it is just the auto-generated app (I haven't added or changed any code at this point). Here are the steps I have taken
Step 1: Create App and make sure it works
ng new <appName>
cd <appName>
ng serve
Step 2: Create a Repo on Github
Step 3: Check if it automatically connected to a repo (and remove if it's not the one we want)
git remote
git remote -v
git remote remove origin
Step 4: Connect to correct Git Repo (replace variables with username and project name)
git remote add origin <https://github.com/USERNAME/PROJECT_NAME.git>
Step 5: Push to Git repo
git branch -m main
git add .
git commit -m "initial commit"
git push -u origin main
Step 6: Hosting
npm install -g gh-pages
ng build --prod --base-href /PROJECT_NAME/ (find project name in angular.json at very bottom
gh-pages -d dist
When I do all of this, it shows that it worked. But then, it just loads a 404 error. After a lot of googling, I think it has something to do with a token. So I went and got the token, but I'm not sure what to do with it.
P.S. already saw Git Hub Pages not Deploying. (404) and it was unhelpful.
The answer was User Error. The code above works and will deploy an app successfully to gitHub pages.
The problem was I was going to https://humanhickory.github.io/ but the ng build --prod --base-href had actually created a new folder which I had to navigate to (so https://humanhickory.github.io//)
Futhermore, I was able to use the token by running gh-pages -d dist a second time. The first time I did it it said "remote: Invalid username or password. Fatal: authentication failed for '....'". However, when I ran the same command a second time, it prompted me to log in. So there's that.
From today only I started getting issue while running deployment scripts from my local VM. I am not sure if it's a known issue or some setup related thing which is missing on my VM .
Authentication failed while running deploy_one_off:
[vvaibhav#gld2vm40 debesys (topic/Add_FIX_IBDC_Session_Subtype_info_to_pub-DEB-107734)]$ /opt/virtualenv/devws/bin/python2 deploy/chef/scripts/deploy_one_off.py -s gla2vm178 --email vagesh.vaibhav#trade.tt -c dropcopyclientnode -r 5fff2fe00e5082b39fd5a978af7bf38770a95ef9 --request-build --run-chef --override-oneoff
Enter your INTAD username:vvaibhav
Enter password for INTAD user vvaibhav:
Checking if dropcopyclientnode cookbook has a build target...DONE
Oops: Failed to authenticate and retrieve AWS Keys from AWS, the package check will
fail. It is safe to try re-running, but if the problem persists please notify
Deployment and/or ELS. Exception:
Just FYI,
This issue was resolved as I worked with Tom today morning. It seems that some aws-keys file became stale and we had to delete those files.
$ ls -ltr ~/.aws-keys*
-rw-r--r-- 1 vvaibhav sysadmins 0 Jan 7 07:42 /home/vvaibhav/.aws-keys_deb_read
I have some GCP users with the roles :
* compute.instances.osAdminLogin
* iam.serviceAccountUser
They connect throw ssh with the GCP web interface in compute engine
When they do sudo ls
For some user the password is requested and some not.
in the folder /var/google-sudoers.d/
for the users that can do sudo without the prompt we can read on their file:
user_name ALL=(ALL) NOPASSWD: ALL
for the others the files are empty
os information :
uname -a
Linux xxx 4.15.0-1027-gcp #28~16.04.1-Ubuntu SMP Fri Jan 18 10:10:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
For the same users, on another vm, in the same gcp project, they all can do sudo.
I am expecting that for all users having the same roles, they have the same sudo behaviour on instances.
What should I do for my users to be able to sudo ? ( except overriding the empty files in the folder /var/google-sudoers.d/ > that is working but may not be stable)
I had a similar problem on a project that was originally set up with the legacy login system (based on SSH keys stored in instance or project metadata). When I converted the project to use OS Login, I lost the ability to sudo without a password on one VM instance. This was a major problem, since I had never set a password for my user account, and therefore was unable to sudo to troubleshoot the problem.
Things I tried that did NOT work:
Rebooting the instance
Explicitly adding role roles/compute.osAdminLogin to my IAM account (I was already a project owner)
I solved the problem by editing the project compute engine metadata to disable OS Login. After disabling, I confirmed that I was able to log into the problematic instance and sudo without a password. I then edited the project metadata again to re-enable OS Login. This time, passwordless sudo worked on the problematic instance. It appears that the instance was not fully reconfigured the first time I switched from legacy login to OS Login.
All of a sudden I started getting "Permission Denied" issues when trying to run any gcloud commands such as gcloud components update -- the issue was avoided if I ran sudo gcloud components update but it's not clear to my why the sudo command is suddenly required? I have actually been trying to run a GCMLE experiment and it had the same error/warning, so I tried updating components and still ran into this issue. I have been travelling for a couple days and did not make any changes since these same commands worked a few days ago. Further, I did not changed my OS (Mac High Sierra 10.13.3) -- were there any changes on the Google side that might explain this change in behavior? What is the best course of action to permanently get around this warning?
(conda-env) MacBook-Pro:user$ gcloud components update
WARNING: Could not setup log file in /Users/$USERNAME/.config/gcloud/logs, (IOError: [Errno 13] Permission denied: u'/Users/$USERNAME/.config/gcloud/logs/2018.03.10/XX.XX.XX.XXXXXX.log')
after sudo gcloud components update I was able to kick off a GCMLE experiment, but I also get the same warning (though my job now submits successfully).
WARNING: Could not setup log file in /Users/#USERNAME/.config/gcloud/logs, (IOError: [Errno 13] Permission denied: u'/Users/$USERNAME/.config/gcloud/logs/2018.03.10/XX.XX.XX.XXXXXX.log')
Based on an answer to a similar question, you probably need to change the permissions to the appropriate directories:
sudo chown -R $USER ~/.config/gcloud
That same post suggests that permissions may have gotten out-of-whack by running a gcloud command with sudo.
In most cases, the problem is not caused by the ~/.config/gcloud directory but the installation directory of gcloud which is owned by root:
drwxr-xr-x 20 root staff 640 Jun 20 18:22 google-cloud-sdk
Solution:
You must change permissions for that directory to your user from:
by:
sudo chown -R $USER /Users/$USER/bin/google-cloud-sdk
I'm making an app with Django and I want to upload it to Heroku but when I do
git push heroku master
I got this error and I don't know how to fix it.
! Your account myemail#gmail.com does not have access to fathomless-depths-4588.
!
! SSH Key Fingerprint: xx:xx:xx:xx:xx:xx:xx:xx:xx:02:xx:xx:79:xx:0f:xx
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
and I'm not using that mail "myemail#gmail.com" it's from an old project, I already use: heroku logout, and heroku login but it doesn't work.
I don't know is the SSH is important that's why I put it on xx xD!
I'll appreciate any help.
You should have a look at heroku-accounts - allows you to manage multiple accounts on the same machine.
https://github.com/ddollar/heroku-accounts.
Hope this helps.