aerror with wazuh-api install

[Kat]

Anyone seen this one before?

Setting up wazuh-api (3.5.0-1) ...

==============================================================================================================

= Don’t forget to secure the API configuration by running the script /var/ossec/api/scripts/configure_api.sh =

==============================================================================================================

cp: cannot stat '/tmp/wazuh-api/api/configuration/auth/user': No such file or directory

dpkg: error processing package wazuh-api (--configure):

 subprocess installed post-installation script returned error exit status 1

Processing triggers for systemd (229-4ubuntu21.4) ...

Processing triggers for ureadahead (0.100.0-19) ...

Errors were encountered while processing:

 wazuh-api

E: Sub-process /usr/bin/dpkg returned an error code (1)

Can't find anything in the logs, and :

# ll /tmp/wazuh-api/api/configuration/

total 16

drwxr-x--- 3 root ossec 4096 Aug 19 23:22 ./

drwxr-x--- 3 root ossec 4096 Aug 19 23:22 ../

-rwxr-xr-x 1 root root  3007 Aug 19 23:37 config.js.debnew*

drwxr-x--- 2 root root  4096 Aug 17 18:26 ssl/

so I am not sure what it is looking for. I will go look at github source I guess and see what it is looking for, but thought I would toss it out here at the same time, just in case.

Kat

[Kat]

Although it refused to clean up - I was able to fix it with: 

apt-get install -f wazuh-api

Still not sure what was causing it at this point - will do some more debugging.

[jesus.g...@wazuh.com]

Hi Kat,

Thanks for your advice. Please could you give us information about the OS where you were trying to run, also the steps followed to reproduce it?

Regards,

Jesús

[Kat]

Ubuntu 16 - current patch level. (In AWS)

Just went through standard install and it came up. Because it was AWS I did not want to start fresh OS since I would have to create new instance and get new IP, but this was odd indeed - never saw it before, but the fix was simple enough to force it.  No other steps other than standard Manager install using DEB packages.

Kat

On Sunday, August 19, 2018 at 6:42:03 PM UTC-5, Kat wrote:

[jesus.g...@wazuh.com]

Ok Kat, 

Thanks in advance. The -f flag is used to fix broken dependencies. The team will review this issue, I'll copy you here once I have light over this.

Regards,

Jesús

[Kat]

My bad - yeah, I was confusing with yum/rpm - forgot this was apt

On Sunday, August 19, 2018 at 6:42:03 PM UTC-5, Kat wrote:

[jesus.g...@wazuh.com]

Hello again Kat, 

After discussing about it with the CI/CD team, they concluded you have a "dirty" machine plus a package bug. The installer 

thinks you are doing an upgrade because it founds some directories under /tmp then it applies some code lines in the wrong way ending 

in the error you reported.

So this is a bug with the packages and the team is currently working to fix it. Thanks for your feedback.

Regards,

Jesús