Pb de synchro entre GLPI et OCS

fyk · 2010-07-22 11:19:52

Bonjour,

voila j'ai un soucis pour synchroniser OCS et GLPI avec le mode OCS NG.
Les deux applicatifs sont installés sur le même serveur qui est une distribution UBUNTU. Les deux applicatifs marchent a super bien mais j'aimerai pouvoir importer la base OCS dans GLPI.

Au moment de la synchro entre les deux, je rentre les infos suivante :

Configuration du module d'import OCS NG -> GLPI

Nom : localhost
Hote OCSweb localhost
Nom de la base de données OCS : ocsweb
Utilisateur de la base de données OCSweb : ocs
Mot de passe de l'utilisateur OCSweb : xxxxxx

Résultat :
Échec de connexion à la base de données OCS NG

Je comprends pas, j'ai donc testé le tout en ligne de commande :
mysql -u ocs -p
use ocsweb
show tables;

Tout est OK, je me connecte bien, la base ocsweb existe bien etc....
Donc j'arrive pas a comprendre d ou ca peut venir.

Si jamais vous avez la solution need de l'aide....

Merci d'avance

yllen · 2010-07-22 12:15:59

Si les 2 sont sur le même serveur, tu dois avoir un port particulier pour chaque base.
Il suffit de rajouter :N°Port à la fin du nom de ton hote (localhost:1111 par exemple)

fyk · 2010-07-22 13:44:32

Ok je vais tester ca tout de suite.

fyk · 2010-07-22 13:49:53

j'ai mis :

localhost:3306 mais ca ne marche toujours pas.

Voila la config de ma base SQL

root@liglpiocs:/etc/mysql# more my.cnf
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/serve … ables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
#
# * Basic Settings
#

#
# * IMPORTANT
# If you make changes to these settings and your system uses apparmor, you may
# also need to also adjust /etc/apparmor.d/usr.sbin.mysqld.
#

user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
bind-address = localhost
bind-address = liglpiocs
bind-address = 172.20.250.196
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 16M
thread_stack = 192K
thread_cache_size = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover = BACKUP
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem

[mysqldump]
quick
quote-names
max_allowed_packet = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
root@liglpiocs:/etc/mysql#

fyk · 2010-07-22 16:53:23

Voici mon erreur en mode debug :

PHP ERROR: mysql_connect() [function.mysql-connect]: Access denied for user 'ocs'@'localhost' (using password: YES) in /usr/share/glpi/inc/dbmysql.class.php at line 74

fyk · 2010-07-23 09:25:52

Personne aurait une idée?

ddurieux · 2010-07-23 09:38:13

Si votre login ou mot de passe pour accéder a la table ocsweb ne fonctionne pas, il faut donc mettre les bonnes informations, après on ne peut pas vous aider plus, c'est vous qui avez définis ce login et mot de passe sur votre base MySQL

Forum GLPI-Project

Announcement

#1 2010-07-22 11:19:52

Pb de synchro entre GLPI et OCS

#2 2010-07-22 12:15:59

Re: Pb de synchro entre GLPI et OCS

#3 2010-07-22 13:44:32

Re: Pb de synchro entre GLPI et OCS

#4 2010-07-22 13:49:53

Re: Pb de synchro entre GLPI et OCS

#5 2010-07-22 16:53:23

Re: Pb de synchro entre GLPI et OCS

#6 2010-07-23 09:25:52

Re: Pb de synchro entre GLPI et OCS

#7 2010-07-23 09:38:13

Re: Pb de synchro entre GLPI et OCS

Board footer