Import problem

[aaarkhipov]

Installed 1.8.4 appliance and configured it. Now want to import XML (I have two XMLs - one was saved on 1.6.6, another one on 1.8.3, makes no difference).

As soon as XML contains references to vfs.* in any form - item, trigger, graph - the import hangs and in some time the screen goes to "Connection reset by peer". No error messages found in apache or zabbix logs on the appliance.

Cleaning up XML and removing all references to vfs.* helps but is it known bug?

Thanks,
Andrei.

[richlv]

can you attach a smallest xml that fails for you this way ? (ideally, single host with a single item)

[aaarkhipov]

Examples

Hello.

Here they are.

The first one - one_host_bad.xml - gives

Error 101 (net::ERR_CONNECTION_RESET): Unknown error.

The second one - one_host_good.xml - differs only in all mentions to vfs.* removed and imports without any problems.

The files are in .zip as the "bad" one does not go via forum upload window either in xml format. Weird, so, I have tested different browsers to exclude their influence - Chrome, IE8, Safary and FF 3.6 - all the same.

Regards,
Andrei.

[richlv]

your xml linked to Template_Linux, and it also had some graphs that referenced host "ams database" or such.
i deleted template reference and all graph information, and the "bad" xml imported just fine. even with the template reference in place it imported just fine as well.

[aaarkhipov]

Well, the thing is - "good" one also has references to Template_Linux. The configuration has template Template_Linux defined.

Anyway, the point is - export/import should help in moving configuration from, let's say, one place to another. In my case Export is OK, but the import ...

There are two options:

1. Import process gives some warning/error messages and imports whatever it can.

2. Documentation describes somewhere what should be and what should not be done to complete export/import.

In my case, import does not go at all - crashes Zabbix. Well, manually cleaning XML takes time but it works.

In any case, thanks for the answers!

Andrei.

[richlv]

Anyway, the point is - export/import should help in moving configuration from, let's say, one place to another. In my case Export is OK, but the import ...

of course. what i'm saying, i can't reproduce the problem here.
if it really can be made to do that, it highly likely is a bug and should be fixed.

[aaarkhipov]

To reproduce

Ah, I see. In my case it was simple:

I downloaded the latest appliance (1.8.4 VMDK)
Started VMWare virtual machine under VMware Server 2
Configured machine - ip address and access for my workstation
Logged in to ZABBIX

Import "bad" XML - voila!

Regards,
Andrei.

[richlv]

just to be sure, i grabbed 1.8.4 vm and tried to import that xml. it failed, as expected. trying to import it w/o graphs succeeded.

can you give exact steps you perform on a fresh vm to reproduce the problem ?

[aaarkhipov]

You just described exactly what I did:

- take appliance 1.8.4
- minimal re-configuration: ip address for the system (we use static IP for the servers) and allow access for the managing workstation
- login as Admin
- Import hosts

Failed.

What I did not try - leave all items intact and remove just graphs. On the other side, in the end import was successful including graphs, just not mentioning vfs.* anywhere in the file.

Andrei.

[richlv]

well, i just can't reproduce it
so you went to configuration->hosts for sure, not configuration->templates by accident ?

[richlv]

also, i don't see how could the import succeed for you. are you _sure_ you are importing just the xml, uploaded as "bad" here ?
it references nonexistent host, and the import expectedly fails here

[aaarkhipov]

just to be sure, i grabbed 1.8.4 vm and tried to import that xml. it failed, as expected. trying to import it w/o graphs succeeded.

Now I'm a bit confused - you just said "... tried to import that xml. it failed, as expected."

I understood, it was a confirmation of reproduction. And, yes, I went to Hosts->Import.

BTW, Template->Import gives the same result.

If you still cannot reproduce, drop me an email and I give you access to the system.

Andrei.

[richlv]

Now I'm a bit confused - you just said "... tried to import that xml. it failed, as expected."

I understood, it was a confirmation of reproduction.

please note one of my previous posts - your "bad" template links (in graph items) to a host that would not exist on an appliance, probably some of your own hosts. as such, the xml import fails - as expected. removing those references from the xml allows it to import.