The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

BytesLog command and problems I got with it

Discussion in 'General Discussion' started by Master Merlin, Apr 25, 2010.

  1. Master Merlin

    Master Merlin Registered

    Joined:
    Mar 3, 2008
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    I installed Wordpress Multi User on my Centos 5, cPanel/WHM, Apache 2.0, PHP 5.3 virtual private server and following the instructions I found out I need to add this to my httpd.conf

    Code:
    <VirtualHost 119.23.117.10>
    DocumentRoot /home/oblak/public_html/projekti
    BytesLog domlogs/projekrobl.org-bytes_log
    ServerAlias *.projekrobl.org
    ServerName www.projekrobl.org
    CustomLog domlogs/projekrobl.org combined
    RedirectMatch 301 (.*) http://projekrobl.org$1
    </VirtualHost>
    I added it and tried restarting apache, I received this error

    Code:
    Syntax error on line 577 of /usr/local/apache/conf/httpd.conf:
    Invalid command 'BytesLog', perhaps mis-spelled or defined by a module not included in the server configuration
    I searched around and found out that I should run this command

    Code:
    root@nevensky [/usr/local/cpanel/apache]# /usr/local/apache/bin/apxs -iac mod_log_bytes.c
    I did it. But it didn't really help because when I ran the command I got dozens of errors

    Code:
    root@nevensky [/usr/local/cpanel/apache]# /usr/local/apache/bin/apxs -iac mod_log_bytes.c
    /usr/local/apache/build/libtool --silent --mode=compile gcc -prefer-pic --param ggc-min-expand=1 --param ggc-min-heapsize=4096 -DAP_HAVE_DESIGNATED_INITIALIZER -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE --param ggc-min-expand=1 --param ggc-min-heapsize=4096 -pthread -I/usr/local/apache/include  -I/usr/local/apache/include   -I/usr/local/apache/include   -c -o mod_log_bytes.lo mod_log_bytes.c && touch mod_log_bytes.slo
    mod_log_bytes.c:66:25: error: multithread.h: No such file or directory
    mod_log_bytes.c:67:22: error: ap_alloc.h: No such file or directory
    mod_log_bytes.c:71: error: 'O_WRONLY' undeclared here (not in a function)
    mod_log_bytes.c:71: error: 'O_APPEND' undeclared here (not in a function)
    mod_log_bytes.c:71: error: 'O_CREAT' undeclared here (not in a function)
    mod_log_bytes.c:76: error: 'S_IRUSR' undeclared here (not in a function)
    mod_log_bytes.c:76: error: 'S_IWUSR' undeclared here (not in a function)
    mod_log_bytes.c:76: error: 'S_IRGRP' undeclared here (not in a function)
    mod_log_bytes.c:76: error: 'S_IROTH' undeclared here (not in a function)
    mod_log_bytes.c:103: error: expected specifier-qualifier-list before 'array_header'
    mod_log_bytes.c: In function 'API_EXPORT':
    mod_log_bytes.c:111: error: expected declaration specifiers before 'ap_table_count'
    mod_log_bytes.c:117: error: expected declaration specifiers before 'API_EXPORT'
    mod_log_bytes.c:134: error: expected ')' before '*' token
    mod_log_bytes.c:147: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
    mod_log_bytes.c:155: error: storage class specified for parameter 'bytes_log_cmds'
    mod_log_bytes.c:155: error: parameter 'bytes_log_cmds' is initialized
    mod_log_bytes.c:156: warning: braces around scalar initializer
    mod_log_bytes.c:156: warning: (near initialization for 'bytes_log_cmds')
    mod_log_bytes.c:156: warning: initialization from incompatible pointer type
    mod_log_bytes.c:156: error: 'set_bytes_log' undeclared (first use in this function)
    mod_log_bytes.c:156: error: (Each undeclared identifier is reported only once
    mod_log_bytes.c:156: error: for each function it appears in.)
    mod_log_bytes.c:156: warning: excess elements in scalar initializer
    mod_log_bytes.c:156: warning: (near initialization for 'bytes_log_cmds')
    mod_log_bytes.c:156: warning: excess elements in scalar initializer
    mod_log_bytes.c:156: warning: (near initialization for 'bytes_log_cmds')
    mod_log_bytes.c:156: warning: excess elements in scalar initializer
    mod_log_bytes.c:156: warning: (near initialization for 'bytes_log_cmds')
    mod_log_bytes.c:156: warning: excess elements in scalar initializer
    mod_log_bytes.c:156: warning: (near initialization for 'bytes_log_cmds')
    mod_log_bytes.c:157: warning: excess elements in scalar initializer
    mod_log_bytes.c:157: warning: (near initialization for 'bytes_log_cmds')
    mod_log_bytes.c:158: warning: braces around scalar initializer
    mod_log_bytes.c:158: warning: (near initialization for 'bytes_log_cmds')
    mod_log_bytes.c:158: warning: excess elements in scalar initializer
    mod_log_bytes.c:158: warning: (near initialization for 'bytes_log_cmds')
    mod_log_bytes.c:162: error: expected declaration specifiers or '...' before 'pool'
    mod_log_bytes.c:163: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
    mod_log_bytes.c:197: error: expected declaration specifiers or '...' before 'pool'
    mod_log_bytes.c:198: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
    mod_log_bytes.c:207: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
    mod_log_bytes.c:220: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token
    mod_log_bytes.c:253: error: parameter 'bytes_log_module' is initialized
    mod_log_bytes.c:254: error: 'this_module_needs_to_be_ported_to_apache_2_0' undeclared (first use in this function)
    mod_log_bytes.c:255: error: 'init_bytes_log' undeclared (first use in this function)
    mod_log_bytes.c:256: warning: initialization makes integer from pointer without a cast
    mod_log_bytes.c:258: error: 'make_bytes_log_state' undeclared (first use in this function)
    mod_log_bytes.c:260: warning: initialization makes integer from pointer without a cast
    mod_log_bytes.c:268: error: 'bytes_log_transaction' undeclared (first use in this function)
    mod_log_bytes.c:268: warning: excess elements in struct initializer
    mod_log_bytes.c:268: warning: (near initialization for 'bytes_log_module')
    mod_log_bytes.c:269: warning: excess elements in struct initializer
    mod_log_bytes.c:269: warning: (near initialization for 'bytes_log_module')
    mod_log_bytes.c:270: warning: excess elements in struct initializer
    mod_log_bytes.c:270: warning: (near initialization for 'bytes_log_module')
    mod_log_bytes.c:271: warning: excess elements in struct initializer
    mod_log_bytes.c:271: warning: (near initialization for 'bytes_log_module')
    mod_log_bytes.c:273: warning: excess elements in struct initializer
    mod_log_bytes.c:273: warning: (near initialization for 'bytes_log_module')
    mod_log_bytes.c:273: error: old-style parameter declarations in prototyped function definition
    mod_log_bytes.c:110: error: parameter name omitted
    mod_log_bytes.c:273: error: expected '{' at end of input
    apxs:Error: Command failed with rc=65536
    .
    Help would be much appreciated.

    Best Regards,
    George Wembston
     
  2. Master Merlin

    Master Merlin Registered

    Joined:
    Mar 3, 2008
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    1
    Is there really nobody who knows how to fix this issue?
     
Loading...

Share This Page