broken ssh?

Similar Questions

• Snapshots are broken now

  Hey guys, I'm having a major problem here. With the help of 5.5U1 and last Veeam.

  Something three days stuck in a process of Veeam backup and after that all snapshots of tasks of backup created, and then never erased.

  So yesterday I discovered SSH to each protected VM veeam production had like 90 delta files and they were not appear in the Snapshot Manager. In addition, 'delete all snapshots' failed. And create the new snapshot failed too. After fiddling around with the restart of management on hosts services and add or remove snapshots, I was able to consolidate most of the snapshot successfully.

  However, I always still have some questions, difficult to know:

  (1) a very large VM still has a complete chain-deltas attached to one of its VMDK. vCenter offers to "consolidate", but then consolidation fails with "cannot allocate memory". Theres a lot of RAM available on the host, like 100 GB +, and memory-wise, it's a small VM. There are like 0, 8 x the size of the virtual machine to free space on the data store, but as all deltas take about 10 GB combined, I think that this should not be a problem, too. There was a similar problem with a big other VM, but it was resolved by turning off the virtual machine and then consolidate. It does not help down with power on this virtual machine.

  Still a bit, I think it's a question of data store space, however I do not see why so much free space would be needed to commit snapshots. Is there any maybe so as to make this file a delta at the same time?

  (2) creating new images is now broken. If I try to create a new snapshot of any virtual computer on the hosts involved (even if its engine turned off and no one protected Veeam platoon), it fails with ' a general error has occurred: The delta files are then created, but the pictures do not appear in the Snapshot Manager. However, if I reboot with /etc/init.d/hostd restart management services and restart etc/init.d/vmxa, these shots failed suddenly appear in Manager and work as they are supposed to. And can be removed successfully.

  If I try to take a picture once again, it fails with the same error, and the cycle continues.

  I tried to restart a server ESXi, but who has done nothing more management restarting services already do. The behavior is the same if I create/delete snapshots in the Web Client via vCenter or if I directly on the host computer in the clish.

  I have a suspicion that this is what has caused the problem of Veeam in the first place, given that taking snapshots apparently fails, but it actually happens in the backstage. It's what might be broken and why?

  We have not a vmware active support contract, and I think that Veeam guys will say that it is a matter of vmware. I have yet to hear a response, but my experience with them tells me that this is what's going to happen.

  So, you're my only hope

  Thanks in advance.

  OK guys, thanks for your comments, I solved the problem.

  #1 has been resolved by restarting the ESXi. After that the command of Consolidation has worked like a charm.

  The pile of COW was probably close to being complete before restarting (after two days with 5 virtual machines running with 90 snapshots + each), and that's why the building had failed.

  Problem #2 was incredibly obscure. What has caused all this strangeness was disconnected from a NFS data store where a large number of installation ISOs if it is located. It was off just on the NAS, without disassembling correctly vSphere.

  It turns out that ALL virtual machines I tried to taking snapshots had an ISO in the CD-ROM set up pointing to the data store. (disconnected, but always present in the config).

  So, looks like that ESXi when you have a unavailiable resource in the configuration of the VM. It throws an error that could mean anything at home, then silently with the creation of a snapshot in the background. Crazy...

  What has helped me discover this was sweeping the newspaper spend on one of the hosts after he tried to create a snapshot.

  Thanks to you two, you certainly have me headed in the right direction!

• SCP broken in 5.0 ESXi?

  I tried to look this up, but found no references to the problem, which surprises me.

  Is broken in 5.0 ESXi scp? I tried it on the 5.0 build 469512 and 1 update version 623860, and it works on any.

  I used scp previously on ESXi 4.x and it worked perfectly fine. I just tested again with the same syntax, and it still works fine.

  Is this a known issue?

  When I try to do scp with ESXi 5.0, he knows the command, but it doesn't seem like he even tried to initiate a connection.

  Eventually it times out.

  You must open the ssh ports in the firewall of ESXi.

  In vSphere Client check the host-> Configuration-> Security Profile-> Firewall-> properties

  and select "SSH Client" If you need to scp connections outgoing resp. "SSH server" If you want to enable incoming connections to PCs.

  -Andreas

