search

CESNET / pakiti-server

Pakiti provides a monitoring mechanism to check the patching status of Linux systems.
BSD 2-Clause "Simplified" License
49 stars 35 forks source link

Tag functionality of pakiti3 client #143

Open bluikko opened 6 years ago

bluikko commented 6 years ago

I could not find any way to group/filter the hosts in the web UI by the pakiti-client parameter --tag. Does this parameter actually do something on the server side? Is the functionality just not done on the server yet? Is it totally deprecated?

Issue #80 talks about pakiti2 client "tag" functionality but this functionality exists in pakiti3 client as well.

Should we use the --site parameter instead of --tag in pakiti3 client as per #80 ?

It would be helpful if the man page (pakiti-client in this case) or some other documentation listed what functionality is expected to work.

kouril commented 6 years ago

The --site parameter should be used to specify the group name, indeed. Tag is there for legacy/compatibility purposes.

bluikko commented 6 years ago

So I should see those "sites" with the "Host groups" (groups.php) functionality in the web UI?

It did not seem to work but will check again.

kouril commented 6 years ago

On Mon, Jul 30, 2018 at 07:35:16AM -0700, bluikko wrote:

So I should see those "sites" with the "Host groups" (groups.php) functionality in the web UI?

yes, that's supposed to work.

bluikko commented 6 years ago

Under "Host groups" in the web UI, there is only one group: "N/A"

Even though some pakiti-clients are called with --site="xxx" and others with --site="yyy" (example).

kouril commented 6 years ago

On Thu, Aug 02, 2018 at 08:08:41AM -0700, bluikko wrote:

Under "Host groups" in the web UI, there is only one group: "N/A"

Even though some pakiti-clients are called with --site="xxx" and others with --site="yyy" (example).

that's strange. What do you use on the client and server sides (versions, configurations)?

bluikko commented 6 years ago
kouril commented 6 years ago

On Mon, Aug 06, 2018 at 11:18:01PM -0700, bluikko wrote:

  • Server version: master from May 22.
  • Client version: 3.0.1-1 from EPEL repository, seems to be from "Jun 08 2015" ...... perhaps too old?

could you please try the current code from pakiti-client? There's been some recent changes to the client code, which are supposed to be compatible (esp. in your scenario) but it's worth checking.

bluikko commented 6 years ago

Run pakiti-client from master of today. (as opposed of the package from EPEL)

Now I get a second copy of the same hostname (example host01.domain.tld) in the "Hosts" list of web UI. So the host is now listed 2 times, updates with the pakiti-client from master updates one of the copies, updates with the pakiti-client from EPEL updates the second of the copies.

And the new copy "HostGroups" value is also "N/A". So the group does not seem to work with client from today's master either; and now another problem with the unexpected second copy of the same host in the list.

By the way is there a way to set the time zone somewhere? All last report times are in GMT. I did not find it in the Config.php file with a few searches like "time" or "zone".

bluikko commented 6 years ago

The server is master from May 22.