cdm: Failed to get FsUsage

[MADANRAJ SIVAGNANAM]

cdm: Failed to get FsUsage  is the error we are getting for a robot and so for cdm probe port is not taken . Please let me know the resolution .



Regards
AMar

[Gene Howard]

Hi we will need more information.
What is the OS type and version?
what is the controller version?
what is the CDM probe version?
if you run the cdm probe from the command line what type of error message do you get?

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[BST IntoIT]

Hi Gene,

I am facing the same issue.

OS type : Unix, Linux 3.10.0 - 1062.9.1 el7.x86_64
Controller Version: 9.20 [Build 9.20.1072, aug 8 2019]
CDM probe version: 6.42-MC
No, I am not running the CDM probe from the command line.

Error I received:
Feb 13 13:49:01:399 [139799423985472] cdm: calling syssyat
Feb 13 13:49:01:452 [139799423985472] cdm: Failed to get FsUsage for /mnt

Regards
Ntsako 

[Gregg Stillwell]

The other File Systems should be working fine..correct. /mnt is typically a temporary FS for out side devices or servers. Is there a FS mount on /mnt? You can run the mount command or just run df and ee if you see it. Then check the /etc/fstab file or vfstab depending on flavor.

[Gene Howard]

is your issue that the CDM probe is not starting so it never gets a port or a pid or just that you get this error?
These would be two different issues.

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[BST IntoIT]

Hi Gene,

Sorry I was not clear.

My issue is that the CDM probe doesn't start and it shows those errors.

We never had the Linux favor in our Environment we are using this server to test.
And when I deploy the probe but it shouldn't start, and see below for logs. It seems it does pickup port and PID but loses it again.




Log start
-----------------------------------------------------------------------------------------------------

Feb 13 13:49:01:399 [139799423985472] cdm: calling syssyat
Feb 13 13:49:01:452 [139799423985472] cdm: Failed to get FsUsage for /mnt
Feb 13 23:00:01:504 [139799423985472] cdm: Failed to get FsUsage for /test2
Feb 13 23:00:01:572 [139799423985472] cdm: ****************[ Starting ]****************
Feb 13 23:00:01:572 [139799423985472] cdm: cdm 6.42
Feb 13 23:00:01:572 [139799423985472] cdm: Nimsoft Corporation
Feb 13 23:00:01:574 [139799423985472] cdm: port=48008 PID=19394
Feb 13 23:00:02:582 [139799423985472] cdm: Failed to get FsUsage for /mnt
Feb 13 23:01:32:584 [139799423985472] cdm: Failed to get FsUsage for /test2
Feb 13 23:15:02:112 [139799423985472] cdm: Failed to get FsUsage for /mnt
Feb 13 23:30:27:348 [139799423985472] cdm: Failed to get FsUsage for /test2
Feb 13 23:30:28:351 [139799423985472] cdm: Failed to get FsUsage for /mnt
Feb 13 23:31:57:581 [139799423985472] cdm: Failed to get FsUsage for /test2
Feb 13 23:31:57:582 [139799423985472] cdm: Failed to get FsUsage for /run/user/2002
Feb 13 23:32:03:450 [140117359241024] cdm: calling syssyat
Feb 13 23:32:03:464 [140117359241024] cdm: Failed to get FsUsage for /mnt
Feb 14 00:05:16:493 [140117359241024] cdm: Failed to get FsUsage for /test2
Feb 14 00:05:16:504 [140117359241024] cdm: ****************[ Starting ]****************
Feb 14 00:05:16:504 [140117359241024] cdm: cdm 6.42
Feb 14 00:05:16:504 [140117359241024] cdm: Nimsoft Corporation
Feb 14 00:05:16:506 [140117359241024] cdm: port=48008 PID=29617
Feb 14 00:05:17:515 [140117359241024] cdm: Failed to get FsUsage for /mnt
Feb 14 00:06:47:591 [140117359241024] cdm: Failed to get FsUsage for /test2
Feb 14 00:06:47:591 [140117359241024] cdm: Failed to get FsUsage for /run/user/2002
Feb 14 00:20:17:939 [140117359241024] cdm: Failed to get FsUsage for /mnt
Feb 14 00:39:17:878 [140650684909376] cdm: calling syssyat
Feb 14 00:39:17:901 [140650684909376] cdm: Failed to get FsUsage for /mnt