• Can't ssh on Mac OS VPN server

  I can connect to my VPN L2TP server with my iPhone running iOS 10 through my network of data carriers and passed to my home network from Comcast, but everything does not work;

  What works:

  Access default Web site running the macOS Server using its IP address

  Public Web surfing

  I can ping my phone of any system IP address on my network

  What does not (what I tried):

  SSH to any system macOS on my network

  Access screen sharing on any system macOS on my network

  Resolve the local hostname to an IP address

  More information

  my iphone is running iOS 10

  My computers are running macOS Sierra

  I use Mac OS as host VPN server

  I use the client VPN L2TP iOS 10.

  Firewalls in the system is disabled.

  Typical VPN connections, you use the DNS server of your iPhone and not the DNS server of the network corresponding to your server.  In addition, Hello services are only available on the LAN.  So you have no way to resolve names to IP adrdesses for the network, you are VPNing.

  The only easy solution from an iPhone is to make a list of IP addresses and use them to connect instead of host names.  using IPs will work as long as your ISP does not also use the same internal (like 192.168 or 10.0) IP address than the network that you connect to.

• Time Machine restore, most of the alias icons are broken?

  I recently restored the system of Time Machine, but my alias (for most) have broken images.  If I copy the aliases, they are all fixed, but I can't do it exactly for each alias on the machine!  Restoration of the alias of Time Machine seems to have the same effect.

  Is it possible for the shot to solve this problem?

  I tried several solutions, compensation resolved cache:

  Deploy sudo rm - rf / *.

  sudo rm - rf ~/Library/Caches/*

  Reset

  If I had known what specific cache which is held the icon broken, images that would have been better.  It turns out that only some of the specific sizes were broken, which explains why the icons seem to appear and then disappear again on another page.

• SSH keys no longer work after macOS Sierra Update

  Hello, I have a problem to connect my servers with my previously stored private ssh key in file .ssh with terminal commands or third-party applications. I should mention that I activated the filevault during the upgrade process. I see that my passphases are stored in the keychain, but I need to enter my password every time I want to connect to servers.

  Hello Marshall,

  Try to create a new ssh key. I think Sierra includes updated logic crypto and he doesn't like really old keys.

• remembering ssh passphrases

  Before moving on to the Sierra, the first time I ran a ssh command every day, he would ask for my password and store the key, making it usable by any other ssh process, no matter where I am connected, thanks to the "forwarding agent. That's what I'm used to and is identical to the way things work on my other computer (which runs on Linux).

  After upgrade to Sierra, passphrases my SSH keys are somehow being 'remembers', but no ssh-agent. I am able to ssh from my laptop directly in one of the servers that I managed, without being asked a password, but because the agent does contain all the keys (i.e. "ssh - add - l" returns "the agent has no identity."), I'm not able to ssh from this server to another server, which also makes the 'scp' and 'git' commands do not work until I go back to the laptop itself and run "ssh - add.

  I tried to use "Keychain Access" to find and remove the element containing the password, but no items in any of my files of trousseau (connection, iCloud, System or root system) contain 'ssh' anywhere in their title. I also tried 'ssh - add - d K' and 'ssh - add - d /Users/xxx/.ssh/id_rsa K. Neither the command seems to have no effect, they are not compensation everywhere where passwords are stored.

  The output of "ssh - vvv" Server1 contains the following items:

  debug1: next authentication method: public key

  debug1: offering public key RSA: /Users/xxx/.ssh/id_rsa

  debug3: send_pubkey_test

  debug3: send packets: type 50

  debug2: we sent a publickey packet, wait for reply

  debug3: receive packets: type 60

  debug1: server accepts key: ssh - rsa Bouasla 279 pkalg

  debug2: input_userauth_pk_ok: PS SHA256:m59cRsLlMQHZk1KlO5fJNlaYBhCIyrE3eF4YaX / + q / A

  debug3: sign_and_send_pubkey: SHA256:m59cRsLlMQHZk1KlO5fJNlaYBhCIyrE3eF4YaX RSA / + q / A

  debug3: search for the Query element: {}

  ACCT = "/ Users/xxx/.ssh/id_rsa";

  AGPR = "com.apple.ssh.passphrases";

  class = genp.

  labl = "SSH: /Users/xxx/.ssh/id_rsa";

  nleg = 1;

  'r_Data' = 1;

  Svce = OpenSSH;

  }

  debug2: using Keychain password

  debug3: send packets: type 50

  debug3: receive packets: type 52

  debug1: successful authentication (public key).

  Authenticated to server1 ([192.168.1.209]: 22).

  How can I make ssh NOT remember passwords for my keys?

  Thanks to http://apple.stackexchange.com/questions/253779/macos-10-12-sierra-will-not-forg and my-ssh-keyfile-password , I found that the password is stored in ~/Library/Keychains/{UUID}/keychain-2.db, rather than in the keychain. It is a sqlite3 file and the element containing the sentence can be removed with the following query:

  ~/Library/keychains/*/Keychain-2.DB $ sqlite3

  SQLite > delete from the genp where agrp = 'com.apple.ssh.passphrases';

  SQLite > .q

  $

  The problem is, the next ssh command I type asks for the password and stores it in the same file again.

  How do you prevent ssh from store my passwords at all?

