upgrade to 1.5

[beemoon]

Hello,
after upgrading to console version 1.5, I can no longer see my workstations. The server update seems to be OK. Everything appears to be working except that my workstations are no longer visible, preventing me from deploying the new agent.
I followed the procedure step by step; could I have missed something?

[sfonteneau]

viewtopic.php?f=9&t=886

Without even knowing if you're using Windows or Linux, it's going to be difficult to help you...

[beemoon]

Sorry,

Linux Debian 9 server
, console on Windows 10 Pro,
Windows 7 Pro clients with agent 1.3

on server.
WAPT Server version: 1.5.1.16,
WAPT Agent version: 1.5.1.16,
WAPT Setup version: 1.5.1.16,
WAPT Deploy version: 1.5.1.16,

console version: 1.5.1.16

[beemoon]

By manually installing the new agent on a client machine (which doesn't report back), it reappears in the console.
Is the old agent not communicating with the new server?

[sfonteneau]

By manually installing the new agent on a client machine (which doesn't report back), it reappears in the console.
Is the old agent not communicating with the new server?

No, indeed, the new agent needs to be version 1.5

Normally when you launch postconf under Linux, you launch the migration of the MongoDB database.

I'm doing some more internal testing.

[beemoon]

I re-ran the command

sudo -u wapt python /opt/wapt/waptserver/waptserver_upgrade.py upgrade2postgres

and here is the result

dumping mongodb data
2018-01-24T15:59:36.855+0100 I NETWORK [initandlisten] connection accepted from 127.0.0.1:41962 #1 (1 connection now open)
2018-01-24T15:59:36.856+0100 Failed: Invalid database name: '/var/lib/mongodb/'
Traceback (most recent call last):
File "/opt/wapt/waptserver/waptserver_upgrade.py", line 200, in
upgrade2postgres()
File "/opt/wapt/waptserver/waptserver_upgrade.py", line 158, in upgrade2postgres
jsondata = create_import_data()
File "/opt/wapt/waptserver/waptserver_upgrade.py", line 77, in create_import_data
data = subprocess.check_output('mongoexport -d wapt -c hosts --jsonArray --db=%s' % mongo_datadir,shell=True)
File "/usr/lib/python2.7/subprocess.py", line 219, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command 'mongoexport -d wapt -c hosts --jsonArray --db=/var/lib/mongodb/' returned non-zero exit status 1
2018-01-24T15:59:36.862+0100 I NETWORK [conn1] end connection 127.0.0.1:41962 (0 connections now open)

[beemoon]

Ah, I changed --dbpath to --db because it was causing an error

[beemoon]

Finally, I removed the `--dbpath` and its parameter because when I run `mongoexport --help`, the option doesn't exist.
The command
`/usr/bin/python /opt/wapt/waptserver/scripts/postconf.py`

runs without errors.

But still no machines in the console!

Since it's a beta/RC... I'm going to redeploy my agents.

[beemoon]

Yes, I found it!!!!

It's the script /opt/wapt/waptserver/waptserver_upgrade.py that's buggy for Linux.

Here's what I changed:

+ data = subprocess.check_output('mongoexport -d wapt -c hosts --jsonArray ',shell=True)^M
- data = subprocess.check_output('mongoexport -d wapt -c hosts --jsonArray --dbpath=%s' %

+ jsondata = json.loads(data)^M
- jsondata = json.load()^M

Now the command
sudo -u wapt python /opt/wapt/waptserver/waptserver_upgrade.py upgrade2postgres/opt/wapt/waptserver/waptserver_up

no longer gives an error and correctly displays the exports; the PCs are back in the console.