Just having a bit of a reshuffle whilst moving off my laptop onto a new Windows PC at work now that I have stopped being freelance and gone full time.
I can't seem to find anything, but is there a setting or something which will enable me to tell ToroiseGit to use my new private key for ALL my existing remotes?
TortoiseGit -> Settings -> Git -> Remote
For each remote, enter putty key
Related
I am trying to get a connection to work on my machine to an AS400 database as per this link.
I have confirmed that there is no firewall blocking the machine I am working on. I have confirmed that the connection info works on a different machine with a .UDL file. I have installed the requisite C++ runtime libraries onto the machine and confirmed it has the appropriate .NET framework (it has 4.7.2). When I try to run the UDL file with the same connection information, I get "Provider cannot be found. Ensure that the provider has been installed properly." As far as I can tell I did, but it is not detecting that?
Can someone help me understand how to get it set up so that the UDL file will indicate if the connection was successful or not? I'm not really sure what is at issue at this point.
edit: I got lucky on more searching and so on further inspection, I can see that it is not in the registry editor. Could that be the issue? How would I add it there properly so that it shows up as a Data Link so that I can configure it correctly?
go here to download and install access client solutions
after installing the base package, navigate in the install folder and find the Windows_Application folder. In that folder, double click on install_acs_64.js. That will install the ODBC drivers.
run the ODBC Data Source Adminstrator app on the windows PC. Click the Add button. Select the IBM i Access ODBC Driver. Make sure to click the Server tab and set the default schema and library list.
Once the ODBC driver is installed you can test the connection by opening Excel and use the Data tab to config a connection to the IBM i database.
I've tried looking at other questions here with similar problems, but unfortunately I haven't been able to solve this issue.
For some basic background info, I'm currently using a PC in a lab and the lab has GPU servers somewhere in the institution. I'm attempting to connect the Atom Editor to the remote host. My PC uses Windows 10 and the remote server is Ubuntu 16.04.
I've looked at thie remote-atom guide but for some reason the "Start Server" option is not working. I've also tried to do what this answer has stated, but unfortunately I don't have sudo permission.
Would there be another way that I can connect Atom remotely? Thank you.
You can easily connect to remote FTP using atom even if you do not have any sudo permission on the sudo server.
On Remote server:
- Create a rsa key (ssh-keygen -t rsa)
- add the public key to .ssh/authorized_keys file
- download the private key to you local desktop
On local machine > open Atom editor:
- press ctrl+space to open the 'ftp-remote-edit'
- add the server if not present already
Atom editor: remote server configs
That's it, you are ready to connect and edit files.
Other viable option is using VS code using winScp.
I cannot ssh into my Google Compute Engine (GCE) Wordpress instance anymore.
It was working one month ago when I tried last.
I use the Google built-in SSH client in a Chrome browser window.
Yesterday I tried an got the following message:
The VM guest environment is outdated and only supports the deprecated
'sshKeys' metadata item. Please follow the steps here to update.
The "Steps here" link navigates to https://cloud.google.com/compute/docs/images/configuring-imported-images#install_guest_environment which does not seem to help me much.
I am not aware of any changes that I may have made.
How can I fix this?
It looks like your instance's disk is full, and so the SSH keys can't be created in the temp directory. You can do the following:
Stop your instance and wait for it to shut down
Click on the disk your instance is using, and choose "edit" at the top
Enter a larger disk size, and save
Go back to your instance and start it up again
You should now be able to connect via SSH. While you're in there, check to see what filled up your hard disk so you can prevent this from happening again (maybe a rogue program is printing out too many logs, etc).
If you're seeing this on Debian 8 or 9, the most likely reason for this is that the google-compute-engine.* packages that allow SSH access to the instance have been removed by apt-get autoremove.
If you have an open SSH connection to the machine or can use a tool like gcloud, running apt-get update && sudo apt-get install gce-compute-image-packages should fix this.
If you no longer have any SSH access, there is a procedure available on the GCP docs site that can be used to restore it.
I've created a bug report here for this.
Might be a bit late, but you can
1) Stop the VM
2) Edit and enable serial console
3) Use the serial connection to login and update the VM
recent days, I meet similar problem, later I find the permission rights of my home directory fools me, as a lazy-bone, I chmod 777 ~
After did that, I cannot ssh via my terminal, even cannot ssh via browser, only get 'The VM guest environment is outdated and only supports the deprecated 'sshKeys' metadata item, Plese follow the steps here to update'. Sounds like you must set 755 to your home dir, not just care your 700 .ssh or 600 authorized_keys.
I met the similar issue after I created a FreeBSD VM, gcloud ssh not works, but I am lucky that I can use the browser window ssh to my VM. Then I manually add the google_compute-engine public key to the .ssh/authorized_keys, now it work, I can use the gcloud ssh to connect. But not sure if this is a better/security way.
I downloaded the Teradata express VM today. But I don't use vmware... i use virtual box instead. I created a new VM and added all the vmdk disk files to virtual box.
but it is throwing error could not find /dev/disk/by-label/ROOT-BE1. Want me to fall back to /dev/disk/by-path/pci-0000:00
does anyone know how to boot the vm image with virtual box?
I have the same problem, with the same message. The same mistake.
The solution is simple. Just change the Storage Controler to SCSI. After this, restart the VM and it will start normally, but in command line.
I try, but i can't run the startx command...
Try adding IDE controller and then add the disk as existing hard disk device. This should let you boot into the OS.
I saw this exact error when trying to load the VM in KVM. What seemed to fix it was selecting 'single user mode' in the grub menu. After booting like this once, selecting the default grub option subsequently allowed the VM to boot further than this error.
Note that I haven't been able to successfully bring up the actual database yet - the service doesn't start automatically, and when I start it manually, it reboots the VM, bringing me back to the same state as before. Maybe you'll have more luck with VirtualBox?
I am having difficulty connecting to a existing Informix database. I am attempting to mimic the configuration that is present on another machine which currently works. By the way, that other machine is on the same network and it is accessing the DB through a tunnel, so I am pretty sure the issue isn't related to the network configuration.
Regardless, here are the steps that I took to try and make the connection
Downloaded clientsdk.3.50.TC9DE and installed this. The working machine uses 3.50.TC2DE, but I couldn't find the installer for that version. (Note that at first I tried using 3.50TC9, not sure if that makes a difference)
Matched the ODBC config in the new machine to the working machine
The working machine has a host name in the Host Name field. I assume this was allowed because the host was set to an IP in the hosts file. Regardless, I am using the IP.
Also I am using C:\Windows\SysWOW64\odbcad32.exe to create the DSN
Made sure that the INFORMIXDIR and PATH directory were correct. as per http://www.dbforums.com/informix/694408-odbc-test-connection-not-successful.html#post2633932 I don't think the locales are the issue because they aren't set in the working machine's Setnet32. Also, I made sure that the locales matched in the ODBC environment settings.
Also, since my INFORMIXDIR is in C:\Program Files (x86)\IBM\Informix\Client-SDK\bin I tried replacing Program Files (x86) with PROGRAM~2 and Client-SDK with CLIENT~1 to no avail.
Tried setting INFORMIXDIR directly in my system environment variables (outside of Setnet32)
Set DBPATH to match the working system in both the user and system environment variables.
Set INFORMIXSERVER to the server in both Setnet and the system environment variables.
Completely lowered the firewall on my machine.
I can ping and telnet into the server.
I have also tried..
Tried this on Windows XP
Tested the ILogin demo. The result was a popup that stated Customer Records Found in the title bar with an empty text area field.
Reinstalled into C:\informix instead of C:\Program Files(x86)...
Rebooted after various steps.
At this point I am at a loss. Has anyone run into this? The only other things I can think of is that I am using Win7 64-bit (with 32 bit drivers) and that the driver is 9DE not 2DE.
Alright so half of the battle is over. I was able to get a "Test connection was successful" on my Win7 machine. We had a copy of the 2.90.TC6 driver available in our file server from way back. I installed it and it worked. So my guess is that the database I am working with isn't compatible with 3.50.TC9DE.
I guess my next course of action is to try and find an installer for 3.50.TC2DE so that I can match the production system.