• Sync ITunes broken 12.5.1

  I've also updated my IPhone to OS 10.0.2 lasest and ITunes for 12.5.1 and synchronization is now broken. The phone does not even get detected in ITunes, but OS 10 Windows detects the phone in the Device Manager.

  Get help from this article If iTunes does not your iPad, iPhone or iPod - Apple Support

• Mac OS Server - local users on console does not.  The shared access or ssh on account works

  A Mac Mini running Mac OS Server has problems with authenticating the passwords of local users.  Users connect the console of the physical computer running macOS app Sierra and Server 5.2.

  I'm looking for a short solution from scratch user and migrating data to a new installation.

  My hunch is that there is an interaction with the server application.  The other Macs, I managed on the same network fail server and do not have these problems.

  I installed a new version of macOS Sierra and then migrate the old data server on using the migration wizard, but the problem persists.

  The server used to have users on the network, but they are all deleted, and all users are the.

  In application server, the only services running time machine, the caching server and file server.  DNS, DHCP and Open Directory services are disabled in the server application.

  A local user password will work normally when the computer is restarted.  But if the user disconnects, and tries to connect to or use the fast user switching back and forth between accounts, the password is not accepted.  On reboot, it will be accepted.

  In addition to passwords are not accepted, other errors when you try to connect to specific customers include:

  "Your account is not a valid directory.  For more information, contact your system administrator'

  or

  "On behalf of user that you selected is not available."  Check your network connection and try again to the user account.  If you are connected to the network, ask system administrator for assistance. »

  If a network is used to access the data of the user using the user name and password, it works.  Similarly, SSH'ing via the terminal using the username and password works.

  An admin user can change the password back and it usually works for one login.  Then the password is denied if the user disconnects or use the fast user switching.

  Thanks in advance for any help on this embarrassing problem!

  I should clarify: it's the passwords of local users on the Mac who stop working (for the connection or fast user switching), until the Mac restarts.

• Do I lose all the iMessages that have not been delivered to my iphone if I withdraw (from iMessage) my phone number? My current iphone is broken and I am planing to get a new one, with in a few months.

  Do I lose all the iMessages that have not been delivered to my iphone if I withdraw (from iMessage) my phone number? My current iphone is broken and I am planing to get a new one in a few months.

  You may lose everything.  iMessage, like most e-mail services, don't keep permanently undeliverable messages.  They only keep in the short period send queue (I don't know exactly how much time but some Apple tech sites indicate no more than 10 days to two weeks) until they are purged.  That's pretty standard as otherwise, large volume, messaging services would be sitting on tera-bytes of messages not delivered each month.

  You actually have to change my phone number?  If not, let alone sign and only in iMessage when you have the new phone with this set of numbers upward to the service.

• Unable to ssh on alternative port

  Mini Mac OS X Server 10.11.6, CommuniGate Pro, no and almost no other stock OS X Server services.

  The server owner recently found on a network that has blocked ports for VPN and SSH connections, so we try to set up the server to allow a SSH tunnel through SOCKS proxy port 443, which is almost always open. (We have no plans on execution of web services via this port on this area.)

  Research indicates that this should be a two-step process: 1) Edit /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf to remove the web listening on ports 80 and 443 ports; (2) edit/etc/ssh/ssh_config for add a SSH listener on port 443. then restart.

  After that, HTTP services are off on 80 and 443, but I can't connect to SSH on port 443. Works very well over 22 yet. Nmapping the server indicates that there is nothing open on port 443. Is there anything else I need to do for this open?

  A user on the stack Exchange responded to this question. Works a charm.

  http://Apple.StackExchange.com/questions/253332/unable-to-SSH-to-OS-x-server-Ove r-replacement-port

• y screen is broken and I don't see how can I unlock my phoneme of display

  1. on IPhone 5 s screen is broken how can I unlock my phone to inport my photos

  Too late now, you need fix the screen first.

