Rudder

In fact the date is missing from fusion inventory. I think

"Bad format" is displayed when there is nothing to show...

We need at least to correct and display nothing...

We may also look into fusion how to display processes startdate from aix.

In fact, start date is not present for all processes:

If the start date is missing => the webapp will display "bad format" => behavior when no info

If the start date is present, the format used to parse it is "yyyy-MM-DD HH:mm" but those values contains the seconds : 2014-03-31 19:11:16. hence the format will not be accepted and will have no value stored in Rudder inventory ( giving "bad format" )

process with missing start dates comes from a ps command.
Those with a start date comes from other parts...

In fact, in fusion 2.2: ps aux is used to get all processes

those older than 24h hours have not their start date parsed (format is like Feb 20, not accepted by fusion)
the others are parsed (format is hh:mm:ss which is parsed correctly)

Fusion 2.3.X seems to contain a bug that fails to output any process at all, it seems the _getProcessesOther function has a faulty matching that fails to correctly parse AIX ps.

Using:

       next unless $line =~
            /^ \s*
            (\S+) \s+
            (\S+) \s+
            (\S+) \s+
            (\S+) \s+
            (\S+) \s+
            (\S+) \s+
            (\S+\s?\S+) \s+
             \S+ \s+
            (.*\S)
            /x;

Seems to do the trick, but Linux support has not been tested yet.

Bug fixed and PR'ed to fusion.

I will commit it in Rudder as soon as we will have an updated Fusion version. => #4594

Fusion PR is here: https://github.com/fusinv/fusioninventory-agent/pull/16

PR opened in Fusion repository + Ticket => https://github.com/fusinv/fusioninventory-agent/pull/17

Applied in changeset packages:commit:6adf79416566141a8e78cbc36ba9b47e6aed920b.