R: importing files inside NagiosQL

[Giorgio Zarrelli]

Hi,

drop the database, then recreate it using the file

nagiosQL_v31_db_mysql.sql

you find in the install/sql directory.


Giorgio


<quota chi="Marco Borsani">
> Well
>
> How can I purge the DB ? I performed a "Delete config files" .. is it
> enough
> ? I'm afraid not ...
>
>
> -----Messaggio originale-----
> Da: Giorgio Zarrelli [mailto:zarrelli at linux.it]
> Inviato: lunedì 21 novembre 2011 14:17
> A: Nagios Users List
> Oggetto: Re: [Nagios-users] importing files inside NagiosQL
>
> Hi,
>
> maybe some remnants from previous import tries? Purge MySQL db and try a
> new
> import, following the suggested (on import page) order of file processing.
>
> Giorgio
>
>
> <quota chi="Marco Borsani">
>> Hi all
>>
>>
>>
>> I am testing NagiosQL and try to import old configuration files inside
>> its DB.
>>
>>
>>
>> No warnings/errors without NagiosQL, but when I import the data inside
>> the DB I see strange situations:
>>
>> 1)      ALL hosts/services keep only the first contact-groups associated
>> (usually are three or six)
>>
>> 2)      Appear some inactive contacts (seven contacts) similar at
>> existing
>> other , that are not anywhere in the original files.
>>
>> 3)      Appear some inactive contact-groups (five contact-group) similar
>> at
>> existing other , that are not anywhere in the original files.
>>
>> 4)      Appear some inactive hosts (ten hosts) similar at existing other
>> ,
>> that are not anywhere in the original files.
>>
>> 5)      Appear some inactive contacts (twenty services) similar at
>> existing
>> other , that are not anywhere in the original files.
>>
>>
>>
>> Any idea ?
>>
>> Regards
>>
>>
>>
>> Marco Borsani
>>
>> Unix and Monitoring Sysadmin
>>
>> Technical Operations Dpt.
>>
>> tel: +39 010 4310115
>>
>> fax: +39 02 30130311
>>
>> cell: +39 329 5953944
>>
>> ITnet Srl
>>
>> Società con socio unico
>>
>> Direzione e Coordinamento di 

>>
>>
>>
>> ----------------------------------------------------------------------
>> -------- All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d_____________________________________
>> __________
>> Nagios-users mailing list
>> Nagios-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>> ::: Please include Nagios version, plugin version (-v) and OS when
>> reporting any issue.
>> ::: Messages without supporting info will risk being sent to /dev/null
>
>
>
> ----------------------------------------------------------------------------
> --
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security threats,
> fraudulent activity, and more. Splunk takes this data and makes sense of
> it.
> IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting
> any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
>



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null