• SSH permissions

  I know that this has been done, but I can't find here or elsewhere.

  I just reinstalled my SSH protocols after replacing a hard drive on the server and (data only) restore from a Time Machine backup. I seemed to have to start the SSH process from scratch.

  I'm from the procedure (which I learned here) ctlow.ca/SSH-VPN_MacOSX.html.

  It worked, but when I connect from the client, it just goes through without asking for password. I think that he asked a password the first time, the password private key (?), but he used to ask for it (in a small text box, echo) every time and then the password (?) server in the Terminal itself, not taken over.

  Now, none of those happening.

  So, I found some notes I had made about it and reset the permissions as 700 .ssh folder and files inside like 600, on the server and the client.

  It ends up looking like this:

  ClientComputer: ~ ClientID$ ls - ael .ssh

  Total 24

  drwx - 5 personal ClientID 170 11 Sep 15:24.

  drwxr-x-wx + 24 personal ClientID 816 13 Sep 08:26...

  0: Group: everyone deny delete

  -rw-@ 1 personal ClientID 32 10 February 2012 config

  -rw - 1 1766 11 Sep 15:11 id_rsa personal ClientID

  -rw - 1 818 11 Sep 15:33 known_hosts personal ClientID

  ====

  ServerComputer: ~ ServerID$ ls - ael .ssh

  Total 16

  drwx - 4 personal ServerID 136 11 Sep 15:28.

  drwxr-xr-x @ 25 personal ServerID 850 11 Sep 15:30...

  0: Group: everyone deny delete

  -rw - 1 416 11 Sep 15:28 authorized_keys personal ServerID

  -rw - 1 391 11 Sep 15:26 known_hosts personal ServerID

  I don't think I'm particularly threatened, but I was happy to have to use two passwords to log into the SSH tunnel. No idea why I wonder no password now? (I did specify a passphrase when generating the key.)

  Thank you.

  Charles

  P.S. The customer running 10.9, 10.11 server.

  P.P.S. For the client-user info window showed "shared folder" which I don't know how it got that way and have unchecked the box. I doubt if that is related to my question.

  Hello Charles,

  I'm not sure what you were doing before, but it seems OK now.

  Most of the internet uses the same set of instructions that tell people not to use a password for the private key. It's a hassle to the running ssh-agent and most people struggle enough as it is with ssh. But on OS X, keychain using ssh-agent. Thus, when you provide a password for your private key, the first time you go, you will be asked (via a beautiful Aqua GUI) your password. You can expect that and save it in the keychain, hence, you will never be asked again. Then, if the rest of your ssh stuff is correct, it will pass all by as you describe. It sounds like what is happening now, and that's how it should work.

  If I were to speculate, I think that maybe before you run a custom build of ssh and ssh-agent command line version. This would explain the double Terminal passwords can be made echo and the other not.

• Tie broken in iOS 10?

  Hello

  I just upgraded to iOS 10. When you connect AP mobile using bluetooth, the connection works OK, but fell after a few seconds when the iPhone screen goes into sleep mode.

  WiFi Hotspot seems to work, but I can't connect to my VPN from my laptop. Then my cell phone connection failed attempts to verify my credentials.

  I have another iPhone that always works 9 and all iOS works without problems. I also tried to use different carriers that had no effect at all.

  It seems that Mobile Hotspot is severely broken in iOS 10. Can anyone confirm this or make suggestions how to fix it? I'm really desperate here.

  Thank you.

  Hi persistent presence!

  I see that you are having problems using Personal Hotspot from your iPhone after updating to iOS 10.  I know it's important to have Personal Hotspot works correctly, and I'm happy to offer assistance.  Please try all relevant measures of this article, there is a section which specifically addresses the Bluetooth connections:

  Get help with Personal Hotspot in iOS

  Thank you for using communities of Apple Support.

  See you soon!

• 10 broken iOS Update-home button

  I just did the update ios10 and my home button has been broken for 2 years. His complete the update but its stuck on a white screen saying "press home to upgrade".» I am unable to do this command and I can't seem to restore on my back up to iTunes... Help please!

  Hi kaylabon87,

  If your Home button does not work on your iPhone and you are unable to update or restore your device, the resource below provides a link to contact AppleCare support.

  If you are unable to update or restore your iPhone, iPad or iPod touch
  
  

  Contact the Apple Support if you are unable to update or restore your device with the recovery mode, or you can use the mode of recovery because of the broken or stuck buttons.

  Last modified: Sep 15, 2016

  Take care.