LSAgent & CentOS 7 -Version check & software inventory

[Knut]

Hello,

We are currently deploying LSAgent v 10.2.0.0 (latest Linux version) on our CentOs boxes.

In the agent log we can see the following line:

2022-09-16 05:51:23,334 [INFO ] : Checking version. Latest Version: 7.0.20.1. Current Version: 10.2.0.0

Is that a known bug ? Will it be fixed in the next version ?

Also, a more problematic issue is that the agent does not pick up installed software on our CentOS7 assets:

Here is the full agent log:

[root@m2c1n1 LansweeperAgent]# ./LSAgent
2022-09-16 08:10:02,657 [INFO ] : Program is Running
2022-09-16 08:10:02,763 [INFO ] : Reading ini file.
2022-09-16 08:10:02,845 [INFO ] : Getting asset id
2022-09-16 08:10:02,846 [INFO ] : Existing asset id found: <REDACTED>
2022-09-16 08:10:02,847 [INFO ] : Creating communication channel
2022-09-16 08:10:02,850 [INFO ] : CreateReachableEndPoint for <REDACTED>
2022-09-16 08:10:02,949 [INFO ] : Url Check with address failed. Endpoint with address '<REDACTED>' was not reachable: Name or service not known (<REDACTED>:9524)
2022-09-16 08:10:02,951 [INFO ] : Connection to url <REDACTED>:9524/lsagent failed
2022-09-16 08:10:03,113 [INFO ] : Creating InternalCommunicationSender to URL <REDACTED>:9524/lsagent 
2022-09-16 08:10:03,117 [INFO ] : Getting asset status from the server
2022-09-16 08:10:03,172 [INFO ] : Asset is enabled
2022-09-16 08:10:03,172 [INFO ] : Retrieving configuration
2022-09-16 08:10:03,172 [INFO ] : Getting configuration from the server
2022-09-16 08:10:03,203 [INFO ] : Updating local config
2022-09-16 08:10:03,206 [INFO ] : Checking version. Latest Version: 7.0.20.1. Current Version: 10.2.0.0
2022-09-16 08:10:03,207 [INFO ] : Waiting for schedule...
2022-09-16 08:10:03,207 [INFO ] : Schedule triggered
2022-09-16 08:10:03,207 [INFO ] : Starting scan
2022-09-16 08:10:03,217 [INFO ] : Scanning computer...
lsblk: invalid option -- 'J'

Usage:
 lsblk [options] [<device> ...]

Options:
 -a, --all            print all devices
 -b, --bytes          print SIZE in bytes rather than in human readable format
 -d, --nodeps         don't print slaves or holders
 -D, --discard        print discard capabilities
 -e, --exclude <list> exclude devices by major number (default: RAM disks)
 -I, --include <list> show only devices with specified major numbers
 -f, --fs             output info about filesystems
 -h, --help           usage information (this)
 -i, --ascii          use ascii characters only
 -m, --perms          output info about permissions
 -l, --list           use list format output
 -n, --noheadings     don't print headings
 -o, --output <list>  output columns
 -p, --paths          print complate device path
 -P, --pairs          use key="value" output format
 -r, --raw            use raw output format
 -s, --inverse        inverse dependencies
 -t, --topology       output info about topology
 -S, --scsi           output info about SCSI devices

 -h, --help     display this help and exit
 -V, --version  output version information and exit

Available columns (for --output):
        NAME  device name
       KNAME  internal kernel device name
     MAJ:MIN  major:minor device number
      FSTYPE  filesystem type
  MOUNTPOINT  where the device is mounted
       LABEL  filesystem LABEL
        UUID  filesystem UUID
   PARTLABEL  partition LABEL
    PARTUUID  partition UUID
          RA  read-ahead of the device
          RO  read-only device
          RM  removable device
       MODEL  device identifier
      SERIAL  disk serial number
        SIZE  size of the device
       STATE  state of the device
       OWNER  user name
       GROUP  group name
        MODE  device node permissions
   ALIGNMENT  alignment offset
      MIN-IO  minimum I/O size
      OPT-IO  optimal I/O size
     PHY-SEC  physical sector size
     LOG-SEC  logical sector size
        ROTA  rotational device
       SCHED  I/O scheduler name
     RQ-SIZE  request queue size
        TYPE  device type
    DISC-ALN  discard alignment offset
   DISC-GRAN  discard granularity
    DISC-MAX  discard max bytes
   DISC-ZERO  discard zeroes data
       WSAME  write same max bytes
         WWN  unique storage identifier
        RAND  adds randomness
      PKNAME  internal parent kernel device name
        HCTL  Host:Channel:Target:Lun for SCSI
        TRAN  device transport type
         REV  device revision
      VENDOR  device vendor

For more details see lsblk(8).
cat: /etc/*version: No such file or directory
/bin/bash: prtconf: command not found
/bin/bash: /usr/sbin/prtconf: No such file or directory
/bin/bash: dpkg-query: command not found
/bin/bash: dpkg: command not found
/bin/bash: flatpak: command not found
/bin/bash: snap: command not found
ls: cannot access <REDACTED>/lib/*/: No such file or directory
ls: cannot access <REDACTED>/sbin/*/: No such file or directory
ls: cannot access /opt/collectd/plugins/*/: No such file or directory
ls: cannot access /opt/LansweeperAgent/*/: No such file or directory
2022-09-16 08:10:11,750 [INFO ] : Computer scan completed
2022-09-16 08:10:11,751 [INFO ] : Serializing ScanResult
2022-09-16 08:10:12,034 [INFO ] : Compressing scan file
2022-09-16 08:10:12,053 [INFO ] : Sending scan
2022-09-16 08:10:12,740 [INFO ] : Scan has been sent
2022-09-16 08:10:12,741 [INFO ] : Saving ini settings
2022-09-16 08:10:12,746 [INFO ] : Creating ini backup.
2022-09-16 08:10:12,746 [INFO ] : Waiting 4 hours until next iteration

The command

rpm -qa

does work when run interactively. Why doesn't the agent pick that up ?

Thanks!

[Knut]

Just a quick head up on this for future readers:

- This is actually a bug that is being investigated by L3 support

[Knut · Accepted solution]

Final update: the fix has been labeled as "LAN-13782" and will soon be merged into lansweeper. Check the changelogs of upcoming versions to see if it has been included in the release.

[lbrown79au]

Can lansweeper provide more than "Check the changelogs of upcoming versions to see if it has been included in the release."? Would be good to have an official ETA.

As we can see from the dates the proposed solution was back in October 22. Four months later after checking every new release changelog for "LAN-13782" it still is yet to be implemented.

Have raised numerous support calls and done testing but still not fixed.

Sorry for coming across grumpy but quite frustrated as we are a large linux shop and not being able to get software reports for months is pretty poor.

[Obi_1_Cinobi]

Hello there!

We have increased the priority on this bug, but as no root cause has been identified yet, we cannot provide you with an ETA at this time. We thank you for understanding.

[Obi_1_Cinobi]

Hello there!

Would it be possible to send us an email at support@lansweeper.com so we can look into this?

[Knut]

Hello @Obi_1_Cinobi 

Thanks for you reply.

I just sent the email.

Regards

[RolandB]

I read with the server version 10.2.4.0  should it be solved.

• Fixed: LAN-13402 Older CentOS and Red Hat Enterprise Linux are not properly recognized as operating systems when performing a Linux scan.

[Knut]

Hello @RolandB 

Thanks for trying to help.

The server is already on version 10.2.4.0 & the assets are recognized as CentOS 7 boxes (which is correct) so I assume there is another bug somewhere.

Cheers,