-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Log end


Regards

Ntsako

[Gregg Stillwell]

Still no Linux version, but if the probe does not start the "Failed to get FsUsage" is not the problem. I would verify you are using the latest robot version. A

[BST IntoIT]

Hi Gregg,

Yes, I am using the latest version so the probe.

And about the OS version, I have attached the picture of the controller probe status:
 System type = unix
System = Linux
System Linux 3.10.0-1062.9.1el7.x86_64

cdm probe version is : cdm 6.42

Regards

Ntsako

[Gregg Stillwell]

Strange looks like CentOS 7. does the cdm probe eventually turn red in IM? Maybe turn your cdm debug higher. maybe check controller log and the systems /etc/log/messages or /var/log/messages, depending on what CentOS calls it, during cdm start. Also maybe run a df and see what type of FS are the ones complaining. Maybe remove unused entries from the /etc/fstab or equivalent file for CentOS. Don't know of the top of my head for that flavor. Also maybe delete cdm probe as well as directory in the probes directory and redeploy. Maybe even try a earlier version. If CentOS 7, you should be able to drop versions.

[BST IntoIT]

Hi Gregg,

Thank you very much for your help the CDM probe has started now.

I am using the earlier version of the CDM probe.

What was happing was the CDM was not starting and I was using the latest version and on top of all it was not turn red it kept on changing the PID number but doesn't obtain the port number.


Regards
Ntsako

[Alex Marques]

Hi BST IntolT


You were successful in solving this door problem because I am having the same problem

Att
Alex Marques

[Gregg Stillwell]

I think he used an older cdm. So first verify you are using the most current 6.50-MC and if that does not work try 6.30-MC or older then 6.42-MC.

[Alex Marques]

Hi Gregg 

In my case, it didn't work

Can you tell me if this linux kernel is supported

Robot controller 9.20 [Build 9.20.1072, August 8, 2019] started
OS = UNIX / Linux / Linux 3.10.0-1127.10.1.el7.x86_64

Because only in this version of the kenel that does not run

Cdm probe log

Jun 24 16:22:22:865 [140276018808640] cdm: ****************[ Starting ]****************
Jun 24 16:22:22:865 [140276018808640] cdm: cdm 6.30
Jun 24 16:22:22:865 [140276018808640] cdm: Nimsoft Corporation
Jun 24 16:22:22:865 [140276018808640] cdm: nimSessionServer - port = 0
Jun 24 16:22:22:971 [140276018808640] cdm: sockCheckLocalPort - close 4
Jun 24 16:22:22:977 [140276018808640] cdm: sockCheckLocalPort - close 4
Jun 24 16:22:22:983 [140276018808640] cdm: sockCheckLocalPort - close 4
Jun 24 16:22:22:989 [140276018808640] cdm: sockCheckLocalPort - close 4
Jun 24 16:22:22:999 [140276018808640] cdm: sockCheckLocalPort - close 4
Jun 24 16:22:24:463 [140615210161984] cdm: SREQUEST: post ->127.0.0.1/48001
Jun 24 16:22:24:468 [140615210161984] cdm: RREPLY: status=invalid argument(3) <-127.0.0.1/48001 h=37 d=0
Jun 24 16:22:24:468 [140615210161984] cdm: nimSessionPostMessage: received status not ok :3(invalid argument)
Jun 24 16:22:24:468 [140615210161984] cdm: SREQUEST: _close ->127.0.0.1/48001

[Gregg Stillwell]

127.0.0.1??? You may have configuration issue check your GetHostByName. do an ifconfig and verify IP address add a /etc/hosts entry correct with IP and hostname and verify robotip entry in robot.cfg.

Here is the robot matrix for compatibility. What robot version are you running?

[Alex Marques]

guys good morning

I mainly want to thank Gregg

After your help was configured in / etc / hosts and it was necessary to redo the installation of the robot and to actually work, it was necessary to restart the machine.

Att

[BST IntoIT]

Hi Alex,

No We didn't the system administrator ended up giving up, and installed the robot because there was others which worked and it was that one which was having problem. He refused to carry on the investigation.

But I once tried to the older version and it work for sometime and then stop work, you can try that.

Regards

Ntsako