Ignore:
Timestamp:
08/26/13 09:45:18 (11 years ago)
Author:
jripsl
Message:

Improve logging.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Monitoring/CNClient/README

    r866 r940  
     1- requirements 
     2        - CentOS 6 
     3        - outgoing internet access (port 80) 
     4        - Forge svn repository access 
     5- add Unix user 
     6        - adduser -m -d /home/cscompute -s /sbin/nologin cscompute 
     7- check if EPEL repository is configured, if not, do steps below 
     8        - for CENTOS 6 
     9          (from http://www.tecmint.com/how-to-enable-epel-repository-for-rhel-centos-6-5/) 
     10                - wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm 
     11                - rpm -ivh epel-release-6-8.noarch.rpm 
     12        - note 
     13                - 
     14                        - if you get error below 
     15                                Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=x86_64 error was 
     16                                No repomd file 
     17                        - then, manually copy files below from another machine 
     18                                - repomd.xml 
     19                                - metalink.xml 
     20- tools 
     21        - yum install gcc screen 
    122- this program uses rabbitmq-c library (v0.3.0) 
    223        - https://github.com/alanxz/rabbitmq-c 
     
    425        - using system package 
    526                - install using commands below 
    6                         - aptitude install librabbitmq0 
    7                         - aptitude install librabbitmq-dev 
     27                        - yum install librabbitmq0 
     28                        - yum install librabbitmq-dev 
    829                - note that it is likely that system packages versions are out of date (we need v0.3.0) 
    9                   so better use installation from source 
     30                  in this case, use installation from source 
    1031        - from source 
    1132                - retrieve source 
     
    3556                          (because of the above error (AAA), you need to run make twice) 
    3657                        - make install 
    37 - compilation (static) 
    38         - gcc -static -I/usr/local/include -L/usr/local/lib -Wall -o sendAMQPMsg send_AMQP_msg.c -lrabbitmq 
    39                 - we get warning below during compilation 
    40                         -  
    41                           <--- 
    42                           /usr/local/lib/librabbitmq.a(librabbitmq_librabbitmq_la-amqp_socket.o): In function `amqp_open_socket': 
    43                           rabbitmq-c-rabbitmq-c-v0.3.0/librabbitmq/amqp_socket.c:66: warning: Using 'getaddrinfo' in statically  
    44                           linked applications requires at runtime the shared libraries from the glibc version used for linking 
    45                           ---> 
    46                         - it means that you may need to be sure all computing node have the same glibc version !!!! 
    47                                 - also means that a different binary must be use in each computing center 
     58- sendAMQPMsg installation 
     59        - svn co svn+ssh://<login here>@forge.ipsl.jussieu.fr/ipsl/forge/projets/libigcm/svn/trunk/Monitoring/CNClient 
     60        - compilation (static) 
     61                - gcc -static -I/usr/local/include -L/usr/local/lib -Wall -o sendAMQPMsg send_AMQP_msg.c -lrabbitmq 
     62                        - we get warning below during compilation 
     63                                -  
     64                                  <--- 
     65                                  /usr/local/lib/librabbitmq.a(librabbitmq_librabbitmq_la-amqp_socket.o): In function `amqp_open_socket': 
     66                                  rabbitmq-c-rabbitmq-c-v0.3.0/librabbitmq/amqp_socket.c:66: warning: Using 'getaddrinfo' in statically  
     67                                  linked applications requires at runtime the shared libraries from the glibc version used for linking 
     68                                  ---> 
     69                                - it means that you may need to be sure all computing node have the same glibc version !!!! 
     70                                        - also means that a different binary must be use in each computing center 
    4871- usage 
    4972        - to send a message in the queue, do 
Note: See TracChangeset for help on using the changeset viewer.