In Tivoli storage manager server 7.1.14 and tape device LTO7 giving an error.
Waiting for mount point in device class in manual library.
Related
I am trying to mount a drive on my local on-premises Windows 10 pro machine (SMB 3.0).
I setup my Vnet in Azure, my Vnet gateway (P2S VPN) and shared file storage account.
The usual way to mount the drive is to use the NET USE commnand such as :
net use [drive letter] \\xxx.file.core.windows.net\fileshare /u:user [Password key]
If I run the NET USE command on a VM it mounts the drive instantly without a problem.
However, running the command from the on-premises Windows 10 pro machine I get the System error 53 has occurred error message.
I know that this error is often due to the fact that the ISP blocks port 445. However, my understanding is that this should not be a problem if I setup and use the P2S VPN. Doesn't the VPN bypass the ISP restrictions ?
I have tested the VPN and connectivity is confirmed.
I've also turned off all firewalls (PC and router) while trying to do this.
When the VPN is connected I try to ping the public IP address of the Vnet but this times out. I have read that Azure does block these ICMP pings.
I have also tried a tracert to my xxx.file.core.windows.net and it does timeout after 5 hops.
Am I trying to do something that cannot be done ?
In Azure, we can't use P2S VPN mount file share to your local PC. Because file share service work on the Internet, and we can't force the file share network traffic through P2S/S2S vpn.
As a workaround, we can deploy a RRAS VPN on Azure VM, and use local PC to connect the RRAS server, after connected, the local PC will get an IP from Azure datacenter, so we can mount file share on you local PC.
Here a blog about how to deploy RRAS on azure VM, please refer to it.
I am trying to learn basics of blockchain by trying the multichain platform, I have been following multichain guide to make a private blockchain, I am using two instances of EC2, I managed to create a blockchain using my first instance :
>multichaind secondChain -daemon
MultiChain Core Daemon build 1.0 alpha 27 protocol 10007
MultiChain server starting
Looking for genesis block...
Genesis block found
Other nodes can connect to this node using:
multichaind secondChain#XXX.XX.X.XX:XXXX
Node started
However, when I try to connect to the blockchain using a second instance of EC2, I am getting rejected :
>multichaind secondChain#XXX.XX.X.XX:XXXX
MultiChain Core Daemon build 1.0 alpha 27 protocol 10007
Retrieving blockchain parameters from the seed node XXX.XX.X.XX:XXXX ...
Error: Couldn't connect to the seed node XXX.XX.X.XX on port XXXX - please check multichaind is running at that address and that your firewall settings allow incoming connections.
Which is kind of expected, as I need to grant connect rights to that machine. However, It should return me a wallet address so I can grant the connection rights.
I think this is related to EC2 settings that are probably not allowing me to connect. I have few knowledge of EC2 and networks in general. I can't figure this out.
Have you checked if the access to the port is granted on the instance you're trying to connect?
If multichaind says "please check multichaind is running at that address and that your firewall settings allow incoming connection"
It is usually one or the other. Port and Running already.
Since you havent yet granted, its probably port.
I started the Cloudera manager successfully but while trying to see the list of files it throws error related to namenode. After that I checked the namenode is started or not , but it says
Unable to connect
Firefox can't establish a connection to the server at quickstart.cloudera:50070.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection. If your computer or network is protected by a firewall
or proxy, make sure that Firefox is permitted to access the Web.
How can I resolve this?
I added a bad script in startup script, turned out this script is blocking and hence ubuntu instance can't boot up to ssh server and I can't ssh into it. Is there a way for me to go to the server console (like from VGA port)? like go to single-user mode or safe mode and fix it?
Thanks in advance.
I don't know of any way to obtain server console access or change boot modes on the EC2 instances...
I had the same issue sometime ago, and I ended up creating a temporary EC2 instance, mounting the root device from the original (failing) EC2 there, modifying the files, then reattaching the device and destroying the temporary instance. Note: you may end up paying more depending on which instance type you launch.
I am using Amazon EC2 services & and its working correctly but suddenly from 3-days before when we try to access our instance using ssh connection we got following error:
"ssh: connect to host ec2----***.compute-1.amazonaws.com port **: Connection timed out"
when I try to access our sites deployed on our EC2 instance, I received the same error ,
"The connection has timed out
The server at ec2----***.compute-1.amazonaws.com is taking too long to respond"
there is no problem in network connection from our side as we are able to access other web site and services smoothly.
I can't even able to access hosted site without this.
I encountered the same problem.
I followed the troubleshooting in http://alestic.com/2010/05/ec2-move-ebs-boot-instance
Then when I tried to start a new instance, I got an message from Amazon:
Server.InsufficientInstanceCapacity: We currently do not have sufficient m1.small capacity in the Availability Zone you requested (us-east-1b). Our system will be working on provisioning additional capacity. You can currently get m1.small capacity by not specifying an Availability Zone in your request or choosing us-east-1d, us-east-1c, us-east-1a.
Maybe, you have an instance is us-east-1b, too.
You can try to access the System Console (either via the amazon web console or elasticfox) and check for any errors/messages that might help you arrive at the cause of this.
In ~/.ssh/config, add the following lines:
ServerAliveInterval 50
This will keep on pinging the server every 50 seconds to keep the connection alive.