Yea thats right. i-doit doesn't know when it has to delete a software because the software is not shown in ocs anymore. It would only be possible to completely remove all software assignments before importing from ocs. But that would result in overwriting or removing manual changes in i-doit..

You have to login with the other mandator in order to sync other mandators. The login parameters are -u -p and -i, where -i is the id of your mandator. -u and -p are username and password

yes, you helpt me alot. otherwise i was still searching thnx!

As far as I can see the problem without really knowing the config, I would say that you are missing some aparametes in the objects Nagios category. You have to turn on atleast some important attributes like "display_name", "check_command", "active_checks_enabled". This is not a complete list of fields, im just trying to recognize it from my memory without testing it. So maybe you should start with playing around with these fields.

This is by design (but not intentionally), because it would be no problem to make the archiving possible from the detail view, but the problem is the question where to jump to after the object has been archived. When developing the function we discovered that it is not that easy to jump to the loction where you have been before and neither is it not easy to jump to the list view of the object type. At that point of time we decided to just skip this functionality, but it is on the list of annoying things we want to resolve for the 1.0 version Greets, Daniel

SOLVED: problem is in our database - foreign keys are missing. They were not created for some strange reason Update runs smoothly after creating foreign keys

Hi, thank you very much, that helped! Olaf

Hi, In i-doit there is already a logbook where you can find all changes of a special object or of the whole cmdb. Regards Christian

Unfortunately this is currently not possible We will create a special object type and categories for blade centers in the future. But i cannot give you an exact date, yet

In older versions there was also a problem with our curl initialisation, this should be fixed in the most recent version now

Every object needs a primary contact. And every assigned contact needs the nagios categories filled out to get exported properly. I think thats your problem

What HTTP Port are you using? There was a problem in version 0.9.9-3 with the Internet Explorer. Does that behaviour also occurs with another browser than IE ?

You are only able to import a special import format into i-doit. There isn't a generic mapping for this. I think your passwords.txt does not match that format. You can check out the correct format by Exporting an object under modules -> export.

ah yes. Thanks! That seems to be the problem. My MySQL DB was set to strict mode….

Thank You tolik25251! It seems that this patch works. Persons at least now showing correctly. I'll watch what will happen in other sections. Once again, thank you very much, tolik25251 You're the best!

See http://www.i-doit.org/forum/index.php/topic,1677.0.html

Hello, Can you tell me how can I do to automatically feed the servers logbooks with Nagios events?  Is it working if Nagios is installed on another server? Here's an history of what I did: -> I entered the parameters in the NDO MySql Server section in Nagios module (on i-doit server).  The communication between i-doit and Nagios is working fine. -> I scheduled a task with cron to launch the command "php /path/controller.php -v -m nagios >> /var/log/idoit".     Here's an extract of what I can find in this log file (same every 10min): * Loading module: nagios    * Logging in..    * Connected to mandator: 1 (xxxx)    * Logged in as: nagsync    * Setting up system environment    * Nagios-Handler initialized (2010-10-12 18:30:02).    * Processing xxxxx..    * Processing xxxxx..    * Logging out -> Through i-doit web interface, I can see that my servers are UP or DOWN, so the communication with Nagios is working well but I cannot get the other monitoring information like CPU use or Memory use… Do you have any idea on what can I do ? Thank you in advance for your answer !

Should be fixed in 0.9.9-3