Run the device configuration wizard If neither works, then you may have a hardware problem. Scan still works though and shows two drives and the library: I'd take 2 steps before panicking, assuming that nothing else has changed in your environment. #CANNOT CONNECT TO ROBOTIC SOFTWARE DAEMON 42 WINDOWS SOFTWARE#Tldd: TLD(1) unable to connect to tldcd on Net-Backup: cannot connect to robotic software daemon (42) tldd: TLD(1) unavailable: initialization failed: Control daemon connect. #CANNOT CONNECT TO ROBOTIC SOFTWARE DAEMON 42 WINDOWS WINDOWS#Library is an StorageTek L180 with 6 drives.Ĭannot Connect To Robotic Software Daemon 42 Windows Live Hotmail Shahani’s inquiries, I had the “conversation” below with the version of Eugene Goostman available at http: //default- environment. Version is NBU 5.1MP6 so we can't call support. I don't know if this is a hardware issue or a software issue. Drive index 2 is incorrect, drive name /dev/st/nh2c0t0l1 is incorrect, No such file or directory Cannot terminate tldcd: cannot connect to robotic software daemon (42) Since yesterday NBU has suddenly lost its ability to talk to the robot. Where does this leave me? On 10:47 AM, Ed Wilts wrote: On Tue, at 10:39 AM, Nate Sanders (sandersn )> wrote: > root office-backup:/usr/openv/netbackup$ netbackup start Rebuilding device nodes. Using robtest I AM able to connect to TLD(1) and pull drive info, but not TLD(0). Bpps -a doesn't show any tld processes running. I tried adding a new robot as TLD(1) in the GUI but inventory fails with 'cannot connect to robotic software daemon (42)'. Cannot connect to the Docker daemon at tcp://localhost:2375. GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together. X86_64 Oracle Linux 5.6 running Netbackup 7.1 with mhvtl. Here is what I am running right now thanks to Marks help. On a Windows server, two areas to check are in Windows Device Manager and the Tape Driver. #CANNOT CONNECT TO ROBOTIC SOFTWARE DAEMON 42 WINDOWS CODE#In general, NetBackup Status Code 277 appears when device changes are made in NetBackup and either the services are not cycled, or the server is not rebooted. Still can't talk to the library with vmchange -robot_info or through the GUI. Did a reboot of the library, scsi-fiber bridge and the host. Library is an StorageTek L180 with 6 drives. NetBackup request daemon started.ĭrive index 2 is incorrect, drive name /dev/st/nh2c0t0l1 is incorrect, No such file or directory Cannot terminate tldcd: cannot connect to robotic software daemon (42) Since yesterday NBU has suddenly lost its ability to talk to the robot. On 10:39 AM, Nate Sanders wrote: root office-backup:/usr/openv/netbackup$ netbackup start Rebuilding device nodes. Going to try a library and scsi-bridge reboot. While NBU can see the two tape drives, the robot its self has vanished. Upon writing/reading my own email it makes sense now that the path didn't change, it's simply not there. Root office-backup:/usr/openv/netbackup$ netbackup start Rebuilding device nodes. It used to connect to the same Wifi SSID without any hassle a few days ago. But it doesn't connect automatically after reboot. If I connect to the robot using a lan cable and then selects that specific wireless SSID listed on NAO's webpage, it'll connect fine. The Wi-Fi is listed in Network Section on NAO's webpage. I need to get this robot online on that specific network. The problem I am facing is that it doesn't automatically connect to one specific Wi-Fi hotspot in my lab. It is running OpenNAO OS Version 2.1.4.13. I am using NAO robot for my Masters Thesis.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |